Browse code
Fix typo in git setup doc.
Signed-off-by: Raghuram Devarakonda <draghuram@gmail.com>
Raghuram Devarakonda authored on 2015/03/23 00:22:47Showing 1 changed files
| ... | ... |
@@ -138,7 +138,7 @@ As you change code in your fork, you make your changes on a repository branch. |
| 138 | 138 |
The branch name should reflect what you are working on. In this section, you |
| 139 | 139 |
create a branch, make a change, and push it up to your fork. |
| 140 | 140 |
|
| 141 |
-This branch is just for testing your config for this guide. The changes arepart |
|
| 141 |
+This branch is just for testing your config for this guide. The changes are part |
|
| 142 | 142 |
of a dry run so the branch name is going to be dry-run-test. To create an push |
| 143 | 143 |
the branch to your fork on GitHub: |
| 144 | 144 |
|