[MANUAL] English:

- manual fixes

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

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

@@ -498,7 +498,7 @@ private function getContactHandler(event:ResultEvent):void {
 Zend_Amf_Parse_TypeLoader::addResourceDirectory(
     "My",
     "application/library/resources/My"
-));
+);
 ]]></programlisting>
 
         <para>

documentation/manual/en/tutorials/paginator-simple.xml

@@ -5,11 +5,11 @@
 
     <para>
         In this first example we won't do anything spectacular, but hopefully it will
-        give you a good idea of what Zend_Paginator is designed to do.
+        give you a good idea of what <classname>Zend_Paginator</classname> is designed to do.
         Let's say we have an array called $data with the numbers 1 to 100 in it, which
-        we want to divide over a number of pages. We can use the static <methodname>factory()</methodname>
-        method in the <classname>Zend_Paginator</classname> class to get a <classname>Zend_Paginator</classname>
-        object with our array in it.
+        we want to divide over a number of pages. We can use the static
+        <methodname>factory()</methodname> method in the <classname>Zend_Paginator</classname>
+        class to get a <classname>Zend_Paginator</classname> object with our array in it.
     </para>
 
     <programlisting language="php"><![CDATA[
@@ -49,7 +49,8 @@ foreach ($paginator as $item) {
 
     <para>
         Now let's try and render the items on the second page. You can use the
-        <methodname>setCurrentPageNumber()</methodname> method to select which page you want to view.
+        <methodname>setCurrentPageNumber()</methodname> method to select which page you want to
+        view.
     </para>
 
     <programlisting language="php"><![CDATA[
@@ -79,10 +80,10 @@ foreach ($paginator as $item) {
 
     <para>
         These simple examples demonstrate a small portion of what can be achieved with
-        <classname>Zend_Paginator</classname>. However, a real application rarely reads its data from a plain
-        array, so the next section is dedicated to showing you how you can use Paginator
-        to paginate the results of a database query. Before reading on, make sure you're familiar with
-        the way <classname>Zend_Db_Select</classname> works!
+        <classname>Zend_Paginator</classname>. However, a real application rarely reads its data
+        from a plain array, so the next section is dedicated to showing you how you can use
+        Paginator to paginate the results of a database query. Before reading on, make sure you're
+        familiar with the way <classname>Zend_Db_Select</classname> works!
     </para>
 
     <para>
@@ -117,8 +118,8 @@ foreach ($paginator as $item) {
         The only difference is that you pass a <classname>Zend_Db_Select</classname> object to the
         Paginator's <methodname>factory()</methodname> method, rather than an array.
         For more details on how the database adapter makes sure that your query
-        is being executed efficiently, see the Zend_Paginator chapter in the reference manual
-        on the DbSelect and DbTableSelect adapters.
+        is being executed efficiently, see the <classname>Zend_Paginator</classname> chapter in the
+        reference manual on the DbSelect and DbTableSelect adapters.
     </para>
 
 </sect1>

documentation/manual/en/tutorials/quickstart-create-form.xml

@@ -69,8 +69,9 @@ class Default_Form_Guestbook extends Zend_Form
 ]]></programlisting>
 
     <para>
-        The above form defines five elements: an email address field, a comment field, a CAPTCHA for
-        preventing spam submissions, a submit button, and a CSRF protection token.
+        The above form defines five elements: an email address field, a comment field, a
+        <acronym>CAPTCHA</acronym> for preventing spam submissions, a submit button, and a
+        <acronym>CSRF</acronym> protection token.
     </para>
 
     <para>
@@ -94,9 +95,10 @@ C:> zf.bat create action sign guestbook
 
     <para>
         Let's add some logic into our guestbook controller's sign action. We need to first check if
-        we're getting a POST or a GET request; in the latter case, we'll simply display the form.
-        However, if we get a POST request, we'll want to validate the posted data against our form,
-        and, if valid, create a new entry and save it. The logic might look like this:
+        we're getting a <acronym>POST</acronym> or a <acronym>GET</acronym> request; in the latter
+        case, we'll simply display the form. However, if we get a <acronym>POST</acronym> request,
+        we'll want to validate the posted data against our form, and, if valid, create a new entry
+        and save it. The logic might look like this:
     </para>
 
     <programlisting language="php"><![CDATA[
@@ -125,7 +127,8 @@ class GuestbookController extends Zend_Controller_Action
 ]]></programlisting>
 
     <para>
-        Of course, we also need to edit the view script; edit <filename>application/views/scripts/guestbook/sign.phtml</filename> to read:
+        Of course, we also need to edit the view script; edit
+        <filename>application/views/scripts/guestbook/sign.phtml</filename> to read:
     </para>
 
     <programlisting language="php"><![CDATA[

documentation/manual/en/tutorials/quickstart-intro-mvc.xml

@@ -77,7 +77,7 @@
             <itemizedlist>
                 <listitem>
                     <para>
-                        <emphasis role="strong">Model</emphasis> - This is the part of your
+                        <emphasis>Model</emphasis> - This is the part of your
                         application that defines its basic functionality behind a set of
                         abstractions. Data access routines and some business logic can be defined in
                         the model.
@@ -86,7 +86,7 @@
 
                 <listitem>
                     <para>
-                        <emphasis role="strong">View</emphasis> - Views define exactly what is
+                        <emphasis>View</emphasis> - Views define exactly what is
                         presented to the user. Usually controllers pass data to each view to render
                         in some format. Views will often collect data from the user, as well. This
                         is where you're likely to find <acronym>HTML</acronym> markup in your
@@ -96,7 +96,7 @@
 
                 <listitem>
                     <para>
-                        <emphasis role="strong">Controller</emphasis> - Controllers bind the whole
+                        <emphasis>Controller</emphasis> - Controllers bind the whole
                         pattern together. They manipulate models, decide which view to display based
                         on the user's request and other factors, pass along the data that each view
                         will need, or hand off control to another controller entirely. Most