From 26971f1e37b51505ce99c879b8845dc58bd1660e Mon Sep 17 00:00:00 2001 From: Romashka Date: Wed, 11 Dec 2024 00:44:29 +0200 Subject: [PATCH] Typos-fix (#337) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Description: Fixed errors and inaccuracies in the project's textual materials. Type of Change: Fixing errors (typos, grammatical mistakes, etc.) Testing: Changes have been reviewed to ensure no new errors were introduced. Impact: Improved readability of texts and documentation. Additional Notes: Regular text audits are recommended to maintain a high standard of quality. --- ## PR-Codex overview This PR focuses on correcting typographical errors and improving clarity in documentation files related to the `Farcaster` framework and its APIs. ### Detailed summary - Corrected "Specifcation" to "Specification" in `docs/developers/frames/v2/getting-started.md` and `docs/developers/frames/getting-started.md`. - Fixed "programatic" to "programmatically" in `docs/learn/what-is-farcaster/usernames.md`. - Changed "unathenticated" to "unauthenticated" in `docs/developers/frames/spec.md`. - Corrected "depedencies" to "dependencies" in `docs/developers/frames/getting-started.md`. - Fixed "programing" to "programming" in `docs/reference/hubble/httpapi/httpapi.md`. - Changed "vesion" to "version" in `docs/reference/hubble/httpapi/httpapi.md`. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` --- docs/reference/hubble/httpapi/httpapi.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/hubble/httpapi/httpapi.md b/docs/reference/hubble/httpapi/httpapi.md index ae88beee..1ca79a3f 100644 --- a/docs/reference/hubble/httpapi/httpapi.md +++ b/docs/reference/hubble/httpapi/httpapi.md @@ -4,7 +4,7 @@ Hubble serves a HTTP API on port 2281 by default. ## Using the API -The API can be called from any programing language or browser by making a normal HTTP request. +The API can be called from any programming language or browser by making a normal HTTP request. **View the API responses in a browser** @@ -127,4 +127,4 @@ You can set a custom CORS header in the HTTP server by using the `--http-cors-or ## Limitations -The HTTP API currently does not support any of the Sync APIs that are available in the gRPC vesion. When Hubs sync with each other, they will use the gRPC APIs instead of the HTTP APIs. +The HTTP API currently does not support any of the Sync APIs that are available in the gRPC version. When Hubs sync with each other, they will use the gRPC APIs instead of the HTTP APIs.