Merge "Gerrit 2.3 ReleaseNotes" into stable-2.3
diff --git a/Documentation/access-control.txt b/Documentation/access-control.txt
index 013c3eb..d2078ab 100644
--- a/Documentation/access-control.txt
+++ b/Documentation/access-control.txt
@@ -780,6 +780,14 @@
and `-1 Do not have copyright` will block submit, while `+1 Copyright
clear` is required to enable submit.
+[[restart_changes]]
+[NOTE]
+Restart the Gerrit web application and reload all browsers after
+making any database changes to approval categories. Browsers are
+sent the list of known categories when they first visit the site,
+and don't notice changes until the page is closed and opened again,
+or is reloaded.
+
Examples of typical roles in a project
--------------------------------------
@@ -873,7 +881,7 @@
deliver different results (build error vs unstable for instance) it's also
possible to set `Code-review` +1 as well.
-If pushing new changes are granted, it's possible to automate cherry-pick of
+If pushing new changes is granted, it's possible to automate cherry-pick of
submitted changes for upload to other branches under certain conditions. This
is probably not the first step of what a project wants to automate however,
and so the push right can be found under the optional section.
@@ -1143,14 +1151,6 @@
link:cmd-show-queue.html[look at the Gerrit task queue via ssh].
-[[restart_changes]]
-[NOTE]
-Restart the Gerrit web application and reload all browsers after
-making any database changes to approval categories. Browsers are
-sent the list of known categories when they first visit the site,
-and don't notice changes until the page is closed and opened again,
-or is reloaded.
-
GERRIT
------
Part of link:index.html[Gerrit Code Review]
