[MANUAL] English:

- some manual fixes

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

documentation/manual/en/module_specs/Zend_Db_Table_Rowset.xml

@@ -1,11 +1,9 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
 <sect1 id="zend.db.table.rowset">
-
     <title>Zend_Db_Table_Rowset</title>
 
     <sect2 id="zend.db.table.rowset.introduction">
-
         <title>Introduction</title>
 
         <para>
@@ -195,7 +193,7 @@ $row9->save();
 
         <para>
             After you have access to an individual Row object, you can manipulate the Row using
-            methods described in <xref linkend="zend.db.table.row" />.
+            methods described in <link linkend="zend.db.table.row">Zend_Db_Table_Row</link>.
         </para>
 
     </sect2>

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

@@ -1,7 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
 <sect2 id="zend.validate.set.in_array">
-
     <title>InArray</title>
 
     <para>
@@ -28,12 +27,14 @@ if ($validator->isValid('value')) {
 ]]></programlisting>
 
         <para>
-            This will behave exactly like <acronym>PHP</acronym>'s <methodname>in_array()</methodname> method.
+            This will behave exactly like <acronym>PHP</acronym>'s
+            <methodname>in_array()</methodname> method.
         </para>
 
         <note>
             <para>
-                Per default this validation is not strict nor can it validate multidimensional arrays.
+                Per default this validation is not strict nor can it validate multidimensional
+                arrays.
             </para>
         </note>
 
@@ -59,15 +60,15 @@ if ($validator->isValid('value')) {
         <title>Strict array validation</title>
 
         <para>
-            As mentioned before you can also do a strict validation within the array. Per default there
-            would be no difference between the integer value <emphasis>0</emphasis> and the string
-            <emphasis>"0"</emphasis>. When doing a strict validation this difference will also be
-            validated and only same types are accepted.
+            As mentioned before you can also do a strict validation within the array. Per default
+            there would be no difference between the integer value <emphasis>0</emphasis> and the
+            string <emphasis>"0"</emphasis>. When doing a strict validation this difference will
+            also be validated and only same types are accepted.
         </para>
 
         <para>
-            A strict validation can also be done by using two different ways. At initiation and by using
-            a method. At initiation you have to give an array with the following structure:
+            A strict validation can also be done by using two different ways. At initiation and by
+            using a method. At initiation you have to give an array with the following structure:
         </para>
 
         <programlisting language="php"><![CDATA[

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

@@ -6,8 +6,8 @@
 
     <para>
         <classname>Zend_Validate_PostCode</classname> allows you to determine if a given value is a
-        valid postal code. Postal codes are specific to cities, and in some locales termed ZIP
-        codes.
+        valid postal code. Postal codes are specific to cities, and in some locales termed
+        <acronym>ZIP</acronym> codes.
     </para>
 
     <para>
@@ -19,7 +19,7 @@
     <para>
         Using a locale is more convenient as Zend Framework already knows the appropriate postal
         code format for each locale; however, you need to use the fully qualified locale (one
-        containing a region specifier) to do so.  For instance, the locale "de" is a locale but
+        containing a region specifier) to do so. For instance, the locale "de" is a locale but
         could not be used with <classname>Zend_Validate_PostCode</classname> as it does not include
         the region; "de_AT", however, would be a valid locale, as it specifies the region code
         ("AT", for Austria).

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

@@ -4,8 +4,9 @@
     <title>Sitemap Validators</title>
 
     <para>
-        The following validators conform to the
-        <ulink url="http://www.sitemaps.org/protocol.php">Sitemap <acronym>XML</acronym> protocol</ulink>.
+        The following validators conform to the <ulink
+            url="http://www.sitemaps.org/protocol.php">Sitemap <acronym>XML</acronym>
+            protocol</ulink>.
     </para>
 
     <sect3 id="zend.validate.sitemap.changefreq">
@@ -28,7 +29,7 @@
         <para>
             Validates whether a string is valid for using as a 'lastmod'
             element in a Sitemap <acronym>XML</acronym> document. The lastmod element should
-            contain a W3C date string, optionally discarding information
+            contain a <acronym>W3C</acronym> date string, optionally discarding information
             about time.
         </para>
         <para>

documentation/manual/en/module_specs/Zend_View-Abstract.xml

@@ -7,7 +7,8 @@
         <classname>Zend_View_Abstract</classname> is the base class on which
         <classname>Zend_View</classname> is built; <classname>Zend_View</classname> itself simply
         extends it and declares a concrete implementation of the
-        <methodname>_run()</methodname> method (which is invoked by <methodname>render()</methodname>).
+        <methodname>_run()</methodname> method (which is invoked by
+        <methodname>render()</methodname>).
     </para>
 
     <para>
@@ -20,8 +21,9 @@
 
     <para>
         <classname>Zend_View</classname> is something of an anti-templating engine in that
-        it uses <acronym>PHP</acronym> natively for its templating. As a result, all of <acronym>PHP</acronym> is
-        available, and view scripts inherit the scope of their calling object.
+        it uses <acronym>PHP</acronym> natively for its templating. As a result, all of
+        <acronym>PHP</acronym> is available, and view scripts inherit the scope of their calling
+        object.
     </para>
 
     <para>