[MANUAL] English:

- manual fixes

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

documentation/manual/en/module_specs/Zend_Config_Writer.xml

@@ -2,6 +2,7 @@
 <!-- Reviewed: no -->
 <sect1 id="zend.config.writer.introduction">
     <title>Zend_Config_Writer</title>
+
     <para>
         <classname>Zend_Config_Writer</classname> gives you the ability to write config
         files out of <classname>Zend_Config</classname> objects. It works with an
@@ -37,8 +38,8 @@
     <para>
         The Ini writer has two modes for rendering with regard to sections.
         By default the top-level configuration is always written into section names.
-        By calling <code>$writer->setRenderWithoutSections()</code> all options are written
-        into the global namespace of the INI file and no sections are applied.
+        By calling <command>$writer->setRenderWithoutSections();</command> all options are written
+        into the global namespace of the <acronym>INI</acronym> file and no sections are applied.
     </para>
 
     <para>
@@ -135,9 +136,9 @@ $writer->write();
     </note>
 
     <para>
-        For all the File-Based writers (INI, XML and PHP Array) internally
-        the <methodname>render()</methodname> is used to build the configuration
-        string. This method can be used from the outside also if you need
+        For all the File-Based writers (<acronym>INI</acronym>, <acronym>XML</acronym> and
+        <acronym>PHP</acronym> Array) internally the <methodname>render()</methodname> is used to
+        build the configuration string. This method can be used from the outside also if you need
         to access the string-representation of the configuration data.
     </para>
 </sect1>

documentation/manual/en/module_specs/Zend_Controller-Plugins-PutHandler.xml

@@ -5,10 +5,10 @@
 
     <para>
         <classname>Zend_Controller_Plugin_PutHandler</classname> provides a drop-in
-        plugin for marshalling PUT request bodies into request parameters, just
-        like POST request bodies. It will inspect the request and, if PUT, will
-        use parse_str to parse the raw PUT body into an array of params
-        which is then set on the request. E.g.,
+        plugin for marshalling <acronym>PUT</acronym> request bodies into request parameters, just
+        like <acronym>POST</acronym> request bodies. It will inspect the request and, if
+        <acronym>PUT</acronym>, will use parse_str to parse the raw <acronym>PUT</acronym> body into
+        an array of params which is then set on the request. E.g.,
     </para>
 
     <programlisting language="txt"><![CDATA[
@@ -28,7 +28,7 @@ $front->registerPlugin(new Zend_Controller_Plugin_PutHandler());
 ]]></programlisting>
 
     <para>
-        Then you can access the PUT body params by name from the request inside
+        Then you can access the <acronym>PUT</acronym> body params by name from the request inside
         your controller:
     </para>
 

documentation/manual/en/module_specs/Zend_Controller-Router-Route-Rest.xml

@@ -28,39 +28,39 @@
             </thead>
             <tbody>
                 <row>
-                    <entry>GET</entry>
+                    <entry><acronym>GET</acronym></entry>
                     <entry><filename>/product/ratings/</filename></entry>
                     <entry><methodname>Product_RatingsController::indexAction()</methodname></entry>
                 </row>
                 <row>
-                    <entry>GET</entry>
+                    <entry><acronym>GET</acronym></entry>
                     <entry><filename>/product/ratings/:id</filename></entry>
                     <entry><methodname>Product_RatingsController::getAction()</methodname></entry>
                 </row>
                 <row>
-                    <entry>POST</entry>
+                    <entry><acronym>POST</acronym></entry>
                     <entry><filename>/product/ratings</filename></entry>
                     <entry><methodname>Product_RatingsController::postAction()</methodname></entry>
                 </row>
                 <row>
-                    <entry>PUT</entry>
+                    <entry><acronym>PUT</acronym></entry>
                     <entry><filename>/product/ratings/:id</filename></entry>
                     <entry><methodname>Product_RatingsController::putAction()</methodname></entry>
                 </row>
                 <row>
-                    <entry>DELETE</entry>
+                    <entry><acronym>DELETE</acronym></entry>
                     <entry><filename>/product/ratings/:id</filename></entry>
                     <entry>
                         <methodname>Product_RatingsController::deleteAction()</methodname>
                     </entry>
                 </row>
                 <row>
-                    <entry>POST</entry>
+                    <entry><acronym>POST</acronym></entry>
                     <entry><command>/product/ratings/:id?_method="PUT"</command></entry>
                     <entry><methodname>Product_RatingsController::putAction()</methodname></entry>
                 </row>
                 <row>
-                    <entry>POST</entry>
+                    <entry><acronym>POST</acronym></entry>
                     <entry><command>/product/ratings/:id?_method="DELETE"</command></entry>
                     <entry>
                         <methodname>Product_RatingsController::deleteAction()</methodname>

documentation/manual/en/module_specs/Zend_Translate-Plurals.xml

@@ -26,7 +26,7 @@
     </para>
 
     <para>
-        There are two way for using plurals... the traditional one, which means that you use a own
+        There are two ways for using plurals... the traditional one, which means that you use a own
         method, and a modern one, which allows you to do plural translations with the same method
         as normal translations.
     </para>