[DOCUMENTATION] English:

 - manual fixes: <acronym>RFC</acronym>* => RFC* where * doesn't begin with a space or a point

git-svn-id: http://framework.zend.com/svn/framework/standard/trunk@17407 44c647ce-9c0f-0410-b52a-842ac1e357ba

documentation/manual/en/module_specs/Zend_Auth_Adapter_Http.xml

@@ -50,7 +50,7 @@
         </itemizedlist>
 
         <para>
-            There are a few notable features of <acronym>RFC</acronym>-2617 that are not
+            There are a few notable features of RFC-2617 that are not
             implemented yet:
         </para>
 

documentation/manual/en/module_specs/Zend_Mail-Encoding.xml

@@ -12,7 +12,7 @@
 
     <para>
         Header Encoding, especially the encoding of the subject, is a tricky topic. <classname>Zend_Mime</classname> currently implements
-        its own algorithm to encode quoted printable headers according to <acronym>RFC</acronym>-2045.
+        its own algorithm to encode quoted printable headers according to RFC-2045.
         This due to the problems of <code>iconv_mime_encode</code> and <code>mb_encode_mimeheader</code>
         with regards to certain charsets. This algorithm only breaks the header at spaces, which might lead to headers
         that far exceed the suggested length of 76 chars. For this cases it is suggested to switch to BASE64

documentation/manual/en/module_specs/Zend_OpenId-Consumer.xml

@@ -510,7 +510,7 @@ $consumer = new Zend_OpenId_Consumer($storage);
                 <para>
                     <emphasis>email</emphasis>
                     - the email address of the user as specified in section 3.4.1
-                    of <acronym>RFC</acronym>2822
+                    of RFC2822
                 </para>
             </listitem>
             <listitem>

documentation/manual/en/module_specs/Zend_Validate-EmailAddress.xml

@@ -39,7 +39,7 @@ if ($validator->isValid($email)) {
 
     <para>
         <classname>Zend_Validate_EmailAddress</classname> will match any valid email address
-        according to <acronym>RFC</acronym>2822. For example, valid emails include <code>bob@domain.com</code>,
+        according to RFC2822. For example, valid emails include <code>bob@domain.com</code>,
         <code>bob+jones@domain.us</code>, <code>"bob@jones"@domain.com</code> and
         <code>"bob jones"@domain.com</code>
     </para>