summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobert Speicher <rspeicher@gmail.com>2016-02-22 15:23:11 -0500
committerRobert Speicher <rspeicher@gmail.com>2016-02-22 15:23:11 -0500
commit9871612d50e2b523097a9fd06fd5852dd5934368 (patch)
tree6e0824a85bc56ba0c5ee28cfc67d7ef6f82a1867
parent493d166d66902e645f3b0afb76526317fd98ceeb (diff)
downloadgitlab-ce-9871612d50e2b523097a9fd06fd5852dd5934368.tar.gz
Add missing word to GitLab Flow doc
[ci skip]
-rw-r--r--doc/workflow/gitlab_flow.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/workflow/gitlab_flow.md b/doc/workflow/gitlab_flow.md
index 0b205ea6de7..1b354bcc0f1 100644
--- a/doc/workflow/gitlab_flow.md
+++ b/doc/workflow/gitlab_flow.md
@@ -16,7 +16,7 @@ It offers a simple, transparent and effective way to work with git.
![Four stages (working copy, index, local repo, remote repo) and three steps between them](four_stages.png)
When converting to git you have to get used to the fact that there are three steps before a commit is shared with colleagues.
-Most version control systems have only step, committing from the working copy to a shared server.
+Most version control systems have only one step, committing from the working copy to a shared server.
In git you add files from the working copy to the staging area. After that you commit them to the local repo.
The third step is pushing to a shared remote repository.
After getting used to these three steps the branching model becomes the challenge.