grammer [RT #18679]

diff --git a/NSEC3-NOTES b/NSEC3-NOTES
index 6278cb9470fd86947cfcf716ddef9c11e7843ace..d23b20eefd2239929d97f63ce0606fa8acca9d06 100644 (file)
--- a/NSEC3-NOTES
+++ b/NSEC3-NOTES
@@ -19,7 +19,7 @@ placing them in the key-directory as specified in named.conf.
                key-directory "dynamic/example.net";
        };
 
-Assuming one KSK and ons ZSK DNSKEY key has been generated.  Then
+Assuming one KSK and one ZSK DNSKEY key have been generated.  Then
 this will cause the zone to be signed with the ZSK and the DNSKEY
 RRset to be signed with the KSK DNSKEY.  A NSEC chain will also be
 generated as part of the initial signing process.
@@ -31,11 +31,11 @@ generated as part of the initial signing process.
        > send
 
 While the update request will complete almost immediately the zone
-will not be completely signed until named has hand time to walk the
+will not be completely signed until named has had time to walk the
 zone and generate the NSEC and RRSIG records.  Initially the NSEC
 record at the zone apex will have the OPT bit set.  When the NSEC
 chain is complete the OPT bit will be cleared.  Additionally when
-the zone fully signed the private type (default TYPE65535) records
+the zone is fully signed the private type (default TYPE65535) records
 will have a non zero value for the final octet. 
 
 The private type record has 5 octets.
@@ -79,10 +79,10 @@ anchor repositories of the new KSK.
 You should then wait for the maximum TLL in the zone before removing the
 old DNSKEY.  If it is a KSK that is being updated you also need to wait
 for the DS RRset in the parent to be updated and its TTL to expire.
-This ensures that all clients will be able to verify atleast a signature
+This ensures that all clients will be able to verify at least a signature
 when you remove the old DNSKEY.
 
-The can be removed the old DNSKEY via UPDATE.  Take care to specify
+The old DNSKEY can be removed via UPDATE.  Take care to specify
 the correct key.  Named will clean out any signatures generated by
 the old key after the update completes.
 
@@ -108,7 +108,7 @@ NSEC chain will be generated before the NSEC3 chain is removed.
                Converting from secure to insecure
 
 To do this remove all the DNSKEY records.  Any NSEC or NSEC3 chains
-will be removed as will as associated NSEC3PARAM records.  The will
+will be removed as well as associated NSEC3PARAM records.  This will
 take place after the update requests completes.
 
                Periodic re-signing.