summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVladimir Shushlin <vshushlin@gitlab.com>2019-07-03 11:47:03 +0000
committerVladimir Shushlin <v.shushlin@gmail.com>2019-07-03 16:24:04 +0300
commit9148d1ea193f024bed770b205e187cbea31a7915 (patch)
tree2aa968bcd02564e3f3a5826e309afb8c6c507335
parenta4ee4bbfe778e861a5b5d4b40eacd0cd18e20fb1 (diff)
downloadgitlab-ce-59286-disable-pages-access-control-for-projects-created-before-enabling-it-on-gitlab-instance-gitlab-com.tar.gz
-rw-r--r--doc/administration/raketasks/maintenance.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/administration/raketasks/maintenance.md b/doc/administration/raketasks/maintenance.md
index 41d2b12a695..626b6304d22 100644
--- a/doc/administration/raketasks/maintenance.md
+++ b/doc/administration/raketasks/maintenance.md
@@ -258,7 +258,7 @@ sudo gitlab-rake gitlab:exclusive_lease:clear[project_housekeeping:4]
Don't run if you've already enabled
[Pages Access Control](../pages/index.md#access-control) a while ago.
-If you enabling [Pages Access Control](../pages/index.md#access-control) much later
+If you're enabling [Pages Access Control](../pages/index.md#access-control) much later
than it was introduced, you may have a lot of projects with pages access level set to
`Everyone with access`(gitlab.com situation).
Enabling access control and redeploying these projects will make them private