@@ -71,7 +71,9 @@ Always rebase and squash your commits before making a pull request.

 5. Edit and save your commit message.

-		Make sure you include your signature.

+		`git commit -s`

+

+		Make sure your message includes <a href="./set-up-git" target="_blank>your signature</a>.

 8. Push any changes to your fork on GitHub.

@@ -23,7 +23,7 @@ You use the `docker` repository and its `Dockerfile` to create a Docker image,

 run a Docker container, and develop code in the container. Docker itself builds,

 tests, and releases new Docker versions using this container.

-If you followed the procedures that <a href="../set-up-prereqs" target="_blank">

+If you followed the procedures that <a href="./set-up-prereqs" target="_blank">

 set up the prerequisites</a>, you should have a fork of the `docker/docker`

 repository. You also created a branch called `dry-run-test`. In this section,

 you continue working with your fork on this branch.

@@ -195,7 +195,7 @@ the branch to your fork on GitHub:

 9. Sign and commit your change.

-        $ git -s -m "Making a dry run test."

+        $ git commit -s -m "Making a dry run test."

         [dry-run-test 6e728fb] Making a dry run test

          1 file changed, 1 insertion(+)

          create mode 100644 TEST.md