From 321b8429f54f74b5741dd0c76f60724a7dcf8ace Mon Sep 17 00:00:00 2001 From: Evan Hunt Date: Sat, 21 Oct 2017 13:28:38 -0700 Subject: [PATCH] [master] doc nit: Base64 is capitalized and not hyphenated --- doc/arm/Bv9ARM-book.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index d7417b98c4..ade3669917 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -1171,7 +1171,7 @@ zone "eng.example.com" { "hmac-sha256", "hmac-sha384" and "hmac-sha512" - 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. @@ -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. hmac-sha1-80. The secret_string 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. @@ -11363,7 +11363,7 @@ example.com CNAME rpz-tcp-only. The trusted-keys 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