summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStan Hu <stanhu@gmail.com>2018-05-30 13:20:49 -0700
committerStan Hu <stanhu@gmail.com>2018-05-30 13:20:49 -0700
commit465a9abd81028cb8fbde57a9c162a03d56765110 (patch)
tree979d3b1a35819236cdd23bfc06449a7af1025c2e
parent439adb96dadd49124d080db0db0b0076d2049c6b (diff)
downloadgitlab-ce-sh-remove-trailing-whitespace-docs.tar.gz
Remove trailing whitespace that was causing EE conflictssh-remove-trailing-whitespace-docs
-rw-r--r--doc/user/project/merge_requests/squash_and_merge.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/user/project/merge_requests/squash_and_merge.md b/doc/user/project/merge_requests/squash_and_merge.md
index a6efe893853..7cf2ce708f8 100644
--- a/doc/user/project/merge_requests/squash_and_merge.md
+++ b/doc/user/project/merge_requests/squash_and_merge.md
@@ -18,7 +18,7 @@ Into a single commit on merge:
![A squashed commit followed by a merge commit][squashed-commit]
-The squashed commit's commit message is the merge request title. And note that
+The squashed commit's commit message is the merge request title. And note that
the squashed commit is still followed by a merge commit, as the merge
method for this example repository uses a merge commit. Squashing also works
with the fast-forward merge strategy, see
@@ -30,7 +30,7 @@ details.
When working on a feature branch, you sometimes want to commit your current
progress, but don't really care about the commit messages. Those 'work in
progress commits' don't necessarily contain important information and as such
-you'd rather not include them in your target branch.
+you'd rather not include them in your target branch.
With squash and merge, when the merge request is ready to be merged,
all you have to do is enable squashing before you press merge to join