anchor.diff:  
   *Step 5:* Rebase updates from `master` into your working branch
   
  -If you fetched the latest changes from `master` before you created your local branch, this step may not be necessary. However, it is good practice to fetch the latest changes from `master` and rebase those onto your working branch.
  +If you fetched the latest changes from `master` before you created your local
  +branch, this step may not be necessary. However, it is good practice to fetch
  +the latest changes from `master` and rebase those onto your working branch.
   
   ----
   $ git rebase upstream/master
   ----
   
   [NOTE]
  +====
   If you find any conflicts you must fix those, and repeat steps 3 and 4.
  +====
   
   *Step 6:* Push all changes to your GitHub account
   
  -when you have rebased, fixed any conflicts, and committed your changes you can push them to your GitHub account. This command adds your local working branch to your GitHub repository.
  +After you have rebased, fixed any conflicts, and committed your changes ,you can
  +push them to your GitHub account. This command adds your local working branch to
  +your GitHub repository:
   
   ----
   $ git push origin <working_branch>
   ----
   
   == Submit PR to merge your work
  -When you have pushed your changes to your GitHub account, you can submit a PR to have your work from your GitHub fork to the `master` branch of the OpenShift documentation repository. The documentation team will review the work, will advise of any further changes that may or may not be required, and finally merge your work.
  -
  -1. Go to your forked GitHub repository on the GitHub website, and you should see your local branch that includes all of your work.
  -2. Click on *Pull Request* to submit the PR against the `master` branch of the `openshift-docs` repository.
  +When you have pushed your changes to your GitHub account, you can submit a PR to
  +have your work from your GitHub fork to the `master` branch of the OpenShift
  +documentation repository. The documentation team will review the work, advise of
  +any further changes that may or may not be required, and finally merge your
  +work.
  +
  +1. Go to your forked GitHub repository on the GitHub website, and you should see
  +your local branch that includes all of your work.
  +2. Click on *Pull Request* to submit the PR against the `master` branch of the
  +`openshift-docs` repository.
   
   == Confirm your changes have been merged
  -When your PR has been merged into the `master` branch, you should confirm and then sync your local and GitHub repositories with the `master` branch.
  +When your PR has been merged into the `master` branch, you should confirm and
  +then sync your local and GitHub repositories with the `master` branch.
   
   1. On your workstation, switch to the `master` branch:
   +
  
positive.code: $ git fetch upstream
  ----
  
  3. Push the latest changes, including your work, to your GitHub account:
  +
  ----
  $ git push origin master
  ----
  
  == Add changes to an existing PR, if required
  In some cases you might have to make changes to a PR that you have already submitted. A PR can contain multiple commits, and we strive to preserve the review history and all discussions that occur around those commits. The following instructions describe how to make changes to an existing PR you have already submitted.
  
  1. Commit whatever updates you have made to the working branch by creating a new commit:
  +
  ----
  $ git commit -am "Detailed message as noted earlier"
  ----
  
  2. To keep the Git history clean, you may be asked to rebase your PR and squash multiple commits into one commit. Before you push your changes in the next step, follow the instructions here to rebase: https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request
  
  3. When you have rebased, push the latest updates to the local working branch to your GitHub account.
  +
  ----
  $ git push origin <working_branch> --force
  ----
  
  The `--force` flag ignores whatever is on the remote server and replaces everything with the local copy. You should now see the new commits in the existing PR. Sometimes a refresh of the browser may be required.
  
  == Delete the local working branch
  When you have confirmed that all of your changes have been accepted and merged, and you have pulled the latest changes on `master` and pushed them to your GitHub account, you can delete the local working branch. Ensure you are in your local repository before proceeding.
  
  1. Delete the local working branch from your workstation.
  +
  
negative.code: ----
  $ git push origin :<working_branch>
  ----
  