[MANUAL] English:

- structural fixes (no translations needed)

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

documentation/manual/en/module_specs/Zend_Measure-Types.xml

@@ -1,16 +1,16 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
 <sect1 id="zend.measure.types">
-
     <title>Types of measurements</title>
 
     <para>
-        All supported measurement types are listed below, each with an example of the standard usage for such
-        measurements.
+        All supported measurement types are listed below, each with an example of the standard usage
+        for such measurements.
     </para>
 
     <table id="zend.measure.types.table-1">
         <title>List of measurement types</title>
+
         <tgroup cols="4">
             <thead>
                 <row>
@@ -20,288 +20,365 @@
                     <entry>Description</entry>
                 </row>
             </thead>
+
             <tbody>
                 <row>
                     <entry>Acceleration</entry>
                     <entry>Zend_Measure_Acceleration</entry>
-                    <entry>Meter per square second | <code>m/s²</code>
+                    <entry>Meter per square second | <code>m/s²</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Acceleration</classname> covers the
+                        physical factor of acceleration.
                     </entry>
-                    <entry><classname>Zend_Measure_Acceleration</classname> covers the
-                            physical factor of acceleration.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Angle</entry>
                     <entry>Zend_Measure_Angle</entry>
-                    <entry>Radiant | <code>rad</code>
+                    <entry>Radiant | <code>rad</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Angle</classname> covers angular dimensions.
                     </entry>
-                    <entry><classname>Zend_Measure_Angle</classname> covers angular dimensions.</entry>
                 </row>
+
                 <row>
                     <entry>Area</entry>
                     <entry>Zend_Measure_Area</entry>
-                    <entry>Square meter | <code>m²</code>
-                    </entry>
+                    <entry>Square meter | <code>m²</code></entry>
                     <entry><classname>Zend_Measure_Area</classname> covers square measures.</entry>
                 </row>
+
                 <row>
                     <entry>Binary</entry>
                     <entry>Zend_Measure_Binary</entry>
-                    <entry>Byte | <code>b</code>
+                    <entry>Byte | <code>b</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Binary</classname> covers binary conversions.
                     </entry>
-                    <entry><classname>Zend_Measure_Binary</classname> covers binary conversions.</entry>
                 </row>
+
                 <row>
                     <entry>Capacitance</entry>
                     <entry>Zend_Measure_Capacitance</entry>
-                    <entry>Farad | <code>F</code>
+                    <entry>Farad | <code>F</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Capacitance</classname> covers physical factor of
+                        capacitance.
                     </entry>
-                    <entry><classname>Zend_Measure_Capacitance</classname> covers physical factor of capacitance.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Cooking volumes</entry>
                     <entry>Zend_Measure_Cooking_Volume</entry>
-                    <entry>Cubic meter | <code>m³</code>
+                    <entry>Cubic meter | <code>m³</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Cooking_Volume</classname> covers volumes
+                        which are used for cooking or written in cookbooks.
                     </entry>
-                    <entry><classname>Zend_Measure_Cooking_Volume</classname> covers volumes
-                            which are used for cooking or written in cookbooks.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Cooking weights</entry>
                     <entry>Zend_Measure_Cooking_Weight</entry>
-                    <entry>Gram | <code>g</code>
+                    <entry>Gram | <code>g</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Cooking_Weight</classname> covers the weights
+                        which are used for cooking or written in cookbooks.
                     </entry>
-                    <entry><classname>Zend_Measure_Cooking_Weight</classname> covers the weights
-                            which are used for cooking or written in cookbooks.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Current</entry>
                     <entry>Zend_Measure_Current</entry>
-                    <entry>Ampere | <code>A</code>
+                    <entry>Ampere | <code>A</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Current</classname> covers the physical factor of
+                        current.
                     </entry>
-                    <entry><classname>Zend_Measure_Current</classname> covers the physical factor of current.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Density</entry>
                     <entry>Zend_Measure_Density</entry>
-                    <entry>Kilogram per cubic meter | <code>kg/m³</code>
+                    <entry>Kilogram per cubic meter | <code>kg/m³</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Density</classname> covers the physical factor of
+                        density.
                     </entry>
-                    <entry><classname>Zend_Measure_Density</classname> covers the physical factor of density.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Energy</entry>
                     <entry>Zend_Measure_Energy</entry>
-                    <entry>Joule | <code>J</code>
+                    <entry>Joule | <code>J</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Energy</classname> covers the physical factor of
+                        energy.
                     </entry>
-                    <entry><classname>Zend_Measure_Energy</classname> covers the physical factor of energy.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Force</entry>
                     <entry>Zend_Measure_Force</entry>
-                    <entry>Newton | <code>N</code>
+                    <entry>Newton | <code>N</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Force</classname> covers the physical factor of
+                        force.
                     </entry>
-                    <entry><classname>Zend_Measure_Force</classname> covers the physical factor of force.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Flow (mass)</entry>
                     <entry>Zend_Measure_Flow_Mass</entry>
-                    <entry>Kilogram per second | <code>kg/s</code>
+                    <entry>Kilogram per second | <code>kg/s</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Flow_Mass</classname> covers the physical factor of
+                        flow rate. The weight of the flowing mass is used as reference point within
+                        this class.
                     </entry>
-                    <entry><classname>Zend_Measure_Flow_Mass</classname> covers the physical factor of flow rate.
-                            The weight of the flowing mass is used as reference point within this class.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Flow (mole)</entry>
                     <entry>Zend_Measure_Flow_Mole</entry>
-                    <entry>Mole per second | <code>mol/s</code>
+                    <entry>Mole per second | <code>mol/s</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Flow_Mole</classname> covers the physical factor of
+                        flow rate. The density of the flowing mass is used as reference point within
+                        this class.
                     </entry>
-                    <entry><classname>Zend_Measure_Flow_Mole</classname> covers the physical factor of flow rate.
-                            The density of the flowing mass is used as reference point within this class.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Flow (volume)</entry>
                     <entry>Zend_Measure_Flow_Volume</entry>
-                    <entry>Cubic meter per second | <code>m³/s</code>
+                    <entry>Cubic meter per second | <code>m³/s</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Flow_Volume</classname> covers the physical factor
+                        of flow rate. The volume of the flowing mass is used as reference point
+                        within this class.
                     </entry>
-                    <entry><classname>Zend_Measure_Flow_Volume</classname> covers the physical factor of flow rate.
-                            The volume of the flowing mass is used as reference point within this class.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Frequency</entry>
                     <entry>Zend_Measure_Frequency</entry>
-                    <entry>Hertz | <code>Hz</code>
+                    <entry>Hertz | <code>Hz</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Frequency</classname> covers the physical factor of
+                        frequency.
                     </entry>
-                    <entry><classname>Zend_Measure_Frequency</classname> covers the physical factor of frequency.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Illumination</entry>
                     <entry>Zend_Measure_Illumination</entry>
-                    <entry>Lux | <code>lx</code>
+                    <entry>Lux | <code>lx</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Illumination</classname> covers the physical factor
+                        of light density.
                     </entry>
-                    <entry><classname>Zend_Measure_Illumination</classname> covers the physical factor of light density.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Length</entry>
                     <entry>Zend_Measure_Length</entry>
-                    <entry>Meter | <code>m</code>
+                    <entry>Meter | <code>m</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Length</classname> covers the physical factor of
+                        length.
                     </entry>
-                    <entry><classname>Zend_Measure_Length</classname> covers the physical factor of length.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Lightness</entry>
                     <entry>Zend_Measure_Lightness</entry>
-                    <entry>Candela per square meter | <code>cd/m²</code>
+                    <entry>Candela per square meter | <code>cd/m²</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Ligntness</classname> covers the physical factor of
+                        light energy.
                     </entry>
-                    <entry><classname>Zend_Measure_Ligntness</classname> covers the physical factor of light energy.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Number</entry>
                     <entry>Zend_Measure_Number</entry>
-                    <entry>Decimal | <code>(10)</code>
+                    <entry>Decimal | <code>(10)</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Number</classname> converts between number formats.
                     </entry>
-                    <entry><classname>Zend_Measure_Number</classname> converts between number formats.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Power</entry>
                     <entry>Zend_Measure_Power</entry>
-                    <entry>Watt | <code>W</code>
+                    <entry>Watt | <code>W</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Power</classname> covers the physical factor of
+                        power.
                     </entry>
-                    <entry><classname>Zend_Measure_Power</classname> covers the physical factor of power.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Pressure</entry>
                     <entry>Zend_Measure_Pressure</entry>
-                    <entry>Newton per square meter | <code>N/m²</code>
+                    <entry>Newton per square meter | <code>N/m²</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Pressure</classname> covers the physical factor of
+                        pressure.
                     </entry>
-                    <entry><classname>Zend_Measure_Pressure</classname> covers the physical factor of pressure.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Speed</entry>
                     <entry>Zend_Measure_Speed</entry>
-                    <entry>Meter per second | <code>m/s</code>
+                    <entry>Meter per second | <code>m/s</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Speed</classname> covers the physical factor of
+                        speed.
                     </entry>
-                    <entry><classname>Zend_Measure_Speed</classname> covers the physical factor of speed.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Temperature</entry>
                     <entry>Zend_Measure_Temperature</entry>
-                    <entry>Kelvin | <code>K</code>
+                    <entry>Kelvin | <code>K</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Temperature</classname> covers the physical factor
+                        of temperature.
                     </entry>
-                    <entry><classname>Zend_Measure_Temperature</classname> covers the physical factor of temperature.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Time</entry>
                     <entry>Zend_Measure_Time</entry>
-                    <entry>Second | <code>s</code>
+                    <entry>Second | <code>s</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Time</classname> covers the physical factor of time.
                     </entry>
-                    <entry><classname>Zend_Measure_Time</classname> covers the physical factor of time.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Torque</entry>
                     <entry>Zend_Measure_Torque</entry>
-                    <entry>Newton meter | <code>Nm</code>
+                    <entry>Newton meter | <code>Nm</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Torque</classname> covers the physical factor of
+                        torque.
                     </entry>
-                    <entry><classname>Zend_Measure_Torque</classname> covers the physical factor of torque.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Viscosity (dynamic)</entry>
                     <entry>Zend_Measure_Viscosity_Dynamic</entry>
-                    <entry>Kilogram per meter second | <code>kg/ms</code>
+                    <entry>Kilogram per meter second | <code>kg/ms</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Viscosity_Dynamic</classname> covers the physical
+                        factor of viscosity. The weight of the fluid is used as reference point
+                        within this class.
                     </entry>
-                    <entry><classname>Zend_Measure_Viscosity_Dynamic</classname> covers the physical factor of viscosity.
-                            The weight of the fluid is used as reference point within this class.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Viscosity (kinematic)</entry>
                     <entry>Zend_Measure_Viscosity_Kinematic</entry>
-                    <entry>Square meter per second | <code>m²/s</code>
+                    <entry>Square meter per second | <code>m²/s</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Viscosity_Kinematic</classname> covers the physical
+                        factor of viscosity. The distance of the flown fluid is used as reference
+                        point within this class.
                     </entry>
-                    <entry><classname>Zend_Measure_Viscosity_Kinematic</classname> covers the physical factor of viscosity.
-                            The distance of the flown fluid is used as reference point within this class.
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Volume</entry>
                     <entry>Zend_Measure_Volume</entry>
-                    <entry>Cubic meter | <code>m³</code>
+                    <entry>Cubic meter | <code>m³</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Volume</classname> covers the physical factor of
+                        volume (content).
                     </entry>
-                    <entry><classname>Zend_Measure_Volume</classname> covers the physical factor of volume (content).
-                        </entry>
                 </row>
+
                 <row>
                     <entry>Weight</entry>
                     <entry>Zend_Measure_Weight</entry>
-                    <entry>Kilogram | <code>kg</code>
+                    <entry>Kilogram | <code>kg</code></entry>
+
+                    <entry>
+                        <classname>Zend_Measure_Weight</classname> covers the physical factor of
+                        weight.
                     </entry>
-                    <entry><classname>Zend_Measure_Weight</classname> covers the physical factor of weight.
-                        </entry>
                 </row>
             </tbody>
         </tgroup>
     </table>
 
     <sect2 id="zend.measure.types.binary">
-
         <title>Hints for Zend_Measure_Binary</title>
 
         <para>
-            Some popular binary conventions, include terms like kilo-, mega-, giga, etc. in normal language use imply
-            base 10, such as 1000 or 10³. However, in the binary format for computers these terms have to be seen for a
-            conversion factor of 1024 instead of 1000. To preclude confusions a few years ago the notation BI was
-            introduced. Instead of kilobyte, kibibyte for kilo-binary-byte should be used.
+            Some popular binary conventions, include terms like kilo-, mega-, giga, etc. in normal
+            language use imply base 10, such as 1000 or 10³. However, in the binary format for
+            computers these terms have to be seen for a conversion factor of 1024 instead of 1000.
+            To preclude confusions a few years ago the notation BI was introduced. Instead of
+            kilobyte, kibibyte for kilo-binary-byte should be used.
         </para>
 
         <para>
-            In the class BINARY both notations can be found, such as <code>KILOBYTE = 1024 - binary conputer conversion
-            KIBIBYTE = 1024 - new notation KILO_BINARY_BYTE = 1024 - new</code>, or the notation, long format
-            <code>KILOBYTE_SI = 1000 - SI notation for kilo (1000)</code>. DVDs for example are marked with the
-            SI-notation, but almost all harddisks are marked in computer binary notation.
+            In the class BINARY both notations can be found, such as <code>KILOBYTE = 1024 - binary
+            conputer conversion KIBIBYTE = 1024 - new notation KILO_BINARY_BYTE = 1024 - new</code>,
+            or the notation, long format
+            <code>KILOBYTE_SI = 1000 - SI notation for kilo (1000)</code>. DVDs for example are
+            marked with the SI-notation, but almost all harddisks are marked in computer binary notation.
         </para>
-
     </sect2>
 
     <sect2 id="zend.measure.types.decimal">
-
         <title>Hints for Zend_Measure_Number</title>
 
         <para>
-            The best known number format is the decimal system. Additionally this class supports the octal system, the
-            hexadecimal system, the binary system, the roman number system and some other less popular systems. Note
-            that only the decimal part of numbers is handled. Any fractional part will be stripped.
+            The best known number format is the decimal system. Additionally this class supports the
+            octal system, the hexadecimal system, the binary system, the roman number system and
+            some other less popular systems. Note that only the decimal part of numbers is handled.
+            Any fractional part will be stripped.
         </para>
-
     </sect2>
 
     <sect2 id="zend.measure.types.roman">
-
         <title>Roman numbers</title>
 
         <para>
-            For the roman number system digits greater 4000 are supported. In reality these digits are shown with a
-            crossbeam on top of the digit. As the crossbeam can not be shown within the computer, an underline has to be
-            used instead of it.
+            For the roman number system digits greater 4000 are supported. In reality these digits
+            are shown with a crossbeam on top of the digit. As the crossbeam can not be shown within
+            the computer, an underline has to be used instead of it.
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -312,9 +389,7 @@ $unit = new Zend_Measure_Number($great,Zend_Measure_Number::ROMAN, $locale);
 // convert to the decimal system
 echo $unit->convertTo(Zend_Measure_Number::DECIMAL);
 ]]></programlisting>
-
     </sect2>
-
 </sect1>
 <!--
 vim:se ts=4 sw=4 et:

documentation/manual/en/module_specs/Zend_Mime_Message.xml

@@ -4,20 +4,24 @@
     <title>Zend_Mime_Message</title>
 
     <sect2 id="zend.mime.message.introduction">
-      <title>Introduction</title>
+        <title>Introduction</title>
 
-      <para><classname>Zend_Mime_Message</classname> represents a <acronym>MIME</acronym> compliant message
-      that can contain one or more separate Parts (Represented as <link
-      linkend="zend.mime.part"><classname>Zend_Mime_Part</classname></link> objects). With
-      <classname>Zend_Mime_Message</classname>, <acronym>MIME</acronym> compliant multipart messages can be generated from
-      <classname>Zend_Mime_Part</classname> objects. Encoding and Boundary handling are handled transparently
-      by the class. <classname>Zend_Mime_Message</classname> objects can also be reconstructed from given
-      strings (experimental). Used by <link linkend="zend.mail"><classname>Zend_Mail</classname></link>.
-      </para>
+        <para>
+            <classname>Zend_Mime_Message</classname> represents a <acronym>MIME</acronym> compliant
+            message that can contain one or more separate Parts (Represented as <link
+                linkend="zend.mime.part"><classname>Zend_Mime_Part</classname></link> objects). With
+            <classname>Zend_Mime_Message</classname>, <acronym>MIME</acronym> compliant multipart
+            messages can be generated from <classname>Zend_Mime_Part</classname> objects. Encoding
+            and Boundary handling are handled transparently by the class.
+            <classname>Zend_Mime_Message</classname> objects can also be reconstructed from given
+            strings (experimental). Used by <link
+                linkend="zend.mail"><classname>Zend_Mail</classname></link>.
+        </para>
     </sect2>
 
     <sect2 id="zend.mime.message.instantiation">
         <title>Instantiation</title>
+
         <para>
             There is no explicit constructor for <classname>Zend_Mime_Message</classname>.
         </para>
@@ -26,17 +30,23 @@
     <sect2 id="zend.mime.message.addparts">
         <title>Adding MIME Parts</title>
 
-        <para><link linkend="zend.mime.part"><classname>Zend_Mime_Part</classname></link>
-        Objects can be added to a given <classname>Zend_Mime_Message</classname> object by calling
-        <code>-&gt;addPart($part)</code></para>
+        <para>
+            <link linkend="zend.mime.part"><classname>Zend_Mime_Part</classname></link>
+            Objects can be added to a given <classname>Zend_Mime_Message</classname> object by
+            calling <code>-&gt;addPart($part)</code>
+        </para>
 
-    <para>An array with all <link linkend="zend.mime.part"><classname>Zend_Mime_Part</classname></link>
-    objects in the <classname>Zend_Mime_Message</classname> is returned
-        from the method <code>-&gt;getParts()</code>. The <classname>Zend_Mime_Part</classname> objects
-        can then be changed since they are stored in the array as references. If
-        parts are added to the array or the sequence is changed, the array needs
-        to be given back to the <link linkend="zend.mime.part"><classname>Zend_Mime_Part</classname></link>
-        object by calling <code>-&gt;setParts($partsArray)</code>.</para>
+        <para>
+            An array with all <link
+                linkend="zend.mime.part"><classname>Zend_Mime_Part</classname></link>
+            objects in the <classname>Zend_Mime_Message</classname> is returned
+            from the method <code>-&gt;getParts()</code>. The <classname>Zend_Mime_Part</classname>
+            objects can then be changed since they are stored in the array as references. If
+            parts are added to the array or the sequence is changed, the array needs
+            to be given back to the <link
+                linkend="zend.mime.part"><classname>Zend_Mime_Part</classname></link>
+            object by calling <code>-&gt;setParts($partsArray)</code>.
+        </para>
 
         <para>
             The function <code>-&gt;isMultiPart()</code> will return <constant>TRUE</constant> if
@@ -49,37 +59,47 @@
     <sect2 id="zend.mime.message.bondary">
         <title>Boundary handling</title>
 
-        <para><classname>Zend_Mime_Message</classname> usually creates and uses its own
-        <classname>Zend_Mime</classname> Object to generate a boundary. If you need to
-        define the boundary or want to change the behaviour of the <classname>Zend_Mime</classname> object
-        used by <classname>Zend_Mime_Message</classname>, you can instantiate the <classname>Zend_Mime</classname>
-        object yourself and then register it to <classname>Zend_Mime_Message</classname>.
-        Usually you will not need to do this. <code>-&gt;setMime(Zend_Mime
-        $mime)</code> sets a special instance of <classname>Zend_Mime</classname> to be used
-        by this <classname>Zend_Mime_Message</classname></para>
+        <para>
+            <classname>Zend_Mime_Message</classname> usually creates and uses its own
+            <classname>Zend_Mime</classname> Object to generate a boundary. If you need to define
+            the boundary or want to change the behaviour of the <classname>Zend_Mime</classname>
+            object used by <classname>Zend_Mime_Message</classname>, you can instantiate the
+            <classname>Zend_Mime</classname> object yourself and then register it to
+            <classname>Zend_Mime_Message</classname>. Usually you will not need to do this.
+            <code>-&gt;setMime(Zend_Mime $mime)</code> sets a special instance of
+            <classname>Zend_Mime</classname> to be used by this
+            <classname>Zend_Mime_Message</classname>
+        </para>
 
-        <para><code>-&gt;getMime()</code> returns the instance of
-        <classname>Zend_Mime</classname> that will be used to render the message when
-        <methodname>generateMessage()</methodname> is called.</para>
+        <para>
+            <code>-&gt;getMime()</code> returns the instance of
+            <classname>Zend_Mime</classname> that will be used to render the message when
+            <methodname>generateMessage()</methodname> is called.
+        </para>
 
-        <para><code>-&gt;generateMessage()</code> renders the <classname>Zend_Mime_Message</classname>
-        content to a string.</para>
+        <para>
+            <code>-&gt;generateMessage()</code> renders the <classname>Zend_Mime_Message</classname>
+            content to a string.
+        </para>
     </sect2>
 
     <sect2 id="zend.mime.message.parse">
-        <title>parsing a string to create a Zend_Mime_Message object
-        (experimental)</title>
+        <title>parsing a string to create a Zend_Mime_Message object (experimental)</title>
 
-        <para>A given <acronym>MIME</acronym> compliant message in string form can be used to
-        reconstruct a <classname>Zend_Mime_Message</classname> Object from it.
-        <classname>Zend_Mime_Message</classname> has a static factory Method to parse this
-        String and return a <classname>Zend_Mime_Message</classname> Object.</para>
+        <para>
+            A given <acronym>MIME</acronym> compliant message in string form can be used to
+            reconstruct a <classname>Zend_Mime_Message</classname> Object from it.
+            <classname>Zend_Mime_Message</classname> has a static factory Method to parse this
+            String and return a <classname>Zend_Mime_Message</classname> Object.
+        </para>
 
-        <para><methodname>Zend_Mime_Message::createFromMessage($str, $boundary)</methodname>
-        decodes the given string and returns a <classname>Zend_Mime_Message</classname>
-        Object that can then be examined using <code>-&gt;getParts()</code></para>
+        <para>
+            <methodname>Zend_Mime_Message::createFromMessage($str, $boundary)</methodname>
+            decodes the given string and returns a <classname>Zend_Mime_Message</classname>
+            Object that can then be examined using <code>-&gt;getParts()</code>
+        </para>
     </sect2>
 </sect1>
 <!--
 vim:se ts=4 sw=4 et:
--->
+-->

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

@@ -2,6 +2,7 @@
 <!-- Reviewed: no -->
 <sect1 id="zend.openid.introduction">
     <title>Introduction</title>
+
     <para>
         <classname>Zend_OpenId</classname> is a Zend Framework component that provides a
         simple <acronym>API</acronym> for building OpenID-enabled sites and identity providers.
@@ -9,28 +10,31 @@
 
     <sect2 id="zend.openid.introduction.what">
         <title>What is OpenID?</title>
+
         <para>
             OpenID is a set of protocols for user-centric digital identities.
             These protocols allows users to create an identity online, using an identity
             provider. This identity can be used on any site that supports OpenID.
             Using OpenID-enabled sites, users do not need to remember traditional
             authentication tokens such as usernames and passwords for each site. All OpenID-enabled
-            sites accept a single OpenID identity. This identity is typically a <acronym>URL</acronym>.
-            It may be the <acronym>URL</acronym> of the user's personal page, blog or other resource that
-            may provide additional information about them. That mean a user needs just one identifier for all sites he or she uses.
-            services. OpenID is an open, decentralized, and free user-centric
-            solution. Users may choose which OpenID provider to use, or even create
-            their own personal identity server. No central authority is required to
-            approve or register OpenID-enabled sites or identity providers.
+            sites accept a single OpenID identity. This identity is typically a
+            <acronym>URL</acronym>. It may be the <acronym>URL</acronym> of the user's personal
+            page, blog or other resource that may provide additional information about them. That
+            mean a user needs just one identifier for all sites he or she uses. services. OpenID is
+            an open, decentralized, and free user-centric solution. Users may choose which OpenID
+            provider to use, or even create their own personal identity server. No central authority
+            is required to approve or register OpenID-enabled sites or identity providers.
         </para>
 
         <para>
-            For more information about OpenID visit the <ulink url="http://www.openid.net/">OpenID official site</ulink>.
+            For more information about OpenID visit the <ulink url="http://www.openid.net/">OpenID
+                official site</ulink>.
         </para>
     </sect2>
 
     <sect2 id="zend.openid.introduction.how">
         <title>How Does it Work?</title>
+
         <para>
             The purpose of the <classname>Zend_OpenId</classname> component is to
             implement the OpenID authentication protocol as described in the following
@@ -38,7 +42,8 @@
         </para>
 
         <para>
-            <inlinegraphic align="center" fileref="figures/zend.openid.protocol.jpg" format="JPEG" scale="100" valign="middle" width="559" />
+            <inlinegraphic align="center" fileref="figures/zend.openid.protocol.jpg" format="JPEG"
+                scale="100" valign="middle" width="559" />
         </para>
 
         <orderedlist>
@@ -48,13 +53,16 @@
                     OpenID identifier to the OpenID consumer through a User-Agent.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     The OpenID consumer performs normalization and discovery on the user-supplied
-                    identifier. Through this process, the consumer obtains the claimed identifier, the <acronym>URL</acronym> of the OpenID provider and an OpenID protocol
+                    identifier. Through this process, the consumer obtains the claimed identifier,
+                    the <acronym>URL</acronym> of the OpenID provider and an OpenID protocol
                     version.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     The OpenID consumer establishes an optional association with the
@@ -63,40 +71,47 @@
                     of the subsequent messages.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
-                    The OpenID consumer redirects the User-Agent to the <acronym>URL</acronym> of the OpenID
-                    provider with an OpenID authentication request.
+                    The OpenID consumer redirects the User-Agent to the <acronym>URL</acronym> of
+                    the OpenID provider with an OpenID authentication request.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     The OpenID provider checks if the User-Agent is already
                     authenticated and, if not, offers to do so.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     The end user enters the required password.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     The OpenID provider checks if it is allowed to pass the user
                     identity to the given consumer, and asks the user if necessary.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     The user allows or disallows passing his identity.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     The OpenID Provider redirects the User-Agent back to the OpenID
                     consumer with an "authentication approved" or "failed" request.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     The OpenID consumer verifies the information received from the
@@ -109,6 +124,7 @@
 
     <sect2 id="zend.openid.introduction.structure">
         <title>Zend_OpenId Structure</title>
+
         <para>
             <classname>Zend_OpenId</classname> consists of two sub-packages. The first one
             is <classname>Zend_OpenId_Consumer</classname> for developing OpenID-enabled sites,
@@ -126,8 +142,9 @@
 
         <note>
             <para>
-                <classname>Zend_OpenId</classname> takes advantage of the <ulink url="http://php.net/gmp">GMP extension</ulink>,
-                where available. Consider enabling the GMP extension for enhanced performance when using
+                <classname>Zend_OpenId</classname> takes advantage of the <ulink
+                    url="http://php.net/gmp">GMP extension</ulink>, where available. Consider
+                enabling the GMP extension for enhanced performance when using
                 <classname>Zend_OpenId</classname>.
             </para>
         </note>
@@ -135,6 +152,7 @@
 
     <sect2 id="zend.openid.introduction.standards">
         <title>Supported OpenID Standards</title>
+
         <para>
             The <classname>Zend_OpenId</classname> component supports the following
             standards:
@@ -146,16 +164,19 @@
                     OpenID Authentication protocol version 1.1
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     OpenID Authentication protocol version 2.0 draft 11
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     OpenID Simple Registration Extension version 1.0
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     OpenID Simple Registration Extension version 1.1 draft 1

documentation/manual/en/module_specs/Zend_Paginator-Advanced.xml

@@ -22,6 +22,7 @@
             <listitem>
                 <para>count()</para>
             </listitem>
+
             <listitem>
                 <para>getItems($offset, $itemCountPerPage)</para>
             </listitem>
@@ -35,8 +36,8 @@
         </para>
 
         <para>
-            If you've ever used the SPL interface
-            <ulink url="http://www.php.net/~helly/php/ext/spl/interfaceCountable.html"><code>Countable</code></ulink>,
+            If you've ever used the SPL interface <ulink
+                url="http://www.php.net/~helly/php/ext/spl/interfaceCountable.html"><code>Countable</code></ulink>,
             you're familiar with <methodname>count()</methodname>. As used with
             <classname>Zend_Paginator</classname>, this is the total number of items
             in the data collection.
@@ -127,7 +128,8 @@ Zend_Paginator::addScrollingStylePrefixPath($prefix, $path);
             <classname>Zend_Paginator</classname> can be told to cache the data it has already
             passed on, preventing the adapter from fetching them each time they are used.
             To tell paginator to automatically cache the adapter's data, just pass to
-            its <methodname>setCache()</methodname> method a <classname>Zend_Cache_Core</classname> instance.
+            its <methodname>setCache()</methodname> method a <classname>Zend_Cache_Core</classname>
+            instance.
         </para>
 
         <para>
@@ -141,9 +143,10 @@ Zend_Paginator::setCache($cache);
         </para>
 
         <para>
-            As far as <classname>Zend_Paginator</classname> has got a <classname>Zend_Cache_Core</classname> instance, data will
-            be cached. Sometimes you would like not to cache data even if you already passed
-            a cache instance. You should then use <methodname>setCacheEnable()</methodname> for that.
+            As far as <classname>Zend_Paginator</classname> has got a
+            <classname>Zend_Cache_Core</classname> instance, data will be cached. Sometimes you
+            would like not to cache data even if you already passed a cache instance. You should
+            then use <methodname>setCacheEnable()</methodname> for that.
         </para>
 
         <para>
@@ -224,12 +227,14 @@ var_dump($paginator->getPageItemCache());
         <title>Zend_Paginator_AdapterAggregate Interface</title>
 
         <para>
-            Depending on your application you might want to paginate objects, whose internal data-structure
-            is equal to existing adapters, but you don't want to break up your encapsulation to allow access
-            to this data. In other cases an object might be in a "has-an adapter" relationship, rather than
-            the "is-an adapter" relationsship that <classname>Zend_Paginator_Adapter_Abstract</classname> promotes.
-            For this cases you can use the <classname>Zend_Paginator_AdapterAggregate</classname> interface that
-            behaves much like the <classname>IteratorAggregate</classname> interface of the PHP SPL extension.
+            Depending on your application you might want to paginate objects, whose internal
+            data-structure is equal to existing adapters, but you don't want to break up your
+            encapsulation to allow access to this data. In other cases an object might be in a
+            "has-an adapter" relationship, rather than the "is-an adapter" relationsship that
+            <classname>Zend_Paginator_Adapter_Abstract</classname> promotes. For this cases you can
+            use the <classname>Zend_Paginator_AdapterAggregate</classname> interface that behaves
+            much like the <classname>IteratorAggregate</classname> interface of the PHP SPL
+            extension.
         </para>
 
         <para>
@@ -248,12 +253,12 @@ interface Zend_Paginator_AdapterAggregate
 
         <para>
             The interface is fairly small and only expects you to return an instance of
-            <classname>Zend_Paginator_Adapter_Abstract</classname>. An Adapter Aggregate instance is then
-            recognized by both <code>Zend_Paginator::factory</code> and the constructor of Zend_Paginator and
-            handled accordingly.
+            <classname>Zend_Paginator_Adapter_Abstract</classname>. An Adapter Aggregate instance is
+            then recognized by both <code>Zend_Paginator::factory</code> and the constructor of
+            Zend_Paginator and handled accordingly.
         </para>
     </sect2>
 </sect1>
 <!--
 vim:se ts=4 sw=4 et:
--->
+-->

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

@@ -17,17 +17,20 @@
                     Paginate arbitrary data, not just relational databases
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     Fetch only the results that need to be displayed
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     Do not force users to adhere to only one way of displaying
                     data or rendering pagination controls
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     Loosely couple <classname>Zend_Paginator</classname> to other Zend
@@ -41,4 +44,4 @@
 </sect1>
 <!--
 vim:se ts=4 sw=4 et:
--->
+-->

documentation/manual/en/module_specs/Zend_Service_Amazon_Ec2-WindowsInstance.xml

@@ -16,6 +16,7 @@
                 Desktop instead of SSH.
             </para>
         </listitem>
+
         <listitem>
             <para>
                 Administrative Password—To access Windows instances the first time,
@@ -23,10 +24,11 @@
                 command.
             </para>
         </listitem>
+
         <listitem>
             <para>
-                Simplified Bundling—To bundle a Windows instance, you use a single command
-                that shuts down the instance, saves it as an <acronym>AMI</acronym>, and restarts it.
+                Simplified Bundling—To bundle a Windows instance, you use a single command that
+                shuts down the instance, saves it as an <acronym>AMI</acronym>, and restarts it.
             </para>
         </listitem>
     </itemizedlist>
@@ -35,15 +37,18 @@
         As part of this service, Amazon EC2 instances can now run Microsoft Windows Server
         2003. Our base Windows image provides you with most of the common functionality associated
         with Windows. However, if you require more than two concurrent Windows users or need to
-        leverage applications that require <acronym>LDAP</acronym>, Kerberos, RADIUS, or other credential services,
-        you must use Windows with Authentication Services. For example, Microsoft Exchange Server
-        and Microsoft SharePoint Server require Windows with Authentication Services.
+        leverage applications that require <acronym>LDAP</acronym>, Kerberos, RADIUS, or other
+        credential services, you must use Windows with Authentication Services. For example,
+        Microsoft Exchange Server and Microsoft SharePoint Server require Windows with
+        Authentication Services.
     </para>
+
     <note>
         <para>
-            To get started using Windows instances, we recommend using the <acronym>AWS</acronym> Management Console.
-            There are differences in pricing between Windows and Windows with Authentication
-            Services instances. For information on pricing, go to the Amazon EC2 Product Page.
+            To get started using Windows instances, we recommend using the <acronym>AWS</acronym>
+            Management Console. There are differences in pricing between Windows and Windows with
+            Authentication Services instances. For information on pricing, go to the Amazon EC2
+            Product Page.
         </para>
     </note>
 
@@ -52,18 +57,10 @@
     </para>
 
     <itemizedlist>
-        <listitem>
-            <para>Windows Authenticated (32-bit)</para>
-        </listitem>
-        <listitem>
-            <para>Windows Authenticated (64-bit)</para>
-        </listitem>
-        <listitem>
-            <para>Windows Anonymous (32-bit)</para>
-        </listitem>
-        <listitem>
-            <para>Windows Anonymous (64-bit)</para>
-        </listitem>
+        <listitem><para>Windows Authenticated (32-bit)</para></listitem>
+        <listitem><para>Windows Authenticated (64-bit)</para></listitem>
+        <listitem><para>Windows Anonymous (32-bit)</para></listitem>
+        <listitem><para>Windows Anonymous (64-bit)</para></listitem>
     </itemizedlist>
 
     <para>
@@ -84,12 +81,14 @@
                 from this instance use the new password.
             </para>
         </listitem>
+
         <listitem>
             <para>
                 Configures the computer name to the internal DNS name. To
                 determine the internal DNS name, see Using Instance Addressing.
             </para>
         </listitem>
+
         <listitem>
             <para>
                 Sends the last three system and application errors from the
@@ -105,21 +104,27 @@
 
         <example id="zend.service.amazon.ec2.windows.instance.operations.bundle">
             <title>Bundles an Amazon EC2 instance running Windows</title>
+
             <para>
                 <methodname>bundle()</methodname> has three require paramters and one optional
             </para>
+
             <itemizedlist>
                 <listitem>
                      <para><emphasis>instanceId</emphasis> The instance you want to bundle</para>
                 </listitem>
+
                 <listitem>
                      <para><emphasis>s3Bucket</emphasis> Where you want the ami to live on S3</para>
                 </listitem>
+
                 <listitem>
                      <para>
-                        <emphasis>s3Prefix</emphasis> The prefix you want to assign to the <acronym>AMI</acronym> on S3
+                        <emphasis>s3Prefix</emphasis> The prefix you want to assign to the
+                        <acronym>AMI</acronym> on S3
                     </para>
                 </listitem>
+
                 <listitem>
                     <para>
                         <emphasis>uploadExpiration</emphasis> The expiration of the upload policy.
@@ -128,11 +133,13 @@
                     </para>
                 </listitem>
             </itemizedlist>
+
             <para>
                 <methodname>bundle()</methodname> returns a multi-demential array that contains
                 instanceId, bundleId, state, startTime, updateTime, progress
                 s3Bucket and s3Prefix.
             </para>
+
             <programlisting language="php"><![CDATA[
 $ec2_instance = new Zend_Service_Amazon_Ec2_Instance_Windows('aws_key',
                                                      'aws_secret_key');
@@ -143,14 +150,17 @@ $return = $ec2_instance->bundle('instanceId', 's3Bucket', 's3Prefix');
 
         <example id="zend.service.amazon.ec2.windows.instance.operations.describe">
             <title>Describes current bundling tasks</title>
+
             <para>
                 <methodname>describeBundle()</methodname> Describes current bundling tasks
             </para>
+
             <para>
                 <methodname>describeBundle()</methodname> returns a multi-demential array that
                 contains instanceId, bundleId, state, startTime, updateTime, progress
                 s3Bucket and s3Prefix.
             </para>
+
             <programlisting language="php"><![CDATA[
 $ec2_instance = new Zend_Service_Amazon_Ec2_Instance_Windows('aws_key',
                                                      'aws_secret_key');
@@ -160,20 +170,22 @@ $return = $ec2_instance->describeBundle('bundleId');
 
         <example id="zend.service.amazon.ec2.windows.instance.operations.cancel">
             <title>Cancels an Amazon EC2 bundling operation</title>
+
             <para>
                 <methodname>cancelBundle()</methodname> Cancels an Amazon EC2 bundling operation
             </para>
+
             <para>
                 <methodname>cancelBundle()</methodname> returns a multi-demential array that
                 contains instanceId, bundleId, state, startTime, updateTime, progress
                 s3Bucket and s3Prefix.
             </para>
+
             <programlisting language="php"><![CDATA[
 $ec2_instance = new Zend_Service_Amazon_Ec2_Instance_Windows('aws_key',
                                                      'aws_secret_key');
 $return = $ec2_instance->cancelBundle('bundleId');
 ]]></programlisting>
-
         </example>
     </sect2>
 </sect1>

documentation/manual/en/module_specs/Zend_Service_Amazon_Sqs.xml

@@ -58,7 +58,6 @@
             service. You will need to be familiar with basic concepts in order
             to use this service.
         </para>
-
     </sect2>
 
     <sect2 id="zend.service.amazon.sqs.features">

documentation/manual/en/module_specs/Zend_Service_Flickr.xml

@@ -2,20 +2,27 @@
 <!-- Reviewed: no -->
 <sect1 id="zend.service.flickr">
     <title>Zend_Service_Flickr</title>
+
     <sect2 id="zend.service.flickr.introduction">
         <title>Introduction</title>
+
         <para>
-            <classname>Zend_Service_Flickr</classname> is a simple <acronym>API</acronym> for using the Flickr REST Web Service. In order to use
-            the Flickr web services, you must have an <acronym>API</acronym> key. To obtain a key and for more information about the
-            Flickr REST Web Service, please visit the
-            <ulink url="http://www.flickr.com/services/api/">Flickr <acronym>API</acronym> Documentation</ulink>.
+            <classname>Zend_Service_Flickr</classname> is a simple <acronym>API</acronym> for using
+            the Flickr REST Web Service. In order to use the Flickr web services, you must have an
+            <acronym>API</acronym> key. To obtain a key and for more information about the Flickr
+            REST Web Service, please visit the <ulink
+                url="http://www.flickr.com/services/api/">Flickr <acronym>API</acronym>
+                Documentation</ulink>.
         </para>
+
         <para>
-            In the following example, we use the <methodname>tagSearch()</methodname> method to search for photos having "php"
-            in the tags.
+            In the following example, we use the <methodname>tagSearch()</methodname> method to
+            search for photos having "php" in the tags.
         </para>
+
         <example id="zend.service.flickr.introduction.example-1">
             <title>Simple Flickr Photo Search</title>
+
             <programlisting language="php"><![CDATA[
 $flickr = new Zend_Service_Flickr('MY_API_KEY');
 
@@ -26,44 +33,58 @@ foreach ($results as $result) {
 }
 ]]></programlisting>
         </example>
+
         <note>
             <title>Optional parameter</title>
+
             <para>
-                <methodname>tagSearch()</methodname> accepts an optional second parameter as an array of options.
+                <methodname>tagSearch()</methodname> accepts an optional second parameter as an
+                array of options.
             </para>
         </note>
     </sect2>
+
     <sect2 id="zend.service.flickr.finding-users">
         <title>Finding Flickr Users' Photos and Information</title>
+
         <para>
-            <classname>Zend_Service_Flickr</classname> provides several ways to get information about Flickr users:
+            <classname>Zend_Service_Flickr</classname> provides several ways to get information
+            about Flickr users:
         </para>
+
         <itemizedlist>
             <listitem>
                 <para>
-                    <methodname>userSearch()</methodname>: Accepts a string query of space-delimited tags and an optional second
-                    parameter as an array of search options, and returns a set of photos as a
-                    <classname>Zend_Service_Flickr_ResultSet</classname> object.
+                    <methodname>userSearch()</methodname>: Accepts a string query of space-delimited
+                    tags and an optional second parameter as an array of search options, and returns
+                    a set of photos as a <classname>Zend_Service_Flickr_ResultSet</classname>
+                    object.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
-                    <methodname>getIdByUsername()</methodname>: Returns a string user ID associated with the given username string.
+                    <methodname>getIdByUsername()</methodname>: Returns a string user ID associated
+                    with the given username string.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
-                    <methodname>getIdByEmail()</methodname>: Returns a string user ID associated with the given email address
-                    string.
+                    <methodname>getIdByEmail()</methodname>: Returns a string user ID associated
+                    with the given email address string.
                 </para>
             </listitem>
         </itemizedlist>
+
         <example id="zend.service.flickr.finding-users.example-1">
             <title>Finding a Flickr User's Public Photos by E-Mail Address</title>
+
             <para>
-                In this example, we have a Flickr user's e-mail address, and we search for the user's public photos by
-                using the <methodname>userSearch()</methodname> method:
+                In this example, we have a Flickr user's e-mail address, and we search for the
+                user's public photos by using the <methodname>userSearch()</methodname> method:
             </para>
+
             <programlisting language="php"><![CDATA[
 $flickr = new Zend_Service_Flickr('MY_API_KEY');
 
@@ -75,14 +96,18 @@ foreach ($results as $result) {
 ]]></programlisting>
         </example>
     </sect2>
+
     <sect2 id="zend.service.flickr.grouppoolgetphotos">
         <title>Finding photos From a Group Pool</title>
+
         <para>
-            <classname>Zend_Service_Flickr</classname> allows to retrieve a group's pool photos based
-            on the group ID. Use the <methodname>groupPoolGetPhotos()</methodname> method:
+            <classname>Zend_Service_Flickr</classname> allows to retrieve a group's pool photos
+            based on the group ID. Use the <methodname>groupPoolGetPhotos()</methodname> method:
         </para>
+
         <example id="zend.service.flickr.grouppoolgetphotos.example-1">
             <title>Retrieving a Group's Pool Photos by Group ID</title>
+
             <programlisting language="php"><![CDATA[
 $flickr = new Zend_Service_Flickr('MY_API_KEY');
 
@@ -93,24 +118,34 @@ $flickr = new Zend_Service_Flickr('MY_API_KEY');
     }
 ]]></programlisting>
         </example>
+
         <note>
             <title>Optional parameter</title>
+
             <para>
-                <methodname>groupPoolGetPhotos()</methodname> accepts an optional second parameter as an array of options.
+                <methodname>groupPoolGetPhotos()</methodname> accepts an optional second parameter
+                as an array of options.
             </para>
         </note>
     </sect2>
+
     <sect2 id="zend.service.flickr.getimagedetails">
         <title>Retrieving Flickr Image Details</title>
+
         <para>
-            <classname>Zend_Service_Flickr</classname> makes it quick and easy to get an image's details based on a given image
-            ID. Just use the <methodname>getImageDetails()</methodname> method, as in the following example:
+            <classname>Zend_Service_Flickr</classname> makes it quick and easy to get an image's
+            details based on a given image ID. Just use the
+            <methodname>getImageDetails()</methodname> method, as in the following example:
         </para>
+
         <example id="zend.service.flickr.getimagedetails.example-1">
             <title>Retrieving Flickr Image Details</title>
+
             <para>
-                Once you have a Flickr image ID, it is a simple matter to fetch information about the image:
+                Once you have a Flickr image ID, it is a simple matter to fetch information about
+                the image:
             </para>
+
             <programlisting language="php"><![CDATA[
 $flickr = new Zend_Service_Flickr('MY_API_KEY');
 
@@ -121,19 +156,43 @@ echo "<a href=\"$image->clickUri\">Click for Image</a>\n";
 ]]></programlisting>
         </example>
     </sect2>
+
     <sect2 id="zend.service.flickr.classes">
         <title>Zend_Service_Flickr Result Classes</title>
+
         <para>
-            The following classes are all returned by <methodname>tagSearch()</methodname> and <methodname>userSearch()</methodname>:
+            The following classes are all returned by <methodname>tagSearch()</methodname> and
+            <methodname>userSearch()</methodname>:
+
             <itemizedlist>
-                <listitem><para><link linkend="zend.service.flickr.classes.resultset"><classname>Zend_Service_Flickr_ResultSet</classname></link></para></listitem>
-                <listitem><para><link linkend="zend.service.flickr.classes.result"><classname>Zend_Service_Flickr_Result</classname></link></para></listitem>
-                <listitem><para><link linkend="zend.service.flickr.classes.image"><classname>Zend_Service_Flickr_Image</classname></link></para></listitem>
+                <listitem>
+                    <para>
+                        <link
+                            linkend="zend.service.flickr.classes.resultset"><classname>Zend_Service_Flickr_ResultSet</classname></link>
+                    </para>
+                </listitem>
+
+                <listitem>
+                    <para>
+                       <link
+                           linkend="zend.service.flickr.classes.result"><classname>Zend_Service_Flickr_Result</classname></link>
+                   </para>
+                </listitem>
+
+                <listitem>
+                    <para>
+                        <link
+                            linkend="zend.service.flickr.classes.image"><classname>Zend_Service_Flickr_Image</classname></link>
+                    </para>
+                </listitem>
             </itemizedlist>
         </para>
+
         <sect3 id="zend.service.flickr.classes.resultset">
             <title>Zend_Service_Flickr_ResultSet</title>
+
             <para>Represents a set of Results from a Flickr search.</para>
+
             <note>
                 <para>
                     Implements the <classname>SeekableIterator</classname> interface for easy
@@ -141,10 +200,13 @@ echo "<a href=\"$image->clickUri\">Click for Image</a>\n";
                     access to a specific result using <methodname>seek()</methodname>.
                 </para>
             </note>
+
             <sect4 id="zend.service.flickr.classes.resultset.properties">
                 <title>Properties</title>
+
                 <table id="zend.service.flickr.classes.resultset.properties.table-1">
                     <title>Zend_Service_Flickr_ResultSet Properties</title>
+
                     <tgroup cols="3">
                         <thead>
                             <row>
@@ -153,17 +215,20 @@ echo "<a href=\"$image->clickUri\">Click for Image</a>\n";
                                 <entry>Description</entry>
                             </row>
                         </thead>
+
                         <tbody>
                             <row>
                                 <entry>totalResultsAvailable</entry>
                                 <entry>int</entry>
                                 <entry>Total Number of Results available</entry>
                             </row>
+
                             <row>
                                 <entry>totalResultsReturned</entry>
                                 <entry>int</entry>
                                 <entry>Total Number of Results returned</entry>
                             </row>
+
                             <row>
                                 <entry>firstResultPosition</entry>
                                 <entry>int</entry>
@@ -173,8 +238,10 @@ echo "<a href=\"$image->clickUri\">Click for Image</a>\n";
                     </tgroup>
                 </table>
             </sect4>
+
             <sect4 id="zend.service.flickr.classes.resultset.totalResults">
                 <title>Zend_Service_Flickr_ResultSet::totalResults()</title>
+
                 <para>
                     <methodsynopsis>
                         <type>int</type>
@@ -182,23 +249,30 @@ echo "<a href=\"$image->clickUri\">Click for Image</a>\n";
                         <void />
                     </methodsynopsis>
                 </para>
+
                 <para>
                     Returns the total number of results in this result set.
                 </para>
+
                 <para>
                     <link linkend="zend.service.flickr.classes">Back to Class List</link>
                 </para>
             </sect4>
         </sect3>
+
         <sect3 id="zend.service.flickr.classes.result">
             <title>Zend_Service_Flickr_Result</title>
+
             <para>
                 A single Image result from a Flickr query
             </para>
+
             <sect4 id="zend.service.flickr.classes.result.properties">
                 <title>Properties</title>
+
                 <table id="zend.service.flickr.classes.result.properties.table-1">
                     <title>Zend_Service_Flickr_Result Properties</title>
+
                     <tgroup cols="3">
                         <thead>
                             <row>
@@ -207,117 +281,185 @@ echo "<a href=\"$image->clickUri\">Click for Image</a>\n";
                                 <entry>Description</entry>
                             </row>
                         </thead>
+
                         <tbody>
                             <row>
                                 <entry>id</entry>
                                 <entry>string</entry>
                                 <entry>Image ID</entry>
                             </row>
+
                             <row>
                                 <entry>owner</entry>
                                 <entry>string</entry>
                                 <entry>The photo owner's <acronym>NSID</acronym>.</entry>
                             </row>
+
                             <row>
                                 <entry>secret</entry>
                                 <entry>string</entry>
                                 <entry>A key used in url construction.</entry>
                             </row>
+
                             <row>
                                 <entry>server</entry>
                                 <entry>string</entry>
-                                <entry>The servername to use for <acronym>URL</acronym> construction.</entry>
+
+                                <entry>
+                                    The servername to use for <acronym>URL</acronym> construction.
+                                </entry>
                             </row>
+
                             <row>
                                 <entry>title</entry>
                                 <entry>string</entry>
                                 <entry>The photo's title.</entry>
                             </row>
+
                             <row>
                                 <entry>ispublic</entry>
                                 <entry>string</entry>
                                 <entry>The photo is public.</entry>
                             </row>
+
                             <row>
                                 <entry>isfriend</entry>
                                 <entry>string</entry>
-                                <entry>The photo is visible to you because you are a friend of the owner.</entry>
+
+                                <entry>
+                                    The photo is visible to you because you are a friend of the
+                                    owner.
+                                </entry>
                             </row>
+
                             <row>
                                 <entry>isfamily</entry>
                                 <entry>string</entry>
-                                <entry>The photo is visible to you because you are family of the owner.</entry>
+
+                                <entry>
+                                    The photo is visible to you because you are family of the owner.
+                                </entry>
                             </row>
+
                             <row>
                                 <entry>license</entry>
                                 <entry>string</entry>
                                 <entry>The license the photo is available under.</entry>
                             </row>
+
                             <row>
                                 <entry>dateupload</entry>
                                 <entry>string</entry>
                                 <entry>The date the photo was uploaded.</entry>
                             </row>
+
                             <row>
                                 <entry>datetaken</entry>
                                 <entry>string</entry>
                                 <entry>The date the photo was taken.</entry>
                             </row>
+
                             <row>
                                 <entry>ownername</entry>
                                 <entry>string</entry>
                                 <entry>The screenname of the owner.</entry>
                             </row>
+
                             <row>
                                 <entry>iconserver</entry>
                                 <entry>string</entry>
-                                <entry>The server used in assembling icon <acronym>URL</acronym>s.</entry>
+
+                                <entry>
+                                    The server used in assembling icon <acronym>URL</acronym>s.
+                                </entry>
                             </row>
+
                             <row>
                                 <entry>Square</entry>
-                                <entry><link linkend="zend.service.flickr.classes.image">Zend_Service_Flickr_Image</link></entry>
+
+                                <entry>
+                                    <link
+                                        linkend="zend.service.flickr.classes.image">Zend_Service_Flickr_Image</link>
+                                </entry>
+
                                 <entry>A 75x75 thumbnail of the image.</entry>
                             </row>
+
                             <row>
                                 <entry>Thumbnail</entry>
-                                <entry><link linkend="zend.service.flickr.classes.image">Zend_Service_Flickr_Image</link></entry>
+
+                                <entry>
+                                    <link
+                                        linkend="zend.service.flickr.classes.image">Zend_Service_Flickr_Image</link>
+                                </entry>
+
                                 <entry>A 100 pixel thumbnail of the image.</entry>
                             </row>
+
                             <row>
                                 <entry>Small</entry>
-                                <entry><link linkend="zend.service.flickr.classes.image">Zend_Service_Flickr_Image</link></entry>
+
+                                <entry>
+                                    <link
+                                        linkend="zend.service.flickr.classes.image">Zend_Service_Flickr_Image</link>
+                                </entry>
+
                                 <entry>A 240 pixel version of the image.</entry>
                             </row>
+
                             <row>
                                 <entry>Medium</entry>
-                                <entry><link linkend="zend.service.flickr.classes.image">Zend_Service_Flickr_Image</link></entry>
+
+                                <entry>
+                                    <link
+                                        linkend="zend.service.flickr.classes.image">Zend_Service_Flickr_Image</link>
+                                </entry>
+
                                 <entry>A 500 pixel version of the image.</entry>
                             </row>
+
                             <row>
                                 <entry>Large</entry>
-                                <entry><link linkend="zend.service.flickr.classes.image">Zend_Service_Flickr_Image</link></entry>
+
+                                <entry>
+                                    <link
+                                        linkend="zend.service.flickr.classes.image">Zend_Service_Flickr_Image</link>
+                                </entry>
+
                                 <entry>A 640 pixel version of the image.</entry>
                             </row>
+
                             <row>
                                 <entry>Original</entry>
-                                <entry><link linkend="zend.service.flickr.classes.image">Zend_Service_Flickr_Image</link></entry>
+
+                                <entry>
+                                    <link
+                                        linkend="zend.service.flickr.classes.image">Zend_Service_Flickr_Image</link>
+                                </entry>
+
                                 <entry>The original image.</entry>
                             </row>
                         </tbody>
                     </tgroup>
                 </table>
+
                 <para>
                     <link linkend="zend.service.flickr.classes">Back to Class List</link>
                 </para>
             </sect4>
         </sect3>
+
         <sect3 id="zend.service.flickr.classes.image">
             <title>Zend_Service_Flickr_Image</title>
+
             <para>Represents an Image returned by a Flickr search.</para>
+
             <sect4 id="zend.service.flickr.classes.image.properties">
                 <title>Properties</title>
+
                 <table id="zend.service.flickr.classes.image.properties.table-1">
                     <title>Zend_Service_Flickr_Image Properties</title>
+
                     <tgroup cols="3">
                         <thead>
                             <row>
@@ -326,22 +468,30 @@ echo "<a href=\"$image->clickUri\">Click for Image</a>\n";
                                 <entry>Description</entry>
                             </row>
                         </thead>
+
                         <tbody>
                             <row>
                                 <entry>uri</entry>
                                 <entry>string</entry>
                                 <entry>URI for the original image</entry>
                             </row>
+
                             <row>
                                 <entry>clickUri</entry>
                                 <entry>string</entry>
-                                <entry>Clickable <acronym>URI</acronym> (i.e. the Flickr page) for the image</entry>
+
+                                <entry>
+                                    Clickable <acronym>URI</acronym> (i.e. the Flickr page) for the
+                                    image
+                                </entry>
                             </row>
+
                             <row>
                                 <entry>width</entry>
                                 <entry>int</entry>
                                 <entry>Width of the Image</entry>
                             </row>
+
                             <row>
                                 <entry>height</entry>
                                 <entry>int</entry>
@@ -350,6 +500,7 @@ echo "<a href=\"$image->clickUri\">Click for Image</a>\n";
                         </tbody>
                     </tgroup>
                 </table>
+
                 <para>
                     <link linkend="zend.service.flickr.classes">Back to Class List</link>
                 </para>

documentation/manual/en/module_specs/Zend_Service_LiveDocx.xml

@@ -38,24 +38,28 @@
                     <classname>Zend_Service_LiveDocx</classname> within a matter of minutes.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     <ulink url="http://www.phplivedocx.org/">
                     <classname>Zend_Service_LiveDocx</classname> blog and web site</ulink>.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     <ulink url="http://www.livedocx.com/pub/documentation/api.aspx">
                     LiveDocx SOAP API documentation</ulink>.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     <ulink url="https://api.livedocx.com/1.2/mailmerge.asmx?wsdl">
                     LiveDocx WSDL</ulink>.
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     <ulink url="https://www.livedocx.com/">LiveDocx blog and web site</ulink>.
@@ -814,7 +818,7 @@ foreach ($blockNames as $blockName) {
                     font-substitution will take place. This may lead to undesirable results.
                 </para>
 
-            <programlisting language="php"><![CDATA[
+                <programlisting language="php"><![CDATA[
 $phpLiveDocx = new Zend_Service_LiveDocx_MailMerge();
 
 $phpLiveDocx->setUsername('myUsername')

documentation/manual/en/module_specs/Zend_Service_Nirvanix.xml

@@ -25,15 +25,15 @@
         <title>Registering with Nirvanix</title>
 
         <para>
-            Before you can get started with <classname>Zend_Service_Nirvanix</classname>, you must first
-            register for an account. Please see the
+            Before you can get started with <classname>Zend_Service_Nirvanix</classname>, you must
+            first register for an account. Please see the
             <ulink url="http://www.nirvanix.com/gettingStarted.aspx">Getting Started</ulink>
             page on the Nirvanix website for more information.
         </para>
 
         <para>
-            After registering, you will receive a Username, Password, and
-            Application Key. All three are required to use <classname>Zend_Service_Nirvanix</classname>.
+            After registering, you will receive a Username, Password, and Application Key.
+            All three are required to use <classname>Zend_Service_Nirvanix</classname>.
         </para>
     </sect2>
 
@@ -41,22 +41,22 @@
         <title>API Documentation</title>
 
         <para>
-            Access to the Nirvanix IMFS is available through both <acronym>SOAP</acronym> and a faster
-            REST service. <classname>Zend_Service_Nirvanix</classname> provides a
+            Access to the Nirvanix IMFS is available through both <acronym>SOAP</acronym> and a
+            faster REST service. <classname>Zend_Service_Nirvanix</classname> provides a
             relatively thin <acronym>PHP</acronym> 5 wrapper around the REST service.
         </para>
 
         <para>
-            <classname>Zend_Service_Nirvanix</classname> aims to make using the Nirvanix REST service
-            easier but understanding the service itself is still essential to be successful
+            <classname>Zend_Service_Nirvanix</classname> aims to make using the Nirvanix REST
+            service easier but understanding the service itself is still essential to be successful
             with Nirvanix.
         </para>
 
         <para>
-            The <ulink url="http://developer.nirvanix.com/sitefiles/1000/API.html">Nirvanix <acronym>API</acronym> Documentation</ulink>
-            provides an overview as well as detailed information using the
-            service. Please familiarize yourself with this document and refer back to it
-            as you use <classname>Zend_Service_Nirvanix</classname>.
+            The <ulink url="http://developer.nirvanix.com/sitefiles/1000/API.html">Nirvanix
+            <acronym>API</acronym> Documentation</ulink> provides an overview as well as detailed
+            information using the service. Please familiarize yourself with this document and refer
+            back to it as you use <classname>Zend_Service_Nirvanix</classname>.
         </para>
     </sect2>
 
@@ -85,9 +85,9 @@
 
                 <listitem>
                     <para>
-                        A proxy object that is more convenient to use than an <acronym>HTTP</acronym> client
-                        alone, mostly removing the need to manually construct <acronym>HTTP</acronym> POST
-                        requests to access the REST service.
+                        A proxy object that is more convenient to use than an
+                        <acronym>HTTP</acronym> client alone, mostly removing the need to manually
+                        construct <acronym>HTTP</acronym> POST requests to access the REST service.
                     </para>
                 </listitem>
 
@@ -143,8 +143,8 @@ $imfs->unlink('/foo.txt');
         </para>
 
         <para>
-            Nirvanix divides its web services into
-            <ulink url="http://developer.nirvanix.com/sitefiles/1000/API.html#_Toc175999879">namespaces</ulink>.
+            Nirvanix divides its web services into <ulink
+                url="http://developer.nirvanix.com/sitefiles/1000/API.html#_Toc175999879">namespaces</ulink>.
             Each namespace encapsulates a group of related operations. After getting
             an instance of <classname>Zend_Service_Nirvanix</classname>, call the
             <methodname>getService()</methodname> method to create a proxy for the namespace
@@ -152,9 +152,9 @@ $imfs->unlink('/foo.txt');
         </para>
 
         <para>
-            After you have a proxy for the namespace you want to use, call methods on it.
-            The proxy will allow you to use any command available on the REST <acronym>API</acronym>. The
-            proxy may also make convenience methods available, which wrap web service
+            After you have a proxy for the namespace you want to use, call methods on it. The
+            proxy will allow you to use any command available on the REST <acronym>API</acronym>.
+            The proxy may also make convenience methods available, which wrap web service
             commands. The example above shows using the IMFS convenience methods to create a
             new file, retrieve and display that file, and finally delete the file.
         </para>
@@ -164,33 +164,37 @@ $imfs->unlink('/foo.txt');
         <title>Understanding the Proxy</title>
 
         <para>
-            In the previous example, we used the <methodname>getService()</methodname> method to return
-            a proxy object to the <constant>IMFS</constant> namespace. The proxy object allows
-            you to use the Nirvanix REST service in a way that's closer to making a normal
-            <acronym>PHP</acronym> method call, as opposed to constructing your own <acronym>HTTP</acronym> request objects.
+            In the previous example, we used the <methodname>getService()</methodname> method to
+            return a proxy object to the <constant>IMFS</constant> namespace. The proxy object
+            allows you to use the Nirvanix REST service in a way that's closer to making a normal
+            <acronym>PHP</acronym> method call, as opposed to constructing your own
+            <acronym>HTTP</acronym> request objects.
         </para>
 
         <para>
             A proxy object may provide convenience methods. These are methods that the
             <classname>Zend_Service_Nirvanix</classname> provides to simplify the use of
             the Nirvanix web services. In the previous example, the methods
-            <methodname>putContents()</methodname>, <methodname>getContents()</methodname>, and <methodname>unlink()</methodname>
-            do not have direct equivalents in the REST <acronym>API</acronym>. They are convenience methods
-            provided by <classname>Zend_Service_Nirvanix</classname> that abstract more complicated
-            operations on the REST <acronym>API</acronym>.
+            <methodname>putContents()</methodname>, <methodname>getContents()</methodname>, and
+            <methodname>unlink()</methodname> do not have direct equivalents in the REST
+            <acronym>API</acronym>. They are convenience methods provided by
+            <classname>Zend_Service_Nirvanix</classname> that abstract more complicated operations
+            on the REST <acronym>API</acronym>.
         </para>
 
         <para>
-            For all other method calls to the proxy object, the proxy will dynamically
-            convert the method call to the equivalent <acronym>HTTP</acronym> POST request to the REST <acronym>API</acronym>.
-            It does this by using the method name as the <acronym>API</acronym> command, and an associative
-            array in the first argument as the POST parameters.
+            For all other method calls to the proxy object, the proxy will dynamically convert the
+            method call to the equivalent <acronym>HTTP</acronym> POST request to the REST
+            <acronym>API</acronym>. It does this by using the method name as the
+            <acronym>API</acronym> command, and an associative array in the first argument as the
+            POST parameters.
         </para>
 
         <para>
-            Let's say you want to call the REST <acronym>API</acronym> method
-            <ulink url="http://developer.nirvanix.com/sitefiles/1000/API.html#_Toc175999923">RenameFile</ulink>,
-            which does not have a convenience method in <classname>Zend_Service_Nirvanix</classname>:
+            Let's say you want to call the REST <acronym>API</acronym> method <ulink
+                url="http://developer.nirvanix.com/sitefiles/1000/API.html#_Toc175999923">RenameFile</ulink>,
+            which does not have a convenience method in
+            <classname>Zend_Service_Nirvanix</classname>:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -209,20 +213,21 @@ $result = $imfs->renameFile(array('filePath' => '/path/to/foo.txt',
             Above, a proxy for the <constant>IMFS</constant> namespace is created. A method,
             <methodname>renameFile()</methodname>, is then called on the proxy. This method does not
             exist as a convenience method in the <acronym>PHP</acronym> code, so it is trapped by
-            <methodname>__call()</methodname> and converted into a POST request to the REST <acronym>API</acronym> where
-            the associative array is used as the POST parameters.
+            <methodname>__call()</methodname> and converted into a POST request to the REST
+            <acronym>API</acronym> where the associative array is used as the POST parameters.
         </para>
 
         <para>
-            Notice in the Nirvanix <acronym>API</acronym> documentation that <code>sessionToken</code> is required
-            for this method but we did not give it to the proxy object. It is added
-            automatically for your convenience.
+            Notice in the Nirvanix <acronym>API</acronym> documentation that
+            <code>sessionToken</code> is required for this method but we did not give it to the
+            proxy object. It is added automatically for your convenience.
         </para>
 
         <para>
-            The result of this operation will either be a <classname>Zend_Service_Nirvanix_Response</classname>
-            object wrapping the <acronym>XML</acronym> returned by Nirvanix, or a <classname>Zend_Service_Nirvanix_Exception</classname>
-            if an error occurred.
+            The result of this operation will either be a
+            <classname>Zend_Service_Nirvanix_Response</classname> object wrapping the
+            <acronym>XML</acronym> returned by Nirvanix, or a
+            <classname>Zend_Service_Nirvanix_Exception</classname> if an error occurred.
         </para>
     </sect2>
 
@@ -230,10 +235,11 @@ $result = $imfs->renameFile(array('filePath' => '/path/to/foo.txt',
         <title>Examining Results</title>
 
         <para>
-            The Nirvanix REST <acronym>API</acronym> always returns its results in <acronym>XML</acronym>. <classname>Zend_Service_Nirvanix</classname>
-            parses this <acronym>XML</acronym> with the <code>SimpleXML</code> extension and then decorates
-            the resulting <code>SimpleXMLElement</code> with a <classname>Zend_Service_Nirvanix_Response</classname>
-            object.
+            The Nirvanix REST <acronym>API</acronym> always returns its results in
+            <acronym>XML</acronym>. <classname>Zend_Service_Nirvanix</classname> parses this
+            <acronym>XML</acronym> with the <code>SimpleXML</code> extension and then decorates the
+            resulting <code>SimpleXMLElement</code> with a
+            <classname>Zend_Service_Nirvanix_Response</classname> object.
         </para>
 
         <para>
@@ -289,8 +295,9 @@ Zend_Service_Nirvanix_Response Object
         </para>
 
         <para>
-            All operations against the REST service result in an <acronym>XML</acronym> return payload that
-            contains a <code>ResponseCode</code> element, such as the following example:
+            All operations against the REST service result in an <acronym>XML</acronym> return
+            payload that contains a <code>ResponseCode</code> element, such as the following
+            example:
         </para>
 
         <programlisting language="xml"><![CDATA[
@@ -308,8 +315,8 @@ Zend_Service_Nirvanix_Response Object
 
         <para>
             To alleviate the need to repeatedly check if the <code>ResponseCode</code>
-            is non-zero, <classname>Zend_Service_Nirvanix</classname> automatically checks each response
-            returned by Nirvanix. If the <code>ResponseCode</code> indicates an
+            is non-zero, <classname>Zend_Service_Nirvanix</classname> automatically checks each
+            response returned by Nirvanix. If the <code>ResponseCode</code> indicates an
             error, a <classname>Zend_Service_Nirvanix_Exception</classname> will be thrown.
         </para>
 
@@ -331,9 +338,10 @@ try {
 ]]></programlisting>
 
         <para>
-            In the example above, <methodname>unlink()</methodname> is a convenience method that wraps the
-            <code>DeleteFiles</code> command on the REST <acronym>API</acronym>. The <code>filePath</code> parameter required by the
-            <ulink url="http://developer.nirvanix.com/sitefiles/1000/API.html#_Toc175999918">DeleteFiles</ulink>
+            In the example above, <methodname>unlink()</methodname> is a convenience method that
+            wraps the <code>DeleteFiles</code> command on the REST <acronym>API</acronym>. The
+            <code>filePath</code> parameter required by the <ulink
+                url="http://developer.nirvanix.com/sitefiles/1000/API.html#_Toc175999918">DeleteFiles</ulink>
             command contains a path that does not exist. This will result in a
             <classname>Zend_Service_Nirvanix</classname> exception being thrown with the message
             "Invalid path" and code 70005.
@@ -341,10 +349,9 @@ try {
 
         <para>
             The <ulink url="http://developer.nirvanix.com/sitefiles/1000/API.html">Nirvanix
-            <acronym>API</acronym> Documentation</ulink> describes the errors associated with each command. Depending
-            on your needs, you may wrap each command in a <code>try</code> block or
-            wrap many commands in the same <code>try</code> block for convenience.
+            <acronym>API</acronym> Documentation</ulink> describes the errors associated with each
+            command. Depending on your needs, you may wrap each command in a <code>try</code> block
+            or wrap many commands in the same <code>try</code> block for convenience.
         </para>
     </sect2>
-
 </sect1>

documentation/manual/en/module_specs/Zend_Service_SlideShare.xml

@@ -1,7 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
 <sect1 id="zend.service.slideshare">
-
     <title>Introduction</title>
 
     <para>
@@ -12,21 +11,21 @@
     </para>
 
     <sect2 id="zend.service.slideshare.basicusage">
-
         <title>Getting Started with Zend_Service_SlideShare</title>
 
         <para>
-            In order to use the <classname>Zend_Service_SlideShare</classname> component you must first create an account
-            on the slideshare.net servers (more information can be found
+            In order to use the <classname>Zend_Service_SlideShare</classname> component you must
+            first create an account on the slideshare.net servers (more information can be found
             <ulink url="http://www.slideshare.net/developers/">here</ulink>) in order to receive an
-            <acronym>API</acronym> key, username, password and shared secret value -- all of which are needed in order
-            to use the <classname>Zend_Service_SlideShare</classname> component.
+            <acronym>API</acronym> key, username, password and shared secret value -- all of which
+            are needed in order to use the <classname>Zend_Service_SlideShare</classname> component.
         </para>
 
         <para>
             Once you have setup an account, you can begin using the
-            <classname>Zend_Service_SlideShare</classname> component by creating a new instance of the
-            <classname>Zend_Service_SlideShare</classname> object and providing these values as shown below:
+            <classname>Zend_Service_SlideShare</classname> component by creating a new instance of
+            the <classname>Zend_Service_SlideShare</classname> object and providing these values as
+            shown below:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -36,18 +35,16 @@ $ss = new Zend_Service_SlideShare('APIKEY',
                                   'USERNAME',
                                   'PASSWORD');
 ]]></programlisting>
-
     </sect2>
 
     <sect2 id="zend.service.slideshare.slideshowobj">
-
         <title>The SlideShow object</title>
 
         <para>
-            All slide shows in the <classname>Zend_Service_SlideShare</classname> component are represented
-            using the <classname>Zend_Service_SlideShare_SlideShow</classname> object (both when retrieving
-            and uploading new slide shows). For your reference a pseudo-code version of this class
-            is provided below.
+            All slide shows in the <classname>Zend_Service_SlideShare</classname> component are
+            represented using the <classname>Zend_Service_SlideShare_SlideShow</classname> object
+            (both when retrieving and uploading new slide shows). For your reference a pseudo-code
+            version of this class is provided below.
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -190,30 +187,26 @@ class Zend_Service_SlideShare_SlideShow {
 ]]></programlisting>
 
         <note>
-
             <para>
                 The above pseudo-class only shows those methods which should be used by end-user
                 developers. Other available methods are internal to the component.
             </para>
-
         </note>
 
         <para>
-            When using the <classname>Zend_Service_SlideShare</classname> component, this data class will be
-            used frequently to browse or add new slide shows to or from the web service.
+            When using the <classname>Zend_Service_SlideShare</classname> component, this data class
+            will be used frequently to browse or add new slide shows to or from the web service.
         </para>
-
     </sect2>
 
     <sect2 id="zend.service.slideshare.getslideshow">
-
         <title>Retrieving a single slide show</title>
 
         <para>
-            The simplest usage of the <classname>Zend_Service_SlideShare</classname> component is the
-            retrieval of a single slide show by slide show ID provided by the slideshare.net
-            application and is done by calling the <methodname>getSlideShow()</methodname> method of a
-            <classname>Zend_Service_SlideShare</classname> object and using the resulting
+            The simplest usage of the <classname>Zend_Service_SlideShare</classname> component is
+            the retrieval of a single slide show by slide show ID provided by the slideshare.net
+            application and is done by calling the <methodname>getSlideShow()</methodname> method of
+            a <classname>Zend_Service_SlideShare</classname> object and using the resulting
             <classname>Zend_Service_SlideShare_SlideShow</classname> object as shown.
         </para>
 
@@ -229,11 +222,9 @@ $slideshow = $ss->getSlideShow(123456);
 print "Slide Show Title: {$slideshow->getTitle()}<br/>\n";
 print "Number of views: {$slideshow->getNumViews()}<br/>\n";
 ]]></programlisting>
-
     </sect2>
 
     <sect2 id="zend.service.slideshare.getslideshowlist">
-
         <title>Retrieving Groups of Slide Shows</title>
 
         <para>
@@ -249,8 +240,8 @@ print "Number of views: {$slideshow->getNumViews()}<br/>\n";
 
                 <para>
                     You can retrieve slide shows from a specific account by using the
-                    <methodname>getSlideShowsByUsername()</methodname> method and providing the username from
-                    which the slide shows should be retrieved
+                    <methodname>getSlideShowsByUsername()</methodname> method and providing the
+                    username from which the slide shows should be retrieved
                 </para>
             </listitem>
 
@@ -304,17 +295,15 @@ foreach($ss_user as $slideshow) {
    print "Slide Show Title: {$slideshow->getTitle}<br/>\n";
 }
 ]]></programlisting>
-
     </sect2>
 
     <sect2 id="zend.service.slideshare.caching">
-
         <title>Zend_Service_SlideShare Caching policies</title>
 
         <para>
-            By default, <classname>Zend_Service_SlideShare</classname> will cache any request against the web
-            service automatically to the filesystem (default path <code>/tmp</code>) for 12 hours.
-            If you desire to change this behavior, you must provide your own
+            By default, <classname>Zend_Service_SlideShare</classname> will cache any request
+            against the web service automatically to the filesystem (default path <code>/tmp</code>)
+            for 12 hours. If you desire to change this behavior, you must provide your own
             <xref linkend="zend.cache" /> object using the <code>setCacheObject</code> method as
             shown:
         </para>
@@ -339,19 +328,17 @@ $ss->setCacheObject($cache);
 
 $ss_user = $ss->getSlideShowsByUser('username', $starting_offset, $limit);
 ]]></programlisting>
-
     </sect2>
 
     <sect2 id="zend.service.slideshare.httpclient">
-
         <title>Changing the behavior of the HTTP Client</title>
 
         <para>
-            If for whatever reason you would like to change the behavior of the <acronym>HTTP</acronym> client when
-            making the web service request, you can do so by creating your own instance of the
-            <classname>Zend_Http_Client</classname> object (see <xref linkend="zend.http" />). This is useful
-            for instance when it is desirable to set the timeout for the connection to something
-            other then default as shown:
+            If for whatever reason you would like to change the behavior of the
+            <acronym>HTTP</acronym> client when making the web service request, you can do so by
+            creating your own instance of the <classname>Zend_Http_Client</classname> object (see
+            <xref linkend="zend.http" />). This is useful for instance when it is desirable to set
+            the timeout for the connection to something other then default as shown:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -365,7 +352,5 @@ $ss = new Zend_Service_SlideShare('APIKEY',
 $ss->setHttpClient($client);
 $ss_user = $ss->getSlideShowsByUser('username', $starting_offset, $limit);
 ]]></programlisting>
-
     </sect2>
-
 </sect1>