Remove the apostrophe 's from plural acronyms

This is to be consistent with our common usage of just using a
plural "s" without apostrophe.

This was brought up via discussion in ticket 37505.

I didn't have this reviewed.

bin/dnssec/dnssec-dsfromkey.docbook

@@ -167,7 +167,7 @@
         <term>-A</term>
         <listitem>
           <para>
-            Include ZSK's when generating DS records.  Without this option,
+            Include ZSKs when generating DS records.  Without this option,
             only keys which have the KSK flag set will be converted to DS
             records and printed.  Useful only in zone file mode. 
           </para>

bin/dnssec/dnssec-keygen.docbook

@@ -158,7 +158,7 @@
           <para>
             The key size does not need to be specified if using a default
             algorithm.  The default key size is 1024 bits for zone signing
-            keys (ZSK's) and 2048 bits for key signing keys (KSK's,
+            keys (ZSKs) and 2048 bits for key signing keys (KSKs,
             generated with <option>-f KSK</option>).  However, if an
             algorithm is explicitly specified with the <option>-a</option>,
             then there is no default key size, and the <option>-b</option>

bin/rndc/rndc.docbook

@@ -620,7 +620,7 @@
             abort the DNSSEC validation process and treat the data as
             insecure rather than bogus.  This continues until the
             NTA's lifetime is elapsed, or until the server is
-            restarted (NTA's do not persist across restarts).
+            restarted (NTAs do not persist across restarts).
           </para>
           <para>
             An existing NTA can be removed by using the

doc/arm/Bv9ARM-book.xml

@@ -5731,7 +5731,7 @@ options {
 		  abort the DNSSEC validation process and treat the data as
 		  insecure rather than bogus.  This continues until the
 		  NTA's lifetime is elapsed, or until the server is
-		  restarted (NTA's do not persist across restarts).
+		  restarted (NTAs do not persist across restarts).
 		</para>
 		<para>
 		  For convenience, TTL-style time unit suffixes can be
@@ -5764,7 +5764,7 @@ options {
 		<para>
 		  Validity checks can be disabled for an individual
 		  NTA by using <command>rndc nta -f</command>, or
-		  for all NTA's by setting <option>nta-recheck</option>
+		  for all NTAs by setting <option>nta-recheck</option>
 		  to zero.
 		</para>
 		<para>

doc/arm/managed-keys.xml

@@ -40,7 +40,7 @@ also in DNSSEC section above here in ARM -->
     <para>To set up an authoritative zone for RFC 5011 trust anchor
     maintenance, generate two (or more) key signing keys (KSKs) for
     the zone. Sign the zone with one of them; this is the "active"
-    KSK. All KSK's which do not sign the zone are "stand-by"
+    KSK. All KSKs which do not sign the zone are "stand-by"
     keys.</para>
     <para>Any validating resolver which is configured to use the
     active KSK as an RFC 5011-managed trust anchor will take note
@@ -82,8 +82,8 @@ $ <userinput>dnssec-signzone -S -K keys example.net</userinput>
     increasing by 128, and wrapping around at 65535. So, for
     example, the key "<filename>Kexample.com.+005+10000</filename>" becomes
     "<filename>Kexample.com.+005+10128</filename>".</para>
-    <para>If two keys have ID's exactly 128 apart, and one is
-    revoked, then the two key ID's will collide, causing several
+    <para>If two keys have IDs exactly 128 apart, and one is
+    revoked, then the two key IDs will collide, causing several
     problems. To prevent this, 
     <command>dnssec-keygen</command> will not generate a new key if
     another key is present which may collide. This checking will
@@ -95,6 +95,6 @@ $ <userinput>dnssec-signzone -S -K keys example.net</userinput>
     multiple directories or on multiple machines.</para>
     <para>It is expected that a future release of BIND 9 will
     address this problem in a different way, by storing revoked
-    keys with their original unrevoked key ID's.</para>
+    keys with their original unrevoked key IDs.</para>
   </sect2>
 </sect1>

doc/arm/pkcs11.xml

@@ -64,7 +64,7 @@
       need. The HSM's provider library must have a complete implementation
       of the PKCS#11 API, so that all these functions are accessible. As of
       this writing, only the Thales nShield HSM and the latest development
-      version of SoftHSM can be used in this fashion.  For other HSM's,
+      version of SoftHSM can be used in this fashion.  For other HSMs,
       including the AEP Keyper, Sun SCA 6000 and older versions of SoftHSM,
       use OpenSSL-based PKCS#11. (Note: As more HSMs become capable of
       supporting native PKCS#11, it is expected that OpenSSL-based