[MANUAL] English:

- manual fixes

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

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

@@ -1,7 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
 <sect1 id="zend.validate.validator_chains">
-
     <title>Validator Chains</title>
 
     <para>
@@ -34,19 +33,19 @@ if ($validatorChain->isValid($username)) {
         12 characters, and then it is checked to ensure that it contains only alphanumeric
         characters. The second validation, for alphanumeric characters, is performed regardless of
         whether the first validation, for length between 6 and 12 characters, succeeds. This means
-        that if both validations fail, <methodname>getMessages()</methodname> will return failure messages from
-        both validators.
+        that if both validations fail, <methodname>getMessages()</methodname> will return failure
+        messages from both validators.
     </para>
 
     <para>
         In some cases it makes sense to have a validator break the chain if its validation process
         fails. <classname>Zend_Validate</classname> supports such use cases with the second
         parameter to the <methodname>addValidator()</methodname> method. By setting
-        <varname>$breakChainOnFailure</varname> to <constant>TRUE</constant>, the added validator will break the
-        chain execution upon failure, which avoids running any other validations that are determined
-        to be unnecessary or inappropriate for the situation. If the above example were written as
-        follows, then the alphanumeric validation would not occur if the string length validation
-        fails:
+        <varname>$breakChainOnFailure</varname> to <constant>TRUE</constant>, the added validator
+        will break the chain execution upon failure, which avoids running any other validations that
+        are determined to be unnecessary or inappropriate for the situation. If the above example
+        were written as follows, then the alphanumeric validation would not occur if the string
+        length validation fails:
 
         <programlisting language="php"><![CDATA[
 $validatorChain->addValidator(

documentation/manual/en/module_specs/Zend_Validate.xml

@@ -1,7 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
 <sect1 id="zend.validate.introduction">
-
     <title>Introduction</title>
 
     <para>
@@ -12,7 +11,6 @@
     </para>
 
     <sect2 id="zend.validate.introduction.definition">
-
         <title>What is a validator?</title>
 
         <para>
@@ -342,9 +340,9 @@ $validator->setTranslator($translate);
         <para>
             With the static <methodname>setDefaultTranslator()</methodname> method you can set
             a instance of <classname>Zend_Translate</classname> which will be used for all
-            validation classes, and can be retrieved with <methodname>getDefaultTranslator()</methodname>.
-            This prevents you from setting a translator manually for all validator classes,
-            and simplifies your code.
+            validation classes, and can be retrieved with
+            <methodname>getDefaultTranslator()</methodname>. This prevents you from setting a
+            translator manually for all validator classes, and simplifies your code.
         </para>
 
         <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Version.xml

@@ -13,8 +13,8 @@
 
     <para>
         The static method <methodname>Zend_Version::compareVersion($version)</methodname>
-        is based on the <acronym>PHP</acronym> function
-        <ulink url="http://php.net/version_compare"><methodname>version_compare()</methodname></ulink>.
+        is based on the <acronym>PHP</acronym> function <ulink
+            url="http://php.net/version_compare"><methodname>version_compare()</methodname></ulink>.
         This method returns -1 if the specified version
         is older than the installed Zend Framework version, 0 if they are the same
         and +1 if the specified version is newer than the

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

@@ -16,8 +16,8 @@
     </para>
 
     <para>
-        The <acronym>API</acronym> for the <code>Action</code> view helper follows that of most <acronym>MVC</acronym>
-        components that invoke controller actions: <code>action($action,
+        The <acronym>API</acronym> for the <code>Action</code> view helper follows that of most
+        <acronym>MVC</acronym> components that invoke controller actions: <code>action($action,
             $controller, $module = null, array $params = array())</code>.
         <varname>$action</varname> and <varname>$controller</varname> are required; if no
         module is specified, the default module is assumed.

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

@@ -4,9 +4,9 @@
     <title>Doctype Helper</title>
 
     <para>
-        Valid HTML and <acronym>XHTML</acronym> documents should include a <constant>DOCTYPE</constant>
-        declaration. Besides being difficult to remember, these can also affect
-        how certain elements in your document should be rendered (for instance,
+        Valid HTML and <acronym>XHTML</acronym> documents should include a
+        <constant>DOCTYPE</constant> declaration. Besides being difficult to remember, these can
+        also affect how certain elements in your document should be rendered (for instance,
         CDATA escaping in <code>&lt;script&gt;</code> and
         <code>&lt;style&gt;</code> elements.
     </para>

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

@@ -55,9 +55,9 @@
 
     <para>
         <code>HeadMeta</code> overrides each of <methodname>append()</methodname>,
-        <methodname>offsetSet()</methodname>, <methodname>prepend()</methodname>, and <methodname>set()</methodname>
-        to enforce usage of the special methods as listed above. Internally, it
-        stores each item as a <code>stdClass</code> token, which it later
+        <methodname>offsetSet()</methodname>, <methodname>prepend()</methodname>, and
+        <methodname>set()</methodname> to enforce usage of the special methods as listed above.
+        Internally, it stores each item as a <code>stdClass</code> token, which it later
         serializes using the <methodname>itemToString()</methodname> method. This allows you
         to perform checks on the items in the stack, and optionally modify these
         items by simply modifying the object returned.

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

@@ -84,9 +84,9 @@ $this->headScript()->appendFile(
 
     <para>
         <code>HeadScript</code> overrides each of <methodname>append()</methodname>,
-        <methodname>offsetSet()</methodname>, <methodname>prepend()</methodname>, and <methodname>set()</methodname>
-        to enforce usage of the special methods as listed above. Internally, it
-        stores each item as a <code>stdClass</code> token, which it later
+        <methodname>offsetSet()</methodname>, <methodname>prepend()</methodname>, and
+        <methodname>set()</methodname> to enforce usage of the special methods as listed above.
+        Internally, it stores each item as a <code>stdClass</code> token, which it later
         serializes using the <methodname>itemToString()</methodname> method. This allows you
         to perform checks on the items in the stack, and optionally modify these
         items by simply modifying the object returned.
@@ -205,8 +205,8 @@ $('foo_form').action = action;
             </para></listitem>
 
             <listitem><para>
-                    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
+                    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>