fix(docs): remove double words (#22494)

muescha · web-flow · commit 75f6ee2ac28b · 2020-03-23T13:33:45.000-04:00
* typo double word

* typo double word

* changed remove double to fix grammer
diff --git a/docs/blog/2018-02-16-bright-future-for-the-web/index.md b/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](/docs/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](https://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](/docs/headless-cms/), meaning that it 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](https://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.
 
diff --git a/docs/blog/2018-09-17-gatsby-v2.md b/docs/blog/2018-09-17-gatsby-v2.md
@@ -181,7 +181,7 @@ Best of all, contributors get free swag! Sign in with GitHub and claim your free
 
 ## Growing the community
 
-The Gatsby community has been growing very rapidly. We're seeing ~90 new PRs per week and it's really exciting to see new contributors tackle different parts of the the project to add documentation, new features, bug fixes, and refactor dusty corners of the codebase.
+The Gatsby community has been growing very rapidly. We're seeing ~90 new PRs per week and it's really exciting to see new contributors tackle different parts of the project to add documentation, new features, bug fixes, and refactor dusty corners of the codebase.
 
 We're investing heavily in scaling the velocity of the OSS project including:
 
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
@@ -11,7 +11,7 @@ In the last three sections, we’ve described the different facets of how to cre
 
 While these trends target different stakeholders, they’re deeply interrelated. That’s because to adopt a new architecture in one area, you often need to adopt new technologies in the other two.
 
-With users after user writing headlines like "[Gatsby + Contentful + Netlify (and Algolia)](/blog/2017-12-06-gatsby-plus-contentful-plus-netlify/)" -- grouping a React-based website framework, a headless CMS, a static host + CDN, and a search provider -- it’s clear these these technologies are meant to be used together.
+With users after user writing headlines like "[Gatsby + Contentful + Netlify (and Algolia)](/blog/2017-12-06-gatsby-plus-contentful-plus-netlify/)" -- grouping a React-based website framework, a headless CMS, a static host + CDN, and a search provider -- it’s clear these technologies are meant to be used together.
 
 Website teams moving to this space have to plan four steps -- one for each category, plus integration.
 
diff --git a/docs/blog/2018-10-25-using-gatsby-without-graphql/index.md b/docs/blog/2018-10-25-using-gatsby-without-graphql/index.md
@@ -215,7 +215,7 @@ Using Gatsby's data layer provides the following benefits:
 - Pushes frontend complexity into queries — many data transformations can be done at build-time within your GraphQL queries (e.g. Markdown -> HTML, images -> responsive images, etc)
 - It’s the perfect data querying language for the often complex/nested data dependencies of modern applications
 - Improves performance by removing data bloat — GraphQL enables you to select only the data you need, not whatever an API returns
-- Enables you to take advantage of hot reloading when developing; For example, in this post's example "Pokémon" site, if you wanted to add a "see other pokémon" section to the pokémon detail view, you would need to change your `gatsby-node.js` to pass all pokémon to to the page, and restart the dev server. In contrast, when using queries, you can add a query and it will hot reload.
+- Enables you to take advantage of hot reloading when developing; For example, in this post's example "Pokémon" site, if you wanted to add a "see other pokémon" section to the pokémon detail view, you would need to change your `gatsby-node.js` to pass all pokémon to the page, and restart the dev server. In contrast, when using queries, you can add a query and it will hot reload.
 
 > Learn more about [GraphQL in Gatsby](/docs/graphql-concepts/).
 
diff --git a/docs/blog/2019-01-01-publish-multiple-gatsby-sites/index.md b/docs/blog/2019-01-01-publish-multiple-gatsby-sites/index.md
@@ -49,7 +49,7 @@ Let’s begin! Navigate to an empty folder in the terminal and clone the repo by
 
 `git clone git@github.com:andrico1234/lerna-monorepo-starter.git`
 
-and navigate into the the `lerna-monorepo-starter` directory.
+and navigate into the `lerna-monorepo-starter` directory.
 
 Go to your GitHub account and create a new repo, this’ll be the repo that you push the site to so that Travis can run the pipeline. For those who need a refresher on how to [create a new repo](https://help.github.com/articles/creating-a-new-repository/). You may have to run `git remote remove origin` so you can point the code to your newly created repo.
 
diff --git a/docs/blog/2019-02-07-pragmatic-lessons-from-converting-to-react-hooks/index.md b/docs/blog/2019-02-07-pragmatic-lessons-from-converting-to-react-hooks/index.md
@@ -47,7 +47,7 @@ const updateStateGood = () =>
   this.setState(state => ({ count: state.count + 1 }))
 ```
 
-The custom `useSlideshow` hook utilizes two different hooks to replace the functionality of the render props component: `useState` and `useEffect`. The current index and playing states are both set with their own calls to useState. The `useEffect` hook checks if the isPlaying state is true and then sets the timeout to advance the slide to the next index. It resets to the first slide after it reaches the last index. The hook clears the timeout when the current index or isPlaying state changes. The hook includes a function to update the the slide. The necessary state and functions are return in an object.
+The custom `useSlideshow` hook utilizes two different hooks to replace the functionality of the render props component: `useState` and `useEffect`. The current index and playing states are both set with their own calls to useState. The `useEffect` hook checks if the isPlaying state is true and then sets the timeout to advance the slide to the next index. It resets to the first slide after it reaches the last index. The hook clears the timeout when the current index or isPlaying state changes. The hook includes a function to update the slide. The necessary state and functions are return in an object.
 
 ```javascript
 function useSlideshow(slides, { timerLength = 5000 } = {}) {
diff --git a/docs/blog/2019-04-12-linear-or-declining-sales-talk-to-developers/index.md b/docs/blog/2019-04-12-linear-or-declining-sales-talk-to-developers/index.md
@@ -110,7 +110,7 @@ So: what can you do?
 
 1. **Get out of your office** and go introduce yourself (always a good start!)
 
-2. **Let them know what your KPI goals are** and ask them how they feel they could help. Explain what you know about the positive benefits benefits of site/app performance. (they love to help and will bend over backwards to do so!)
+2. **Let them know what your KPI goals are** and ask them how they feel they could help. Explain what you know about the positive benefits of site/app performance. (they love to help and will bend over backwards to do so!)
 
 3. **Talk to them about the benefits that performance has on your goals** and what it means to you, your team and the overall company. (not everyone connects the dots to the work they are doing and how important of a role they play within the company. IMHO, the developers are your Kings and Queens of the castle...so treat them as such!)
 
diff --git a/docs/blog/2019-10-15-free-headless-cms/index.md b/docs/blog/2019-10-15-free-headless-cms/index.md
@@ -18,7 +18,7 @@ How do you know which headless CMS is right for your site? In this post, we’ll
 
 2. This headless CMS has to be robust enough to grow with the site over time.
 
-3. This headless CMS has to work with with frontend frameworks like Gatsby.
+3. This headless CMS has to work with frontend frameworks like Gatsby.
 
 The difficulty with these must-haves is that there are no _truly free_ options. There are open source projects that provide code for free, but you have to host it somewhere. Then, there are hosted headless CMS’s with generous free tiers. But most of them have prohibitive pricing once your project grows.
 
diff --git a/docs/blog/2019-11-21-how-to-convert-an-existing-gatsby-blog-to-use-mdx/index.md b/docs/blog/2019-11-21-how-to-convert-an-existing-gatsby-blog-to-use-mdx/index.md
@@ -93,7 +93,7 @@ For reference, here's the full configuration for `gatsby-plugin-mdx`.
 },
 ```
 
-Then, replace `gatsby-plugin-feed` with `gatsby-plugin-feed-mdx`. This will allow the the RSS feed of the site to parse MDX.
+Then, replace `gatsby-plugin-feed` with `gatsby-plugin-feed-mdx`. This will allow the RSS feed of the site to parse MDX.
 
 ```diff:title=gatsby-config.js
 - `gatsby-plugin-feed`,
diff --git a/docs/contributing/translation/maintainers.md b/docs/contributing/translation/maintainers.md
@@ -40,7 +40,7 @@ The Gatsby learning team is in charge of determining priorities for which docs s
 
 Don't be afraid to ask for help! If you're not sure about something, you can post in the `#localization` channel on the [Gatsby Discord](https://gatsby.dev/discord) or create an issue in the Gatsby repo.
 
-If it feels like there is too much work and you need help, you have the ability to to add more codeowners by editing the `CODEOWNERS` file in the repo. Are there any contributors who are making exceptional contributions? If so, consider making them a codeowner.
+If it feels like there is too much work and you need help, you have the ability to add more codeowners by editing the `CODEOWNERS` file in the repo. Are there any contributors who are making exceptional contributions? If so, consider making them a codeowner.
 
 We also understand that life sometimes gets in the way. If you find that you are no longer able to satisfy your codeowner duties, let the Gatsby team know so we can figure out the best path forward.
 
diff --git a/docs/contributing/translation/new-translations.md b/docs/contributing/translation/new-translations.md
@@ -2,7 +2,7 @@
 title: Starting a New Translation
 ---
 
-This page lists the steps to take to create a a new Gatsbyjs.org translation.
+This page lists the steps to take to create a new Gatsbyjs.org translation.
 
 ## Creating a translation
 
diff --git a/docs/docs/sourcing-from-graphcms.md b/docs/docs/sourcing-from-graphcms.md
@@ -24,7 +24,7 @@ Navigate inside of the project with `cd gatsby-site`.
 
 ### Add the source plugin
 
-Additionally, you need the the `gatsby-source-graphql` library. Because GraphCMS uses GraphQL natively, you will take advantage of Gatsby's ability to simply stitch two GraphQL APIs together, reducing the time required to transform content. There is no need to use a special gatsby-source-x-cms plugin, the GraphQL source plugin is all you need.
+Additionally, you need the `gatsby-source-graphql` library. Because GraphCMS uses GraphQL natively, you will take advantage of Gatsby's ability to simply stitch two GraphQL APIs together, reducing the time required to transform content. There is no need to use a special gatsby-source-x-cms plugin, the GraphQL source plugin is all you need.
 
 You can install this component with:
 
diff --git a/examples/using-remark/src/pages/2016-04-15---hello-world-kitchen-sink/index.md b/examples/using-remark/src/pages/2016-04-15---hello-world-kitchen-sink/index.md
@@ -106,7 +106,7 @@ Strikethrough uses two tildes. ~~Scratch this.~~
 
 ## Lists
 
-In this example, leading and trailing spaces are shown with with dots: ⋅
+In this example, leading and trailing spaces are shown with dots: ⋅
 
 ```no-highlight
 1. First ordered list item
diff --git a/packages/gatsby-dev-cli/CHANGELOG.md b/packages/gatsby-dev-cli/CHANGELOG.md
@@ -333,7 +333,7 @@ See [Conventional Commits](https://conventionalcommits.org) for commit guideline
 
 ### Bug Fixes
 
-- check for for both unix and win32 path separators ([#8837](https://github.com/gatsbyjs/gatsby/issues/8837)) ([57cd191](https://github.com/gatsbyjs/gatsby/commit/57cd191))
+- check for both unix and win32 path separators ([#8837](https://github.com/gatsbyjs/gatsby/issues/8837)) ([57cd191](https://github.com/gatsbyjs/gatsby/commit/57cd191))
 
 <a name="2.4.4"></a>
 
diff --git a/packages/gatsby-plugin-mdx/README.md b/packages/gatsby-plugin-mdx/README.md
@@ -513,7 +513,7 @@ The following components can be customized with the MDXProvider:
 | `a`             | [Link](https://github.com/syntax-tree/mdast#link)                    | `<https://mdxjs.com>` or `[MDX](https://mdxjs.com)` |
 | `img`           | [Image](https://github.com/syntax-tree/mdast#image)                  | `![alt](https://mdx-logo.now.sh)`                   |
 
-It's important to define the `components` you pass in in a stable way
+It's important to define the `components` you pass in a stable way
 so that the references don't change if you want to be able to navigate
 to a hash. That's why we defined `components` outside of any render
 functions in these examples.
diff --git a/packages/gatsby-plugin-sharp/README.md b/packages/gatsby-plugin-sharp/README.md
@@ -252,7 +252,7 @@ quoting the Sharp documentation:
 #### tracedSVG
 
 Generates a traced SVG of the image (see [the original GitHub issue][9]) and
-returns the SVG as "[optimized URL-encoded][10]" `data:` URI. It it used in
+returns the SVG as "[optimized URL-encoded][10]" `data:` URI. It used in
 [gatsby-image](/packages/gatsby-image/) to provide an
 alternative to the default inline base64 placeholder image.
 
diff --git a/packages/gatsby/CHANGELOG.md b/packages/gatsby/CHANGELOG.md
@@ -201,7 +201,7 @@ See [Conventional Commits](https://conventionalcommits.org) for commit guideline
 
 ### Bug Fixes
 
-- **gatsby:** Fix static query parsing for for a special case ([#21551](https://github.com/gatsbyjs/gatsby/issues/21551)) ([dd344ac](https://github.com/gatsbyjs/gatsby/commit/dd344ac))
+- **gatsby:** Fix static query parsing for a special case ([#21551](https://github.com/gatsbyjs/gatsby/issues/21551)) ([dd344ac](https://github.com/gatsbyjs/gatsby/commit/dd344ac))
 
 ## [2.19.18](https://github.com/gatsbyjs/gatsby/compare/gatsby@2.19.17...gatsby@2.19.18) (2020-02-17)
 
