chore(docs): Fix case of Gatsby, Strapi, Bootstrap and WordPress (#19626

)

docs/blog/2017-10-01-migrating-my-blog-from-hexo-to-gatsby/index.md

@@ -82,7 +82,7 @@ are many ways you could do this but I'll go over what I did.
 To get all the Gatsby files you can use the Gatsby CLI.
 
 ```yaml
-gatsby new temp-gatsby-files # Initialize gatsby in a temp directory
+gatsby new temp-gatsby-files # Initialize Gatsby in a temp directory
 cp -R temp-gatsby-files/* ./ # Copy all the files into your root directory
 rm -rf temp-gatsby-files     # Remove the temp directory
 ```

docs/docs/creating-a-source-plugin.md

@@ -4,7 +4,7 @@ title: Creating a Source Plugin
 
 Source plugins are essentially out of the box integrations between Gatsby and various third-party systems.
 
-These systems can be CMSs like Contentful or Wordpress, other cloud services like Lever and Strava, or your local filesystem -- literally anything that has an API. Currently, Gatsby has [over 300 source plugins](/plugins/?=gatsby-source).
+These systems can be CMSs like Contentful or WordPress, other cloud services like Lever and Strava, or your local filesystem -- literally anything that has an API. Currently, Gatsby has [over 300 source plugins](/plugins/?=gatsby-source).
 
 Once a source plugin brings data into Gatsby's system, it can be transformed further with **transformer plugins**.
 

docs/docs/themes/conventions.md

@@ -7,7 +7,7 @@ As methodologies for building Gatsby Themes begin to formalize and standardize,
 ## Naming
 
 It's required to prefix themes with `gatsby-theme-`. So if you'd like to name your theme "awesome" you
-can name it `gatsby-theme-awesome` and place that as the `name` key in your `package.json`. Prefixing themes with `gatsby-theme` enables gatsby in identifying theme packages for compilation.
+can name it `gatsby-theme-awesome` and place that as the `name` key in your `package.json`. Prefixing themes with `gatsby-theme` enables Gatsby in identifying theme packages for compilation.
 
 ## Initializing required directories
 

docs/starters.yml

@@ -1864,7 +1864,7 @@
     - Web app manifest
 - url: https://gatsby.magicsoup.io/
   repo: https://github.com/magicsoup-io/gatsby-starter-magicsoup
-  description: A production ready gatsby starter using magicsoup.io
+  description: A production ready Gatsby starter using magicsoup.io
   tags:
     - SEO
     - Markdown
@@ -2086,7 +2086,7 @@
     - Typings for scss files are automatically generated
     - Responsiveness from the beginning through easy breakpoint configuration
     - Enforce the DRY principle, no hardcoded and repeated `margin`, `font-size`, `color`, `box-shadow`, `border-radius` ... properties anymore
-    - Docker ready - you can run gatsby dev mode on your machine environment or with docker-compose
+    - Docker ready - you can run Gatsby dev mode on your machine environment or with docker-compose
 - url: https://prismic-i18n.lekoarts.de/
   repo: https://github.com/LekoArts/gatsby-starter-prismic-i18n
   description: Based on gatsby-starter-prismic with Internationalization (i18n) support.
@@ -2506,7 +2506,7 @@
     - Benefits section
     - Email signup form
     - Easily configurable
-    - Includes standard gatsby starter features
+    - Includes standard Gatsby starter features
 - url: https://anubhavsrivastava.github.io/gatsby-starter-aerial
   repo: https://github.com/anubhavsrivastava/gatsby-starter-aerial
   description: Single page starter based on the Aerial site template by HTML5 up, suitable for one page personal page.
@@ -3002,7 +3002,7 @@
     - Minimal
 - url: https://gatsby-typescript-starter-default.netlify.com/
   repo: https://github.com/RobertoMSousa/gatsby-typescript-starter-default
-  description: Simple gatsby starter using TypeScript and eslint instead of outdated tslint.
+  description: Simple Gatsby starter using TypeScript and eslint instead of outdated tslint.
   tags:
     - Language:TypeScript
     - SEO
@@ -3388,7 +3388,7 @@
     - Eslint and Stylelint to enforce code style
 - url: http://demo.nagui.me
   repo: https://github.com/kimnagui/gatsby-starter-nagui
-  description: A gatsby starter that full responsive blog.
+  description: A Gatsby starter that full responsive blog.
   tags:
     - Blog
     - AWS
@@ -3581,7 +3581,7 @@
     - CSS based sidebar
     - CSS based Modals
     - Content is fetched from JSON Files
-    - Only one extra plugin from default gatsby starter
+    - Only one extra plugin from default Gatsby starter
 - url: https://gatsby-starter-profile-site.netlify.com/
   repo: https://github.com/Mr404Found/gatsby-starter-profile-site
   description: A minimal and clean starter build with gatsby.
@@ -4265,7 +4265,7 @@
     - Google Analytics
 - url: https://gatsby-typescript-storybook-starter.netlify.com/
   repo: https://github.com/RobertoMSousa/gatsby-typescript-storybook-starter
-  description: A gatsby starter with storybook, tags and eslint
+  description: A Gatsby starter with storybook, tags and eslint
   tags:
     - Language:TypeScript
     - Styling:CSS-in-JS
@@ -4333,7 +4333,7 @@
     - Husky & lint-staged to automate checking
 - url: https://gatsby-strapi-starter.netlify.com/
   repo: https://github.com/jeremylynch/gatsby-strapi-starter
-  description: Get started with strapi, bootstrap (reactstrap) and gatsby FAST!
+  description: Get started with Strapi, Bootstrap (reactstrap) and Gatsby FAST!
   tags:
     - CMS:Strapi
     - Styling:Bootstrap

packages/gatsby-plugin-catch-links/src/__tests__/catch-links.js

@@ -257,7 +257,7 @@ describe(`anchor target attribute looks like _self if`, () => {
   })
 })
 
-describe(`navigation is routed through gatsby if the destination href`, () => {
+describe(`navigation is routed through Gatsby if the destination href`, () => {
   // We're going to manually set up the event listener here
   let hrefHandler
   let eventDestroyer

packages/gatsby/src/bootstrap/load-themes/index.js

@@ -27,7 +27,7 @@ const resolveTheme = async (
     // local themes nested in other themes is potential source of problems:
     // because those are not hosted by npm, there is potential for multiple
     // local themes with same name that do different things and name being
-    // main identifier that gatsby uses right now, it's safer not to support it for now.
+    // main identifier that Gatsby uses right now, it's safer not to support it for now.
     if (isMainConfig) {
       pathToLocalTheme = path.join(path.resolve(`.`), `plugins`, themeName)
       // is a local plugin OR it doesn't exist
@@ -81,7 +81,7 @@ const processTheme = (
   const themesList = useLegacyThemes
     ? themeConfig && themeConfig.__experimentalThemes
     : themeConfig && themeConfig.plugins
-  // gatsby themes don't have to specify a gatsby-config.js (they might only use gatsby-node, etc)
+  // Gatsby themes don't have to specify a gatsby-config.js (they might only use gatsby-node, etc)
   // in this case they're technically plugins, but we should support it anyway
   // because we can't guarantee which files theme creators create first
   if (themeConfig && themesList) {