[DOCUMENTATION] English:

 - manual fixes: wrap acronym MIME|TCP|PEM|SSL|RFC|ASCII|ACL|ASIN|AMI|CPU|RAM|AWS|NSID with <acronym> inside <para>

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

documentation/manual/en/module_specs/Zend_Auth_Adapter_Ldap.xml

@@ -308,7 +308,7 @@ Array
                         <entry><emphasis><property>useStartTls</property></emphasis></entry>
                         <entry>
                             Whether or not the <acronym>LDAP</acronym> client should use
-                            <acronym>TLS</acronym> (aka SSLv2) encrypted transport. A value of
+                            <acronym>TLS</acronym> (aka <acronym>SSL</acronym>v2) encrypted transport. A value of
                             <constant>TRUE</constant> is strongly favored in production
                             environments to prevent passwords from be transmitted in clear text.
                             The default value is <constant>FALSE</constant>, as servers frequently

documentation/manual/en/module_specs/Zend_Date-Constants.xml

@@ -8,7 +8,7 @@
         Whenever a <classname>Zend_Date</classname> method has a <varname>$parts</varname>
         parameter, one of the constants below can be used as the argument for that parameter, in
         order to select a specific part of a date or indicate the date format used or desired (e.g.
-        RFC 822).
+        <acronym>RFC</acronym> 822).
     </para>
 
     <sect2 id="zend.date.constants.using">

documentation/manual/en/module_specs/Zend_Feed-ConsumingAtom.xml

@@ -97,12 +97,12 @@ foreach ($feed as $entry) {
             </listitem>
             <listitem>
                 <para>
-                    <code>published</code> - the date the entry was published, in RFC 3339 format
+                    <code>published</code> - the date the entry was published, in <acronym>RFC</acronym> 3339 format
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <code>updated</code> - the date the entry was last updated, in RFC 3339 format
+                    <code>updated</code> - the date the entry was last updated, in <acronym>RFC</acronym> 3339 format
                 </para>
             </listitem>
         </itemizedlist>

documentation/manual/en/module_specs/Zend_Feed-ConsumingRss.xml

@@ -83,7 +83,7 @@ foreach ($channel as $item) {
         <itemizedlist>
             <listitem>
                 <para>
-                    <code>pubDate</code> - The publication date of this set of content, in RFC 822
+                    <code>pubDate</code> - The publication date of this set of content, in <acronym>RFC</acronym> 822
                     date format
                 </para>
             </listitem>
@@ -132,7 +132,7 @@ foreach ($channel as $item) {
             </listitem>
             <listitem>
                 <para>
-                    <code>pubDate</code> - The date the item was published, in RFC 822 date format
+                    <code>pubDate</code> - The date the item was published, in <acronym>RFC</acronym> 822 date format
                 </para>
             </listitem>
         </itemizedlist>

documentation/manual/en/module_specs/Zend_File_Transfer-Validators.xml

@@ -39,8 +39,8 @@
 
         <listitem>
             <para>
-                <code>ExcludeMimeType</code>: This validator validates the MIME type of files. It
-                can also validate MIME types and will throw an error if the MIME type of specified
+                <code>ExcludeMimeType</code>: This validator validates the <acronym>MIME</acronym> type of files. It
+                can also validate <acronym>MIME</acronym> types and will throw an error if the <acronym>MIME</acronym> type of specified
                 file matches.
             </para>
         </listitem>
@@ -108,8 +108,8 @@
 
         <listitem>
             <para>
-                <code>MimeType</code>: This validator validates the MIME type of files. It can also
-                validate MIME types and will throw an error if the MIME type of a specified
+                <code>MimeType</code>: This validator validates the <acronym>MIME</acronym> type of files. It can also
+                validate <acronym>MIME</acronym> types and will throw an error if the <acronym>MIME</acronym> type of a specified
                 file does not match.
             </para>
         </listitem>
@@ -533,7 +533,7 @@ $upload->addValidator('ExcludeExtension',
         <note>
             <para>
                 Note that this validator only checks the file extension. It does not check the
-                file's MIME type.
+                file's <acronym>MIME</acronym> type.
             </para>
         </note>
     </sect2>
@@ -542,29 +542,29 @@ $upload->addValidator('ExcludeExtension',
         <title>ExcludeMimeType Validator</title>
 
         <para>
-            The <code>ExcludeMimeType</code> validator checks the MIME type of transferred files.
+            The <code>ExcludeMimeType</code> validator checks the <acronym>MIME</acronym> type of transferred files.
             It supports the following options:
         </para>
 
         <itemizedlist>
             <listitem>
                 <para>
-                    <code>*</code>: Sets any key individually or use a numeric array. Sets the MIME
+                    <code>*</code>: Sets any key individually or use a numeric array. Sets the <acronym>MIME</acronym>
                     type to validate against.
                 </para>
 
                 <para>
-                    With this option you can define the MIME type of files that are not to be
+                    With this option you can define the <acronym>MIME</acronym> type of files that are not to be
                     accepted.
                 </para>
             </listitem>
         </itemizedlist>
 
         <para>
-            This validator accepts multiple MIME types, either as a comma-delimited string, or as
+            This validator accepts multiple <acronym>MIME</acronym> types, either as a comma-delimited string, or as
             an array. You may also use the methods <methodname>setMimeType()</methodname>,
             <methodname>addMimeType()</methodname>, and <methodname>getMimeType()</methodname> to
-            set and retrieve the MIME types.
+            set and retrieve the <acronym>MIME</acronym> types.
         </para>
 
         <example id="zend.file.transfer.validators.excludemimetype.example">
@@ -586,17 +586,17 @@ $upload->addValidator('ExcludeMimeType', false, 'image');
         </example>
 
         <para>
-            The above example shows that it is also possible to disallow groups of MIME types.
-            For example, to disallow all images, just use 'image' as the MIME type. This can be used
-            for all groups of MIME types like 'image', 'audio', 'video', 'text', etc.
+            The above example shows that it is also possible to disallow groups of <acronym>MIME</acronym> types.
+            For example, to disallow all images, just use 'image' as the <acronym>MIME</acronym> type. This can be used
+            for all groups of <acronym>MIME</acronym> types like 'image', 'audio', 'video', 'text', etc.
         </para>
 
         <note>
             <para>
-                Note that disallowing groups of MIME types will disallow all members of this group
+                Note that disallowing groups of <acronym>MIME</acronym> types will disallow all members of this group
                 even if this is not intentional. When you disallow 'image' you will disallow all
                 types of images like 'image/jpeg' or 'image/vasa'. When you are not sure if you want
-                to disallow all types, you should disallow only specific MIME types instead of
+                to disallow all types, you should disallow only specific <acronym>MIME</acronym> types instead of
                 complete groups.
             </para>
         </note>
@@ -712,7 +712,7 @@ if (!$upload->isValid('C:\temp\myfile.MO')) {
         <note>
             <para>
                 Note that this validator only checks the file extension. It does not check the
-                file's MIME type.
+                file's <acronym>MIME</acronym> type.
             </para>
         </note>
     </sect2>
@@ -907,7 +907,7 @@ $upload->addValidator('IsCompressed', false, 'zip');
 
         <note>
             <para>
-                Note that there is no check if you set a MIME type that is not a archive. For
+                Note that there is no check if you set a <acronym>MIME</acronym> type that is not a archive. For
                 example, it would be possible to define gif files to be accepted by this validator.
                 Using the 'MimeType' validator for files which are not archived will result in more
                 readable code.
@@ -944,7 +944,7 @@ $upload->addValidator('IsImage', false, 'jpeg');
 
         <note>
             <para>
-                Note that there is no check if you set a MIME type that is not an image. For
+                Note that there is no check if you set a <acronym>MIME</acronym> type that is not an image. For
                 example, it would be possible to define zip files to be accepted by this validator.
                 Using the 'MimeType' validator for files which are not images will result in more
                 readable code.
@@ -1059,19 +1059,19 @@ $upload->addValidator('Md5',
         <title>MimeType Validator</title>
 
         <para>
-            The <code>MimeType</code> validator checks the MIME type of transferred files.
+            The <code>MimeType</code> validator checks the <acronym>MIME</acronym> type of transferred files.
             It supports the following options:
         </para>
 
         <itemizedlist>
             <listitem>
                 <para>
-                    <code>*</code>: Sets any key or use a numeric array. Sets the MIME type to
+                    <code>*</code>: Sets any key or use a numeric array. Sets the <acronym>MIME</acronym> type to
                     validate against.
                 </para>
 
                 <para>
-                    Defines the MIME type of files to be accepted.
+                    Defines the <acronym>MIME</acronym> type of files to be accepted.
                 </para>
             </listitem>
 
@@ -1089,9 +1089,9 @@ $upload->addValidator('Md5',
         </itemizedlist>
 
         <para>
-            This validator accepts multiple MIME type, either as a comma-delimited string, or as an
+            This validator accepts multiple <acronym>MIME</acronym> type, either as a comma-delimited string, or as an
             array. You may also use the methods <methodname>setMimeType()</methodname>,
-            <methodname>addMimeType()</methodname>, and <methodname>getMimeType()</methodname> to set and retrieve MIME
+            <methodname>addMimeType()</methodname>, and <methodname>getMimeType()</methodname> to set and retrieve <acronym>MIME</acronym>
             type.
         </para>
 
@@ -1126,17 +1126,17 @@ $upload->addValidator('MimeType',
         </example>
 
         <para>
-            The above example shows that it is also possible to limit the accepted MIME type to a
-            group of MIME types. To allow all images just use 'image' as MIME type. This can be used
-            for all groups of MIME types like 'image', 'audio', 'video', 'text, and so on.
+            The above example shows that it is also possible to limit the accepted <acronym>MIME</acronym> type to a
+            group of <acronym>MIME</acronym> types. To allow all images just use 'image' as <acronym>MIME</acronym> type. This can be used
+            for all groups of <acronym>MIME</acronym> types like 'image', 'audio', 'video', 'text, and so on.
         </para>
 
         <note>
             <para>
-                Note that allowing groups of MIME types will accept all members of this group even
+                Note that allowing groups of <acronym>MIME</acronym> types will accept all members of this group even
                 if your application does not support them. When you allow 'image' you will also get
                 'image/xpixmap' or 'image/vasa' which could be problematic. When you are not sure if
-                your application supports all types you should better allow only defined MIME types
+                your application supports all types you should better allow only defined <acronym>MIME</acronym> types
                 instead of the complete group.
             </para>
         </note>
@@ -1145,12 +1145,12 @@ $upload->addValidator('MimeType',
             <para>
                 This component will use the <code>fileinfo</code> extension if it is available. If
                 it's not, it will degrade to the <code>mime_content_type</code> function. And if the
-                function call fails it will use the MIME type which is given by <acronym>HTTP</acronym>.
+                function call fails it will use the <acronym>MIME</acronym> type which is given by <acronym>HTTP</acronym>.
             </para>
 
             <para>
                 You should be aware of possible security problems when you have whether
-                <code>fileinfo</code> nor <code>mime_content_type</code> available. The MIME type
+                <code>fileinfo</code> nor <code>mime_content_type</code> available. The <acronym>MIME</acronym> type
                 given by <acronym>HTTP</acronym> is not secure and can be easily manipulated.
             </para>
         </note>

documentation/manual/en/module_specs/Zend_Gdata_Calendar.xml

@@ -637,7 +637,7 @@ $when->reminders = array($reminder);
                 them is outside the scope of this document. However, more information can be found
                 in the <ulink url="http://code.google.com/apis/gdata/elements.html#gdRecurrence">
                 Common Elements section of the Google Data <acronym>API</acronym>s Developer Guide</ulink>, as well as
-                in RFC 2445.
+                in <acronym>RFC</acronym> 2445.
             </para>
             <programlisting language="php"><![CDATA[
  // Create a new entry using the calendar service's magic factory method

documentation/manual/en/module_specs/Zend_Http_Client-Adapters.xml

@@ -108,13 +108,13 @@
             <note>
                 <title>Persistent TCP Connections</title>
                 <para>
-                    Using persistent TCP connections can potentially speed up
+                    Using persistent <acronym>TCP</acronym> connections can potentially speed up
                     <acronym>HTTP</acronym> requests - but in most use cases, will have little
                     positive effect and might overload the <acronym>HTTP</acronym> server you are
                     connecting to.
                 </para>
                 <para>
-                    It is recommended to use persistent TCP connections only if
+                    It is recommended to use persistent <acronym>TCP</acronym> connections only if
                     you connect to the same server very frequently, and are
                     sure that the server is capable of handling a large number
                     of concurrent connections. In any case you are encouraged
@@ -137,10 +137,10 @@
                     are only relevant when connecting using <acronym>HTTP</acronym>S.
                 </para>
                 <para>
-                    While the default SSL settings should work for most
+                    While the default <acronym>SSL</acronym> settings should work for most
                     applications, you might need to change them if the server
                     you are connecting to requires special client setup. If so,
-                    you should read the sections about SSL transport layers and
+                    you should read the sections about <acronym>SSL</acronym> transport layers and
                     options <ulink url="http://www.php.net/manual/en/transports.php#transports.inet">here</ulink>.
                 </para>
             </note>
@@ -162,7 +162,7 @@ $response = $client->request();
 ]]></programlisting>
         </example>
         <para>
-            The result of the example above will be similar to opening a TCP
+            The result of the example above will be similar to opening a <acronym>TCP</acronym>
             connection using the following <acronym>PHP</acronym> command:
         </para>
         <para>
@@ -175,7 +175,7 @@ $response = $client->request();
                 Starting from Zend Framework 1.9, <classname>Zend_Http_Client_Adapter_Socket</classname>
                 provides direct access to the underlying <ulink url="http://php.net/manual/en/stream.contexts.php">stream context</ulink>
                 used to connect to the remote server. This allows the user to pass
-                specific options and parameters to the TCP stream, and to the SSL wrapper in
+                specific options and parameters to the <acronym>TCP</acronym> stream, and to the <acronym>SSL</acronym> wrapper in
                 case of <acronym>HTTP</acronym>S connections.
             </para>
 

documentation/manual/en/module_specs/Zend_Http_Client-Advanced.xml

@@ -267,7 +267,7 @@ $client->setAuth('shahar', 'myPassword!');
             if the server supports keep-alive connections, the connection to the
             server will only be closed once all requests are done and the Client
             object is destroyed. This prevents the overhead of opening and
-            closing TCP connections to the server.
+            closing <acronym>TCP</acronym> connections to the server.
         </para>
         <para>
             When you perform several requests with the same client, but want

documentation/manual/en/module_specs/Zend_InfoCard-Basics.xml

@@ -66,8 +66,8 @@
 
         <para>
             Note, Information cards can only be <code>HTTP POST</code>ed to
-            SSL-encrypted <acronym>URL</acronym>s. Please consult your web server's documentation
-            on how to set up SSL encryption.
+            <acronym>SSL</acronym>-encrypted <acronym>URL</acronym>s. Please consult your web server's documentation
+            on how to set up <acronym>SSL</acronym> encryption.
         </para>
     </sect2>
 
@@ -142,7 +142,7 @@ if (isset($_POST['xmlToken'])) {
             In the example above, we first create an instance of the
             <classname>Zend_Auth_Adapter_InfoCard</classname> and pass the <acronym>XML</acronym> data posted
             by the card selector into it. Once an instance has been created you
-            must then provide at least one SSL certificate public/private key
+            must then provide at least one <acronym>SSL</acronym> certificate public/private key
             pair used by the web server that received the <code>HTTP
             POST</code>. These files are used to validate the destination
             of the information posted to the server and are a requirement when
@@ -209,7 +209,7 @@ if (isset($_POST['xmlToken'])) {
             In the example above, we use the <classname>Zend_InfoCard</classname> component
             independently to validate the token provided by the user. As was the
             case with the <classname>Zend_Auth_Adapter_InfoCard</classname>, we create an
-            instance of <classname>Zend_InfoCard</classname> and then set one or more SSL
+            instance of <classname>Zend_InfoCard</classname> and then set one or more <acronym>SSL</acronym>
             certificate public/private key pairs used by the web server. Once
             configured, we can use the <methodname>process()</methodname> method to process
             the information card and return the results.

documentation/manual/en/module_specs/Zend_Json-Server.xml

@@ -433,7 +433,7 @@ $server->handle();
 
             <para>
                 At its most basic, a Service Mapping Description indicates the
-                method of transport (POST, GET, TCP/IP, etc), the request
+                method of transport (POST, GET, <acronym>TCP</acronym>/IP, etc), the request
                 envelope type (usually based on the protocol of the server), the
                 target <acronym>URL</acronym> of the service provider, and a map of services
                 available. In the case of <acronym>JSON</acronym>-RPC, the service map is a list of

documentation/manual/en/module_specs/Zend_Loader-Autoloader-Resource.xml

@@ -8,7 +8,7 @@
         follow Zend Framework coding standard guidelines, but which do not have
         a 1:1 mapping between the class name and the directory structure. Their
         primary purpose is to facilitate autoloading application resource code,
-        such as application-specific models, forms, and ACLs.
+        such as application-specific models, forms, and <acronym>ACL</acronym>s.
     </para>
 
     <para>

documentation/manual/en/module_specs/Zend_Locale-Introduction.xml

@@ -128,7 +128,7 @@
             Locale identifiers consist of information about the user's language and preferred/primary geographic region
             (e.g. state or province of home or workplace). The locale identifier strings used in Zend Framework are
             internationally defined standard abbreviations of language and region, written as
-            <code>language_REGION</code>. Both the language and region parts are abbreviated to alphabetic, ASCII
+            <code>language_REGION</code>. Both the language and region parts are abbreviated to alphabetic, <acronym>ASCII</acronym>
             characters.
         </para>
 

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

@@ -21,7 +21,7 @@ $mail->createAttachment($myImage,
 ]]></programlisting>
     </example>
     <para>
-        If you want more control over the MIME part generated for this attachment you can use the return value
+        If you want more control over the <acronym>MIME</acronym> part generated for this attachment you can use the return value
         of <methodname>createAttachment()</methodname> to modify its attributes. The <methodname>createAttachment()</methodname> method
         returns a <classname>Zend_Mime_Part</classname> object:
     </para>

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

@@ -3,8 +3,8 @@
 <sect1 id="zend.mail.boundary">
     <title>Controlling the MIME Boundary</title>
     <para>
-        In a multipart message, a MIME boundary for separating the different parts of the message is normally
-        generated at random. In some cases, however, you might want to specify the MIME boundary that is used.
+        In a multipart message, a <acronym>MIME</acronym> boundary for separating the different parts of the message is normally
+        generated at random. In some cases, however, you might want to specify the <acronym>MIME</acronym> boundary that is used.
         This can be done using the <methodname>setMimeBoundary()</methodname> method, as in the following example:
     </para>
     <example id="zend.mail.boundary.example-1">

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

@@ -6,13 +6,13 @@
         Text and HTML message bodies are encoded with the quotedprintable mechanism by default. Message headers
         are also encoded with the quotedprintable mechanism if you do not specify base64 in <methodname>setHeaderEncoding()</methodname>.
         All other attachments are encoded via base64 if no other encoding is given in the <methodname>addAttachment()</methodname>
-        call or assigned to the MIME part object later. 7Bit and 8Bit encoding currently only pass on the
+        call or assigned to the <acronym>MIME</acronym> part object later. 7Bit and 8Bit encoding currently only pass on the
         binary content data.
     </para>
 
     <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 RFC-2045.
+        its own algorithm to encode quoted printable headers according to <acronym>RFC</acronym>-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_Mail-HtmlMails.xml

@@ -4,8 +4,8 @@
     <title>HTML E-Mail</title>
     <para>
         To send an e-mail in HTML format, set the body using the method <methodname>setBodyHTML()</methodname> instead of
-        <methodname>setBodyText()</methodname>. The MIME content type will automatically be set to <code>text/html</code>
-        then. If you use both HTML and Text bodies, a multipart/alternative MIME message will automatically be
+        <methodname>setBodyText()</methodname>. The <acronym>MIME</acronym> content type will automatically be set to <code>text/html</code>
+        then. If you use both HTML and Text bodies, a multipart/alternative <acronym>MIME</acronym> message will automatically be
         generated:
     </para>
     <example id="zend.mail.html-mails.example-1">

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

@@ -9,7 +9,7 @@
         <title>Getting started</title>
 
         <para>
-            <classname>Zend_Mail</classname> provides generalized functionality to compose and send both text and MIME-compliant
+            <classname>Zend_Mail</classname> provides generalized functionality to compose and send both text and <acronym>MIME</acronym>-compliant
             multipart e-mail messages. Mail can be sent with <classname>Zend_Mail</classname> via the default <classname>Zend_Mail_Transport_Sendmail</classname>
             transport or via <classname>Zend_Mail_Transport_Smtp</classname>.
         </para>

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

@@ -3,11 +3,11 @@
 <sect1 id="zend.mail.smtp-secure">
   <title>Securing SMTP Transport</title>
 
-  <para><classname>Zend_Mail</classname> also supports the use of either TLS or SSL to
+  <para><classname>Zend_Mail</classname> also supports the use of either TLS or <acronym>SSL</acronym> to
   secure a SMTP connection. This can be enabled be passing the 'ssl' parameter
   to the configuration array in the <classname>Zend_Mail_Transport_Smtp</classname>
   constructor with a value of either 'ssl' or 'tls'. A port can optionally be
-  supplied, otherwise it defaults to 25 for TLS or 465 for SSL.</para>
+  supplied, otherwise it defaults to 25 for TLS or 465 for <acronym>SSL</acronym>.</para>
 
   <example id="zend.mail.smtp-secure.example-1">
     <title>Enabling a secure connection within Zend_Mail_Transport_Smtp</title>

documentation/manual/en/module_specs/Zend_Mail_Read.xml

@@ -122,7 +122,7 @@ $mail = new Zend_Mail_Storage_Maildir(array('dirname' =>
         <para>
             For remote storages the two most popular protocols are supported: Pop3 and Imap. Both need at least a host
             and a user to connect and login. The default password is an empty string, the default port as given in the
-            protocol RFC.
+            protocol <acronym>RFC</acronym>.
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -144,7 +144,7 @@ $mail = new Zend_Mail_Storage_Pop3(array('host'     => 'example.com',
 ]]></programlisting>
 
         <para>
-            For both storages SSL and TLS are supported. If you use SSL the default port changes as given in the RFC.
+            For both storages <acronym>SSL</acronym> and TLS are supported. If you use <acronym>SSL</acronym> the default port changes as given in the <acronym>RFC</acronym>.
         </para>
 
         <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Mime.xml

@@ -6,17 +6,17 @@
     <sect2 id="zend.mime.mime.introduction">
         <title>Introduction</title>
         <para>
-            <classname>Zend_Mime</classname> is a support class for handling multipart MIME messages. It is used by <link
+            <classname>Zend_Mime</classname> is a support class for handling multipart <acronym>MIME</acronym> messages. It is used by <link
             linkend="zend.mail"><classname>Zend_Mail</classname></link> and <link
             linkend="zend.mime.message"><classname>Zend_Mime_Message</classname></link> and may be used by applications requiring
-            MIME support.
+            <acronym>MIME</acronym> support.
         </para>
     </sect2>
 
     <sect2 id="zend.mime.mime.static">
     <title>Static Methods and Constants</title>
     <para>
-        <classname>Zend_Mime</classname> provides a simple set of static helper methods to work with MIME:
+        <classname>Zend_Mime</classname> provides a simple set of static helper methods to work with <acronym>MIME</acronym>:
         <itemizedlist>
             <listitem>
                 <para>
@@ -37,7 +37,7 @@
         </itemizedlist>
     </para>
     <para>
-        <classname>Zend_Mime</classname> defines a set of constants commonly used with MIME Messages:
+        <classname>Zend_Mime</classname> defines a set of constants commonly used with <acronym>MIME</acronym> Messages:
         <itemizedlist>
             <listitem>
                 <para>
@@ -91,10 +91,10 @@
     <sect2 id="zend.mime.mime.instantiation">
     <title>Instantiating Zend_Mime</title>
     <para>
-        When Instantiating a <classname>Zend_Mime</classname> Object, a MIME boundary is stored that
+        When Instantiating a <classname>Zend_Mime</classname> Object, a <acronym>MIME</acronym> boundary is stored that
         is used for all subsequent non-static method calls on that object.
         If the constructor is called with a string parameter, this value
-        is used as a MIME boundary. If not, a random MIME boundary is generated
+        is used as a <acronym>MIME</acronym> boundary. If not, a random <acronym>MIME</acronym> boundary is generated
         during construction time.
     </para>
     <para>
@@ -102,17 +102,17 @@
         <itemizedlist>
             <listitem>
                 <para>
-                    <methodname>boundary()</methodname>: Returns the MIME boundary string.
+                    <methodname>boundary()</methodname>: Returns the <acronym>MIME</acronym> boundary string.
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <methodname>boundaryLine()</methodname>: Returns the complete MIME boundary line.
+                    <methodname>boundaryLine()</methodname>: Returns the complete <acronym>MIME</acronym> boundary line.
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <methodname>mimeEnd()</methodname>: Returns the complete MIME end boundary line.
+                    <methodname>mimeEnd()</methodname>: Returns the complete <acronym>MIME</acronym> end boundary line.
                 </para>
             </listitem>
         </itemizedlist>

documentation/manual/en/module_specs/Zend_Mime_Message.xml

@@ -6,10 +6,10 @@
     <sect2 id="zend.mime.message.introduction">
       <title>Introduction</title>
 
-      <para><classname>Zend_Mime_Message</classname> represents a MIME compliant message
+      <para><classname>Zend_Mime_Message</classname> represents a <acronym>MIME</acronym> compliant message
       that can contain one or more separate Parts (Represented as <link
       linkend="zend.mime.part"><classname>Zend_Mime_Part</classname></link> objects). With
-      <classname>Zend_Mime_Message</classname>, MIME compliant multipart messages can be generated from
+      <classname>Zend_Mime_Message</classname>, <acronym>MIME</acronym> compliant multipart messages can be generated from
       <classname>Zend_Mime_Part</classname> objects. Encoding and Boundary handling are handled transparently
       by the class. <classname>Zend_Mime_Message</classname> objects can also be reconstructed from given
       strings (experimental). Used by <link linkend="zend.mail"><classname>Zend_Mail</classname></link>.
@@ -68,7 +68,7 @@
         <title>parsing a string to create a Zend_Mime_Message object
         (experimental)</title>
 
-        <para>A given MIME compliant message in string form can be used to
+        <para>A given <acronym>MIME</acronym> compliant message in string form can be used to
         reconstruct a <classname>Zend_Mime_Message</classname> Object from it.
         <classname>Zend_Mime_Message</classname> has a static factory Method to parse this
         String and return a <classname>Zend_Mime_Message</classname> Object.</para>

documentation/manual/en/module_specs/Zend_Mime_Part.xml

@@ -6,7 +6,7 @@
     <sect2 id="zend.mime.part.introduction">
       <title>Introduction</title>
 
-      <para>This class represents a single part of a MIME message. It contains the
+      <para>This class represents a single part of a <acronym>MIME</acronym> message. It contains the
       actual content of the message part plus information about its encoding,
       content type and original filename. It provides a method for generating a
       string from the stored data. <classname>Zend_Mime_Part</classname> objects can be

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 RFC2822
+                    of <acronym>RFC</acronym>2822
                 </para>
             </listitem>
             <listitem>
@@ -558,7 +558,7 @@ $consumer = new Zend_OpenId_Consumer($storage);
             <listitem>
                 <para>
                     <emphasis>timezone</emphasis>
-                    - an ASCII string from a TimeZone database. For example,
+                    - an <acronym>ASCII</acronym> string from a TimeZone database. For example,
                     "Europe/Paris" or "America/Los_Angeles".
                 </para>
             </listitem>

documentation/manual/en/module_specs/Zend_Search_Lucene-BestPractice.xml

@@ -357,7 +357,7 @@ foreach ($docIds as $id) {
         </para>
 
         <para>
-            You shouldn't be concerned with encoding if you work with pure ASCII data, but you should be careful if this is not the case.
+            You shouldn't be concerned with encoding if you work with pure <acronym>ASCII</acronym> data, but you should be careful if this is not the case.
         </para>
 
         <para>

documentation/manual/en/module_specs/Zend_Search_Lucene-IndexCreation.xml

@@ -200,8 +200,8 @@ $index->optimize();
             <title>MergeFactor auto-optimization option</title>
             <para>
                 <emphasis>MergeFactor</emphasis> determines how often segment indices are merged by addDocument().
-                With smaller values, less RAM is used while indexing, and searches on unoptimized indices are faster,
-                but indexing speed is slower. With larger values, more RAM is used during indexing, and while searches
+                With smaller values, less <acronym>RAM</acronym> is used while indexing, and searches on unoptimized indices are faster,
+                but indexing speed is slower. With larger values, more <acronym>RAM</acronym> is used during indexing, and while searches
                 on unoptimized indices are slower, indexing is faster. Thus larger values (&gt; 10) are best for batch
                 index creation, and smaller values (&lt; 10) for indices that are interactively maintained.
             </para>

documentation/manual/en/module_specs/Zend_Service_Akismet.xml

@@ -320,7 +320,7 @@ $akismet->submitHam($data));
             <listitem>
                 <para>
                     <methodname>getPort()</methodname> and <methodname>setPort()</methodname>
-                    allow you to retrieve and modify the TCP port used to make
+                    allow you to retrieve and modify the <acronym>TCP</acronym> port used to make
                     the request.
                 </para>
             </listitem>

documentation/manual/en/module_specs/Zend_Service_Amazon.xml

@@ -110,7 +110,7 @@ $amazon = new Zend_Service_Amazon('AMAZON_API_KEY', 'JP', 'AMAZON_SECRET_KEY');
         <title>Looking up a Specific Amazon Item by ASIN</title>
         <para>
             The <methodname>itemLookup()</methodname> method provides the ability to fetch a particular Amazon item when
-            the ASIN is known.
+            the <acronym>ASIN</acronym> is known.
         </para>
         <example id="zend.service.amazon.itemlookup.example.asin">
             <title>Looking up a Specific Amazon Item by ASIN</title>

documentation/manual/en/module_specs/Zend_Service_Amazon_Ec2-CloudWatch.xml

@@ -59,7 +59,7 @@ $return = $ec2_ebs->listMetrics();
                     <para>
                         <emphasis>MeasureName</emphasis> The measure name that corresponds to
                         the measure for the gathered metric. Valid <acronym>EC2</acronym> Values are
-                        CPUUtilization, NetworkIn, NetworkOut, DiskWriteOps
+                        <acronym>CPU</acronym>Utilization, NetworkIn, NetworkOut, DiskWriteOps
                         DiskReadBytes, DiskReadOps, DiskWriteBytes. Valid Elastic
                         Load Balancing Metrics are Latency, RequestCount, HealthyHostCount
                         UnHealthyHostCount. <ulink

documentation/manual/en/module_specs/Zend_Service_Amazon_Ec2-Image.xml

@@ -13,7 +13,7 @@
         <example id="zend.service.amazon.ec2.images.register">
             <title>Register an AMI with EC2</title>
             <para>
-                <code>register</code> Each AMI is associated with an unique ID which
+                <code>register</code> Each <acronym>AMI</acronym> is associated with an unique ID which
                 is provided by the Amazon EC2 service through the RegisterImage
                 operation. During registration, Amazon EC2 retrieves the specified
                 image manifest from Amazon S3 and verifies that the image is owned by
@@ -32,8 +32,8 @@ $ip = $ec2_img->register('imageLocation');
         <example id="zend.service.amazon.ec2.images.deregister">
             <title>Deregister an AMI with EC2</title>
             <para>
-                <code>deregister</code>, Deregisters an AMI. Once deregistered, instances
-                of the AMI can no longer be launched.
+                <code>deregister</code>, Deregisters an <acronym>AMI</acronym>. Once deregistered, instances
+                of the <acronym>AMI</acronym> can no longer be launched.
             </para>
             <para>
                 <code>deregister</code> returns boolean true or false.
@@ -48,9 +48,9 @@ $ip = $ec2_img->deregister('imageId');
         <example id="zend.service.amazon.ec2.images.describe">
             <title>Describe an AMI</title>
             <para>
-                <code>describe</code> Returns information about AMIs, AKIs, and ARIs
+                <code>describe</code> Returns information about <acronym>AMI</acronym>s, AKIs, and ARIs
                 available to the user. Information returned includes image type,
-                product codes, architecture, and kernel and RAM disk IDs. Images
+                product codes, architecture, and kernel and <acronym>RAM</acronym> disk IDs. Images
                 available to the user include public images available for any user
                 to launch, private images owned by the user making the request,
                 and private images owned by other users for which the user has
@@ -91,24 +91,24 @@ $ip = $ec2_img->deregister('imageId');
             </table>
             </para>
             <para>
-                The list of AMIs returned can be modified by specifying AMI IDs, AMI owners,
+                The list of <acronym>AMI</acronym>s returned can be modified by specifying <acronym>AMI</acronym> IDs, <acronym>AMI</acronym> owners,
                 or users with launch permissions. If no options are specified, Amazon EC2 returns
-                all AMIs for which the user has launch permissions.
+                all <acronym>AMI</acronym>s for which the user has launch permissions.
             </para>
             <para>
-                If you specify one or more AMI IDs, only AMIs that have the specified IDs are returned.
-                If you specify an invalid AMI ID, a fault is returned. If you specify an AMI ID for which
+                If you specify one or more <acronym>AMI</acronym> IDs, only <acronym>AMI</acronym>s that have the specified IDs are returned.
+                If you specify an invalid <acronym>AMI</acronym> ID, a fault is returned. If you specify an <acronym>AMI</acronym> ID for which
                 you do not have access, it will not be included in the returned results.
             </para>
             <para>
-                If you specify one or more AMI owners, only AMIs from the specified owners and for
+                If you specify one or more <acronym>AMI</acronym> owners, only <acronym>AMI</acronym>s from the specified owners and for
                 which you have access are returned. The results can include the account IDs of the
-                specified owners, amazon for AMIs owned by Amazon or self for AMIs that you own.
+                specified owners, amazon for <acronym>AMI</acronym>s owned by Amazon or self for <acronym>AMI</acronym>s that you own.
             </para>
             <para>
                 If you specify a list of executable users, only users that have launch permissions
-                for the AMIs are returned. You can specify account IDs (if you own the AMI(s)), self
-                for AMIs for which you own or have explicit permissions, or all for public AMIs.
+                for the <acronym>AMI</acronym>s are returned. You can specify account IDs (if you own the <acronym>AMI</acronym>(s)), self
+                for <acronym>AMI</acronym>s for which you own or have explicit permissions, or all for public <acronym>AMI</acronym>s.
             </para>
             <para>
                 <code>describe</code> returns an array for all the images that match the critera that was
@@ -128,7 +128,7 @@ $ip = $ec2_img->describe();
 
         <example id="zend.service.amazon.ec2.images.attribute.modify">
             <title>Modify Image Attributes</title>
-            <para>Modifies an attribute of an AMI</para>
+            <para>Modifies an attribute of an <acronym>AMI</acronym></para>
             <para>
             <table id="zend.service.amazon.ec2.images.attribute.modify-table">
                 <title>Valid Attributes</title>
@@ -188,7 +188,7 @@ $return = $ec2_img->modifyAttribute('imageId',
         <example id="zend.service.amazon.ec2.images.attribute.reset">
             <title>Reset an AMI Attribute</title>
             <para>
-                <code>resetAttribute</code> will reset the attribute of an AMI to its default value.
+                <code>resetAttribute</code> will reset the attribute of an <acronym>AMI</acronym> to its default value.
                 <emphasis>The productCodes attribute cannot be reset.</emphasis>
             </para>
             <programlisting language="php"><![CDATA[
@@ -200,7 +200,7 @@ $return = $ec2_img->resetAttribute('imageId', 'launchPermission');
         <example id="zend.service.amazon.ec2.images.attribute.describe">
             <title>Describe AMI Attribute</title>
             <para>
-                <code>describeAttribute</code> returns information about an attribute of an AMI.
+                <code>describeAttribute</code> returns information about an attribute of an <acronym>AMI</acronym>.
                 Only one attribute can be specified per call. Currently only launchPermission and
                 productCodes are supported.
             </para>

documentation/manual/en/module_specs/Zend_Service_Amazon_Ec2-Instance.xml

@@ -8,14 +8,14 @@
 
         <para>
             Amazon EC2 instances are grouped into two families: standard and
-            High-CPU. Standard instances have memory to CPU ratios suitable
+            High-CPU. Standard instances have memory to <acronym>CPU</acronym> ratios suitable
             for most general purpose applications; High-CPU instances have
-            proportionally more CPU resources than memory (RAM) and are well
+            proportionally more <acronym>CPU</acronym> resources than memory (RAM) and are well
             suited for compute-intensive applications. When selecting instance
             types, you might want to use less powerful instance types for your
             web server instances and more powerful instance types for your
-            database instances. Additionally, you might want to run CPU instance
-            types for CPU-intensive data processing tasks.
+            database instances. Additionally, you might want to run <acronym>CPU</acronym> instance
+            types for <acronym>CPU</acronym>-intensive data processing tasks.
         </para>
         <para>
             One of the advantages of EC2 is that you pay by the instance hour,
@@ -461,7 +461,7 @@ $return = $ec2_instance->consoleOutput('instanceId');
             </para>
             <para>
                 The <code>confirmProduct</code> operation can only be executed by the
-                owner of the AMI. This feature is useful when an AMI owner is providing
+                owner of the <acronym>AMI</acronym>. This feature is useful when an <acronym>AMI</acronym> owner is providing
                 support and wants to verify whether a user's instance is eligible.
             </para>
             <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Service_Amazon_Ec2-Securitygroups.xml

@@ -102,7 +102,7 @@ $return = $ec2_sg->delete('mygroup');
             <para>
                 Permissions are specified by the IP protocol (TCP, UDP or ICMP), the
                 source of the request (by IP range or an Amazon EC2 user-group pair),
-                the source and destination port ranges (for TCP and UDP), and the
+                the source and destination port ranges (for <acronym>TCP</acronym> and UDP), and the
                 ICMP codes and types (for ICMP). When authorizing ICMP, -1 can be used
                 as a wildcard in the type and code fields.
             </para>
@@ -161,7 +161,7 @@ $return = $ec2_sg->authorizeGroup('mygroup', 'securityGroupName', 'ownerId');
             <para>
                 Permissions are specified by the IP protocol (TCP, UDP or ICMP), the
                 source of the request (by IP range or an Amazon EC2 user-group pair),
-                the source and destination port ranges (for TCP and UDP), and the
+                the source and destination port ranges (for <acronym>TCP</acronym> and UDP), and the
                 ICMP codes and types (for ICMP). When authorizing ICMP, -1 can be used
                 as a wildcard in the type and code fields.
             </para>

documentation/manual/en/module_specs/Zend_Service_Amazon_Ec2-WindowsInstance.xml

@@ -26,7 +26,7 @@
         <listitem>
             <para>
                 Simplified Bundling—To bundle a Windows instance, you use a single command
-                that shuts down the instance, saves it as an AMI, and restarts it.
+                that shuts down the instance, saves it as an <acronym>AMI</acronym>, and restarts it.
             </para>
         </listitem>
     </itemizedlist>
@@ -41,14 +41,14 @@
     </para>
     <note>
         <para>
-            To get started using Windows instances, we recommend using the AWS Management Console.
+            To get started using Windows instances, we recommend using the <acronym>AWS</acronym> Management Console.
             There are differences in pricing between Windows and Windows with Authentication
             Services instances. For information on pricing, go to the Amazon EC2 Product Page.
         </para>
     </note>
 
     <para>
-        Amazon EC2 currently provides the following Windows AMIs:
+        Amazon EC2 currently provides the following Windows <acronym>AMI</acronym>s:
     </para>
 
     <itemizedlist>
@@ -67,7 +67,7 @@
     </itemizedlist>
 
     <para>
-        The Windows public AMIs that Amazon provides are unmodified
+        The Windows public <acronym>AMI</acronym>s that Amazon provides are unmodified
         versions of Windows with the following two exceptions: we added
         drivers to improve the networking and disk I/O performance and
         we created the Amazon EC2 configuration service. The Amazon EC2
@@ -79,8 +79,8 @@
             <para>
                 Randomly sets the Administrator password on initial launch,
                 encrypts the password with the user's SSH key, and reports
-                it to the console. This operation happens upon initial AMI
-                launch. If you change the password, AMIs that are created
+                it to the console. This operation happens upon initial <acronym>AMI</acronym>
+                launch. If you change the password, <acronym>AMI</acronym>s that are created
                 from this instance use the new password.
             </para>
         </listitem>
@@ -117,7 +117,7 @@
                 </listitem>
                 <listitem>
                      <para>
-                        <emphasis>s3Prefix</emphasis> The prefix you want to assign to the AMI on S3
+                        <emphasis>s3Prefix</emphasis> The prefix you want to assign to the <acronym>AMI</acronym> on S3
                     </para>
                 </listitem>
                 <listitem>

documentation/manual/en/module_specs/Zend_Service_Amazon_Ec2.xml

@@ -24,7 +24,7 @@
         <para>
             To make using the Ec2 class easier to use there are two static methods that can be
             invoked from any of the Ec2 Elements. The first static method is <code>setKeys</code>
-            which will defind you AWS Access Keys as default keys. When you then create any new
+            which will defind you <acronym>AWS</acronym> Access Keys as default keys. When you then create any new
             object you don't need to pass in any keys to the constructor.
         </para>
         <example id="zend.service.amazon.ec2.staticmethods.setkeys">

documentation/manual/en/module_specs/Zend_Service_Amazon_S3.xml

@@ -238,7 +238,7 @@ foreach($list as $bucket) {
                 <varlistentry><term><constant>S3_CONTENT_TYPE_HEADER</constant></term>
                     <listitem>
                     <para>
-                    MIME content type of the data. If not specified, the type will be guessed according
+                    <acronym>MIME</acronym> content type of the data. If not specified, the type will be guessed according
                     to the file extension of the object name.
                     </para>
                     </listitem>
@@ -312,7 +312,7 @@ echo "Go to http://s3.amazonaws.com/my-own-bucket/Pictures/Me.png to see me!\n";
                         <variablelist>
                         <varlistentry><term><code>type</code></term>
                             <listitem>
-                            <para>The MIME type of the item.</para>
+                            <para>The <acronym>MIME</acronym> type of the item.</para>
                             </listitem>
                         </varlistentry>
                         <varlistentry><term><code>size</code></term>

documentation/manual/en/module_specs/Zend_Service_Amazon_Sqs.xml

@@ -15,7 +15,7 @@
             tasks, without losing messages or requiring each component to be
             always available. Amazon SQS makes it easy to build an automated
             workflow, working in close conjunction with the Amazon Elastic
-            Compute Cloud (Amazon EC2) and the other AWS infrastructure web
+            Compute Cloud (Amazon EC2) and the other <acronym>AWS</acronym> infrastructure web
             services.
         </para>
 

documentation/manual/en/module_specs/Zend_Service_Delicious.xml

@@ -381,7 +381,7 @@ Zend_Rest_Client::getHttpClient()->setConfig(array(
         </example>
         <note>
             <para>
-                When a <classname>Zend_Service_Delicious</classname> object is constructed, the SSL transport
+                When a <classname>Zend_Service_Delicious</classname> object is constructed, the <acronym>SSL</acronym> transport
                 of <classname>Zend_Rest_Client</classname> is set to <code>'ssl'</code> rather than the default of
                 <code>'ssl2'</code>. This is because del.icio.us has some problems with <code>'ssl2'</code>, such
                 as requests taking a long time to complete (around 2 seconds).

documentation/manual/en/module_specs/Zend_Text_Figlet.xml

@@ -5,7 +5,7 @@
     <para>
         <classname>Zend_Text_Figlet</classname> is a component which enables developers to
         create a so called FIGlet text. A FIGlet text is a string, which is
-        represented as ASCII art. FIGlets use a special font format, called
+        represented as <acronym>ASCII</acronym> art. FIGlets use a special font format, called
         FLT (FigLet Font). By default, one standard font is shipped with
         <classname>Zend_Text_Figlet</classname>, but you can download additional fonts at
         <ulink url="http://www.figlet.org/fontdb.cgi">http://www.figlet.org</ulink>.

documentation/manual/en/module_specs/Zend_Uri.xml

@@ -117,7 +117,7 @@ $valid = Zend_Uri::check('http://uri.in.question');
 
         <para>
             By default, <classname>Zend_Uri</classname> will not accept the following characters, defined by
-            the RFC as "unwise" and invalid: <code>"{", "}", "|", "\", "^", "`"</code>.
+            the <acronym>RFC</acronym> as "unwise" and invalid: <code>"{", "}", "|", "\", "^", "`"</code>.
             However, many implementations do accept these characters as valid.
         </para>
 

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 RFC2822. For example, valid emails include <code>bob@domain.com</code>,
+        according to <acronym>RFC</acronym>2822. 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>

documentation/manual/en/module_specs/Zend_View-Helpers-HeadScript.xml

@@ -205,7 +205,7 @@ $('foo_form').action = action;
             </para></listitem>
 
             <listitem><para>
-                    The script MIME type is assumed to be 'text/javascript'; if you
+                    The script <acronym>MIME</acronym> type is assumed to be 'text/javascript'; if you
                     wish to specify a different type, you will need to pass it
                     as the second argument to <methodname>captureStart()</methodname>.
             </para></listitem>

documentation/manual/en/module_specs/Zend_View-Helpers-Navigation.xml

@@ -82,13 +82,13 @@
         <listitem>
             <para>
                 <code>{get|set}Acl()</code>, <code>{get|set}Role()</code>,
-                gets/sets ACL (<classname>Zend_Acl</classname>) instance and
+                gets/sets <acronym>ACL</acronym> (<classname>Zend_Acl</classname>) instance and
                 role (<type>String</type> or
                 <classname>Zend_Acl_Role_Interface</classname>) used for
                 filtering out pages when rendering, and
-                <code>{get|set}UseAcl()</code> controls whether ACL should
+                <code>{get|set}UseAcl()</code> controls whether <acronym>ACL</acronym> should
                 be enabled. The methods <methodname>hasAcl()</methodname> and
-                <methodname>hasRole()</methodname> checks if the helper has an ACL
+                <methodname>hasRole()</methodname> checks if the helper has an <acronym>ACL</acronym>
                 instance or a role registered.
             </para>
         </listitem>
@@ -184,13 +184,13 @@
         <listitem>
             <para>
                 <code>static setDefaultAcl()</code> is used for setting
-                a defualt ACL object that will be used by helpers.
+                a defualt <acronym>ACL</acronym> object that will be used by helpers.
             </para>
         </listitem>
         <listitem>
             <para>
                 <code>static setDefaultRole()</code> is used for setting
-                a default ACL that will be used by helpers
+                a default <acronym>ACL</acronym> that will be used by helpers
             </para>
         </listitem>
     </itemizedlist>
@@ -262,32 +262,32 @@ $this->navigation()->addPage(array(
         <title>Integration with ACL</title>
 
         <para>
-            All navigational view helpers support ACL inherently from the
+            All navigational view helpers support <acronym>ACL</acronym> inherently from the
             class <classname>Zend_View_Helper_Navigation_HelperAbstract</classname>.
             A <classname>Zend_Acl</classname> object can be assigned to
             a helper instance with <code>$helper->setAcl($acl)</code>, and role
             with <code>$helper->setRole('member')</code> or
-            <code>$helper->setRole(new Zend_Acl_Role('member'))</code> . If ACL
+            <code>$helper->setRole(new Zend_Acl_Role('member'))</code> . If <acronym>ACL</acronym>
             is used in the helper, the role in the helper must be allowed by
-            the ACL to access a page's <code>resource</code> and/or have the
+            the <acronym>ACL</acronym> to access a page's <code>resource</code> and/or have the
             page's <code>privilege</code> for the page to be included when
             rendering.
         </para>
 
         <para>
-            If a page is not accepted by ACL, any descendant page will also
+            If a page is not accepted by <acronym>ACL</acronym>, any descendant page will also
             be excluded from rendering.
         </para>
 
         <para>
             The
             <link linkend="zend.view.helpers.initial.navigation.navigation">proxy
-            helper</link> will inject its own ACL and role to the helper it
+            helper</link> will inject its own <acronym>ACL</acronym> and role to the helper it
             proxies to if the proxied helper doesn't already have any.
         </para>
 
         <para>
-            The examples below all show how ACL affects rendering.
+            The examples below all show how <acronym>ACL</acronym> affects rendering.
         </para>
     </sect4>
 
@@ -325,7 +325,7 @@ $this->navigation()->addPage(array(
             </listitem>
             <listitem>
                 <para>
-                    The assumed ACL and router setup is shown below the
+                    The assumed <acronym>ACL</acronym> and router setup is shown below the
                     container setup.
                 </para>
             </listitem>
@@ -1321,7 +1321,7 @@ Output:
             <para>
                 This example shows how to render a menu from a container
                 registered/found in the view helper. Notice how pages
-                are filtered out based on visibility and ACL.
+                are filtered out based on visibility and <acronym>ACL</acronym>.
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -1973,7 +1973,7 @@ echo $this->navigation()->sitemap();
 
             <para>
                 Notice how pages that are invisible or pages with
-                ACL roles incompatible with the view helper are filtered
+                <acronym>ACL</acronym> roles incompatible with the view helper are filtered
                 out:
             </para>
 
@@ -2035,7 +2035,7 @@ echo $this->navigation()->sitemap();
 ]]></programlisting>
 
             <para>
-                Render the sitemap using no ACL role (should filter out
+                Render the sitemap using no <acronym>ACL</acronym> role (should filter out
                 /community/account):
             </para>
 
@@ -2175,7 +2175,7 @@ echo $this->navigation()
 
         <para>
             When proxying to other helpers, the Navigation helper can inject
-            its container, ACL/role, and translator. This means that you
+            its container, <acronym>ACL</acronym>/role, and translator. This means that you
             won't have to explicitly set all three in all navigational
             helpers, nor resort to injecting by means of
             <classname>Zend_Registry</classname> or static methods.
@@ -2186,7 +2186,7 @@ echo $this->navigation()
                <para>
                    <methodname>findHelper()</methodname> finds the given helper,
                    verifies that it is a navigational helper, and injects
-                   container, ACL/role and translator.
+                   container, <acronym>ACL</acronym>/role and translator.
                </para>
            </listitem>
            <listitem>
@@ -2199,7 +2199,7 @@ echo $this->navigation()
            <listitem>
                <para>
                    <code>{get|set}InjectAcl()</code> gets/sets a flag
-                   indicating whether the ACL/role should be injected to
+                   indicating whether the <acronym>ACL</acronym>/role should be injected to
                    proxied helpers. Default is <constant>TRUE</constant>.
                </para>
            </listitem>