updating content files

content/github/getting-started-with-github/quickstart/github-flow.md

@@ -14,17 +14,17 @@ versions:
 topics:
   - Pull requests
   - Fundamentals
-miniTocMaxHeadingLevel: 4
+miniTocMaxHeadingLevel: 3
 ---
-### Introduction
+## Introduction
 
 {% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow. The {% data variables.product.prodname_dotcom %} flow is useful for everyone, not just developers. For example, here at {% data variables.product.prodname_dotcom %}, we use {% data variables.product.prodname_dotcom %} flow for our [site policy](https://github.com/github/site-policy), [documentation](https://github.com/github/docs), and [roadmap](https://github.com/github/roadmap).
 
-### Prerequisites
+## Prerequisites
 
 To follow {% data variables.product.prodname_dotcom %} flow, you will need {% data variables.product.prodname_dotcom %} account and a repository. For information on how to create an account, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)." For information on how to create a repository, see "[Create a repo](/github/getting-started-with-github/create-a-repo)."{% if currentVersion == "free-pro-team@latest" %} For information on how to find an existing repository to contribute to, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %}
 
-### Following {% data variables.product.prodname_dotcom %} flow
+## Following {% data variables.product.prodname_dotcom %} flow
 
 {% tip %}
 
@@ -36,13 +36,13 @@ To follow {% data variables.product.prodname_dotcom %} flow, you will need {% da
 
 {% endtip %}
 
-#### Create a branch
+### Create a branch
 
   Create a branch in your repository. A short, descriptive branch name enables your collaborators to see ongoing work at a glance. For example, `increase-test-timeout` or `add-code-of-conduct`. For more information, see "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)."
 
   By creating a branch, you create a space to work without affecting the default branch. Additionally, you give collaborators a chance to review your work.
 
-#### Make changes
+### Make changes
 
 On your branch, make any desired changes to the repository. For more information, see "[Creating new files](/articles/creating-new-files)," "[Editing files](/articles/editing-files)," "[Renaming a file](/articles/renaming-a-file)," "[Moving a file to a new location](/articles/moving-a-file-to-a-new-location)," or "[Deleting files in a repository](/github/managing-files-in-a-repository/deleting-files-in-a-repository)."
 
@@ -62,7 +62,7 @@ Continue to make, commit, and push changes to your branch until you are ready to
 
 {% endtip %}
 
-#### Create a pull request
+### Create a pull request
 
 Create a pull request to ask collaborators for feedback on your changes. Pull request review is so valuable that some repositories require an approving review before pull requests can be merged. If you want early feedback or advice before you complete your changes, you can mark your pull request as a draft. For more information, see "[Creating a pull request](/articles/creating-a-pull-request)."
 
@@ -78,13 +78,13 @@ Your repository may be configured to automatically request a review from specifi
 
 If your repository has checks configured to run on pull requests, you will see any checks that failed on your pull request. This helps you catch errors before merging your branch. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)."
 
-#### Address review comments
+### Address review comments
 
 Reviewers should leave questions, comments, and suggestions. Reviewers can comment on the whole pull request or add comments to specific lines. You and reviewers can insert images or code suggestions to clarify comments. For more information, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)."
 
 You can continue to commit and push changes in response to the reviews. Your pull request will update automatically.
 
-#### Merge your pull request
+### Merge your pull request
 
 Once your pull request is approved, merge your pull request. This will automatically merge your branch so that your changes appear on the default branch. {% data variables.product.prodname_dotcom %} retains the history of comments and commits in the pull request to help future contributors understand your changes. For more information, see "[Merging a pull request](/articles/merging-a-pull-request)."
 
@@ -92,7 +92,7 @@ Once your pull request is approved, merge your pull request. This will automatic
 
 Branch protection settings may block merging if your pull request does not meet certain requirements. For example, you need a certain number of approving reviews or an approving review from a specific team. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
 
-#### Delete your branch
+### Delete your branch
 
 After you merge your pull request, delete your branch. This indicates that the work on the branch is complete and prevents you or others from accidentally using old branches. For more information, see "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)."