[svn] commit: r457 - in /branches/jinmei-dnsrrparams/src/lib/dns/cpp: rrclass.h rrtype.h

[BIND 10 source code commits]

Author: jinmei
Date: Wed Jan 13 05:37:24 2010
New Revision: 457

Log:
some editorial fixes

Modified:
    branches/jinmei-dnsrrparams/src/lib/dns/cpp/rrclass.h
    branches/jinmei-dnsrrparams/src/lib/dns/cpp/rrtype.h

Modified: branches/jinmei-dnsrrparams/src/lib/dns/cpp/rrclass.h
==============================================================================
--- branches/jinmei-dnsrrparams/src/lib/dns/cpp/rrclass.h (original)
+++ branches/jinmei-dnsrrparams/src/lib/dns/cpp/rrclass.h Wed Jan 13 05:37:24 2010
@@ -94,7 +94,7 @@
     /// \param classcode An 16-bit integer code corresponding to the RRClass.
     explicit RRClass(uint16_t classcode) : classcode_(classcode) {}
     ///
-    /// A valid string is one of "well known" textual class representations
+    /// A valid string is one of "well-known" textual class representations
     /// such as "IN" or "CH", or in the standard format for "unknown"
     /// classes as defined in RFC3597, i.e., "CLASSnnnn".
     ///
@@ -103,7 +103,7 @@
     ///
     /// As for the format of "CLASSnnnn", "nnnn" must represent a valid 16-bit
     /// unsigned integer, which may contain leading 0's as long as it consists
-    /// of at most 5 characters (exclusive).
+    /// of at most 5 characters (inclusive).
     /// For example, "CLASS1" and "CLASSS001" are valid and represent the same
     /// class, but "CLASS65536" and "CLASS000001" are invalid.
     /// A "CLASSnnnn" representation is valid even if the corresponding class

Modified: branches/jinmei-dnsrrparams/src/lib/dns/cpp/rrtype.h
==============================================================================
--- branches/jinmei-dnsrrparams/src/lib/dns/cpp/rrtype.h (original)
+++ branches/jinmei-dnsrrparams/src/lib/dns/cpp/rrtype.h Wed Jan 13 05:37:24 2010
@@ -102,7 +102,7 @@
     explicit RRType(uint16_t typecode) : typecode_(typecode) {}
     /// Constructor from a string.
     ///
-    /// A valid string is one of "well known" textual type representations
+    /// A valid string is one of "well-known" textual type representations
     /// such as "A", "AAAA", or "NS", or in the standard format for "unknown"
     /// RR types as defined in RFC3597, i.e., "TYPEnnnn".
     ///
@@ -111,7 +111,7 @@
     ///
     /// As for the format of "TYPEnnnn", "nnnn" must represent a valid 16-bit
     /// unsigned integer, which may contain leading 0's as long as it consists
-    /// of at most 5 characters (exclusive).
+    /// of at most 5 characters (inclusive).
     /// For example, "TYPE1" and "TYPE001" are valid and represent the same
     /// RR type, but "TYPE65536" and "TYPE000001" are invalid.
     /// A "TYPEnnnn" representation is valid even if the corresponding type code