summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarcia Ramos <marcia@gitlab.com>2019-04-09 15:18:58 +0000
committerMarcia Ramos <marcia@gitlab.com>2019-04-09 15:18:58 +0000
commit12e35b49576beed0519d1c52aa6fb592d7c59fc7 (patch)
treeadb5c3e613a3d9cad143230528b94f48f35f509a
parenta5378031d1d8dae83622b210897f4a790d55fab6 (diff)
parent8938cf8874075a8049a92d5ee0c62a74fc471439 (diff)
downloadgitlab-ce-12e35b49576beed0519d1c52aa6fb592d7c59fc7.tar.gz
Merge branch 'patch-50' into 'master'
Fix grammar and try to make clearer how a fork works See merge request gitlab-org/gitlab-ce!26929
-rw-r--r--doc/gitlab-basics/fork-project.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/gitlab-basics/fork-project.md b/doc/gitlab-basics/fork-project.md
index 6c232fe6086..a128a7c7dd3 100644
--- a/doc/gitlab-basics/fork-project.md
+++ b/doc/gitlab-basics/fork-project.md
@@ -1,8 +1,8 @@
# How to fork a project
-A fork is a copy of an original repository that you can put in another namespace
-where you can experiment and apply changes that you can later decide if
-publishing or not, without affecting your original project.
+A fork is a copy of an original repository that you put in another namespace
+where you can experiment and apply changes that you can later decide whether or
+not to share, without affecting the original project.
It takes just a few steps to fork a project in GitLab.