Add remark-lint-heading-increment and resolve issues (gatsbyjs#23689)

Bruce · gatsbybot · Marcy Sutton · web-flow · commit 7131cb8b9aae · 2020-06-01T18:38:44.000-07:00
* Add remark-lint-heading-increment and resolve issues

* Make requested changes

* Apply suggestions from code review

Co-authored-by: gatsbybot &lt;mathews.kyle+gatsbybot@gmail.com&gt;
Co-authored-by: Marcy Sutton &lt;marcy@gatsbyjs.com&gt;
diff --git a/.remarkrc.js b/.remarkrc.js
@@ -24,7 +24,6 @@ module.exports = {
     // We would like these rules to be enabled, but they require significant content changes
     // and need additional PRs to be implemented
     ["remark-lint-emphasis-marker", false],
-    ["remark-lint-heading-increment", false],
     ["remark-lint-no-heading-punctuation", false],
     ["remark-lint-list-item-spacing", false],
 
diff --git a/docs/blog/100days/gatsby-image/index.md b/docs/blog/100days/gatsby-image/index.md
@@ -17,29 +17,29 @@ Gatsby sites are known for their [blazing fast speed](/blog/2019-01-30-flamingo-
 
 This week’s challenge invites you to add images to your blog and learn about a popular and powerful Gatsby feature, `gatsby-image`.
 
-#### Part 1
+### Part 1
 
 Add images to your markdown-based blog posts. If you are doing each challenge sequentially, then you have a [Gatsby blog that uses markdown](/blog/100days/start-blog/) for blog posts, and is [deployed live to a CDN](/blog/100days/free-hosting/).
 
 But what good is a blog without beautiful images? We want you to use the resources section below to add auto-optimized images to your markdown blog posts!
 
-#### Part 2
+### Part 2
 
 Now it’s time to get direct experience using the `Img`React component provided by [`gatsby-image`](/packages/gatsby-image/)! Create an about page using JSX, then use the gatsby-image API to transform a normal selfie into a square, black-and-white image.
 
 Bonus: Take note of the build times for your site before and after you add images to your project. Also, record the performance of specific pages with images, using [a tool like Lighthouse](/docs/audit-with-lighthouse/). As a Gatsby Developer you should be aware of how images affect your site’s production and user experience.
 
-### Challenge Resources
+## Challenge Resources
 
-#### Part 1 Resource
+### Part 1 Resource
 
 Follow this tutorial that explains how to [add images to your markdown-based pages](/docs/working-with-images-in-markdown/). After you configure your site as outlined, Gatsby will auto-optimize your images for you.
 
-#### Part 2 Resource
+### Part 2 Resource
 
 [Create an About page](/docs/recipes/pages-layouts/#creating-pages-automatically) using JSX, the preferred templating language for [React](/docs/glossary/react/). After that, you can [learn about gatsby-image](/docs/working-with-images), then [use its API](/docs/gatsby-image/) to transform your selfie into a black-and-white square.
 
-### How to Get Help
+## How to Get Help
 
 Depending on your experience with Gatsby and React, this may be the hardest challenge we've given you. So, if you get stuck, please ask for help from the [Gatsby community](/contributing/community/) and the [ASKGatsbyJS](https://twitter.com/AskGatsbyJS) Twitter account. You can find fellow Gatsby Developers on [Discord](https://discordapp.com/invite/gatsby), [Reddit](https://www.reddit.com/r/gatsbyjs/), [Spectrum](https://spectrum.chat/gatsby-js), and [Dev](https://dev.to/t/gatsby).
 
diff --git a/docs/blog/2018-2-7-jam-out-your-blog/index.md b/docs/blog/2018-2-7-jam-out-your-blog/index.md
@@ -145,11 +145,11 @@ With all of that said, this process has a few caveats related to working within
 1. If you follow a folder structure enclosing an index.md file for your posts, you will need to add the new folder within the URL of the post
 2. Inserting an image adds extra markup which you will need to remove for an image to show up within your post. Prose will upload the image within the same directory as your index.md file.
 
-#### Default
+### Default
 
 ![Default Prose image path](before-post-title.png)
 
-#### After (this will work)
+### After (this will work)
 
 ![After image path change](after-post-title.png)
 
diff --git a/docs/blog/2019-04-29-component-shadowing/index.md b/docs/blog/2019-04-29-component-shadowing/index.md
@@ -125,7 +125,7 @@ user-site
 Now, blue and red will have your custom values and will be reflected in the theme wherever
 `theme.colors.blue` and `theme.colors.red` are used.
 
-#### How much shadowing is too much shadowing?
+### How much shadowing is too much shadowing?
 
 If you've found yourself shadowing a large amount of components in a particular theme it
 might make sense to use a fork instead.
diff --git a/docs/blog/2019-11-25-introducing-gatsby-preview-for-cosmic-js/index.md b/docs/blog/2019-11-25-introducing-gatsby-preview-for-cosmic-js/index.md
@@ -19,23 +19,23 @@ We’re excited to announce the official release of Gatsby Preview for [Cosmic](
 4. After onboarding, go to any Post in your Cosmic Bucket and find the big, beautiful, purple button to preview your content.
    ![Cosmic Gatsby Preview Screenshot](./cosmic-js-gatsby-preview-screenshot.jpg)
 
-#### What happens?
+### What happens?
 
 After clicking the “Open Preview” button, a new tab will open to instantly show you what the content looks like for this specific version on your Gatsby website. This simple one-click preview will greatly enhance your content team’s content-creation workflow.
 
 ![Cosmic Gatsby Preview Screenshot](./cosmic-js-gatsby-preview-screenshot.gif)
 
-#### How did this integration happen?
+### How did this integration happen?
 
 The Cosmic / Gatsby Preview integration is the result of close collaboration between both teams to make the integration as easy as possible. Both sides had to refactor a bit of existing functionality to make it seamless. And the feedback that came from the collaboration effort actually helped to improve both products. We’re happy to say this powerful feature can be integrated in just a few clicks.
 
-#### Why is this a big deal?
+### Why is this a big deal?
 
 Both Gatsby and Cosmic believe deeply in providing developers the best development experience possible. But it’s not just about developers. Content creation team members are crucial to building great web products. And one of the most requested features for content creators is preview, but this has been a challenge for developer teams pushing for highly-optimized JAMStack websites built on Gatsby.
 
 Gatsby Preview solves this problem by providing a simple button for content creators to experience an instant preview of content directly in the CMS dashboard. Gatsby preview with the [Cosmic headless CMS](https://www.cosmicjs.com/headless-cms), is a further extension to empower content creators to preview content quickly and easily, giving teams faster content marketing velocity.
 
-#### What’s next?
+### What’s next?
 
 We’re excited to continue to work closely with the Gatsby team to help create more value-added integrations between both services. It’s our goal to continue to provide the full spectrum of team members the best tools to be successful.
 
diff --git a/docs/blog/2020-01-08-git-workflows/index.md b/docs/blog/2020-01-08-git-workflows/index.md
@@ -293,13 +293,13 @@ At this point, we have the freedom to organize our commits however we want. We c
 
 No flow is without tradeoffs, and this one has a couple:
 
-##### 1. It rewrites history
+### 1. It rewrites history
 
 This flow relies heavily on rebasing, which rewrites history. This means that pushing to GitHub requires a force-push, which can be scary, especially for folks newer to using Git.
 
 This also makes it harder to collaborate on a feature; you need to communicate clearly before rebasing, to make sure everyone's work is in beforehand.
 
-##### 2. It involves some branch juggling
+### 2. It involves some branch juggling
 
 With 3-4 incremental branches, developers have to bounce between them and make sure they're kept in sync. This can be tedious.
 
diff --git a/docs/docs/production-app.md b/docs/docs/production-app.md
@@ -95,15 +95,15 @@ This bundle is produced from [production-app.js](https://github.com/gatsbyjs/gat
 
 This contains the small [webpack-runtime](https://webpack.js.org/concepts/manifest/#runtime) as a separate bundle (configured in `optimization` section). In practice, the app and webpack-runtime are always needed together.
 
-##### framework-[contenthash].js
+### framework-[contenthash].js
 
 The framework bundle contains the React framework. Based on user behavior, React hardly gets upgraded to a newer version. Creating a separate bundle improves users' browser cache hit rate as this bundle is likely not going to be updated often.
 
-##### commons-[contenthash].js
+### commons-[contenthash].js
 
 Libraries used on every Gatsby page are bundled into the commons javascript file. By bundling these together, you can make sure your users only need to download this bundle once.
 
-##### component---[name]-[contenthash].js
+### component---[name]-[contenthash].js
 
 This is a separate bundle for each page. The mechanics for how these are split off from the main production app are covered in [Code Splitting](/docs/how-code-splitting-works/).
 
