[MANUAL] English:

- manual fixes

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

documentation/manual/en/module_specs/Zend_Exception-Basic.xml

@@ -5,7 +5,8 @@
 
     <para>
         <classname>Zend_Exception</classname> is the base class for all exceptions thrown by Zend
-        Framework.  This class extends the base <classname>Exception</classname> class of PHP.
+        Framework. This class extends the base <classname>Exception</classname> class of
+        <acronym>PHP</acronym>.
     </para>
 
     <example id="zend.exception.catchall.example">

documentation/manual/en/module_specs/Zend_Exception-Previous.xml

@@ -4,11 +4,12 @@
     <title>Previous Exceptions</title>
 
     <para>
-        Since Zend Framework 1.10, <classname>Zend_Exception</classname> implements the PHP 5.3
-        support for previous exceptions. Simply put, when in a <methodname>catch</methodname>
-        block, you can throw a new exception that references the original exception, which helps
-        provide additional context when debugging. By providing this support in Zend Framework, your
-        code may now be forwards compatible with PHP 5.3.
+        Since Zend Framework 1.10, <classname>Zend_Exception</classname> implements the
+        <acronym>PHP</acronym> 5.3 support for previous exceptions. Simply put, when in a
+        <methodname>catch()</methodname> block, you can throw a new exception that references the
+        original exception, which helps provide additional context when debugging. By providing this
+        support in Zend Framework, your code may now be forwards compatible with
+        <acronym>PHP</acronym> 5.3.
     </para>
 
     <para>

documentation/manual/en/module_specs/Zend_Feed-ConsumingAtomSingle.xml

@@ -4,10 +4,11 @@
     <title>Consuming a Single Atom Entry</title>
 
     <para>
-        Single Atom <code>&lt;entry&gt;</code> elements are also valid by themselves. Usually the
-        <acronym>URL</acronym> for an entry is the feed's <acronym>URL</acronym> followed by
-        <code>/&lt;entryId&gt;</code>, such as <code>http://atom.example.com/feed/1</code>, using
-        the example <acronym>URL</acronym> we used above.
+        Single Atom <command>&lt;entry&gt;</command> elements are also valid by themselves. Usually
+        the <acronym>URL</acronym> for an entry is the feed's <acronym>URL</acronym> followed by
+        <command>/&lt;entryId&gt;</command>, such as
+        <filename>http://atom.example.com/feed/1</filename>, using the example
+        <acronym>URL</acronym> we used above.
     </para>
 
     <para>
@@ -28,7 +29,7 @@ $entry = $feed->current();
 
     <para>
         Alternatively, you could instantiate the entry object directly if you know you are accessing
-        an <code>&lt;entry&gt;</code>-only document:
+        an <command>&lt;entry&gt;</command>-only document:
     </para>
 
     <example id="zend.feed.consuming-atom-single-entry.example.entryatom">

documentation/manual/en/module_specs/Zend_Feed-ModifyingFeed.xml

@@ -23,22 +23,22 @@ echo $entry->saveXML();
 ]]></programlisting>
 
         <para>
-            This will output a full (includes <code>&lt;?xml ... &gt;</code> prologue)
+            This will output a full (includes <command>&lt;?xml ... &gt;</command> prologue)
             <acronym>XML</acronym> representation of the new entry, including any necessary
             <acronym>XML</acronym> namespaces.
         </para>
 
         <para>
             Note that the above will work even if the existing entry does not already have an author
-            tag. You can use as many levels of <code>-&gt;</code> access as you like before getting
-            to an assignment; all of the intervening levels will be created for you automatically if
-            necessary.
+            tag. You can use as many levels of <command>-&gt;</command> access as you like before
+            getting to an assignment; all of the intervening levels will be created for you
+            automatically if necessary.
         </para>
     </example>
 
     <para>
-        If you want to use a namespace other than <code>atom:</code>, <code>rss:</code>, or
-        <code>osrss:</code> in your entry, you need to register the namespace with
+        If you want to use a namespace other than <command>atom:</command>, <command>rss:</command>,
+        or <command>osrss:</command> in your entry, you need to register the namespace with
         <classname>Zend_Feed</classname> using
         <methodname>Zend_Feed::registerNamespace()</methodname>. When you are modifying an existing
         element, it will always maintain its original namespace. When adding a new element, it will

documentation/manual/en/module_specs/Zend_Feed_Writer.xml

@@ -158,9 +158,11 @@ $out = $feed->export('atom');
     </author>
     <link rel="hub" href="http://pubsubhubbub.appspot.com/"/>
     <entry>
-        <title type="html"><![CDATA[All Your Base Are Belong To Us]]]]><![CDATA[></title>
+        <title type="html"><![CDATA[All Your Base Are Belong To
+            Us]]]]><![CDATA[></title>
         <summary type="html">
-            <![CDATA[Exposing the difficultly of porting games to English.]]]]><![CDATA[>
+            <![CDATA[Exposing the difficultly of porting games to
+                English.]]]]><![CDATA[>
         </summary>
         <published>2009-12-14T20:28:18+00:00</published>
         <updated>2009-12-14T20:28:18+00:00</updated>