chore(docs): fix several typos in blog and elsewhere (#13265)

## Description  ## Related Issues
gatsbyjs · Apr 11, 2019 · 7a308e6 · 7a308e6
1 parent d879508
commit 7a308e6
Show file tree

Hide file tree

Showing 6 changed files with 8 additions and 8 deletions.
diff --git a/docs/blog/2018-10-18-creating-compelling-content-experiences/index.md b/docs/blog/2018-10-18-creating-compelling-content-experiences/index.md
@@ -120,7 +120,7 @@ Today, the CMS is being reimagined.
 
 With maturity comes growing functionality and complexity; a shift from monolithic to modular architectures.
 
-Today, there's a multitude of vendors, frameworks, and approaches for content modelling, authentication, search, analytics, payments, development environemnt, performance, and so on.
+Today, there's a multitude of vendors, frameworks, and approaches for content modelling, authentication, search, analytics, payments, development environment, performance, and so on.
 
 The key question becomes: how to bring these pieces into a unified whole?
 

diff --git a/docs/blog/2018-10-18-vscode-gatsby-development/index.md b/docs/blog/2018-10-18-vscode-gatsby-development/index.md
@@ -78,7 +78,7 @@ _NOTE_: You most likely will want to add the `.vscode` folder to your `.gitignor
 
 In this article we have learned some of the basics about configuring and using VS Code for development on the Gatsby project. That being said, the Extensions and configuration discussed here can be applied to _any_ modern JavaScript web project that **may or may not use** Gatsby.
 
-You may want to browse through the [VS Code Updates page](https://code.visualstudio.com/updates/) to see some of the recent features added. You'll notice they publish major updates monthly. It seems they are listening to the user community and continually adding features to the Editor and improvements to the user expereince.
+You may want to browse through the [VS Code Updates page](https://code.visualstudio.com/updates/) to see some of the recent features added. You'll notice they publish major updates monthly. It seems they are listening to the user community and continually adding features to the Editor and improvements to the user experience.
 
 A great way to contribute is to browse the [open issues on GitHub](https://github.com/gatsbyjs/gatsby/issues), and find some that look interesting! Armed with some of the techniques I've shown here today, authoring these fixes, features, and more will be a breeze thanks to some of the great features of VS Code.
 

diff --git a/docs/blog/2018-11-07-gatsby-for-apps/index.md b/docs/blog/2018-11-07-gatsby-for-apps/index.md
@@ -27,7 +27,7 @@ To begin, what even _is_ an application, anyways?
 
 ## What is an application?
 
-I've previously attempted the [surprisingly difficult task][whats-an-app] of defining what consititutes a traditional web application. In an effort to not re-hash all the work there, I think there are several, key features that indicate a more app-like experience:
+I've previously attempted the [surprisingly difficult task][whats-an-app] of defining what constitutes a traditional web application. In an effort to not re-hash all the work there, I think there are several, key features that indicate a more app-like experience:
 
 - dynamic data fetching
 - user authentication and authenticated client-only routes
@@ -75,7 +75,7 @@ These two web applications will serve as key foundational pieces to keep in mind
 
 What if I told you... that building a Gatsby website enables all of these traditional web-app like functionalities because a Gatsby "static site" is an application?
 
-Every Gatsby application isn't merely static. It's _as much_ static HTML rendered up-front, as possible. Client-side JavaScript (via React!) takes over as the enginge for dynamic application functionality. A quick overview of Gatsby's general build process is effective to illustrate the concept.
+Every Gatsby application isn't merely static. It's _as much_ static HTML rendered up-front, as possible. Client-side JavaScript (via React!) takes over as the engine for dynamic application functionality. A quick overview of Gatsby's general build process is effective to illustrate the concept.
 
 1. Inject pages with data (from [GraphQL][gatsby-graphql] or even [without using GraphQL][gatsby-without-graphql])
 1. Use the [ReactDOMServer.renderToString][react-dom-render-to-string] API to invoke server-side APIs to render React components to _HTML_ files

diff --git a/docs/blog/2019-01-25-blazing-fast-development-with-gatsby-and-sanity-io/index.md b/docs/blog/2019-01-25-blazing-fast-development-with-gatsby-and-sanity-io/index.md
@@ -72,7 +72,7 @@ If you [add a token with read permissions](https://github.com/sanity-io/example-
 
 The source plugin uses Sanity.io’s export API. It streams all your documents in one go. So it's not only _very_ fast, it's also just a single API call for all your content. Regardless of the number of documents or their size. Thanks to this you can build your website with Gatsby thousands of times a month on the free developer plan (you can also add your card to the [dev plan](https://www.sanity.io/pricing/dev-2018-08-21) for an affordable pay-as-you-go option should you blow past the generous base quotas).
 
-You also avoid time consuming processing of images. Our image pipeline scales and crops the images for you and we have already baked in Low-Quality-Image-Placeholder (LQIP) into the image asset data structure so you don't need to extract it yourself to have it be part of your build. This while keeping compability with `gatsby-image`. We keep your image assets on a global edge cache and store the exact version you asked for to keep it fast.
+You also avoid time consuming processing of images. Our image pipeline scales and crops the images for you and we have already baked in Low-Quality-Image-Placeholder (LQIP) into the image asset data structure so you don't need to extract it yourself to have it be part of your build. This while keeping compatibility with `gatsby-image`. We keep your image assets on a global edge cache and store the exact version you asked for to keep it fast.
 
 We think some people might prefer to keep assets as part of their build and are thinking of including an option for this as well. [Let us know](https://slack.sanity.io) if you're one of them!
 

diff --git a/docs/blog/2019-02-27-reactiflux-q-and-a/index.md b/docs/blog/2019-02-27-reactiflux-q-and-a/index.md
@@ -87,7 +87,7 @@ We're also working on adding [Gatsby Theme support](/blog/2018-11-11-introducing
 
 ---
 
-**Q:** Do you hope or believe that gatsby (and JAM-stack in general), headless CMS's and microservices will overcome rigid and outrdated wordpress sites and architechture? — max
+**Q:** Do you hope or believe that gatsby (and JAM-stack in general), headless CMS's and microservices will overcome rigid and outdated wordpress sites and architecture? — max
 
 **A:** Yup! That's why I started [the Gatsby OSS project and company](/blog/2018-05-24-launching-new-gatsby-company/)! CMSs we're designed in the late 1990s and are very outdated for today's cloud/serverless computing environment. We want Gatsby to be able to replace CMSs.
 
@@ -157,7 +157,7 @@ It's a great place to get started. That said, I'd also encourage to check out [a
 
 ---
 
-**Q:** How is authenication handled in gatsby? — Reinhard
+**Q:** How is authentication handled in gatsby? — Reinhard
 
 **A:** Great question! So in general, and I probably say it far too often, but a Gatsby app is just a React application.
 

diff --git a/docs/blog/2019-03-01-localization-with-gatsby-and-sanity/index.md b/docs/blog/2019-03-01-localization-with-gatsby-and-sanity/index.md
@@ -7,7 +7,7 @@ image: "./images/gatsby-sanity-l10n.png"
 showImageInArticle: true
 ---
 
-Localization is a common problem and there are _many_ solutions, each with their own benifits and trade-offs. With Gatsby and Sanity.io its possible to achieve a solution that is easy to work with and extend. If you haven't already read about why Gatsby and Sanity.io pair so well check out the blog post by [Knut Melvær](/contributors/knut-melvaer/): [Blazing fast development with Gatsby and Sanity.io](/blog/2019-01-25-blazing-fast-development-with-gatsby-and-sanity-io).
+Localization is a common problem and there are _many_ solutions, each with their own benefits and trade-offs. With Gatsby and Sanity.io its possible to achieve a solution that is easy to work with and extend. If you haven't already read about why Gatsby and Sanity.io pair so well check out the blog post by [Knut Melvær](/contributors/knut-melvaer/): [Blazing fast development with Gatsby and Sanity.io](/blog/2019-01-25-blazing-fast-development-with-gatsby-and-sanity-io).
 
 I have completed two sites with Gatsby and Sanity that required localization. The first site needed to maintain every link from the original site without redirects: each language living in its own subdomain, `es.my-web-page.com` for example. The simplest solution at the time was to use multiple builds which always bothered me. The second site I vowed to do it the _right™_ way.