[master] doc nit: Base64 is capitalized and not hyphenated

diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml
index d7417b98c42c29d74b83e6a8d0b9734fdfc8b320..ade3669917c48fcbe58a8e954681fcccf9bf5957 100644 (file)
--- a/doc/arm/Bv9ARM-book.xml
+++ b/doc/arm/Bv9ARM-book.xml
@@ -1171,7 +1171,7 @@ zone "eng.example.com" {
                  "<userinput>hmac-sha256</userinput>",
                  "<userinput>hmac-sha384</userinput>"
                  and "<userinput>hmac-sha512</userinput>"
-                 have any meaning.  The secret is a base-64 encoded string
+                 have any meaning.  The secret is a Base64 encoded string
                  as specified in RFC 3548.
                </para>
 
@@ -3552,7 +3552,7 @@ $ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa.
          number of required bits preceded by a dash, e.g.
          <literal>hmac-sha1-80</literal>.  The
          <replaceable>secret_string</replaceable> is the secret
-         to be used by the algorithm, and is treated as a base-64
+         to be used by the algorithm, and is treated as a Base64
          encoded string.
        </para>
 
@@ -11363,7 +11363,7 @@ example.com                 CNAME   rpz-tcp-only.
          <para>
            The <command>trusted-keys</command> statement can contain
            multiple key entries, each consisting of the key's
-           domain name, flags, protocol, algorithm, and the Base-64
+           domain name, flags, protocol, algorithm, and the Base64
            representation of the key data.
            Spaces, tabs, newlines and carriage returns are ignored
            in the key data, so the configuration may be split up into