Fix typos (#2345)

gatsbyjs · Oct 5, 2017 · 916809c · 916809c
1 parent 75a6d5f
commit 916809c
Show file tree

Hide file tree

Showing 14 changed files with 16 additions and 16 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -607,7 +607,7 @@ markdown files. This will be getting an overhaul soon.
 
 ## [1.0.0-alpha3] - 2016-10-05
 ### Added
-- Introduce way to programatically add components to `<head>` + API to take over SSR rendering [a39c2a5](https://github.com/gatsbyjs/gatsby/commit/a39c2a5)
+- Introduce way to programmatically add components to `<head>` + API to take over SSR rendering [a39c2a5](https://github.com/gatsbyjs/gatsby/commit/a39c2a5)
 - Extract webpack manifest from commons.js so it doesn't change on every
   build improving its cachability
 [0941d33](https://github.com/gatsbyjs/gatsby/commit/0941d33)

diff --git a/docs/blog/2017-07-19-creating-a-blog-with-gatsby/index.md b/docs/blog/2017-07-19-creating-a-blog-with-gatsby/index.md
@@ -243,7 +243,7 @@ The underlying query name `BlogPostByPath` (note: these query names need to be u
 
 `frontmatter`, is of course our data structure we provided at the beginning of our Markdown file. Each key we define there will be available to be injected into the query.
 
-At this point, we have a bunch of plugins installed to load files off of disk, transform Markdown to HTML, and other utilities. We have a single, lonely Markdown file that will be rendered as a blog post. Finally, we have a React template for blog posts, as well as a wired up GraphQL query to query for a blog post and inject the React template with the queried data. Next up: programatically creating the necessary static pages (and injecting the templates) with Gatsby's Node API. Let's get down to it.
+At this point, we have a bunch of plugins installed to load files off of disk, transform Markdown to HTML, and other utilities. We have a single, lonely Markdown file that will be rendered as a blog post. Finally, we have a React template for blog posts, as well as a wired up GraphQL query to query for a blog post and inject the React template with the queried data. Next up: programmatically creating the necessary static pages (and injecting the templates) with Gatsby's Node API. Let's get down to it.
 
 An important note to make at this point is that the GraphQL query takes place at **build** time. The component is injected with the `data` prop that is seeded by the GraphQL query. Unless anything dynamic (e.g. logic in `componentDidMount`, state changes, etc.) occurs, this component will be pure, rendered HTML generated via the React rendering engine, GraphQL, and Gatsby!
 
@@ -304,7 +304,7 @@ We're using GraphQL to get all Markdown nodes and making them available under th
 
 One cool note here is that the `gatsby-plugin-remark` plugin exposes some useful data for us to query with GraphQL, e.g. `excerpt` (a short snippet to display as a preview), `id` (a unique identifier for each post), etc.
 
-We now have our query written, but we haven't yet programatically created the pages (with the `createPage` action creator). Let's do that!
+We now have our query written, but we haven't yet programmatically created the pages (with the `createPage` action creator). Let's do that!
 
 ### Creating the pages
 

diff --git a/docs/blog/gatsbygram-case-study/index.md b/docs/blog/gatsbygram-case-study/index.md
@@ -169,7 +169,7 @@ const slash = require(`slash`)
 
 // Implement the Gatsby API “createPages”. This is
 // called after the Gatsby bootstrap is finished so you have
-// access to any information necessary to programatically
+// access to any information necessary to programmatically
 // create pages.
 exports.createPages = ({ graphql, boundActionCreators }) => {
   const { createPage } = boundActionCreators

diff --git a/docs/docs/building-with-components.md b/docs/docs/building-with-components.md
@@ -69,11 +69,11 @@ export default AboutPage;
 
 ### Page template components
 
-You can programatically create pages using "page template components". All pages are React components but very often these components are fairly simple wrappers around data from files or other sources.
+You can programmatically create pages using "page template components". All pages are React components but very often these components are fairly simple wrappers around data from files or other sources.
 
 `src/templates/post.jsx` is an example of a page component. It queries GraphQL for markdown data and then renders the page using this data.
 
-See [part four](/tutorial/part-four/) of the tutorial for a detailed introduction to programatically creating pages.
+See [part four](/tutorial/part-four/) of the tutorial for a detailed introduction to programmatically creating pages.
 
 Example:
 

diff --git a/docs/docs/creating-and-modifying-pages.md b/docs/docs/creating-and-modifying-pages.md
@@ -2,7 +2,7 @@
 title: "Creating and modifying pages"
 ---
 
-Gatsby makes it easy to programatically control your pages.
+Gatsby makes it easy to programmatically control your pages.
 
 Pages can be created in three ways:
 

diff --git a/docs/tutorial/part-four/index.md b/docs/tutorial/part-four/index.md
@@ -594,7 +594,7 @@ In our index page's query, change `allMarkdownRemark` to `  allMarkdownRemark(so
 
 Try opening Graph*i*QL and playing with different sort options. You can sort the `allFile` connection along with other connections.
 
-## Programatically creating pages from data
+## Programmatically creating pages from data
 
 So this is great! We have a nice index page where we're querying our markdown files. But we don't want to just see excerpts, we want actual pages for our markdown files.
 

diff --git a/examples/gatsbygram/gatsby-node.js b/examples/gatsbygram/gatsby-node.js
@@ -6,7 +6,7 @@ const slash = require(`slash`)
 
 // Implement the Gatsby API “createPages”. This is
 // called after the Gatsby bootstrap is finished so you have
-// access to any information necessary to programatically
+// access to any information necessary to programmatically
 // create pages.
 exports.createPages = ({ graphql, boundActionCreators }) => {
   const { createPage } = boundActionCreators

diff --git a/examples/hn/gatsby-node.js b/examples/hn/gatsby-node.js
@@ -5,7 +5,7 @@ const slash = require(`slash`)
 
 // Implement the Gatsby API “createPages”. This is
 // called after the Gatsby bootstrap is finished so you have
-// access to any information necessary to programatically
+// access to any information necessary to programmatically
 // create pages.
 exports.createPages = ({ graphql, boundActionCreators }) => {
   const { createPage } = boundActionCreators

diff --git a/examples/using-contentful/gatsby-node.js b/examples/using-contentful/gatsby-node.js
@@ -5,7 +5,7 @@ const slash = require(`slash`)
 
 // Implement the Gatsby API “createPages”. This is
 // called after the Gatsby bootstrap is finished so you have
-// access to any information necessary to programatically
+// access to any information necessary to programmatically
 // create pages.
 exports.createPages = ({ graphql, boundActionCreators }) => {
   const { createPage } = boundActionCreators

diff --git a/examples/using-drupal/gatsby-node.js b/examples/using-drupal/gatsby-node.js
@@ -5,7 +5,7 @@ const slash = require(`slash`)
 
 // Implement the Gatsby API “createPages”. This is
 // called after the Gatsby bootstrap is finished so you have
-// access to any information necessary to programatically
+// access to any information necessary to programmatically
 // create pages.
 exports.createPages = ({ graphql, boundActionCreators }) => {
   const { createPage } = boundActionCreators

diff --git a/examples/using-mongodb/gatsby-node.js b/examples/using-mongodb/gatsby-node.js
@@ -5,7 +5,7 @@ const slash = require(`slash`)
 
 // Implement the Gatsby API “createPages”. This is
 // called after the Gatsby bootstrap is finished so you have
-// access to any information necessary to programatically
+// access to any information necessary to programmatically
 // create pages.
 exports.createPages = ({ graphql, boundActionCreators }) => {
   const { createPage } = boundActionCreators

diff --git a/examples/using-wordpress/gatsby-node.js b/examples/using-wordpress/gatsby-node.js
@@ -5,7 +5,7 @@ const slash = require(`slash`)
 
 // Implement the Gatsby API “createPages”. This is
 // called after the Gatsby bootstrap is finished so you have
-// access to any information necessary to programatically
+// access to any information necessary to programmatically
 // create pages.
 // Will create pages for Wordpress pages (route : /{slug})
 // Will create pages for Wordpress posts (route : /post/{slug})

diff --git a/packages/gatsby-source-wordpress/README.md b/packages/gatsby-source-wordpress/README.md
@@ -473,7 +473,7 @@ const slash = require(`slash`)
 
 // Implement the Gatsby API “createPages”. This is
 // called after the Gatsby bootstrap is finished so you have
-// access to any information necessary to programatically
+// access to any information necessary to programmatically
 // create pages.
 // Will create pages for WordPress pages (route : /{slug})
 // Will create pages for WordPress posts (route : /post/{slug})

diff --git a/www/src/pages/docs/tutorial-links.yml b/www/src/pages/docs/tutorial-links.yml
@@ -36,4 +36,4 @@
     ">> Build a page with a GraphQL query": /tutorial/part-four/#build-a-page-with-a-graphql-query
     ">> Transformer Plugins": /tutorial/part-four/#transformer-plugins
     ">> Create a list of our site’s markdown files in src/pages/index.js": /tutorial/part-four/#create-a-list-of-our-sites-markdown-files-in-srcpagesindexjs
-    ">> Programatically creating pages from data": /tutorial/part-four/#programatically-creating-pages-from-data
+    ">> Programmatically creating pages from data": /tutorial/part-four/#programmatically-creating-pages-from-data