Prefer H3's over H4's in documentation

Author: godfrzero

03_managing_collections/creating_documentation.md

@@ -1,6 +1,6 @@
 All users of Postman Cloud get access to Postman's Documenter! This is a new feature that lets you view auto-generated documentation for all your collections. You can also publish this documentation and share it publicly for people to consume.
 
-#### Viewing Documentation for Collections
+### Viewing Documentation for Collections
 
 * Make sure you're signed in to Postman. When signed in, your username will be displayed in the top-right corner.
 * Click the arrow next to any collection name. You should see the collection browser open up.
@@ -15,7 +15,7 @@ All users of Postman Cloud get access to Postman's Documenter! This is a new fea
 
 * Keep in mind that this link is restricted to users in your Postman Cloud Team. To make this documentation available to other users (as a link on your website, perhaps), you&\#39'll need to Publish it!
 
-#### Publishing Public Documentation for Collections
+### Publishing Public Documentation for Collections
 
 Published documentation is a way of sharing your collection's documentation with the world. If you're able to view documentation for one of your collections, published docs are a click away!
 

07_postman_for_public_apis/run_button_api.md

@@ -1,7 +1,7 @@
 The JS Run in Postman button exposes an API via the `_pm` function. These API methods allow you to dynamically alter button behavior.
 Note that the `_pm` API is not available for the static Run in Postman button.
 
-#### Creating a new environment
+### Creating a new environment
 
 A new environment can be dynamically created using the `env.create` method:
 
@@ -25,7 +25,7 @@ Note:
 * The `env.create` action will return truthy on success, false on failure.
 * `env.create` cannot be used to create duplicate environments. Subsequent calls with an existing environment name will fail.
 
-#### Editing an existing environment
+### Editing an existing environment
 
 An environment which was included in the Run Button embed code or created with `env.create` can be modified using the `env.assign` method:
 
@@ -50,7 +50,7 @@ Note:
 * `env.assign` cannot be used to create new environments. Calls to `_pm` using `env.assign` will fail if the environment doesn't already exist.
 * `env.assign` will allow assignment to environments created using `env.create` and inline environments from the button embed code.
 
-#### Replacing an existing environment
+### Replacing an existing environment
 
 An entire environment can be replaced using the `env.replace` method.