chore: fix spelling, grammar, links, whitespace and end of files (#30063

)
gatsbyjs · Mar 8, 2021 · 542d945 · 542d945
1 parent 28956fe
commit 542d945
Show file tree

Hide file tree

Showing 10 changed files with 20 additions and 21 deletions.
diff --git a/README.md b/README.md
@@ -61,7 +61,7 @@
 Gatsby is a modern web framework for blazing fast websites.
 
 - **Go Beyond Static Websites.** Get all the benefits of static websites with none of the
-  limitations. Gatsby sites are fully functional React apps so you can create high-quality,
+  limitations. Gatsby sites are fully functional React apps, so you can create high-quality,
   dynamic web apps, from blogs to e-commerce sites to user dashboards.
 
 - **Use a Modern Stack for Every Site.** No matter where the data comes from, Gatsby sites are
@@ -76,7 +76,7 @@ Gatsby is a modern web framework for blazing fast websites.
   splitting, image optimization, inlining critical styles, lazy-loading, prefetching resources,
   and more to ensure your site is fast — no manual tuning required.
 
-- **Host at Scale for Pennies.** Gatsby sites don’t require servers so you can host your entire
+- **Host at Scale for Pennies.** Gatsby sites don’t require servers, so you can host your entire
   site on a CDN for a fraction of the cost of a server-rendered site. Many Gatsby sites can be
   hosted entirely free on [Gatsby Cloud](https://www.gatsbyjs.com/cloud/) and other similar services.
 
@@ -99,7 +99,6 @@ You can get a new Gatsby site up and running on your local dev environment in 5
 
    ```shell
    npm install -g gatsby-cli
-
    ```
 
 2. **Create a Gatsby site from a Gatsby starter.**

diff --git a/examples/ecommerce-tutorial-with-stripe/netlify.toml b/examples/ecommerce-tutorial-with-stripe/netlify.toml
@@ -1,11 +1,11 @@
-# Settings in the [build] context are global and are applied to all contexts 
-# unless otherwise overridden by more specific contexts.  
+# Settings in the [build] context are global and are applied to all contexts
+# unless otherwise overridden by more specific contexts.
 [build]
-  # Directory to change to before starting a build. 
+  # Directory to change to before starting a build.
   # This is where we will look for package.json/.nvmrc/etc.
   base = "/"
 
-  # Directory (relative to root of your repo) that contains the deploy-ready 
+  # Directory (relative to root of your repo) that contains the deploy-ready
   # HTML files and assets generated by the build. If a base directory has
   # been specified, include it in the publish directory path.
   publish = "public/"
@@ -16,4 +16,4 @@
 [template.environment]
   GATSBY_STRIPE_PUBLISHABLE_KEY = "Add your Stripe publishable key here: pk_test_xxx"
   GATSBY_BUTTON_PRICE_ID = "The price id for the one-time purchase product: price_xxx"
-  STRIPE_SECRET_KEY = "Add your Stripe secret key here: sk_test_xxx"
+  STRIPE_SECRET_KEY = "Add your Stripe secret key here: sk_test_xxx"
diff --git a/examples/recipes-gatsby-image/src/pages/examples/fixed-max-width.js b/examples/recipes-gatsby-image/src/pages/examples/fixed-max-width.js
@@ -7,7 +7,7 @@ import Layout from "../../components/layout"
 /*
   1. write a query for sourced images
   2. be sure to query for the fixed field
-  3. adad a style prop to the Img component 
+  3. add a style prop to the Img component
 */
 
 export default () => {

diff --git a/examples/recipes-gatsby-image/src/pages/examples/inline-styles.js b/examples/recipes-gatsby-image/src/pages/examples/inline-styles.js
@@ -5,7 +5,7 @@ import Img from "gatsby-image"
 import Layout from "../../components/layout"
 
 /*
-  1. write query 
+  1. write query
   2. pass data into img component
 */
 

diff --git a/examples/recipes-gatsby-image/src/pages/examples/relative-path.js b/examples/recipes-gatsby-image/src/pages/examples/relative-path.js
@@ -5,7 +5,7 @@ import Img from "gatsby-image"
 import Layout from "../../components/layout"
 
 /*
-  1. write query 
+  1. write query
   2. pass data into img component
 */
 

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
@@ -30,9 +30,9 @@ The examples on this page cover the basic Markdown syntax and are adapted from
 ---
 
 This is intended as a quick reference and showcase. For more complete info, see
-[John Gruber's original spec](http://daringfireball.net/projects/markdown/) and
+[John Gruber's original spec](https://daringfireball.net/projects/markdown/) and
 the
-[GitHub-flavored Markdown info page](http://github.github.com/github-flavored-markdown/).
+[GitHub-flavored Markdown info page](https://github.github.com/github-flavored-markdown/).
 
 ##### Table of Contents
 
@@ -173,8 +173,8 @@ example.com (but not on GitHub, for example).
 Some text to show that the reference links can follow later.
 
 [arbitrary case-insensitive reference text]: https://www.mozilla.org
-[1]: http://slashdot.org
-[link text itself]: http://www.reddit.com
+[1]: https://slashdot.org
+[link text itself]: https://www.reddit.com
 ```
 
 [I'm an inline-style link](https://www.google.com)

diff --git a/packages/gatsby-cli/src/handlers/plugin.ts b/packages/gatsby-cli/src/handlers/plugin.ts
@@ -11,7 +11,7 @@ export default async (root: string, cmd: string | undefined): Promise<void> => {
         - What You Don't Need Plugins For (https://www.gatsbyjs.com/docs/what-you-dont-need-plugins-for/)
         - Loading Plugins from Your Local Plugins Folder (https://www.gatsbyjs.com/docs/loading-plugins-from-your-local-plugins-folder/)
         - Plugin Library (https://www.gatsbyjs.com/plugins/)
-  
+
         Creating a plugin:
         - Naming a Plugin (https://www.gatsbyjs.com/docs/naming-a-plugin/)
         - Files Gatsby Looks for in a Plugin (https://www.gatsbyjs.com/docs/files-gatsby-looks-for-in-a-plugin/)

diff --git a/packages/gatsby-source-contentful/src/extend-node-type.js b/packages/gatsby-source-contentful/src/extend-node-type.js
@@ -788,7 +788,7 @@ exports.extendNodeType = ({ type, store }) => {
             The image formats to generate. Valid values are AUTO (meaning the same format as the source image), JPG, PNG, and WEBP.
             The default value is [AUTO, WEBP], and you should rarely need to change this. Take care if you specify JPG or PNG when you do
             not know the formats of the source images, as this could lead to unwanted results such as converting JPEGs to PNGs. Specifying
-            both PNG and JPG is not supported and will be ignored. 
+            both PNG and JPG is not supported and will be ignored.
         `,
         defaultValue: [``, `webp`],
       },

diff --git a/packages/gatsby-transformer-documentationjs/src/__tests__/fixtures/complex-example.js b/packages/gatsby-transformer-documentationjs/src/__tests__/fixtures/complex-example.js
@@ -27,9 +27,9 @@ exports.complex = {
     ready: new Promise(),
     nested: {
       foo: `bar`,
-      callback: message => { 
+      callback: message => {
         return message.split(`,`)
       }
     }
   }
-}
+}
diff --git a/packages/gatsby-transformer-screenshot/README.md b/packages/gatsby-transformer-screenshot/README.md
@@ -7,7 +7,7 @@ property, and creates `Screenshot` child nodes with a `screenshotFile` field.
 [Live demo](https://thatotherperson.github.io/gatsby-screenshot-demo/)
 ([source](https://github.com/ThatOtherPerson/gatsby-screenshot-demo))
 
-Data should be in a yaml file named `sites.yml` and look like:
+Data should be in a YAML file named `sites.yml` and look like:
 
 ```yaml
 - url: https://reactjs.org/
@@ -31,7 +31,7 @@ module.exports = {
 }
 ```
 
-By default, the plugin will target nodes sourced from a yaml file named `sites.yml`.
+By default, the plugin will target nodes sourced from a YAML file named `sites.yml`.
 
 To source additional node types, supply an array of the types to a `nodeTypes` option on the plugin.