Merge pull request #59 from microsoft/jowedeki/fix-docs-spacing

Fix whitespace issue in docs.

pages/commands/rush_change.md

@@ -24,7 +24,7 @@ are backwards and forwards compatible. Examples are: Modifying a private API
 or fixing a bug in the logic of how an existing API works. HOTFIX
 (EXPERIMENTAL) - these are changes that are hotfixes targeting a specific
 older version of the package. When a hotfix change is added, other changes
-will not be able to increment the version number.Enable this feature by
+will not be able to increment the version number. Enable this feature by
 setting 'hotfixChangeEnabled' in your rush.json.
 
 Optional arguments:
@@ -35,7 +35,7 @@ Optional arguments:
                         "git diff" to detect changes.
   -b BRANCH, --target-branch BRANCH
                         If this parameter is specified, compare the checked
-                        out branch with the specified branch todetermine
+                        out branch with the specified branch to determine
                         which projects were changed. If this parameter is not
                         specified, the checked out branch is compared against
                         the "master" branch.

pages/commands/rush_publish.md

@@ -25,7 +25,7 @@ Optional arguments:
                         be applied to package.json files.
   -b BRANCH, --target-branch BRANCH
                         If this flag is specified, applied changes and
-                        deleted change requests will becommitted and merged
+                        deleted change requests will be committed and merged
                         into the target branch.
   -p, --publish         If this flag is specified, applied changes will be
                         published to npm.

pages/commands/rush_version.md

@@ -33,7 +33,7 @@ Optional arguments:
                         The name of the version policy
   --override-bump BUMPTYPE
                         Overrides the bump type in the version-policy.json
-                        for the specified version policy.Valid BUMPTYPE
+                        for the specified version policy. Valid BUMPTYPE
                         values include: prerelease, patch, preminor, minor,
                         major. This setting only works for lock-step version
                         policy in bump action.