chore(*): fix lots of typos (#15301)

Author: minho42

.github/actions/high-priority-prs/src/__tests__/fixtures/data.json

@@ -7098,13 +7098,13 @@
               {
                 "commit": {
                   "authoredDate": "2019-05-19T22:50:18Z",
-                  "message": "fix focusing on navigation from 404 to different 404, improve focus managment tests"
+                  "message": "fix focusing on navigation from 404 to different 404, improve focus management tests"
                 }
               },
               {
                 "commit": {
                   "authoredDate": "2019-05-19T22:55:39Z",
-                  "message": "fix most of focus navigation focus managment in development\n\nnavigating from and to 404 doesn't focus router wrapper correctly. This is because 404 in development is special case (see notes before skipped e2e-tests/development-runtime accessibility tests). This can be fixed but require a lot of changes which would be out of scope of this PR and would potentially make it harder to merge page manifest changes, so for now lets ship fixes that are already here."
+                  "message": "fix most of focus navigation focus management in development\n\nnavigating from and to 404 doesn't focus router wrapper correctly. This is because 404 in development is special case (see notes before skipped e2e-tests/development-runtime accessibility tests). This can be fixed but require a lot of changes which would be out of scope of this PR and would potentially make it harder to merge page manifest changes, so for now lets ship fixes that are already here."
                 }
               },
               {

.github/actions/high-priority-prs/src/data.json

@@ -7098,13 +7098,13 @@
               {
                 "commit": {
                   "authoredDate": "2019-05-19T22:50:18Z",
-                  "message": "fix focusing on navigation from 404 to different 404, improve focus managment tests"
+                  "message": "fix focusing on navigation from 404 to different 404, improve focus management tests"
                 }
               },
               {
                 "commit": {
                   "authoredDate": "2019-05-19T22:55:39Z",
-                  "message": "fix most of focus navigation focus managment in development\n\nnavigating from and to 404 doesn't focus router wrapper correctly. This is because 404 in development is special case (see notes before skipped e2e-tests/development-runtime accessibility tests). This can be fixed but require a lot of changes which would be out of scope of this PR and would potentially make it harder to merge page manifest changes, so for now lets ship fixes that are already here."
+                  "message": "fix most of focus navigation focus management in development\n\nnavigating from and to 404 doesn't focus router wrapper correctly. This is because 404 in development is special case (see notes before skipped e2e-tests/development-runtime accessibility tests). This can be fixed but require a lot of changes which would be out of scope of this PR and would potentially make it harder to merge page manifest changes, so for now lets ship fixes that are already here."
                 }
               },
               {

docs/blog/2018-02-16-bright-future-for-the-web/index.md

@@ -24,7 +24,7 @@ It was for those reasons that I was hesitant to pull the trigger on a static sit
 
 One day after airing my grievances about the current state of static site generators on Slack a fellow developer recommend that I check out Gatsby. Gatsby is yet another static site generator but what really set it apart for me was how it was built with [React](https://reactjs.org/) and emphasized a rich plugin system. This was a big plus for me as I was itching to learn more about React and the plugin system alleviated some initial pain that I would have had dealing with mundane tasks. Out of the box you get a fantastic development environment with live reloading that required almost no configuration. With Gatsby specific plugins and React components it can handle pretty much anything you throw at it.
 
-Next came integrating the statically generated site with data stored in a CMS. Again Gatsby was well suited for this and I was able to easily integrate with Contentful via the [gatsby-source-contentful](/packages/gatsby-source-contentful/) plugin. Contentful is an example of a headless CMS, meaning that is is not tied to any particular technology or language. Contentful allows you to store content using a pleasant user interface and it can then output the data via an API. Best of all Contentful puts you in the driver seat and lets you define your own content model however you see fit. Think [WordPress Advanced Custom Fields](https://www.advancedcustomfields.com/) on steroids. With the content stored in Contentful Gatsby then uses the Contenful API along with the awesome power of [GraphQL](http://graphql.org/) to query data at build time. Cool stuff!
+Next came integrating the statically generated site with data stored in a CMS. Again Gatsby was well suited for this and I was able to easily integrate with Contentful via the [gatsby-source-contentful](/packages/gatsby-source-contentful/) plugin. Contentful is an example of a headless CMS, meaning that is is not tied to any particular technology or language. Contentful allows you to store content using a pleasant user interface and it can then output the data via an API. Best of all Contentful puts you in the driver seat and lets you define your own content model however you see fit. Think [WordPress Advanced Custom Fields](https://www.advancedcustomfields.com/) on steroids. With the content stored in Contentful Gatsby then uses the Contentful API along with the awesome power of [GraphQL](http://graphql.org/) to query data at build time. Cool stuff!
 
 The final piece of the puzzle was determining where to host the website. I had recently experimented with Netlify on a somewhat [pointless website for my dog](https://www.doggoforhire.com/) and I was impressed by its ease of use and how they offered a fully featured developer tier for free. In no time I was able to get my Gatsby powered website up and running on Netlify. Then with the help of webhooks I was able to have Contentful tell Netlify to “rebuild” the website whenever a new post was published. Finally with Netlify’s form handling functionality I hooked up a contact form all without a single line of backend code or even a database.
 

docs/blog/2018-03-07-why-we-created-the-plugin-library/index.md

@@ -75,7 +75,7 @@ Here’s a sampling of screenshots that many community members contributed to an
 
 The plugin ecosystem is a huge part of what makes Gatsby awesome because plugins and packages make Gatsby extensible. There's a virtuous cycle where people find plugins, use them, contribute to them, and create new ones. We hope to accelerate this cycle, so the Gatsby ecosystem can develop faster and more people can build awesome sites!
 
-Here are some ways you can help make the Gatsby plugin ecoystem great:
+Here are some ways you can help make the Gatsby plugin ecosystem great:
 
 - Share feedback on the plugin library on [GitHub Issue #4394](https://github.com/gatsbyjs/gatsby/issues/4394).
 - If you created a plugin and it's not showing up in the library, double check that the package has "gatsby-plugin" in its keywords.

docs/blog/2018-10-18-creating-compelling-content-experiences/index.md

@@ -36,7 +36,7 @@ This allows content teams to replace their heavyweight CMS monolith with their c
 
 ### Second, pick a UI development library
 
-[React and Angular are both excellent, ubiquitious, modern choices](/blog/2018-10-11-rise-of-modern-web-development), with rich community ecosystems to address website-specific concerns like:
+[React and Angular are both excellent, ubiquitous, modern choices](/blog/2018-10-11-rise-of-modern-web-development), with rich community ecosystems to address website-specific concerns like:
 
 - SEO
 - Routing

docs/blog/2018-2-6-choosing-a-back-end/index.md

@@ -44,7 +44,7 @@ Firstly, though, why do we want a Headless CMS and a JAMstack for the project? T
 
 ---
 
-![Contenful](contentful.png)
+![Contentful](contentful.png)
 
 ### Contentful
 

docs/blog/2019-02-20-introducing-use-static-query/index.md

@@ -107,7 +107,7 @@ const useSiteMetadata = () => {
 }
 ```
 
-Now everytime you need the site title, you can use this custom hook.
+Now every time you need the site title, you can use this custom hook.
 
 ```jsx
 const Header = () => {

docs/blog/2019-03-22-introducing-gatsby-preview-beta/index.md

@@ -2,7 +2,7 @@
 title: Introducing Gatsby Preview Beta
 date: 2019-03-22
 author: Marisa Morby
-excerpt: "Introducing the Gatsby Preview Beta: learn more and sign up today for early access to our first commerical product."
+excerpt: "Introducing the Gatsby Preview Beta: learn more and sign up today for early access to our first commercial product."
 tags:
   - preview
   - cloud

docs/blog/2019-04-02-behind-the-scenes-what-makes-gatsby-great/index.md

@@ -16,7 +16,7 @@ Gatsby is **great** from a multititude of perspectives. Our community is **great
 As such--this post focuses on just a single element of what makes Gatsby great: performance. To prime the discussion, let's consider [this post on the `webdev` subreddit on Reddit](https://www.reddit.com/r/webdev/comments/9z5dsr/how_does_reactjs_have_such_a_fast_website/?st=jtqbllhm&sh=60148ea7).
 
 <Pullquote citation="reddit/r/webdev">
-Genuine question, every page is loaded immediatley [sic] on click. Seriously never seen such a quick website before. Any insight as to how they're able to achieve this?
+Genuine question, every page is loaded immediately [sic] on click. Seriously never seen such a quick website before. Any insight as to how they're able to achieve this?
 </Pullquote>
 
 Fun fact--that website in question is [reactjs.org](https://reactjs.org) which, as you may or may not know, is an application built with and powered by Gatsby 💪
@@ -134,7 +134,7 @@ Next:
   - Traditional examples are something like [EC2](https://aws.amazon.com/ec2/)
 - Configure the VM to be able to run Node.js code
   - Consider using [Docker](https://www.docker.com/) to ensure you have a consistent Node.js environment
-- Set up auto-scaling to ensure we can accomodate and fall-over based upon heavy load or error states
+- Set up auto-scaling to ensure we can accommodate and fall-over based upon heavy load or error states
   - Consider using [Kubernetes](https://kubernetes.io/), [Rancher](https://rancher.com/), etc.
 
 Does this sound like something that sparks joy? ✨Oh--let's talk about the deploy process, too.
@@ -363,7 +363,7 @@ The feature seamlessly falls back to default behavior if `IntersectionObserver`
 
 **Mobile**
 
-Most mobile browsers support `IntersectionObserver` but none (of course!) support the `onMouseEnter` event. This means that the strong, non-idle fetch will not be triggered on mobile. This is not necessarily ideal--but the beauty of the feature is that the `prefetch` generally takes care of the necessary resource(s) being avalable.
+Most mobile browsers support `IntersectionObserver` but none (of course!) support the `onMouseEnter` event. This means that the strong, non-idle fetch will not be triggered on mobile. This is not necessarily ideal--but the beauty of the feature is that the `prefetch` generally takes care of the necessary resource(s) being available.
 
 **Data-constrained devices**
 

docs/docs/adding-search-with-algolia.md

@@ -11,7 +11,7 @@ Two things before you begin:
 
 ## Configuring the Algolia plugin
 
-First, you'll need to add [`gatsby-plugin-algolia`](https://github.com/algolia/gatsby-plugin-algolia) and [`react-instantsearch-dom`](https://github.com/algolia/react-instantsearch) to your project. `react-instantsearch` is Algolia's library containing off-the-shelf React components which you can import to save yourself a lot of work. You'll also be using `dotenv` which gets shipped with Gatsby by default. You're going to need it to specify your Algolia app ID and both the search and admin API keys without commiting them to version control.
+First, you'll need to add [`gatsby-plugin-algolia`](https://github.com/algolia/gatsby-plugin-algolia) and [`react-instantsearch-dom`](https://github.com/algolia/react-instantsearch) to your project. `react-instantsearch` is Algolia's library containing off-the-shelf React components which you can import to save yourself a lot of work. You'll also be using `dotenv` which gets shipped with Gatsby by default. You're going to need it to specify your Algolia app ID and both the search and admin API keys without committing them to version control.
 
 ```shell
 npm install --save gatsby-plugin-algolia react-instantsearch-dom algoliasearch dotenv

docs/docs/graphql-reference.md

@@ -142,7 +142,7 @@ To add variables to page component queries, pass these in the `context` object [
 
 You can also group values on the basis of a field e.g. the title, date or category and get the field value, the total number of occurrences and edges.
 
-The query below gets us all categories (`fieldValue`) applied to a book and how many books (`totalCount`) given category is aplied to. In addition we're grabbing the `title` of books in given category. You can see for example that there are 3 books in `magical creatures` category.
+The query below gets us all categories (`fieldValue`) applied to a book and how many books (`totalCount`) given category is applied to. In addition we're grabbing the `title` of books in given category. You can see for example that there are 3 books in `magical creatures` category.
 
 <iframe title="Grouping values" src="https://gatsby-1774317511.gtsb.io/___graphql?query=%7B%0A%20%20allMarkdownRemark(filter%3A%20%7Bfrontmatter%3A%20%7Btitle%3A%20%7Bne%3A%20%22%22%7D%7D%7D)%20%7B%0A%20%20%20%20group(field%3A%20frontmatter___categories)%20%7B%0A%20%20%20%20%20%20fieldValue%0A%20%20%20%20%20%20totalCount%0A%20%20%20%20%20%20edges%20%7B%0A%20%20%20%20%20%20%20%20node%20%7B%0A%20%20%20%20%20%20%20%20%20%20frontmatter%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20title%0A%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%20%20nodes%20%7B%0A%20%20%20%20%20%20frontmatter%20%7B%0A%20%20%20%20%20%20%20%20title%0A%20%20%20%20%20%20%20%20categories%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A&explorerIsOpen=false" width="600" height="400"></iframe>
 

docs/docs/hosting-on-netlify.md

@@ -44,14 +44,14 @@ As written on the website, we only need to drag and drop our `public` folder ove
 
 #### Git Repository Setup
 
-We can use git with Netlify to host our website. There are many benefits of this such as we can have past versions of our website so that we can rollback to previous versions whenever we want, no need to manually build our website and upload it everytime we change anything. Netlify supports [GitHub](https://github.com/), [GitLab](https://about.gitlab.com/) and [Bitbucket](https://bitbucket.org/). All we have to do is push our code to the respective repository. Our repository can be private or public.
+We can use git with Netlify to host our website. There are many benefits of this such as we can have past versions of our website so that we can rollback to previous versions whenever we want, no need to manually build our website and upload it every time we change anything. Netlify supports [GitHub](https://github.com/), [GitLab](https://about.gitlab.com/) and [Bitbucket](https://bitbucket.org/). All we have to do is push our code to the respective repository. Our repository can be private or public.
 
 Now, login to Netlify and we will see a `New site from git` button at the top right corner on our screen. Click on it and connect with the same git provider that you used to host your website and authorize Netlify to use your account. Choose your website repository and it will take you to deploy settings with below options.
 
 - Branch to deploy: We can specify the branch, when we push to that particular branch, then only Netlify will build and deploy our site. The default is `master`.
 - Build Command: We can specify the command we want Netlify to run when we push to above branch. The default is `npm run build`.
 - Publish directory: We can specify which folder should Netlify use to host our website. eg. public, dist, build. The default is `public`.
-- Advanced build settings: If our site needs enviromnent variables to build, we can spectify them by clicking on `Show advanced` and then the `New Variable` button.
+- Advanced build settings: If our site needs environment variables to build, we can spectify them by clicking on `Show advanced` and then the `New Variable` button.
 
 Click on `Deploy site` button and Netlify will start to build and deploy process we specified. In a few moments, it will give us our site URL like `random-name.netlify.com`. We can go to the `Deploys` tab and see what is actually happening.
 

docs/docs/localization-i18n.md

@@ -10,7 +10,7 @@ This guide is a brief look at the options that exist for enhancing your Gatsby p
 
 ## Choosing a package
 
-There are a few React i18n packages out there. Several options include [react-intl](https://github.com/yahoo/react-intl), the community [Gatsby plugin](https://www.npmjs.com/package/gatsby-plugin-i18n) and [react-i18next](https://github.com/i18next/react-i18next/). There are several factors to consider when choosing a package: Do you already use a similiar package in another project? How well does the package meet the needs of your users? Are you or your team already familiar with a certain package? Is the package well documented and maintained?
+There are a few React i18n packages out there. Several options include [react-intl](https://github.com/yahoo/react-intl), the community [Gatsby plugin](https://www.npmjs.com/package/gatsby-plugin-i18n) and [react-i18next](https://github.com/i18next/react-i18next/). There are several factors to consider when choosing a package: Do you already use a similar package in another project? How well does the package meet the needs of your users? Are you or your team already familiar with a certain package? Is the package well documented and maintained?
 
 ### gatsby-plugin-i18n
 

docs/docs/migrating-from-v1-to-v2.md

@@ -141,7 +141,7 @@ There are some implications to this change:
 
 - To learn more about the decision behind this removal, read the [RFC for removing the special layout component](https://github.com/gatsbyjs/rfcs/blob/master/text/0002-remove-special-layout-components.md).
 
-We reccomend the following migration path:
+We recommend the following migration path:
 
 #### 1. Convert the layout's children from a render prop to a normal prop (required)
 

docs/docs/porting-from-create-react-app-to-gatsby.md

@@ -167,7 +167,7 @@ For more information about errors encountered during builds, see the doc on [deb
 
 ### Routing
 
-There are two possibilites of routes that you can set up: static and client-only. Gatsby automatically turns React components in the pages folder into static routes. This means that a statically rendered page directly corresponds to index.html files in the app's built assets, whereas a client-only route is rendered by the client and configured by the routing setup you define. Both types of pages can [fetch data at runtime](/docs/client-data-fetching/) just like any other React app.
+There are two possibilities of routes that you can set up: static and client-only. Gatsby automatically turns React components in the pages folder into static routes. This means that a statically rendered page directly corresponds to index.html files in the app's built assets, whereas a client-only route is rendered by the client and configured by the routing setup you define. Both types of pages can [fetch data at runtime](/docs/client-data-fetching/) just like any other React app.
 
 > **Note**: An advantage to having pages in separate files like this is a defined way of [automatically code splitting](/docs/how-code-splitting-works/), whereas Create React App requires you to use the `import()` syntax to assign what elements should be loaded dynamically