dictionary.txt

@@ -1199,7 +1199,6 @@ Makenna
 Manjaro
 Mapbox
 Marcar
-markdown-autocomplete
 markdownlint
 markdownRemark
 Martyn
@@ -1454,7 +1453,6 @@ PNG
 POC
 podcasters
 pogo
-poject
 PokéAPI
 Pokémon
 polyfill
@@ -1941,7 +1939,7 @@ trainings
 transactional
 transformational
 transformative
-transifex
+Transifex
 TransitionLink
 TransitionPortal
 TransitionState
@@ -1965,6 +1963,8 @@ Tumblr
 turndown
 tweetstorm
 Twilio
+*twitter
+Twitter
 TXT
 typeBuilder
 typecheck

docs/blog/2018-06-16-announcing-gatsby-v2-beta-launch/index.md

@@ -54,4 +54,4 @@ The [v2 roadmap](https://github.com/gatsbyjs/gatsby/projects/2) details everythi
 
 We ❤️ your feedback. Try out the [migration guide](/docs/migrating-from-v1-to-v2/) and let us know how you get on. [Issues](https://github.com/gatsbyjs/gatsby/issues) and [pull requests](https://github.com/gatsbyjs/gatsby/pulls) are welcome (for real).
 
-Finally a big thank you to all of [Gatsby's contributors](https://github.com/gatsbyjs/gatsby/graphs/contributors) for their time and effort on every version of Gatsby. Special thanks in particular to everyone who's helped with v2 so far: [@ajayns](https://github.com/ajayns) [@brizzoli](https://github.com/brizzoli) [@calcsam](https://github.com/calcsam) [@CanRau](https://github.com/CanRau) [@chmac](https://github.com/chmac) [@danielfarrell](https://github.com/danielfarrell) [@davidluhr](https://github.com/davidluhr) [@daydream05](https://github.com/daydream05) [@dennari](https://github.com/dennari) [@Drew-Slagter](https://github.com/Drew-Slagter) [@dvonlehman](https://github.com/dvonlehman) [@flipactual](https://github.com/flipactual) [@hsribei](https://github.com/hsribei) [@jlengstorf](https://github.com/jlengstorf) [@jquense](https://github.com/jquense) [@Khaledgarbaya](https://github.com/Khaledgarbaya) [@kkemple](https://github.com/kkemple) [@kripod](https://github.com/kripod) [@KyleAMathews](https://github.com/KyleAMathews) [@LeKoArts](https://github.com/LeKoArts) [@lettertwo](https://github.com/lettertwo) [@m-allanson](https://github.com/m-allanson) [@mathieudutour](https://github.com/mathieudutour) [@mottox2](https://github.com/mottox2) [@mquandalle](https://github.com/mquandalle) [@nihgwu](https://github.com/nihgwu) [@noelebrun](https://github.com/noelebrun) [@pieh](https://github.com/pieh) [@piotrkwiecinski](https://github.com/piotrkwiecinski) [@resir014](https://github.com/resir014) [@ryanditjia](https://github.com/ryanditjia) [@syndia](https://github.com/syndia) [@ThatOtherPerson](https://github.com/ThatOtherPerson) [@thebigredgeek](https://github.com/thebigredgeek) [@thescientist13](https://github.com/thescientist13) [@tsriram](https://github.com/tsriram)
+Finally a big thank you to all of [Gatsby's contributors](https://github.com/gatsbyjs/gatsby/graphs/contributors) for their time and effort on every version of Gatsby. Special thanks in particular to everyone who's helped with v2 so far: [@ajayns](https://github.com/ajayns) [@brizzoli](https://github.com/brizzoli) [@calcsam](https://github.com/calcsam) [@CanRau](https://github.com/CanRau) [@chmac](https://github.com/chmac) [@danielfarrell](https://github.com/danielfarrell) [@davidluhr](https://github.com/davidluhr) [@daydream05](https://github.com/daydream05) [@dennari](https://github.com/dennari) [@Drew-Slagter](https://github.com/Drew-Slagter) [@dvonlehman](https://github.com/dvonlehman) [@flipactual](https://github.com/flipactual) [@hsribei](https://github.com/hsribei) [@jlengstorf](https://github.com/jlengstorf) [@jquense](https://github.com/jquense) [@Khaledgarbaya](https://github.com/Khaledgarbaya) [@kkemple](https://github.com/kkemple) [@kripod](https://github.com/kripod) [@KyleAMathews](https://github.com/KyleAMathews) [@LekoArts](https://github.com/LekoArts) [@lettertwo](https://github.com/lettertwo) [@m-allanson](https://github.com/m-allanson) [@mathieudutour](https://github.com/mathieudutour) [@mottox2](https://github.com/mottox2) [@mquandalle](https://github.com/mquandalle) [@nihgwu](https://github.com/nihgwu) [@noelebrun](https://github.com/noelebrun) [@pieh](https://github.com/pieh) [@piotrkwiecinski](https://github.com/piotrkwiecinski) [@resir014](https://github.com/resir014) [@ryanditjia](https://github.com/ryanditjia) [@syndia](https://github.com/syndia) [@ThatOtherPerson](https://github.com/ThatOtherPerson) [@thebigredgeek](https://github.com/thebigredgeek) [@thescientist13](https://github.com/thescientist13) [@tsriram](https://github.com/tsriram)

docs/blog/2019-09-26-announcing-gatsby-15m-series-a-funding-round/index.md

@@ -18,7 +18,7 @@ With Gatsby, we’re reinventing website technology so people can create sites t
 
 Gatsby strips away much of the complexity that plagues website development. Teams tell us that they can build stunning sites 3-5x faster with Gatsby—and have a lot more fun in the process.
 
-The web is an incredible medium. Anyone, anywhere can produce a site and ship their ideas to the world. [Individuals, teams, and organizations are turning to Gatsby to create websites and apps that stand out](https://www.gatsbyjs.org/blog/tags/case-studies)[.](https://www.gatsbyjs.org/blog/tags/case-studies)
+The web is an incredible medium. Anyone, anywhere can produce a site and ship their ideas to the world. [Individuals, teams, and organizations are turning to Gatsby to create websites and apps that stand out.](https://www.gatsbyjs.org/blog/tags/case-studies)
 
 ## From the CMS to the content mesh
 

docs/blog/2020-07-08-blog-2.0/index.md

@@ -54,7 +54,7 @@ What's even better is that images can be relative paths to files in your project
 
 ### Improved SEO
 
-And what about getting that amazing social sharing image to make your post pop on twitter or LinkedIn? You're good to go! Your featured image is automatically used for social sharing. And if you'd rather use a different image, for dimension reasons or otherwise, `socialImage` is available in your frontmatter as well.
+And what about getting that amazing social sharing image to make your post pop on Twitter or LinkedIn? You're good to go! Your featured image is automatically used for social sharing. And if you'd rather use a different image, for dimension reasons or otherwise, `socialImage` is available in your frontmatter as well.
 
 Don't have an image for this post? That's ok! The theme will revert to a social sharing card that doesn't leave a big file avatar.
 

docs/blog/2020-07-13-i18n-pain-points/index.md

@@ -44,7 +44,7 @@ This is a non-exhaustive list of issues I most commonly read and heard. Feel fre
 
 9. **Right-to-left support has to be added manually.** Adapting the styles has currently no happy path.
 
-10. **Difficult to integrate SaaS localization platforms.** There are not many plugins that deal with localization platforms such as Crowdin and transifex, meaning you have to handle the integration yourself. This can be difficult.
+10. **Difficult to integrate SaaS localization platforms.** There are not many plugins that deal with localization platforms such as Crowdin and Transifex, meaning you have to handle the integration yourself. This can be difficult.
 
 ## What this means for future development
 
@@ -56,6 +56,6 @@ Most importantly the great variety of responses received thus far showed that ou
 
 ## What's next?
 
-The alpha of gatsby-theme-i18n and its child themes will be released very soon. Until then (and in the future, as well) you can join the [Discord channel](https://discord.gg/cQ2MPUz) to chat as more details on how to contribute will follow. Also, keep an eye out for the announcement post.
+The alpha of `gatsby-theme-i18n` and its child themes will be released very soon. Until then (and in the future, as well) you can join the [Discord channel](https://discord.gg/cQ2MPUz) to chat as more details on how to contribute will follow. Also, keep an eye out for the announcement post.
 
 I encourage all interested parties to try out the theme when it's ready and get involved in the process of refining it. And then show us the awesome things you build!

docs/blog/2020-07-20-Khaled-Garbaya-Life-After-Recipes/index.md

@@ -2,7 +2,7 @@
 title: "Life Before and After Gatsby Recipes"
 date: 2020-07-20
 author: Khaled Garbaya
-excerpt: "Recipes are designed to make life as a Gatsby developer even easier. Here's the receipts: Let's take a look at how setting up a Contentful blog with TailwindCSS on Gatsby goes from seven steps to just one, thanks to Recipes."
+excerpt: "Recipes are designed to make life as a Gatsby developer even easier, and Khaled Garbaya shows exactly how much. He walks through setting up a Contentful blog with TailwindCSS before and after Gatsby Recipes -- taking us from seven steps to just one."
 tags:
   - gatsby-recipes
   - mdx
@@ -18,7 +18,7 @@ Instead, wouldn't it be nice if you could make the setup instructions more inter
 
 Enter: Gatsby Recipes
 
-Gatsby Recipes [launched just recently](/blog/2020-04-15-announcing-gatsby-recipes/) to help automate everyday tasks like creating pages and layouts, installing and setting up plugins, adding a blog to a site, setting up Typescript, and many more routine tasks. With the release of this new feature, which is run from the CLI, Gatsby has created [25+ official recipes](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-recipes/recipes)that you can explore, including Theme UI, Sass, Cypress, animated page transitions, and persistent layout components. And since then, because they are so useful but also fun and easy to create, the community has also been busy contributing all kinds of other useful Recipes.
+Gatsby Recipes [launched just recently](/blog/2020-04-15-announcing-gatsby-recipes/) to help automate everyday tasks like creating pages and layouts, installing and setting up plugins, adding a blog to a site, setting up Typescript, and many more routine tasks. With the release of this new feature, which is run from the CLI, Gatsby has created [25+ official recipes](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-recipes/recipes) that you can explore, including Theme UI, Sass, Cypress, animated page transitions, and persistent layout components. And since then, because they are so useful but also fun and easy to create, the community has also been busy contributing all kinds of other useful Recipes.
 
 ## Gatsby, Before Recipes: A long and winding workflow
 
@@ -79,7 +79,7 @@ module.exports = {
 
 7. Get the credentials from your Contentful space, and add the plugin in your `gatsby-config.js` file. (Excellent [guidance for setting up Contentful + Gatsby](https://www.gatsbyjs.com/guides/contentful/) is already detailed in the Gatsby docs, so we won't go into that here).
 
-8. _Just kidding, there is no step eight. Seven steps is enough!_ I don't know about you, but there is no way I manage to get through this process each time without making a typo somewhere or forgetting one of the steps. I even forgot one small step when first typing out the above list, which is importing the tailwind.css file into your layout file.
+8. _Just kidding, there is no step eight. Seven steps is enough!_ I don't know about you, but there is no way I manage to get through this process each time without making a typo somewhere or forgetting one of the steps. I even forgot one small step when first typing out the above list, which is importing the `tailwind.css` file into your layout file.
 
 There are a few ways we could possibly avoid doing this manual process. One would be to create a boilerplate or a starter project and clone it with each new project. Unfortunately this then creates its own set of problems: first, it's a chore keeping starters up to date. Also, they only work well with fresh new projects. Even when they do work, starters can be very opinionated and force you to use extra stuff that you don't need.
 
@@ -93,7 +93,7 @@ Don't get me wrong -- starters are amazing. But they try to do too many jobs, se
 
 ## Gatsby, After Recipes: Three little words
 
-All those steps we just went through above? (Well, the ones we remembered, anyway). Now that Recipes are here, all that setup can be replaced with three little words: `gatsby recipe contentful`.
+All those steps we just went through above? (Well, the ones we remembered, anyway). Now that Recipes are here, all that setup can be replaced with three little words: `gatsby recipe tailwind`.
 
 https://twitter.com/kylemathews/status/1256258010717941760
 

docs/docs/add-seo-component.md

@@ -215,6 +215,6 @@ const query = graphql`
 You could also put the Facebook and Twitter meta-tags into their own components, add custom favicons you placed in your `static` folder, and add [schema.org](https://schema.org/) data (Google will use that for their [Structured Data](https://developers.google.com/search/docs/guides/intro-structured-data)). To see how that works you can have a look at these two examples:
 
 - [marisamorby.com](https://github.com/marisamorby/marisamorby.com/blob/master/packages/gatsby-theme-blog-sanity/src/components/seo.js)
-- [gatsby-starter-prismic](https://github.com/LeKoArts/gatsby-starter-prismic/blob/master/src/components/SEO/SEO.jsx)
+- [gatsby-starter-prismic](https://github.com/LekoArts/gatsby-starter-prismic/blob/master/src/components/SEO/SEO.jsx)
 
 As mentioned at the beginning you are also able to use the component in templates, like in [this example](https://github.com/jlengstorf/marisamorby.com/blob/6e86f845185f9650ff95316d3475bb8ac86b15bf/src/templates/post.js#L12-L18).

docs/docs/graphql-concepts.md

@@ -380,6 +380,6 @@ export const query = graphql`
 
 ### Advanced readings on GraphQL
 
-- [GraphQL specification](https://facebook.github.io/graphql/October2016/)
+- [GraphQL specification](https://spec.graphql.org/October2016/)
 - [Interfaces and Unions](https://medium.com/the-graphqlhub/graphql-tour-interfaces-and-unions-7dd5be35de0d)
 - [Relay Compiler (which Gatsby uses to process queries)](https://facebook.github.io/relay/docs/en/compiler-architecture.html)

docs/docs/overview-of-the-gatsby-build-process.md

@@ -155,7 +155,7 @@ A [cache](/docs/glossary#cache) is also used to detect changes to `gatsby-*.js`
 
 ## What happens when you run `gatsby build`?
 
-To see the code where many of these processes are happening, refer to the code and comments in the [`build`](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/src/commands/build.ts) and [`bootstrap`](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/src/bootstrap/index.js) files of the repository.
+To see the code where many of these processes are happening, refer to the code and comments in the [`build`](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/src/commands/build.ts) and [`bootstrap`](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/src/bootstrap/index.ts) files of the repository.
 
 A Node.js server process powers things behind the scenes when you run the `gatsby build` command. The process of converting assets and pages into HTML that can be rendered in a browser by a [server-side](/docs/glossary#server-side) language like Node.js is referred to as server-side rendering, or SSR. Since Gatsby builds everything ahead of time, this creates an entire site with all of the data your pages need at once. When the site is deployed, it doesn't need to run with server-side processes because everything has been gathered up and compiled by Gatsby.
 

docs/docs/sourcing-from-prismic.md

@@ -225,6 +225,6 @@ This was an example meant to help you understand how Prismic works with Gatsby.
 - Add relationships between posts, e.g. with categories
 - Query data from Prismic for single pages
 
-As mentioned in the beginning of this guide, if you got stuck, you can compare your code to the [gatsby-starter-prismic](https://github.com/LeKoArts/gatsby-starter-prismic) which is the project set up in the videos. A working example created by following this guide is available in the [commit history](https://github.com/LeKoArts/gatsby-starter-prismic/tree/4aa5d52e79a0b4d90f0a671c24eb8289eb15a42b) of the aforementioned starter. More advanced usages of Prismic in Gatsby would be [Slices](https://intercom.help/prismicio/content-modeling-and-custom-types/field-reference/slices) and [Labels](https://intercom.help/prismicio/content-modeling-and-custom-types/structure-your-content/add-custom-styles-to-rich-text).
+As mentioned in the beginning of this guide, if you got stuck, you can compare your code to the [gatsby-starter-prismic](https://github.com/LekoArts/gatsby-starter-prismic) which is the project set up in the videos. A working example created by following this guide is available in the [commit history](https://github.com/LekoArts/gatsby-starter-prismic/tree/4aa5d52e79a0b4d90f0a671c24eb8289eb15a42b) of the aforementioned starter. More advanced usages of Prismic in Gatsby would be [Slices](https://intercom.help/prismicio/content-modeling-and-custom-types/field-reference/slices) and [Labels](https://intercom.help/prismicio/content-modeling-and-custom-types/structure-your-content/add-custom-styles-to-rich-text).
 
 <!-- Links to more advanced tutorials will go here -->

docs/docs/tailwind-css.md

@@ -143,7 +143,7 @@ plugins: [
 **Note:** Optionally you can add a corresponding configuration file (by default it will be `tailwind.config.js`).
 If you are adding a custom configuration, you will need to load it after `tailwindcss`.
 
-### 4. Add custom CSS/SCSS files
+### 3. Add custom CSS/SCSS files
 
 **Note**: This approach is not needed if you chose CSS-in-JS above, as you can already nest styles and `@apply` rules directly from your `.js` files.
 
@@ -181,7 +181,7 @@ In `gatsby-browser.js` add an import rule for your Tailwind directives and custo
 import "./src/css/index.css"
 ```
 
-### 5. Purging your CSS
+### 4. Purging your CSS
 
 Now we've fully configured Tailwind CSS, we want to make sure that only the classes we need are delivered to the browser. By default, Tailwind is a very large library because it includes every combination of every class you might think of. Most of these you won't need, so we use PurgeCSS to remove any unused classes.
 

docs/tutorial/part-six/index.md

@@ -70,11 +70,11 @@ module.exports = {
 
 Restart the development server then refresh (or open again) GraphiQL and look at the autocomplete:
 
-![markdown-autocomplete](markdown-autocomplete.png)
+![GraphiQL screenshot showing new `gatsby-transformer-remark` autocomplete options](markdown-autocomplete.png)
 
 Select `allMarkdownRemark` again and run it as you did for `allFile`. You'll see there the markdown file you recently added. Explore the fields that are available on the `MarkdownRemark` node.
 
-![markdown-query](markdown-query.png)
+![GraphiQL screenshot showing the result of a query](markdown-query.png)
 
 Ok! Hopefully, some basics are starting to fall into place. Source plugins bring data _into_ Gatsby's data system and _transformer_ plugins transform raw content brought by source plugins. This pattern can handle all data sourcing and data transformation you might need when building a Gatsby site.
 
@@ -150,7 +150,7 @@ export const query = graphql`
 
 Now the frontpage should look like:
 
-![frontpage](frontpage.png)
+![Screenshot of the frontpage](frontpage.png)
 
 But your one blog post looks a bit lonely. So let's add another one at `src/pages/pandas-and-bananas.md`
 
@@ -165,7 +165,7 @@ Do Pandas eat bananas? Check out this short video that shows that yes! pandas do
 <iframe width="560" height="315" src="https://www.youtube.com/embed/4SZl1r2O_bY" frameborder="0" allowfullscreen></iframe>
 ```
 
-![two-posts](two-posts.png)
+![Frontpage showing two posts](two-posts.png)
 
 Which looks great! Except… the order of the posts is wrong.
 

examples/using-MDX/package.json

@@ -5,7 +5,7 @@
   "version": "0.1.0",
   "author": "Kyle Mathews <mathews.kyle@gmail.com>",
   "dependencies": {
-    "@mdx-js/mdx": "^1.6.6",
+    "@mdx-js/mdx": "^1.6.11",
     "@mdx-js/react": "^1.6.6",
     "gatsby": "^2.23.12",
     "gatsby-image": "^2.4.9",
@@ -18,7 +18,8 @@
     "gatsby-transformer-sharp": "^2.5.7",
     "prop-types": "^15.7.2",
     "react": "^16.12.0",
-    "react-charts": "^2.0.1",
+    "react-charts": "^2.0.0-beta.7",
+    "react-chat-elements": "^10.9.2",
     "react-dom": "^16.12.0",
     "react-helmet": "^5.2.1"
   },

examples/using-video/src/pages/index.js

@@ -9,6 +9,6 @@ export default () => (
     <source src={DogVideo} type="video/mp4" />
     <track kind="transcript" srcLang="en" src={Transcript} />
     <track kind="captions" srcLang="en" src={Captions} />
-    <track kind="descriptions" srcLang="en" src={Description} />
+    <track kind="description" srcLang="en" src={Description} />
   </video>
 )