From dc899c4eaf1261ba0d5a740271bba0bfc866ae3c Mon Sep 17 00:00:00 2001 From: Mary Anthony Date: Sat, 14 Mar 2015 21:28:55 -0700 Subject: [PATCH] Adding in minor copy edits Signed-off-by: Mary Anthony --- docs/sources/project/create-pr.md | 4 +++- docs/sources/project/set-up-dev-env.md | 2 +- docs/sources/project/set-up-git.md | 2 +- 3 files changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/sources/project/create-pr.md b/docs/sources/project/create-pr.md index be3b5fe409..84de397090 100644 --- a/docs/sources/project/create-pr.md +++ b/docs/sources/project/create-pr.md @@ -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 +If you followed the procedures that set up the prerequisites, 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. diff --git a/docs/sources/project/set-up-git.md b/docs/sources/project/set-up-git.md index 64b2ba13d4..ba42c81006 100644 --- a/docs/sources/project/set-up-git.md +++ b/docs/sources/project/set-up-git.md @@ -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