[DOCUMENTATION] English:

 - fix typos

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

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

@@ -6,32 +6,32 @@
     <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 
+        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.,
     </para>
 
     <programlisting language="txt"><![CDATA[
 PUT /notes/5.xml HTTP/1.1
-    
+
 title=Hello&body=World
 ]]></programlisting>
 
     <para>
-        To receive the 'title' and 'body' params as regular request params, 
+        To receive the 'title' and 'body' params as regular request params,
         register the plugin:
     </para>
-    
+
     <programlisting language="php"><![CDATA[
 $front = Zend_Controller_Front::getInstance();
 $front->registerPlugin(new Zend_Controller_Plugin_PutHandler());
 ]]></programlisting>
-            
+
     <para>
         Then you can access the PUT body params by name from the request inside
         your controller:
     </para>
-    
+
     <programlisting language="php"><![CDATA[
 ...
 public function putAction()

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

@@ -5,13 +5,13 @@
 
     <para>
         The <classname>Zend_Rest</classname> component contains a RESTful route
-        for <classname>Zend_Controller_Router_Rewrite</classname>. This route
+        for <classname>Zend_Controller_Router_Rewrite</classname>.  This route
         offers a standardized routing scheme that routes requests by translating
-        the <acronym>HTTP</acronym> method and the <acronym>URI</acronym>
-        to a module, controller, and action. The table below provides an overview
-        of how request methods and <acronym>URI</acronym>'s are routed.
+        the HTTP method and the URI to a module, controller, and action.  The
+        table below provides an overview of how request methods and URI's are
+        routed.
     </para>
-    
+
     <table frame="all">
         <title>Zend_Rest_Route Behavior</title>
 
@@ -22,49 +22,45 @@
             <thead>
                 <row>
                     <entry>Method</entry>
-                    <entry><acronym>URI</acronym></entry>
+                    <entry>URI</entry>
                     <entry>Module_Controller::action</entry>
                 </row>
             </thead>
             <tbody>
                 <row>
                     <entry>GET</entry>
-                    <entry><filename>/product/ratings/</filename></entry>
-                    <entry><methodname>Product_RatingsController::indexAction()</methodname></entry>
+                    <entry>/product/ratings/</entry>
+                    <entry>Product_RatingsController::indexAction()</entry>
                 </row>
                 <row>
                     <entry>GET</entry>
-                    <entry><filename>/product/ratings/:id</filename></entry>
-                    <entry><methodname>Product_RatingsController::getAction()</methodname></entry>
+                    <entry>/product/ratings/:id</entry>
+                    <entry>Product_RatingsController::getAction()</entry>
                 </row>
                 <row>
                     <entry>POST</entry>
-                    <entry><filename>/product/ratings</filename></entry>
-                    <entry><methodname>Product_RatingsController::postAction()</methodname></entry>
+                    <entry>/product/ratings</entry>
+                    <entry>Product_RatingsController::postAction()</entry>
                 </row>
                 <row>
                     <entry>PUT</entry>
-                    <entry><filename>/product/ratings/:id</filename></entry>
-                    <entry><methodname>Product_RatingsController::putAction()</methodname></entry>
+                    <entry>/product/ratings/:id</entry>
+                    <entry>Product_RatingsController::putAction()</entry>
                 </row>
                 <row>
                     <entry>DELETE</entry>
-                    <entry><filename>/product/ratings/:id</filename></entry>
-                    <entry>
-                        <methodname>Product_RatingsController::deleteAction()</methodname>
-                    </entry>
+                    <entry>/product/ratings/:id</entry>
+                    <entry>Product_RatingsController::deleteAction()</entry>
                 </row>
                 <row>
                     <entry>POST</entry>
-                    <entry><filename>/product/ratings/:id?_method="PUT"</filename></entry>
-                    <entry><methodname>Product_RatingsController::putAction()</methodname></entry>
+                    <entry><literallayout>/product/ratings/:id?_method="PUT"</literallayout></entry>
+                    <entry>Product_RatingsController::putAction()</entry>
                 </row>
                 <row>
                     <entry>POST</entry>
-                    <entry><filename>/product/ratings/:id?_method="DELETE"</filename></entry>
-                    <entry>
-                        <methodname>Product_RatingsController::deleteAction()</methodname>
-                    </entry>
+                    <entry><literallayout>/product/ratings/:id?_method="DELETE"</literallayout></entry>
+                    <entry>Product_RatingsController::deleteAction()</entry>
                 </row>
             </tbody>
         </tgroup>
@@ -74,7 +70,7 @@
         To enable <classname>Zend_Rest_Route</classname> for an entire
         application, construct it with no config params and add it as the
         default route on the front controller:
-    </para> 
+    </para>
 
     <programlisting language="php"><![CDATA[
 $front     = Zend_Controller_Front::getInstance();
@@ -94,7 +90,7 @@ $front->getRouter()->addRoute('default', $restRoute);
         To enable <classname>Zend_Rest_Route</classname> for specific modules,
         construct it with an array of module names as the 3rd constructor
         argument:
-    </para> 
+    </para>
 
     <programlisting language="php"><![CDATA[
 $front     = Zend_Controller_Front::getInstance();
@@ -106,7 +102,7 @@ $front->getRouter()->addRoute('rest', $restRoute);
         To enable <classname>Zend_Rest_Route</classname> for specific
         controllers, add an array of controller names as the value of each
         module array element.
-    </para> 
+    </para>
 
     <programlisting language="php"><![CDATA[
 $front     = Zend_Controller_Front::getInstance();
@@ -120,46 +116,36 @@ $front->getRouter()->addRoute('rest', $restRoute);
         <title>Zend_Rest_Controller</title>
 
         <para>
-            To help guide development of Controllers for use with 
+            To help guide development of Controllers for use with
             <classname>Zend_Rest_Route</classname>, extend your Controllers from
             <classname>Zend_Rest_Controller</classname>.
             <classname>Zend_Rest_Controller</classname> defines the 5 most-commonly
             needed operations for RESTful resources in the form of abstract action
             methods.
         </para>
-    
+
         <itemizedlist>
             <listitem>
-                <para>
-                    <emphasis><methodname>indexAction()</methodname></emphasis> - 
-                    Should retrieve an index of resources and assign it to view.
-                </para>
+                <emphasis><methodname>indexAction</methodname></emphasis> -
+                Should retrieve an index of resources and assign it to view.
             </listitem>
             <listitem>
-                <para>
-                    <emphasis><methodname>getAction()</methodname></emphasis> - 
-                    Should retrieve a single resource identified by <acronym>URI</acronym>
-                    and assign it to view.
-                </para>
+                <emphasis><methodname>getAction</methodname></emphasis> -
+                Should retrieve a single resource identified by URI and assign
+                it to view.
             </listitem>
             <listitem>
-                <para>
-                    <emphasis><methodname>postAction()</methodname></emphasis> - 
-                    Should accept a new single resource and persist its state.
-                </para>
+                <emphasis><methodname>postAction</methodname></emphasis> -
+                Should accept a new single resource and persist its state.
             </listitem>
             <listitem>
-                <para>
-                    <emphasis><methodname>putAction()</methodname></emphasis> - 
-                    Should accept a single resource idenitifed by <acronym>URI</acronym>
-                    and persist its state.
-                </para>
+                <emphasis><methodname>putAction</methodname></emphasis> -
+                Should accept a single resource identified by URI and persist
+                its state.
             </listitem>
             <listitem>
-                <para>
-                    <emphasis><methodname>deleteAction()</methodname></emphasis> - 
-                    Should delete a single resource identified by <acronym>URI</acronym>.
-                </para>
+                <emphasis><methodname>deleteAction</methodname></emphasis> -
+                Should delete a single resource identified by URI.
             </listitem>
         </itemizedlist>
 

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

@@ -422,7 +422,7 @@ $client = new Zend_Http_Client($uri, $config);
 
         <para>
             By default the cURL adapter is configured to behave exactly like
-            the Socket Adapter and it also accepts the same configuration parameters 
+            the Socket Adapter and it also accepts the same configuration parameters
             as the Socket and Proxy adapters. You can also change the cURL options by either specifying
             the 'curloptions' key in the constructor of the adapter or by calling
             <code>setCurlOption($name, $value)</code>. The <code>$name</code> key

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

@@ -310,7 +310,7 @@ $queue = Zend_Queue::factory('Db', $options);
                 While Apache's ActiveMQ will support multiple subscriptions, the
                 <classname>Zend_Queue</classname> does not. You must create a
                 new <classname>Zend_Queue</classname> object for each individual
-                subcription.
+                subscription.
             </para>
 
             <para>

documentation/manual/en/module_specs/Zend_Queue-Custom.xml

@@ -14,7 +14,7 @@
             or the abstract class
             <classname>Zend_Queue_Adapter_AdapterAbstract</classname>. I
             suggest reviewing <classname>Zend_Queue_Adapter_Array</classname> as
-            this adapter is the easist to conceptualize.
+            this adapter is the easiest to conceptualize.
         </para>
 
         <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Queue-Framework.xml

@@ -156,7 +156,7 @@ foreach ($messages as $i => $message) {
 
             <listitem>
                 <para>
-                    <methodname>isExists()</methodname> - checks the existance of a queue
+                    <methodname>isExists()</methodname> - checks the existence of a queue
                 </para>
             </listitem>
         </itemizedlist>

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

@@ -11,7 +11,7 @@
     <para>
         A message queue is a method for distributed processing. For example, a
         Job Broker application may accept multiple applications for jobs from
-        a varity of sources.
+        a variety of sources.
     </para>
 
     <para>