Changeset 1692 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

23/06/12 12:01:38 (10 years ago)

Author:

julian.reschke@…

Message:

Simplify use of "Note:", make upper/lowercase of sentence start consistent; use "—" where appropriate

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (8 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -16 +16 @@
   <!ENTITY ID-YEAR "2012">
   <!ENTITY mdash "&#8212;">
+  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
   <!ENTITY caching-overview       "<xref target='Part6' x:rel='#caching.overview' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY cache-incomplete       "<xref target='Part6' x:rel='#response.cacheability' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -308 +309 @@
 <x:note>
   <t>
-    <x:h>Note:</x:h> The term 'user agent' covers both those situations where
+    &Note; The term 'user agent' covers both those situations where
     there is a user (human) interacting with the software agent (and for which
     user interface or interactive suggestions might be made, e.g., warning the
@@ -1187 +1188 @@
 <x:note>
   <t>
-   <x:h>Note:</x:h> The "Set-Cookie" header field as implemented in
+   &Note; The "Set-Cookie" header field as implemented in
    practice can occur multiple times, but does not use the list syntax, and
    thus cannot be combined into a single line (<xref target="RFC6265"/>). (See Appendix A.2.3 of <xref target="Kri2001"/>
@@ -1978 +1979 @@
 </t>
 <x:note><t>
-   <x:h>Note:</x:h> Use of program names for the identification of encoding formats
+   &Note; Use of program names for the identification of encoding formats
    is not desirable and is discouraged for future encodings. Their
    use here is representative of historical practice, not good
@@ -1984 +1985 @@
 </t></x:note>
 <x:note><t>
-   <x:h>Note:</x:h> For compatibility with previous implementations of HTTP,
+   &Note; For compatibility with previous implementations of HTTP,
    applications &SHOULD; consider "x-gzip" and "x-compress" to be
    equivalent to "gzip" and "compress" respectively.
@@ -2009 +2010 @@
 <x:note>
   <t>
-    <x:h>Note:</x:h> Some incorrect implementations send the "deflate" 
+    &Note; Some incorrect implementations send the "deflate" 
     compressed data without the zlib wrapper.
    </t>
@@ -2084 +2085 @@
          response on behalf of downstream recipients.
       </t><t>
-         <x:h>Note:</x:h> HTTP/1.1 does not define any means to limit the size of a
+         &Note; HTTP/1.1 does not define any means to limit the size of a
          chunked response such that a client can be assured of buffering
          the entire response.</t>
@@ -2128 +2129 @@
 <x:note>
   <t>
-     <x:h>Note:</x:h> "Quality values" is a misnomer, since these values merely represent
+     &Note; "Quality values" is a misnomer, since these values merely represent
      relative degradation in desired quality.
   </t>