Clean up a handful of typos [i18nIgnore] (#14197)

Co-authored-by: Yan <61414485+yanthomasdev@users.noreply.github.com>

Author: ethanhawksley

src/content/docs/en/guides/actions.mdx

@@ -699,7 +699,7 @@ export const onRequest = defineMiddleware(async (context, next) => {
 
 ## Security when using actions
 
-Actions are accessible as public endpoints based on the name of the action. For example, the action `blog.like()` will be accessible from `/_actions/blog.like`. This is useful for unit testing action results and debugging production errors. However, this means you **must** use same authorization checks that you would consider for API endpoints and on-demand rendered pages.
+Actions are accessible as public endpoints based on the name of the action. For example, the action `blog.like()` will be accessible from `/_actions/blog.like`. This is useful for unit testing action results and debugging production errors. However, this means you **must** use the same authorization checks that you would consider for API endpoints and on-demand rendered pages.
 
 ### Authorize users from an action handler
 

src/content/docs/en/guides/authentication.mdx

@@ -23,7 +23,7 @@ There is no official authentication solution for Astro, but you can find [commun
 
 Better Auth is a framework-agnostic authentication (and authorization) framework for TypeScript. It provides a comprehensive set of features out of the box and includes a plugin ecosystem that simplifies adding advanced functionalities.
 
-It supports Astro out of the box, and you can use it to add authentication to your astro project.
+It supports Astro out of the box, and you can use it to add authentication to your Astro project.
 
 ### Installation
 

src/content/docs/en/guides/backend/firebase.mdx

@@ -435,7 +435,7 @@ if (Astro.cookies.has("__session")) {
 
 `src/pages/dashboard.astro` will verify the user's session cookie using the Firebase server app. If the user is not authenticated, the page will redirect the user to the `/signin` page.
 
-The example page below display the user's name and a button to sign out. Clicking the button will send a `GET` request to the `/api/auth/signout` endpoint.
+The example page below displays the user's name and a button to sign out. Clicking the button will send a `GET` request to the `/api/auth/signout` endpoint.
 
 The endpoint will delete the user's session cookie and redirect the user to the `/signin` page.
 

src/content/docs/en/guides/backend/supabase.mdx

@@ -142,7 +142,7 @@ Create these endpoints in the `src/pages/api/auth` directory of your project. If
 - package.json
 </FileTree>
 
-`register.ts` creates a new user in Supabase. It accepts a `POST` request with the an email and password. It then uses the Supabase SDK to create a new user.
+`register.ts` creates a new user in Supabase. It accepts a `POST` request with an email and password. It then uses the Supabase SDK to create a new user.
 
 ```ts title="src/pages/api/auth/register.ts"
 // With `output: 'static'` configured:
@@ -172,7 +172,7 @@ export const POST: APIRoute = async ({ request, redirect }) => {
 };
 ```
 
-`signin.ts` signs in a user. It accepts a `POST` request with the an email and password. It then uses the Supabase SDK to sign in the user.
+`signin.ts` signs in a user. It accepts a `POST` request with an email and password. It then uses the Supabase SDK to sign in the user.
 
 ```ts title="src/pages/api/auth/signin.ts"
 // With `output: 'static'` configured:

src/content/docs/en/guides/cms/drupal.mdx

@@ -116,7 +116,7 @@ To retrieve an individual entity, the URL structure will be `/jsonapi/{entity_ty
 
 #### Retrieving only certain fields
 
-Retrieve only certain field by adding the Query String field to the request.
+Retrieve only certain fields by adding the Query String field to the request.
 
 GET: `/jsonapi/{entity_type_id}/{bundle_id}?field[entity_type]=field_list`
 

src/content/docs/en/guides/cms/frontmatter-cms.mdx

@@ -139,7 +139,7 @@ Open the **Front Matter CMS Dashboard**; you can do this as follows:
 
 ### Using Markdoc with Front Matter CMS
 
-To use Markdoc with Front Matter CMS, you must configure this in the `frontMatter.content.supportedFileTypes`. This setting lets the CMS know which types of files it can progress.
+To use Markdoc with Front Matter CMS, you must configure this in the `frontMatter.content.supportedFileTypes`. This setting lets the CMS know which types of files it can process.
 
 You can configure the setting as follows:
 

src/content/docs/en/guides/middleware.mdx

@@ -250,7 +250,7 @@ export function onRequest (context, next) {
 };
 ```
 
-The `next()` function accepts the same payload of [the `Astro.rewrite()` function](/en/reference/api-reference/#rewrite). The location of the rewrite path can be provided as a string, URL, or `Request`.
+The `next()` function accepts the same payload as [the `Astro.rewrite()` function](/en/reference/api-reference/#rewrite). The location of the rewrite path can be provided as a string, URL, or `Request`.
 
 When you have multiple middleware functions chained via [sequence()](#chaining-middleware), submitting a path to `next()` will rewrite the `Request` in place and the middleware will not execute again. The next middleware function in the chain will receive the new `Request` with its updated `context`.
 

src/content/docs/en/guides/routing.mdx

@@ -528,7 +528,7 @@ const { page } = Astro.props;
 
 A more advanced use-case for pagination is **nested pagination.** This is when pagination is combined with other dynamic route params. You can use nested pagination to group your paginated collection by some property or tag.
 
-For example, if you want to group your paginated Markdown posts by some tag, you would use nested pagination by creating a `/src/pages/[tag]/[page].astro` page that would match the following URLS:
+For example, if you want to group your paginated Markdown posts by some tag, you would use nested pagination by creating a `/src/pages/[tag]/[page].astro` page that would match the following URLs:
 
 - `/red/1` (tag=red)
 - `/red/2` (tag=red)

src/content/docs/en/guides/server-islands.mdx

@@ -90,7 +90,7 @@ However, [the browser limits URLs to a maximum length of 2048 bytes](https://chr
 
 ## Accessing the page URL in a server island
 
-In most cases you, your server island component can get information about the page rendering it by [passing props](/en/basics/astro-components/#component-props) like in normal components.
+In most cases, your server island component can get information about the page rendering it by [passing props](/en/basics/astro-components/#component-props) like in normal components.
 
 However, server islands run in their own isolated context outside of the page request. `Astro.url` and `Astro.request.url` in a server island component both return a URL that looks like `/_server-islands/Avatar` instead of the current page's URL in the browser. Additionally, if you are prerendering the page you will not have access to information such as query parameters in order to pass as props.
 

src/content/docs/en/guides/troubleshooting.mdx

@@ -24,7 +24,7 @@ console.log('Hi! I’m the client. This is logged in browser dev console.');
 
 A `console.log()` statement in Astro frontmatter will always output to the **terminal** running the Astro CLI. This is because Astro runs on the server, and never in the browser.
 
-Code that is written or imported inside of an Astro `<script>` tag is run in the browser. Any `console.log()` statements or other debug output will be  printed to the **console in your browser**.
+Code that is written or imported inside of an Astro `<script>` tag is run in the browser. Any `console.log()` statements or other debug output will be printed to the **console in your browser**.
 
 ### Debugging framework components