p4u1/docker-cli
0
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Fix a typo and a minor formatting issue in the docs.

Browse Source 
Signed-off-by: Eric-Olivier Lamey <eo@lamey.me>
Upstream-commit: 173d0918a8ddffe1ba8a057527feccb6bee7f30b
Component: engine
This commit is contained in:
Eric-Olivier Lamey
2015-06-07 07:07:04 +00:00
parent 34bcda9fbc
commit b9079beed3
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
components/engine/docs/sources/project/create-pr.md
View File

@ -75,9 +75,9 @@ Always rebase and squash your commits before making a pull request.
6. Edit and save your commit message.
`git commit -s`
$ git commit -s
Make sure your message includes <a href="./set-up-git" target="_blank>your signature</a>.
Make sure your message includes <a href="../set-up-git" target="_blank">your signature</a>.
7. Force push any changes to your fork on GitHub.

2
components/engine/docs/sources/project/test-and-docs.md
View File

@ -102,7 +102,7 @@ Run the entire test suite on your current repository:
* creates a new binary
* cross-compiles all the binaries for the various operating systems
* runs the all the tests in the system
* runs all the tests in the system
It can take several minutes to run all the tests. When they complete
successfully, you see the output concludes with something like this:

4
components/engine/docs/sources/project/work-issue.md
View File

@ -178,9 +178,9 @@ You should pull and rebase frequently as you work.
6. Edit and save your commit message.
`git commit -s`
$ git commit -s
Make sure your message includes <a href="./set-up-git" target="_blank>your signature</a>.
Make sure your message includes <a href="../set-up-git" target="_blank">your signature</a>.
7. Force push any changes to your fork on GitHub.