chore(docs): Fix typos (#35119)

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

@@ -5,7 +5,7 @@ examples:
     href: "https://github.com/gatsbyjs/gatsby-functions-beta/tree/main/examples/basic-form"
 ---
 
-Forms are common to capture user information from site visitors. They range in complexity from simple newsletter email capture boxes, to detailed lead capture forms and signup pages requiring visitors to enter their first & last name, email, and several additional self-identificaton questions.
+Forms are common to capture user information from site visitors. They range in complexity from simple newsletter email capture boxes, to detailed lead capture forms and signup pages requiring visitors to enter their first & last name, email, and several additional self-identification questions.
 
 The humble `<form>` element has evolved a lot since it was created in 1995. By default, a `<form>` stores its input internally and refresh the page when you `submit`. Today, developers generally want to store input in Javascript so you can validate fields and send the data to a third-party system.
 

docs/docs/how-to/performance/improving-build-performance.md

@@ -66,7 +66,7 @@ If build speeds are sufficiently painful, your CMS is the primary contributor, a
 
 #### Conditionally applying plugin options using environment variables
 
-Your source plugin may have options that control which or how many entries, files, etc. are sourced. In order to speed up sourcing for e.g. `gatsby develop` or your staging environment, you can use environment variables to apply different plugin options depending on the current environment. To see an example of this pattern using `gatsby-source-filesytem` you can visit the [sourcing from the filesystem](/docs/how-to/sourcing-data/sourcing-from-the-filesystem/) documentation.
+Your source plugin may have options that control which or how many entries, files, etc. are sourced. In order to speed up sourcing for e.g. `gatsby develop` or your staging environment, you can use environment variables to apply different plugin options depending on the current environment. To see an example of this pattern using `gatsby-source-filesystem` you can visit the [sourcing from the filesystem](/docs/how-to/sourcing-data/sourcing-from-the-filesystem/) documentation.
 
 #### If your site is multi-language, consider breaking it into several sites
 

docs/docs/performance-tracing.md

@@ -45,7 +45,7 @@ There are many OpenTracing compatible backends available. Below are examples of
 built-in support for OpenTelemetry. The following is an example of configuring Gatsby to send build traces
 to [Honeycomb](https://www.honeycomb.io/).
 
-1. Install necesary dependencies
+1. Install necessary dependencies
 
 ```shell
 npm install @grpc/grpc-js @opentelemetry/api @opentelemetry/auto-instrumentations-node @opentelemetry/exporter-collector-grpc @opentelemetry/sdk-node @opentelemetry/shim-opentracing opentracing

docs/docs/reference/release-notes/v2.31/index.md

@@ -112,7 +112,7 @@ A big **Thank You** to [our community who contributed](https://github.com/gatsby
   - chore(docs): plugin contentful - fix brand name, code blocks for names [PR #28915](https://github.com/gatsbyjs/gatsby/pull/28915)
   - readme(gatsby-plugin-emotion): fix table [PR #28906](https://github.com/gatsbyjs/gatsby/pull/28906)
   - chore(docs): google plugin analytics - upgrade to gtag, fix code [PR #28918](https://github.com/gatsbyjs/gatsby/pull/28918)
-  - chore(docs): realease notes - code fences, code language [PR #28936](https://github.com/gatsbyjs/gatsby/pull/28936)
+  - chore(docs): release notes - code fences, code language [PR #28936](https://github.com/gatsbyjs/gatsby/pull/28936)
   - chore(docs): typography - brand name [PR #28931](https://github.com/gatsbyjs/gatsby/pull/28931)
   - chore(docs): routing - brand name, code language, code block [PR #28929](https://github.com/gatsbyjs/gatsby/pull/28929)
 

docs/docs/reference/release-notes/v3.1/index.md

@@ -96,7 +96,7 @@ You can find more information on how to switch to [`gatsby-plugin-image`](https:
   - chore: make ./starters/upgrade-starters.sh executable [PR #30102](https://github.com/gatsbyjs/gatsby/pull/30102)
 
 - [imshubhamsingh](https://github.com/imshubhamsingh): chore(docs): updated doc for payment using square [PR #27272](https://github.com/gatsbyjs/gatsby/pull/27272)
-- [ahmetcanaydemir](https://github.com/ahmetcanaydemir): fix(gatsby-react-router-scroll): debounce function for scollListener [PR #26933](https://github.com/gatsbyjs/gatsby/pull/26933)
+- [ahmetcanaydemir](https://github.com/ahmetcanaydemir): fix(gatsby-react-router-scroll): debounce function for scrollListener [PR #26933](https://github.com/gatsbyjs/gatsby/pull/26933)
 - [talohana](https://github.com/talohana): chore(docs): add paths to unit-testing using typescript [PR #28029](https://github.com/gatsbyjs/gatsby/pull/28029)
 - [hashimwarren](https://github.com/hashimwarren): chore(docs): Update headless WordPress article [PR #29402](https://github.com/gatsbyjs/gatsby/pull/29402)
 - [lorensr](https://github.com/lorensr): chore(docs): Add twitter links to tutorial [PR #29696](https://github.com/gatsbyjs/gatsby/pull/29696)

docs/docs/reference/release-notes/v3.12/index.md

@@ -31,7 +31,7 @@ With this release we opt-in 20% of users for a final test before the full releas
 
 ## Improvements to `gatsby-source-shopify`
 
-Our `gatsby-source-shopify` plugin received mulitple bug fixes and improvements in this release. If you use Sales Channels you might have gotten wrong results in the past. The filter for it was fixed in [PR #32674](https://github.com/gatsbyjs/gatsby/pull/32674). With [PR #32710](https://github.com/gatsbyjs/gatsby/pull/32710) the plugin will also only query location fields when you activate locations since it requires additional permissions. If you're using [Gatsby Cloud](https://www.gatsbyjs.com/products/cloud/) production builds will now be prioritized over content previews and branch previews (via [PR #32144](https://github.com/gatsbyjs/gatsby/pull/32144)).
+Our `gatsby-source-shopify` plugin received multiple bug fixes and improvements in this release. If you use Sales Channels you might have gotten wrong results in the past. The filter for it was fixed in [PR #32674](https://github.com/gatsbyjs/gatsby/pull/32674). With [PR #32710](https://github.com/gatsbyjs/gatsby/pull/32710) the plugin will also only query location fields when you activate locations since it requires additional permissions. If you're using [Gatsby Cloud](https://www.gatsbyjs.com/products/cloud/) production builds will now be prioritized over content previews and branch previews (via [PR #32144](https://github.com/gatsbyjs/gatsby/pull/32144)).
 
 Shopify recently deprecated the `valueType` field on metafields. We've updated the API version to `2021-07`, added the new `type` field and aliased the old `valueType` to this new field. So the breaking change is backwards compatible, see [PR #32774](https://github.com/gatsbyjs/gatsby/pull/32774) for all details.
 

docs/docs/reference/release-notes/v3.5/index.md

@@ -72,7 +72,7 @@ A big **Thank You** to [our community who contributed](https://github.com/gatsby
 - [fshowalter](https://github.com/fshowalter): fix(gatsby-transformer-remark): Activate footnotes by default & remove included options with remark v13 [PR #31019](https://github.com/gatsbyjs/gatsby/pull/31019)
 - [axe312ger](https://github.com/axe312ger)
 
-  - test(e2e-contentful): add schema.sql for comparision with later updates [PR #31074](https://github.com/gatsbyjs/gatsby/pull/31074)
+  - test(e2e-contentful): add schema.sql for comparison with later updates [PR #31074](https://github.com/gatsbyjs/gatsby/pull/31074)
   - fix(gatsby): upgrade css-minimizer-webpack-plugin to v2 [PR #31176](https://github.com/gatsbyjs/gatsby/pull/31176)
 
 - [joshua-isaac](https://github.com/joshua-isaac): chore(docs): Update sourcing from agility cms [PR #30966](https://github.com/gatsbyjs/gatsby/pull/30966)

docs/docs/reference/release-notes/v4.0/index.md

@@ -139,7 +139,7 @@ A big **Thank You** to [our community who contributed](https://github.com/gatsby
   - chore(gatsby-source-contentful): clean up code base and introduce es-module syntax [PR #33213](https://github.com/gatsbyjs/gatsby/pull/33213)
 - [fbuireu](https://github.com/fbuireu): chore(gatsby-source-contentful): Fix RichText example [PR #33261](https://github.com/gatsbyjs/gatsby/pull/33261)
 - [alvis](https://github.com/alvis): fix(gatsby): correct the definition for getNode [PR #33259](https://github.com/gatsbyjs/gatsby/pull/33259)
-- [Xenonym](https://github.com/Xenonym): chore(docs): fix typo in site perfomance guide [PR #33294](https://github.com/gatsbyjs/gatsby/pull/33294)
+- [Xenonym](https://github.com/Xenonym): chore(docs): fix typo in site performance guide [PR #33294](https://github.com/gatsbyjs/gatsby/pull/33294)
 - [labifrancis](https://github.com/labifrancis): chore(docs): Improve Shopify guide [PR #33298](https://github.com/gatsbyjs/gatsby/pull/33298)
 - [aaronadamsCA](https://github.com/aaronadamsCA): chore(gatsby): Fix static query types, document useStaticQuery [PR #33322](https://github.com/gatsbyjs/gatsby/pull/33322)
 - [crstnre](https://github.com/crstnre): docs: fix "(r)esource congestion" [PR #33392](https://github.com/gatsbyjs/gatsby/pull/33392)

docs/docs/reference/release-notes/v4.2/index.md

@@ -57,7 +57,7 @@ You can find the support plans for the major versions of Gatsby on the newly cre
 - `gatsby`: Test files inside the `src/api` (Gatsby Functions) directory are now excluded by default, via [PR #33834](https://github.com/gatsbyjs/gatsby/pull/33834)
 - `gatsby-source-wordpress`:
   - Fix for `'createRoot' is not exported from 'react-dom' (imported as 'ReactDOM').` warning, via [PR #33991](https://github.com/gatsbyjs/gatsby/pull/33991)
-  - Hydrate images in develop on first occurence, via [PR #33989](https://github.com/gatsbyjs/gatsby/pull/33989)
+  - Hydrate images in develop on first occurrence, via [PR #33989](https://github.com/gatsbyjs/gatsby/pull/33989)
 - `gatsby-core-utils`: Add retry on HTTP status codes to `fetchRemoteFile`, via [PR #33461](https://github.com/gatsbyjs/gatsby/pull/33461)
 - Content Sync:
   - Content Sync is a Gatsby Cloud feature for improving the Preview experience for content authors. You can read more about it in the [conceptual guide](/docs/conceptual/content-sync/)

docs/docs/reference/release-notes/v4.6/index.md

@@ -25,7 +25,7 @@ if you have any [issues](https://github.com/gatsbyjs/gatsby/issues).
 
 ## Speeding Up Subsequent Queries
 
-Subseqent queries now get a ~10-15% performance boost! You'll see this improvement after your first `gatsby build` for all following runs (unless the cache is cleared). These percentage may defer depending on the complexity of nodes. We were able to achieve this by caching `rootNode` & `trackedRootNodes` across instances of `graphqlRunner` via [PR #33695](https://github.com/gatsbyjs/gatsby/pull/33695)
+Subsequent queries now get a ~10-15% performance boost! You'll see this improvement after your first `gatsby build` for all following runs (unless the cache is cleared). These percentage may defer depending on the complexity of nodes. We were able to achieve this by caching `rootNode` & `trackedRootNodes` across instances of `graphqlRunner` via [PR #33695](https://github.com/gatsbyjs/gatsby/pull/33695)
 
 ## Tracking Image Changes in Markdown Files