From e39d4c2e13a70db2d56058cd1597e1c3e90806ba Mon Sep 17 00:00:00 2001 From: Alex Date: Fri, 19 Oct 2018 03:56:33 +0200 Subject: [PATCH] docs: fix spelling (#9228) Fixed some typos --- .../2018-09-25-announcing-graphql-stitching-support/index.md | 2 +- docs/docs/adding-tags-and-categories-to-blog-posts.md | 2 +- docs/docs/api-specification.md | 4 ++-- docs/docs/centralizing-your-sites-navigation.md | 2 +- docs/docs/static-vs-normal-queries.md | 4 ++-- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/blog/2018-09-25-announcing-graphql-stitching-support/index.md b/docs/blog/2018-09-25-announcing-graphql-stitching-support/index.md index 833ea09e2c181..3c0b9af28c3c3 100644 --- a/docs/blog/2018-09-25-announcing-graphql-stitching-support/index.md +++ b/docs/blog/2018-09-25-announcing-graphql-stitching-support/index.md @@ -15,7 +15,7 @@ Gatsby v1 shipped last year with a plugin-powered data layer that let you easily But in the last year, a lot has changed. More and more services are shipping with native GraphQL APIs. CMSs like [GraphCMS](https://graphcms.com/), [AppSync](https://aws.amazon.com/appsync/), and [TakeShape](https://www.takeshape.io/) all have launched GraphQL APIs. [Contentful](https://www.contentful.com/) is launching a [native GraphQL API as well soon](https://www.contentful.com/blog/2018/07/04/graphql-abstract-syntax-tree-new-schema/). -Watching the spread of GraphQL has all been incredibly exciting to watch and a fullfillment of our vision for the future of the web where sites easily stitch together data from many sources. +Watching the spread of GraphQL has all been incredibly exciting to watch and a fulfillment of our vision for the future of the web where sites easily stitch together data from many sources. But unfortunately, these new GraphQL APIs have been awkward to use inside Gatsby as you first had to wrap the API inside a Gatsby source plugin before you could query the data from your components. diff --git a/docs/docs/adding-tags-and-categories-to-blog-posts.md b/docs/docs/adding-tags-and-categories-to-blog-posts.md index 3ead189fcb3ec..d4732a2a1a340 100644 --- a/docs/docs/adding-tags-and-categories-to-blog-posts.md +++ b/docs/docs/adding-tags-and-categories-to-blog-posts.md @@ -226,7 +226,7 @@ exports.createPages = ({ actions, graphql }) => { Some notes: -- Our graphql query only looks for data we need to generate these pages. Anything else can be queried again later (and, if you notice, we do this above in the tags template for the post title). +- Our GraphQL query only looks for data we need to generate these pages. Anything else can be queried again later (and, if you notice, we do this above in the tags template for the post title). - While making the tag pages, note that we pass `tag` through in the `context`. This is the value that gets used in the `TagPage` query to limit our search to only posts tagged with the tag in the URL. ## Make a tags index page (`/tags`) that renders a list of all tags diff --git a/docs/docs/api-specification.md b/docs/docs/api-specification.md index 83d1950d33fdf..d62b640014b4c 100644 --- a/docs/docs/api-specification.md +++ b/docs/docs/api-specification.md @@ -56,9 +56,9 @@ See ## Concepts - _Page_ — a site page with a pathname, a template component, and optional - graphql query. + GraphQL query. - _Page Component_ — React.js component that renders a page and can optionally - specify a graphql query + specify a GraphQL query - _Component extensions_ — extensions that are resolvable as components. `.js` and `.jsx` are supported by core. But plugins can add support for other compile-to-js languages. diff --git a/docs/docs/centralizing-your-sites-navigation.md b/docs/docs/centralizing-your-sites-navigation.md index 92f4ae5794365..c111d9838d8fa 100644 --- a/docs/docs/centralizing-your-sites-navigation.md +++ b/docs/docs/centralizing-your-sites-navigation.md @@ -92,7 +92,7 @@ Perfect! You now have a way of obtaining data from the `gatsby-config.js` file. Inside your project, locate the `src/components` folder and navigate to the `layout.js` file. Within this layout component you should notice a component named `StaticQuery`. -StaticQuery is a new component introduced in Gatsby V2, which allows you to run GraphQL queries within your components, not just pages. It allows developers to colocate data with their components. +StaticQuery is a new component introduced in Gatsby V2, which allows you to run GraphQL queries within your components, not just pages. It allows developers to collocate data with their components. Let's extend the query within this component to include the menu links, so it looks like so: diff --git a/docs/docs/static-vs-normal-queries.md b/docs/docs/static-vs-normal-queries.md index bfeedce8c6f7f..fa61accfb30e5 100644 --- a/docs/docs/static-vs-normal-queries.md +++ b/docs/docs/static-vs-normal-queries.md @@ -10,7 +10,7 @@ Static Queries don't need to get run for each page. Just once Started here because they're referenced in page-query-runner:findIdsWithDataDependencies. -The redux `staticQueryComponents` is a map fronm component jsonName to StaticQueryObject. E.g +The redux `staticQueryComponents` is a map from component jsonName to StaticQueryObject. E.g ```javascript { @@ -25,7 +25,7 @@ The redux `staticQueryComponents` is a map fronm component jsonName to StaticQue } ``` -The `staticQueryComponents` redux namespace is owned by the `static-query-components.js` reducer with reacts to `REPLACE_STATIC_QUERY` actinos. +The `staticQueryComponents` redux namespace is owned by the `static-query-components.js` reducer with reacts to `REPLACE_STATIC_QUERY` actions. It is created in query-watcher. TODO: Check other usages