chore(docs): Fix typo in adding common features (#37611)

docs/docs/how-to/adding-common-features/adding-forms.md

@@ -67,7 +67,7 @@ You do this by passing a function that prevents page refresh as an `onSubmit` pr
 
 The `handleSubmit` function calls `preventDefault()` on the event which prevents the page from refreshing. After this, you'll want to insert desired behavior, like sending the data to a third-party service.
 
-You may want to make additional changes to visual form display after submit, like disabling the form submit button after submission, showing a spinning wheel, or changing the button color.
+You may want to make additional changes in the visual form display after submit, like disabling the form submit button after submission, showing a spinning wheel, or changing the button color.
 
 If you need to use any sort of authentication token to submit data, you can use Gatsby Functions (Gatsby's implementation of serverless functions) to [run this logic while keeping any of your credentials secure](https://www.gatsbyjs.com/docs/reference/functions/getting-started/#forms).
 

docs/docs/how-to/adding-common-features/localization-i18n.md

@@ -9,9 +9,9 @@ Serving users content in a way that is adapted to their language & culture is pa
 
 There are two hard parts of internationalization:
 
-- **Content storage and workflow.** Coordinating with internal or external translators to translate both existing and new content into required languages can be time-consuming. In addition, adding another approver into the content publishing process can slow things down without careful workflow design.
+- **Content storage and workflow.** Coordinating with internal or external translators to translate both existing and new content into the required languages can be time-consuming. In addition, adding another approver into the content publishing process can slow things down without careful workflow design.
 
-- **Display, templating, and routing.** At minimum, internationalization means users must be redirected, either to a subdomain (eg `fr.example.com/blog`) or path prefix (eg `example.com/fr/blog`). In addition, internationalization efforts also come with logic around sections or pages that should be present in some languages but not others.
+- **Display, templating, and routing.** At minimum, internationalization means users must be redirected, either to a subdomain (eg `fr.example.com/blog`) or a path prefix (eg `example.com/fr/blog`). In addition, internationalization efforts also come with logic around sections or pages that should be present in some languages but not others.
 
 This guide is a brief look at the options that exist for enhancing your Gatsby project for internationalization.
 
@@ -43,9 +43,9 @@ More detailed information about react-intl's [APIs](https://github.com/formatjs/
 
 React-i18next is an internationalization library built on the i18next framework. It uses components to make sure translations render correctly or to re-render your content when the user language changes.
 
-React-i18next is more extensible than other options with a variety of plugins, utilities, and configurations. Common plugins allow for detecting a user's language or adding an additional layer of local caching. Other options include caching, a backend plugin to load translations from your server, or bundling translations with webpack.
+React-i18next is more extensible than other options with a variety of plugins, utilities, and configurations. Common plugins allow for detecting a user's language or adding an additional layer of local caching. Other options include caching, a backend plugin to load the translations from your server, or bundling translations with webpack.
 
-This framework also has experimental support for the React suspense API and it supports a stable version of React hooks.
+This framework also has experimental support for the React suspense API, and it supports a stable version of React hooks.
 
 ## Other resources
 

docs/docs/how-to/adding-common-features/processing-payments-with-stripe.md

@@ -21,7 +21,7 @@ To get started, create a [Stripe account](https://dashboard.stripe.com/register)
 
 Once logged into the Stripe dashboard, you can find your API keys under the Developers menu. Before you activate your account, you'll only have access to your test API keys. You'll need to use your publishable and secret keys as described in the documentation for any plugins, starters, or other integrations you use. Test keys allow you to test your Stripe integration without making real payments. To access your live API keys, activate your account. The e-commerce tutorial describes how to [add your Stripe keys when using the gatsby-source-stripe plugin](/tutorial/ecommerce-tutorial/#add-the-stripe-source-plugin).
 
-While testing, you must use the key(s) that include the word test. For production code, you will need to use the live keys. As the names imply, your publishable key may be included in code that you share publicly (for example, on the frontend, and in GitHub), whereas your secret key should not be shared with anyone or committed to any public repo. It’s important to restrict access to this secret key because anyone who has it could potentially read or send requests from your Stripe account and see information about charges or purchases or even refund customers.
+While testing, you must use the key(s) that include the word test. For production code, you will need to use the live keys. As the names imply, your publishable key may be included in the code that you share publicly (for example, on the frontend, and in GitHub), whereas your secret key should not be shared with anyone or committed to any public repo. It’s important to restrict access to this secret key because anyone who has it could potentially read or send requests from your Stripe account and see information about charges or purchases or even refund customers.
 
 ## Resources for using Stripe