chore(docs): Fix case of WordPress. (#18264)

docs/blog/2017-09-18-gatsby-modern-static-generation/index.md

@@ -41,9 +41,9 @@ backend. The client side JS file that shows the modal dialog has nothing to do
 with the PUG file you wrote and eventually became HTML. The client side logic
 only manipulates directly the DOM.
 
-This architecture is fairly similar to a Wordpress site. A Wordpress engine also
+This architecture is fairly similar to a WordPress site. A WordPress engine also
 generates the HTML and serve it to the browser, after which the client side JS
-you wrote kicks in and starts manipulating the DOM. Wordpress’s responses can be
+you wrote kicks in and starts manipulating the DOM. WordPress’s responses can be
 cached, of course, and served to the client; that setup effectively makes it
 another static site generator with a GUI text editor.
 
@@ -154,7 +154,7 @@ installing dependencies, run:
 
 ## An alternative to HTML caching
 
-Now let’s bring these threads together. Let’s say you have a Wordpress site.
+Now let’s bring these threads together. Let’s say you have a WordPress site.
 You’re caching the content, which is nice for performance, but you’re building
 on it now and want to move to a more modern web development experience.
 
@@ -164,16 +164,16 @@ tired of updating it, ssh-ing to the server, doing migrations and doing other
 ops required by such a stack. (There are paid hosting options, of course, but
 that comes with a different set of problems). So I switched to Gatsby.
 
-Another option, if you want to keep Wordpress' Admin UI is to maintain your
+Another option, if you want to keep WordPress' Admin UI is to maintain your
 content, is to separate the backend from the frontend.
 
 Imagine that instead of having [memcached](https://memcached.org/) caching your
 HTML in front of your WordPress site, you trigger a hook each time your database
 changes that will re-generate the frontend using Gatsby’s
-[Wordpress plugin](/packages/gatsby-source-wordpress/). Yes, Gatsby supports
+[WordPress plugin](/packages/gatsby-source-wordpress/). Yes, Gatsby supports
 multiple backend sources to load your content. Instead of storing them inside
 your version control like me, you can just as well load them from your
-Wordpress's MySQL database.
+WordPress's MySQL database.
 
 To conclude, Gatsby will allow us to:
 

docs/blog/2017-10-05-portfolio-site-gatsby-wordpress/index.md

@@ -76,7 +76,7 @@ GraphQL schema. Here is an example of my Projects page which includes pulling
 some ACF fields which were originally defined in my Projects page template:
 
 ```js
-// Pull the project page content from Wordpress
+// Pull the project page content from WordPress
 export const projectsPageQuery = graphql`
   query projectsPageQuery {
     wordpressPage(slug: { eq: "projects" }) {

docs/blog/2017-12-06-gatsby-plus-contentful-plus-netlify/index.md

@@ -49,7 +49,7 @@ for a quick breakdown on why web development is, for lack of a better phrase,
 “going back to the basics.”
 
 Having dealt with my share of CMS headaches with Joomla in the almost-forgotten
-past, and Wordpress in the more recent years, I’ve been on a quest to simplify
+past, and WordPress in the more recent years, I’ve been on a quest to simplify
 things. I don’t want to worry about having a plugin or theme get hacked or the
 constant nagging to install updates. I also would prefer to not deal with themes
 at all and just have flexible building blocks to shape my site’s appearance via
@@ -83,19 +83,19 @@ Okay, now back to some static hurdles.
 Our site has a lot of content (~300 articles) that needs to be maintained by
 non-developers, my co-workers. This meant we needed an approachable interface
 for copy and content editing. I wanted to make it as convenient as logging into
-Wordpress and publishing from there, without the Wordpress. So the publishing
+WordPress and publishing from there, without the WordPress. So the publishing
 experience couldn’t rely on creating a file and committing changes to a Git
 repo.
 
 > Sidebar: There is
-> [Gatsby-Source-Wordpress](/packages/gatsby-source-wordpress/)
-> plugin that pulls in content via a Wordpress API. However, to me, this was not
+> [Gatsby-Source-WordPress](/packages/gatsby-source-wordpress/)
+> plugin that pulls in content via a WordPress API. However, to me, this was not
 > appealing because I was trying to avoid hosting a traditional CMS entirely.
 
 # Solution: Contentful + Gatsby
 
 Contentful is a hosted [headless CMS](/docs/headless-cms/) with a fantastic user experience. It’s
-similar to having a backend like Wordpress, but you are fully responsible for
+similar to having a backend like WordPress, but you are fully responsible for
 the frontend layer. The beauty of Contentful is threefold.
 
 - Intuitive and attractive UI

docs/blog/2018-01-22-getting-started-gatsby-and-wordpress/index.md

@@ -70,7 +70,7 @@ module.exports = {
     {
       resolve: `gatsby-source-wordpress`,
       options: {
-        // your wordpress source
+        // your WordPress source
         baseUrl: `amberley.me`,
         protocol: `https`,
         // is it hosted on wordpress.com, or self-hosted?

docs/blog/2018-02-09-announcing-gatsby-manor-themes-for-gatsbyjs/index.md

@@ -39,7 +39,7 @@ to over-engineer simple websites. Not to mention that building a development
 environment alone is the biggest requirement when starting from scratch.
 Therefore another option needed to be explored.
 
-[Wordpress](https://wordpress.org/) would be the fastest solution to build a
+[WordPress](https://wordpress.org/) would be the fastest solution to build a
 website but I wanted to be able to rapidly prototype on customs themes.
 Unfortunately, understanding the architecture to develop themes on this stack
 would require additional time. Not to mention I dislike PHP (#sorryNotSorry 😅)

docs/blog/2018-03-07-why-we-created-the-plugin-library/index.md

@@ -38,7 +38,7 @@ Next, we analyzed over 10 admirable and/or popular plugin libraries to draw from
 - [Sketch extension library](https://sketchapp.com/extensions/)
 - [Chrome plugin library](https://chrome.google.com/webstore/detail/plugins/mmcblfncjaclajmegihojiekebofjcen?hl=en)
 - [Microsoft Visual Studio Code Extensions](https://marketplace.visualstudio.com/VSCode)
-- [Wordpress Plugins](https://wordpress.org/plugins/)
+- [WordPress Plugins](https://wordpress.org/plugins/)
 - [Npms.io](https://npms.io/)
 - [Yarnpkg.com](https://yarnpkg.com/en/packages)
 - [Apple App store](https://www.apple.com/ios/app-store/)

docs/blog/2018-03-29-migration-from-wordpress-to-gatsby/index.md

@@ -24,7 +24,7 @@ The results of a [Lighthouse audit](https://www.vojtechruzicka.com/chrome-audit-
 
 ![lighthouse audit before](./chrome-audit-score-before.jpg)
 
-Especially the performance. With such long page load times, many users just leave before the page fully loads. Especially when on mobile and low-quality connections. Another issue is security. With a significant part of web powered by WordPress, it is a target of automated attacks all the time. That means constant fear of losing your precious blog. And its internal database storing all the content was pretty much a black box for me. And of course, there's cost involved. As I didn't want to manage my installation, keep it updated and in good shape, I paid for hosted solution. Last but not least, Wordpress is built with PHP, which I am not familiar with and it is something I am not eager to learn. That means that any customizations or tweaks are out of the question for me.
+Especially the performance. With such long page load times, many users just leave before the page fully loads. Especially when on mobile and low-quality connections. Another issue is security. With a significant part of web powered by WordPress, it is a target of automated attacks all the time. That means constant fear of losing your precious blog. And its internal database storing all the content was pretty much a black box for me. And of course, there's cost involved. As I didn't want to manage my installation, keep it updated and in good shape, I paid for hosted solution. Last but not least, WordPress is built with PHP, which I am not familiar with and it is something I am not eager to learn. That means that any customizations or tweaks are out of the question for me.
 
 Long story short, I decided to get rid of WordPress and replace it with a much more lightweight solution. There was a brief moment where I considered using Medium instead, but I decided I value control of my own content more. After listening to a very inspiring lightning talk by [Ladislav Prskavec](https://twitter.com/abtris/) about JAM Stack, I decided its time to give it a try.
 

docs/blog/2018-07-17-announcing-gatsby-preview/index.md

@@ -25,7 +25,7 @@ With Gatsby Preview, once teams connect their GitHub repositories and CMS to our
 
 While we continue development on this product, we’re releasing it today in an invite-only alpha. To [apply to use the service, fill out this form](https://www.gatsbyjs.com/preview/) and we’ll be in touch. There will be no charge for the service while it’s in alpha.
 
-Over the next few months, we’ll be adding integration with other CMSs like Drupal, Wordpress, and other hosted CMSs like Contentful, as well as moving Preview into general availability.
+Over the next few months, we’ll be adding integration with other CMSs like Drupal, WordPress, and other hosted CMSs like Contentful, as well as moving Preview into general availability.
 
 We’re incredibly excited to launch our first commercial service and to continue to push forward the Gatsby experience! We’re looking forward to meeting more of you and working together to push forward the modern web.
 

docs/blog/2018-1-18-strapi-and-gatsby/index.md

@@ -184,7 +184,7 @@ _Important links from Video:_
 
 #### Create a Content Type
 
-Strapi CMS projects are based on a data structure called Content Types (equivalent to models in frameworks and Content Types in Wordpress).
+Strapi CMS projects are based on a data structure called Content Types (equivalent to models in frameworks and Content Types in WordPress).
 
 [Create a Content Type](http://localhost:1337/admin/plugins/content-type-builder/) named `article` with four fields:
 

docs/blog/2018-10-03-gatsby-perf/index.md

@@ -78,7 +78,7 @@ Gatsby v1 was in many ways an experiment to prove out some meaningful ideas:
 - Static site generation _and_ app-like functionality with React hydration
 - A pluggable and extensible architecture to augment and enhance Gatsby's base feature set and give Gatsby superpowers.
 
-[Pull data from Wordpress at build time][gatsby-source-wordpress]? Sure. [Author your application in TypeScript][gatsby-plugin-typescript]? Seems reasonable. All this while maintaining sane and optimized defaults to truly squeeze every ounce of performance out of your application.
+[Pull data from WordPress at build time][gatsby-source-wordpress]? Sure. [Author your application in TypeScript][gatsby-plugin-typescript]? Seems reasonable. All this while maintaining sane and optimized defaults to truly squeeze every ounce of performance out of your application.
 
 Gatsby v2 set out to build upon this solid foundation, while focusing on improvements in speed and developer experience.
 

docs/blog/2018-10-04-journey-to-the-content-mesh/index.md

@@ -13,7 +13,7 @@ Over time, the feature landscape broadened -- key areas like search, analytics,
 
 ## Modularizing the CMS
 
-Today, a website team running an e-commerce site can store product inventory in [Shopify](https://www.shopify.com/), product listings in [Salsify](https://www.salsify.com/) and reviews in [Bazaarvoice](https://www.bazaarvoice.com/). A team running a paywalled content site can create stories in [Wordpress](https://wordpress.org/), store video in [JWPlayer](https://www.jwplayer.com/), user data in [Auth0](https://auth0.com/), and subscription data in [Recurly](https://recurly.com/).
+Today, a website team running an e-commerce site can store product inventory in [Shopify](https://www.shopify.com/), product listings in [Salsify](https://www.salsify.com/) and reviews in [Bazaarvoice](https://www.bazaarvoice.com/). A team running a paywalled content site can create stories in [WordPress](https://wordpress.org/), store video in [JWPlayer](https://www.jwplayer.com/), user data in [Auth0](https://auth0.com/), and subscription data in [Recurly](https://recurly.com/).
 
 When website teams want to add search, they can turn to [Algolia](https://www.algolia.com/); for payments, [Stripe](http://stripe.com); for analytics, [Segment](https://segment.com/); for A/B testing, [Optimizely](https://www.optimizely.com/); for personalization, [Evergage](https://www.evergage.com/).
 

docs/blog/2018-10-10-unbundling-of-the-cms/index.md

@@ -23,13 +23,13 @@ But creating compelling experiences is challenging:
 
 ## Generic vs best-of-breed
 
-When compared with purpose-built CMSs like Shopify for e-commerce or Wordpress for blogging, enterprise CMS applications like Sitecore, Evoq or Adobe Experience Manager (AEM) provide generic content modules.
+When compared with purpose-built CMSs like Shopify for e-commerce or WordPress for blogging, enterprise CMS applications like Sitecore, Evoq or Adobe Experience Manager (AEM) provide generic content modules.
 
 The enterprise CMS core development experiences are based in C#, ASP.NET, and J2EE -- languages and frameworks a decade out of date for frontend development. Add-ons are expensive and are difficult-to-use compared to pure-play alternatives.
 
 Best-of-breed products have emerged to provide top-notch alternatives in each of these areas, but have been difficult to integrate.
 
-One popular, paywalled, news site that currently stores all content and data in Drupal 7 is migrating to a microservices setup. They’ll handle stories in [Wordpress](https://wordpress.org/), store video in [JWPlayer](https://www.jwplayer.com/), and user data in [Auth0](https://auth0.com/). They’re doing development in React and using [Segment](https://segment.com) for analytics, [Stripe](http://stripe.com) for payments and [Recurly](https://recurly.com/) for subscriptions.
+One popular, paywalled, news site that currently stores all content and data in Drupal 7 is migrating to a microservices setup. They’ll handle stories in [WordPress](https://wordpress.org/), store video in [JWPlayer](https://www.jwplayer.com/), and user data in [Auth0](https://auth0.com/). They’re doing development in React and using [Segment](https://segment.com) for analytics, [Stripe](http://stripe.com) for payments and [Recurly](https://recurly.com/) for subscriptions.
 
 Another digital consumer brand moved from using Sitecore as a content and development platform to using [Contentful](https://www.contentful.com/) as a [headless CMS](/docs/headless-cms/), [Yotpo](https://www.yotpo.com/) for user-generated content -- primarily reviews, while development transitioned to React to provide a modern look and feel.
 

docs/blog/2018-10-18-creating-compelling-content-experiences/index.md

@@ -106,7 +106,7 @@ Middleman allows connections to third-party data sources, though currently only
 
 Gatsby is the only content mesh option that creates fast websites, supports modern development frameworks, _and_ connects to enterprise content systems. Gatsby features:
 
-- **Integrations with 120+ backends**, including 15+ enterprise content systems like Wordpress, Drupal, Contentful, Contentstack, Salsify and Shopify, as well as the ability to add additional sources.
+- **Integrations with 120+ backends**, including 15+ enterprise content systems like WordPress, Drupal, Contentful, Contentstack, Salsify and Shopify, as well as the ability to add additional sources.
 
 - **A React development environment**, along with key plugins that provide key website features like SEO, routing, accessibility, and i18n.
 

docs/blog/2018-11-07-gatsby-for-apps/index.md

@@ -157,7 +157,7 @@ These performance optimizations aren't opt-in; they're enabled, by default. As n
 
 ### Plugins and the Gatsby Ecosystem
 
-One of the key benefits of Gatsby is its highly modular architecture. Need a plugin for [sourcing data from Wordpress][gatsby-source-wordpress]? Sure, seems reasonable. Need to [transform yaml data][gatsby-transformer-yaml] into a usable, JavaScript object? Yeah, why not! Want to [stitch in a remote GraphQL API][gatsby-source-graphql] and inject the data at _build_ time? Oh, you're fancy! Want to load optimized, responsive, blur-in images? Yep.
+One of the key benefits of Gatsby is its highly modular architecture. Need a plugin for [sourcing data from WordPress][gatsby-source-wordpress]? Sure, seems reasonable. Need to [transform yaml data][gatsby-transformer-yaml] into a usable, JavaScript object? Yeah, why not! Want to [stitch in a remote GraphQL API][gatsby-source-graphql] and inject the data at _build_ time? Oh, you're fancy! Want to load optimized, responsive, blur-in images? Yep.
 
 Let's take a look at that image functionality provided by one of our components, `gatsby-image`, in slightly more detail.
 

docs/blog/2018-2-3-sites-with-headless-cms/index.md

@@ -7,7 +7,7 @@ tags: ["headless-cms", "contentful", "content-mesh"]
 
 ## What is a traditional CMS?
 
-A traditional Content Management System (CMS)--like Wordpress, Drupal, or Joomla--manages three things for a website: content, admin screens, and presentation layer. These three things are tightly integrated, which has advantages. For example, there’s only one system to learn / one vendor relationship, and overall, there may be fewer choices to make. In addition, traditional CMSs have been around for so long that many teams are familiar with them and many websites are already be running on them. Both advantages.
+A traditional Content Management System (CMS)--like WordPress, Drupal, or Joomla--manages three things for a website: content, admin screens, and presentation layer. These three things are tightly integrated, which has advantages. For example, there’s only one system to learn / one vendor relationship, and overall, there may be fewer choices to make. In addition, traditional CMSs have been around for so long that many teams are familiar with them and many websites are already be running on them. Both advantages.
 
 You can think of a traditional CMS like an old home built by one person and with custom fittings. Gorgeous, and expensive to maintain, like the home in _The Money Pit_ (1986) with Tom Hanks and Shelley Long.