Config guide: Fix formatting issues
* Add missing closing parenthesis in 2 places
* Fix formatting of bullet lists
Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: Ie13e202b59140920381a3118b061ef2736cd8be2
diff --git a/resources/Documentation/config-guide.md b/resources/Documentation/config-guide.md
index 0975cff..2a20478 100644
--- a/resources/Documentation/config-guide.md
+++ b/resources/Documentation/config-guide.md
@@ -257,11 +257,11 @@
control who can approve changes:
* Configure the `Code-Review` label with a voting range from `-2` to `+2` (see
- [label configuration](../../../Documentation/config-labels.html#label_Code-Review).
+ [label configuration](../../../Documentation/config-labels.html#label_Code-Review)).
* For the code owners assign permissions to allow voting from `Code-Review-2` to
`Code-Review+2` and allow other users only to vote from `Code-Review-1` to
`Code-Review+1` (see [label
- permissions](../../../Documentation/access-control.html#category_review_labels)
+ permissions](../../../Documentation/access-control.html#category_review_labels))
* Setup a submit requirement that requires a `Code-Review+2` approval for making
the change submittable, optionally with disallowing self approvals (see
[submit
@@ -271,6 +271,7 @@
for changes to become submittable.
Advantages of this approach over using the `@PLUGIN@` plugin:
+
* it requires less configuration as you do not need to maintain code owner
config files (aka `OWNERS` files)
* groups are supported (permissions can be assigned to groups, but code
@@ -280,6 +281,7 @@
detect if a change is submittable
Disadvantages:
+
* there are no code owner suggestions and no code owner specific UI controls
---
