summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatt Penna <mpenna@gitlab.com>2019-09-12 02:33:32 +0000
committerEvan Read <eread@gitlab.com>2019-09-12 02:33:32 +0000
commit2b9a8de11a0913fb7655cfd7f3d7cf82302b69d6 (patch)
treee350e9de031b931ce2c7525effbdb38d4b5778df
parentb3d5dac9c03c207f7bb007154657f779caa8d1a8 (diff)
downloadgitlab-ce-2b9a8de11a0913fb7655cfd7f3d7cf82302b69d6.tar.gz
Docs: Clarified wording to match Permissions doc
-rw-r--r--doc/user/project/protected_branches.md5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/user/project/protected_branches.md b/doc/user/project/protected_branches.md
index 895c8ac88e7..1de3e3b5387 100644
--- a/doc/user/project/protected_branches.md
+++ b/doc/user/project/protected_branches.md
@@ -5,9 +5,8 @@ type: reference, howto
# Protected Branches
[Permissions](../permissions.md) in GitLab are fundamentally defined around the
-idea of having read or write permission to the repository and branches. To
-prevent people from messing with history or pushing code without review, we've
-created protected branches.
+idea of having read or write permission to the repository and branches. To impose
+further restrictions on certain branches, they can be protected.
## Overview