Fix issues in REST API documentation
* a block with an example response was not closed, breaking the
rendering of all follow-up content
* use correct syntax for indended list items
* add missing space in one sentence
Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I275f3afb1d83d6e5a24b7023fb34fbd7c2dd1853
diff --git a/resources/Documentation/rest-api.md b/resources/Documentation/rest-api.md
index 5013366..7044cd8 100644
--- a/resources/Documentation/rest-api.md
+++ b/resources/Documentation/rest-api.md
@@ -166,6 +166,7 @@
"value": 1
}
}
+```
### <a id="list-code-owner-config-files">List Code Owner Config Files
_'GET /projects/[\{project-name\}](../../../Documentation/rest-api-projects.html#project-name)/branches/[\{branch-id\}](../../../Documentation/rest-api-projects.html#branch-id)/code_owners.config_files/'_
@@ -460,10 +461,10 @@
All REST endpoints may return the following responses:
* `409 Conflict` is returned if a request cannot be executed due to:
-** an non-parseable code owner config file (in this case the project owners need
- to fix the code owner config file)
-** an invalid plugin configuration (in this case the project owners need to fix
- the code-owners plugin configuration)
+ * an non-parseable code owner config file (in this case the project owners
+ need to fix the code owner config file)
+ * an invalid plugin configuration (in this case the project owners need to
+ fix the code-owners plugin configuration)
## <a id="ids"> IDs
@@ -471,7 +472,7 @@
An arbitrary absolute path.
-The leading'/' can be omitted.
+The leading '/' can be omitted.
The path may or may not exist in the branch.
