chore: Fix Typos across repository (gatsbyjs#15923)

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

@@ -3649,7 +3649,7 @@
               {
                 "commit": {
                   "authoredDate": "2019-04-29T06:37:51Z",
-                  "message": "remove accidentally commited .patch file"
+                  "message": "remove accidentally committed .patch file"
                 }
               },
               {
@@ -4853,7 +4853,7 @@
               {
                 "commit": {
                   "authoredDate": "2019-05-26T18:18:31Z",
-                  "message": "skip checking if createTypes is available - this is hard requirment now and wouldn't work without it"
+                  "message": "skip checking if createTypes is available - this is hard requirement now and wouldn't work without it"
                 }
               },
               {
@@ -6424,7 +6424,7 @@
         {
           "createdAt": "2019-05-17T13:04:21Z",
           "updatedAt": "2019-06-03T13:52:10Z",
-          "title": "fix(www): Normalize data from airtable on schema level, remove unnessecary hook.",
+          "title": "fix(www): Normalize data from airtable on schema level, remove unnecessary hook.",
           "url": "https://github.com/gatsbyjs/gatsby/pull/14114",
           "author": {
             "url": "https://github.com/freiksenet"
@@ -6465,7 +6465,7 @@
               {
                 "commit": {
                   "authoredDate": "2019-05-17T13:03:04Z",
-                  "message": "Normalize data from airtable on schema level, remove unnessecary hook."
+                  "message": "Normalize data from airtable on schema level, remove unnecessary hook."
                 }
               },
               {

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

@@ -3345,7 +3345,7 @@
               {
                 "commit": {
                   "authoredDate": "2019-04-29T06:37:51Z",
-                  "message": "remove accidentally commited .patch file"
+                  "message": "remove accidentally committed .patch file"
                 }
               },
               {
@@ -3357,7 +3357,7 @@
               {
                 "commit": {
                   "authoredDate": "2019-06-24T21:58:25Z",
-                  "message": "feat: add basic caching so an icon isn't generated multiple times durring a single build."
+                  "message": "feat: add basic caching so an icon isn't generated multiple times during a single build."
                 }
               },
               {
@@ -3775,13 +3775,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."
                 }
               },
               {
@@ -4673,7 +4673,7 @@
               {
                 "commit": {
                   "authoredDate": "2019-05-26T18:18:31Z",
-                  "message": "skip checking if createTypes is available - this is hard requirment now and wouldn't work without it"
+                  "message": "skip checking if createTypes is available - this is hard requirement now and wouldn't work without it"
                 }
               },
               {
@@ -4745,7 +4745,7 @@
               {
                 "commit": {
                   "authoredDate": "2019-06-24T19:31:56Z",
-                  "message": "revert unnecesary change"
+                  "message": "revert unnecessary change"
                 }
               },
               {
@@ -6507,7 +6507,7 @@
               {
                 "commit": {
                   "authoredDate": "2019-06-27T15:15:53Z",
-                  "message": "Removed the difference between static and normal query from page.\n\nWill add this to seperate page on difference between Static and Normal query ."
+                  "message": "Removed the difference between static and normal query from page.\n\nWill add this to separate page on difference between Static and Normal query ."
                 }
               }
             ]

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 💪

docs/blog/2019-06-12-performance-improvements-for-large-sites/index.md

@@ -29,7 +29,7 @@ The central problem was that Gatsby generates a file for each build called `page
 
 When a user clicks a link to another page, Gatsby first looks up the manifest for the page's component and query result file. Gatsby then downloads them (if they haven't already been prefetched), and then passes the loaded query results to the page's component and renders it. Since `pages-manifest` contains the list of all pages on the site, Gatsby can also immediately show a 404 if necessary if the page is not able to be located.
 
-This works great for small sites, but as a Gatsby application grows, so too does the size of the page manfiest. The bigger the manifest gets the more data the browser has to download before any UI navigation can occur leading to slowdowns in important metrics like Time to Interactive (TTI).
+This works great for small sites, but as a Gatsby application grows, so too does the size of the page manifest. The bigger the manifest gets the more data the browser has to download before any UI navigation can occur leading to slowdowns in important metrics like Time to Interactive (TTI).
 
 Even after the manifest had been loaded, the manifest had to be searched for the matching path. This was necessary since pages can be declared with a [matchPath](https://www.gatsbyjs.org/docs/gatsby-internals-terminology/#matchpath) (a Regular Expression used to match client-only paths). Huge manifest files resulted in perceptable lag when clicking links too!
 

docs/creators/creators.yml

@@ -117,7 +117,7 @@
   portfolio: true
 - name: Michael Uloth
   type: individual
-  description: Michael Uloth is a Toronto-based web developer who specializes in building fast-loading, accessibile websites with Gatsby.
+  description: Michael Uloth is a Toronto-based web developer who specializes in building fast-loading, accessible websites with Gatsby.
   location: Toronto
   website: "https://www.michaeluloth.com"
   github: "https://github.com/ooloth"

docs/docs/building-a-contact-form.md

@@ -47,7 +47,7 @@ Each method detailed below will start with the following contact form:
 
 If you're hosting your site with Netlify, you gain access to their excellent [form handling feature](https://www.netlify.com/docs/form-handling/).
 
-Setting this up only invloves adding a few form attributes:
+Setting this up only involves adding a few form attributes:
 
 ```diff:title=src/pages/contact.js
 - <form method="post" action="#">

docs/docs/gatsby-repl.md

@@ -41,7 +41,7 @@ gatsby > babelrc
 
 ### `components`
 
-Returns a Map object with all of the components in your Gatsby environment (see [Mozilla Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) docs for more information on Map objects and how to use them). Propeties that get returned: `name`, `componentPath`, `query`, `pages`, and `isInBootstrap:`.
+Returns a Map object with all of the components in your Gatsby environment (see [Mozilla Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) docs for more information on Map objects and how to use them). Properties that get returned: `name`, `componentPath`, `query`, `pages`, and `isInBootstrap:`.
 
 Usage: `components`
 
@@ -200,7 +200,7 @@ gatsby > siteConfig.siteMetadata
 
 ### `staticQueries`
 
-Returns a Map object with all of the static queries in your Gatsby environment. Propeties that get returned: `name`, `componentPath`, `id`, `query`, and `hash`.
+Returns a Map object with all of the static queries in your Gatsby environment. Properties that get returned: `name`, `componentPath`, `id`, `query`, and `hash`.
 
 Usage: `staticQueries`
 

docs/sites.yml

@@ -1176,7 +1176,7 @@
   main_url: "https://mottox2.com"
   url: "https://mottox2.com"
   source_url: "https://github.com/mottox2/website"
-  description: Web developer / UI Desinger in Tokyo Japan.
+  description: Web developer / UI Designer in Tokyo Japan.
   featured: false
   categories:
     - Blog
@@ -2905,7 +2905,7 @@
   url: https://www.dekema.com/
   main_url: https://www.dekema.com/
   description: >
-    Worldclass crafting: Furnace, fervor, fullfilment. Delivering highest demand for future craftsmanship. Built using Gatsby v2 and Prismic.
+    Worldclass crafting: Furnace, fervor, fulfillment. Delivering highest demand for future craftsmanship. Built using Gatsby v2 and Prismic.
   categories:
     - Healthcare
     - Science
@@ -3634,7 +3634,7 @@
 - title: Gábor Fűzy pianist
   main_url: "https://pianobar.hu"
   url: "https://pianobar.hu"
-  description: Gábor Fűzy pianist's offical website built with Gatsby v2.
+  description: Gábor Fűzy pianist's official website built with Gatsby v2.
   categories:
     - Music
   built_by: Zoltán Bedi
@@ -4609,7 +4609,7 @@
   url: https://our-academy.org/
   source_url: "https://github.com/ouracademy/website"
   description: >
-    Ouracademy is an organization that promoves the education in software development throught blog posts & videos smiley.
+    Ouracademy is an organization that promoves the education in software development through blog posts & videos smiley.
   categories:
     - Open Source
     - Blog
@@ -5518,7 +5518,7 @@
   url: https://lendo.at
   main_url: https://lendo.at
   description: >
-    A Comparsion site for best private loan offer from banks in Austria.
+    A Comparison site for best private loan offer from banks in Austria.
   categories:
     - Business
     - Finance

docs/starters.yml

@@ -1259,7 +1259,7 @@
     - Minimal UI and Styling
 - url: https://gatsby-tutorial-starter.netlify.com/
   repo: https://github.com/justinformentin/gatsby-v2-tutorial-starter
-  description: Simple, modern desgined blog with post lists, tags, and easily customizable code.
+  description: Simple, modern designed blog with post lists, tags, and easily customizable code.
   tags:
     - Blog
     - Linting
@@ -1964,7 +1964,7 @@
     - Pagination logic
 - url: https://gatsby-blogger.netlify.com/
   repo: https://github.com/aslammultidots/blogger
-  description: A Simple, clean and modern desgined blog with firebase authentication feature and easily customizable code.
+  description: A Simple, clean and modern designed blog with firebase authentication feature and easily customizable code.
   tags:
     - Blog
     - Redux
@@ -2745,7 +2745,7 @@
     - SEO (including robots.txt, sitemap generation, automated yet customisable metadata, and social sharing data)
     - Google Analytics
     - PostCSS support
-    - Developer enviornment variables
+    - Developer environment variables
     - Accessibility support
     - Based on Gatsby Starter Default
 - url: https://material-ui-starter.netlify.com/
@@ -2962,7 +2962,7 @@
     - Web App Manifest
 - url: https://yellowcake.netlify.com/
   repo: https://github.com/thriveweb/yellowcake
-  description: A starter project for creating lightning-fast websites with Gatsby v2 and Netlify-CMS v2 + Uploadcare intergration.
+  description: A starter project for creating lightning-fast websites with Gatsby v2 and Netlify-CMS v2 + Uploadcare integration.
   tags:
     - CMS:Netlify
     - Netlify

e2e-tests/development-runtime/cypress/integration/functionality/accessibility.js

@@ -1,4 +1,4 @@
-describe(`focus managment`, () => {
+describe(`focus management`, () => {
   it(`Focus router wrapper after navigation to regular page (from index)`, () => {
     cy.visit(`/`).waitForRouteChange()
 

e2e-tests/development-runtime/cypress/integration/navigation/linking.js

@@ -35,7 +35,7 @@ describe(`navigation`, () => {
     cy.location(`pathname`).should(`equal`, `/`)
   })
 
-  describe(`non-existant route`, () => {
+  describe(`non-existent route`, () => {
     beforeEach(() => {
       cy.getTestElement(`broken-link`)
         .click()

e2e-tests/development-runtime/src/pages/index.js

@@ -23,7 +23,7 @@ const IndexPage = ({ data }) => (
     <Link to="/안녕" data-testid="page-with-unicode-path">
       Go to page with unicode path
     </Link>
-    <Link to="/__non_existant_page__/" data-testid="broken-link">
+    <Link to="/__non_existent_page__/" data-testid="broken-link">
       Go to a broken link
     </Link>
     <h2>Blog posts</h2>

e2e-tests/production-runtime/.env.production

@@ -1,4 +1,4 @@
-# This file is commited to repo only to validate that env vars are available
+# This file is committed to repo only to validate that env vars are available
 # to use in frontend and don't leak if not used (secrets used in Node).
 # You should NOT commit `.env` files to your repository for production sites.
 EXISTING_VAR=foo bar

e2e-tests/production-runtime/cypress/integration/accessibility.js

@@ -1,4 +1,4 @@
-describe(`focus managment`, () => {
+describe(`focus management`, () => {
   it(`Focus router wrapper after navigation to regular page (from index)`, () => {
     cy.visit(`/`).waitForRouteChange()
 

examples/using-asciidoc/src/pages/test.adoc

@@ -40,8 +40,8 @@ NOTE: Items marked with TODO are either not yet supported or a work in progress.
 
 .Inline markup
 * single quotes around a phrase place 'emphasis'
-* astericks around a phrase make the text *bold*
-* double astericks around one or more **l**etters in a word make those letters bold
+* asterisk around a phrase make the text *bold*
+* double asterisk around one or more **l**etters in a word make those letters bold
 * double underscore around a __sub__string in a word emphasize that substring
 * use carrots around characters to make them ^super^script
 * use tildes around characters to make them ~sub~script

junit.xml

@@ -1066,7 +1066,7 @@
     </testcase>
     <testcase classname="watching copying files copies cache-dir files" name="watching copying files copies cache-dir files" time="0.001">
     </testcase>
-    <testcase classname="watching copying files filters non-existant files/directories" name="watching copying files filters non-existant files/directories" time="0.001">
+    <testcase classname="watching copying files filters non-existent files/directories" name="watching copying files filters non-existent files/directories" time="0.001">
     </testcase>
     <testcase classname="watching copying files filters duplicate directories" name="watching copying files filters duplicate directories" time="0.001">
     </testcase>
@@ -1208,7 +1208,7 @@
     </testcase>
     <testcase classname="Merge gatsby config Merging siteMetadata is recursive" name="Merge gatsby config Merging siteMetadata is recursive" time="0.002">
     </testcase>
-    <testcase classname="Merge gatsby config Merging proxy is overriden" name="Merge gatsby config Merging proxy is overriden" time="0">
+    <testcase classname="Merge gatsby config Merging proxy is overridden" name="Merge gatsby config Merging proxy is overridden" time="0">
     </testcase>
   </testsuite>
   <testsuite name="&lt;Img /&gt;" errors="0" failures="0" skipped="0" timestamp="2018-11-27T15:50:30" time="2.154" tests="5">

packages/gatsby-dev-cli/src/__tests__/watch.js

@@ -129,7 +129,7 @@ describe(`watching`, () => {
       )
     })
 
-    it(`filters non-existant files/directories`, () => {
+    it(`filters non-existent files/directories`, () => {
       fs.existsSync.mockReset().mockImplementation(file => false)
 
       watch(...args)

packages/gatsby-dev-cli/src/watch.js

@@ -21,7 +21,7 @@ const quit = () => {
 const MAX_COPY_RETRIES = 3
 
 /*
- * non-existant packages break on('ready')
+ * non-existent packages break on('ready')
  * See: https://github.com/paulmillr/chokidar/issues/449
  */
 async function watch(

packages/gatsby-plugin-canonical-urls/src/__tests__/__snapshots__/gatsby-ssr.js.snap

@@ -48,7 +48,7 @@ exports[`gatsby-plugin-canonical-urls strips a trailing slash on the siteUrl and
 }
 `;
 
-exports[`gatsby-plugin-canonical-urls strips search paramaters if option stripQueryString is true 1`] = `
+exports[`gatsby-plugin-canonical-urls strips search parameters if option stripQueryString is true 1`] = `
 [MockFunction] {
   "calls": Array [
     Array [

packages/gatsby-plugin-canonical-urls/src/__tests__/gatsby-browser.js

@@ -35,7 +35,7 @@ describe(`gatsby-plugin-canonical-urls`, () => {
       `"<link data-basehost=\\"someurl.com\\" data-baseprotocol=\\"http:\\" href=\\"http://someurl.com/hogwarts?house=gryffindor\\" rel=\\"canonical\\">"`
     )
   })
-  it(`should strip search paramaters if option stripQueryString is true`, () => {
+  it(`should strip search parameters if option stripQueryString is true`, () => {
     const pluginOptions = {
       stripQueryString: true,
     }

packages/gatsby-plugin-canonical-urls/src/__tests__/gatsby-ssr.js

@@ -39,7 +39,7 @@ describe(`gatsby-plugin-canonical-urls`, () => {
     expect(setHeadComponents).toHaveBeenCalledTimes(1)
   })
 
-  it(`strips search paramaters if option stripQueryString is true`, async () => {
+  it(`strips search parameters if option stripQueryString is true`, async () => {
     const pluginOptions = {
       siteUrl: `http://someurl.com`,
       stripQueryString: true,

packages/gatsby-plugin-facebook-analytics/src/gatsby-ssr.js

@@ -17,7 +17,7 @@ export const onRenderBody = ({ setPostBodyComponents }, pluginOptions) => {
   if (process.env.NODE_ENV === `production` || includeInDevelopment || debug) {
     setPostBodyComponents([
       <script
-        key="plugin-facebook-analitycs"
+        key="plugin-facebook-analytics"
         dangerouslySetInnerHTML={{
           __html: stripIndent(`
             window.fbAsyncInit = function() {

packages/gatsby-plugin-feed/README.md

@@ -76,7 +76,7 @@ module.exports = {
 
 Each feed must include `output`, `query`, and `title`. Additionally, it is strongly recommended to pass a custom `serialize` function, otherwise an internal serialize function will be used which may not exactly match your particular use case.
 
-`match` is an optional configuration, indicating which pages will have feed reference included. The accepted types of `match` are `string` or `undefined`. By default, when `match` is not configured, all pages will have feed reference inserted. If `string` is provided, it will be used to build a RegExp and then to test whether `pathname` of current page satisifed this regular expression. Only pages that satisifed this rule will have feed reference included.
+`match` is an optional configuration, indicating which pages will have feed reference included. The accepted types of `match` are `string` or `undefined`. By default, when `match` is not configured, all pages will have feed reference inserted. If `string` is provided, it will be used to build a RegExp and then to test whether `pathname` of current page satisfied this regular expression. Only pages that satisfied this rule will have feed reference included.
 
 All additional options are passed through to the [`rss`][rss] utility. For more info on those additional options, [explore the `itemOptions` section of the `rss` package](https://www.npmjs.com/package/rss#itemoptions).