doc: fix generated manual pages (#3571)

Went over all generated manual pages and fixed some markdown issues,
mostly escaping "_" to avoid underlining entire paragraphs.

Some textual fixes in route53 and other cloud DNS plugins.

Regenerated the markdown with mmark.

Signed-off-by: Miek Gieben <miek@miek.nl>

1 files changed, 3 insertions, 7 deletions

diff --git a/plugin/clouddns/README.md b/plugin/clouddns/README.md
index 9ae6d52e0..6ff4a2b24 100644
--- a/plugin/clouddns/README.md
+++ b/plugin/clouddns/README.md
@@ -28,22 +28,18 @@ clouddns [ZONE:PROJECT_ID:HOSTED_ZONE_NAME...] {
     domains (private vs. public hosted zone), CoreDNS does the lookup in the given order here.
     Therefore, for a non-existing resource record, SOA response will be from the rightmost zone.
 
-*   **PROJECT_ID** the project ID of the Google Cloud project.
+*   **PROJECT\_ID** the project ID of the Google Cloud project.
 
-*   **HOSTED_ZONE_NAME** the name of the hosted zone that contains the resource record sets to be
+*   **HOSTED\_ZONE\_NAME** the name of the hosted zone that contains the resource record sets to be
     accessed.
 
-*   `credentials` is used for reading the credential file.
-
-*   **FILENAME** GCP credentials file path (normally a .json file).
+*   `credentials` is used for reading the credential file from **FILENAME** (normally a .json file).
 
 *   `fallthrough` If zone matches and no record can be generated, pass request to the next plugin.
     If **[ZONES...]** is omitted, then fallthrough happens for all zones for which the plugin is
     authoritative. If specific zones are listed (for example `in-addr.arpa` and `ip6.arpa`), then
     only queries for those zones will be subject to fallthrough.
 
-*   **ZONES** zones it should be authoritative for. If empty, the zones from the configuration block
-
 ## Examples
 
 Enable clouddns with implicit GCP credentials and resolve CNAMEs via 10.0.0.1: