summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormlncn <ben@agaric.com>2019-04-03 02:30:36 +0000
committermlncn <ben@agaric.com>2019-04-03 02:30:36 +0000
commit8938cf8874075a8049a92d5ee0c62a74fc471439 (patch)
tree8198d489515884dfba72f44f1ade7f76e7526035
parent14e2e61de7010034a7e9aaa967b6ee7e3c061d18 (diff)
downloadgitlab-ce-8938cf8874075a8049a92d5ee0c62a74fc471439.tar.gz
Fix grammar and try to make clearer how a fork works
-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.