[DOCUMENTATION] English:

- manual fixes

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

documentation/manual/en/module_specs/Zend_Db_Statement.xml

@@ -81,7 +81,7 @@ $stmt = new Zend_Db_Statement_Mysqli($db, $sql);
 
         <para>
             If you use <emphasis>positional parameters</emphasis>, or those
-            that are marked with a question mark symbol (<code>?</code>), pass
+            that are marked with a question mark symbol ('<emphasis>?</emphasis>'), pass
             the bind values in a plain array.
         </para>
 
@@ -99,7 +99,7 @@ $stmt->execute(array('goofy', 'FIXED'));
         <para>
             If you use <emphasis>named parameters</emphasis>, or those that are
             indicated by a string identifier preceded by a colon character
-            (<code>:</code>), pass the bind values in an associative array.
+            ('<emphasis>:</emphasis>'), pass the bind values in an associative array.
             The keys of this array should match the parameter names.
         </para>
 

documentation/manual/en/module_specs/Zend_Dojo-View-Dojo.xml

@@ -292,7 +292,7 @@ $view->dojo()->addLayer('/js/foo/foo.js');
             <listitem><para><methodname>isEnabled()</methodname>: determine whether or not
                     Dojo integration is enabled.</para></listitem>
             <listitem><para><methodname>requireModule($module)</methodname>: setup a
-                    <code>dojo.require</code> statement.</para></listitem>
+                    <property>dojo.require</property> statement.</para></listitem>
             <listitem><para><methodname>getModules()</methodname>: determine what modules
                     have been required.</para></listitem>
             <listitem><para><methodname>registerModulePath($module, $path)</methodname>:
@@ -346,8 +346,8 @@ $view->dojo()->addLayer('/js/foo/foo.js');
                     a single dojo/dijit configuration value.</para></listitem>
             <listitem><para><methodname>getDjConfig()</methodname>: get all dojo/dijit
                     configuration values.</para></listitem>
-            <listitem><para><code>getDjConfigOption($option, $default =
-                    null)</code>: get a single dojo/dijit configuration
+            <listitem><para><methodname>getDjConfigOption($option, $default =
+                    null)</methodname>: get a single dojo/dijit configuration
                     value.</para></listitem>
             <listitem><para><methodname>addStylesheetModule($module)</methodname>: add a
                     stylesheet based on a module theme.</para></listitem>

documentation/manual/en/module_specs/Zend_Dojo.xml

@@ -22,7 +22,7 @@
 
     <para>
         The Dojo distribution itself may be found in the
-        <code>externals/dojo/</code> directory of the Zend Framework
+        <filename>externals/dojo/</filename> directory of the Zend Framework
         distribution. This is a source distribution, which includes Dojo's full
         javascript source, unit tests, and build tools. You can symlink this
         into your javascript directory, copy it, or use the build tool to create

documentation/manual/en/module_specs/Zend_File_Transfer-Migration.xml

@@ -365,8 +365,8 @@ $upload->addValidator('Size',
                 As noted by users, the validators from <classname>Zend_File_Transfer</classname>
                 do not work the same way like the default ones from
                 <classname>Zend_Form</classname>. <classname>Zend_Form</classname> allows the usage
-                of a <code>breakChainOnFailure</code> parameter which breaks the validation for all
-                further validators when an validation error has occurred.
+                of a <varname>$breakChainOnFailure</varname> parameter which breaks the validation
+                for all further validators when an validation error has occurred.
             </para>
 
             <para>
@@ -380,8 +380,8 @@ $upload->addValidator('Size',
                 </para></listitem>
 
                 <listitem><para>
-                    New method <acronym>API</acronym>: <code>addValidator($validator, $breakChainOnFailure, $options,
-                        $files)</code>.
+                    New method <acronym>API</acronym>: <methodname>addValidator($validator,
+                    $breakChainOnFailure, $options, $files)</methodname>.
                 </para></listitem>
             </itemizedlist>
 

documentation/manual/en/module_specs/Zend_Filter-Set.xml

@@ -105,8 +105,8 @@
             stripped from it, except those that have been explicitly allowed. In addition to the
             ability to specify which tags are allowed, developers can specify which attributes are
             allowed across all allowed tags and for specific tags only. Finally, this filter offers
-            control over whether comments (e.g., <code>&lt;!-- ... --&gt;</code>) are removed or
-            allowed.
+            control over whether comments (e.g., <command>&lt;!-- ... --&gt;</command>) are removed
+            or allowed.
         </para>
     </sect2>
 

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

@@ -563,10 +563,10 @@ class RegistrationController extends Zend_Controller_Action
 ]]></programlisting>
 
             <para>
-                The above methods allow us to use notations such as "<code>$subForm =
-                    $this-&gt;getCurrentSubForm();</code>" to retrieve the current
-                sub form for validation, or "<code>$next =
-                    $this-&gt;getNextSubForm();</code>" to get the next one to
+                The above methods allow us to use notations such as "<command>$subForm =
+                    $this-&gt;getCurrentSubForm();</command>" to retrieve the current
+                sub form for validation, or "<command>$next =
+                    $this-&gt;getNextSubForm();</command>" to get the next one to
                 display.
             </para>
 

documentation/manual/en/module_specs/Zend_Form-I18n.xml

@@ -27,7 +27,7 @@
         <para>
             You can disable translation for any form, element, display group, or
             sub form by calling its <methodname>setDisableTranslator($flag)</methodname>
-            method or passing a <code>disableTranslator</code> option to the
+            method or passing a <property>disableTranslator</property> option to the
             object. This can be useful when you want to selectively disable
             translation for individual elements or sets of elements.
         </para>

documentation/manual/en/module_specs/Zend_Gdata_AuthSub.xml

@@ -55,7 +55,7 @@
         <para>
             After Google's authentication server redirects the user's browser
             back to the current application, a GET request parameter is set,
-            called <code>token</code>.
+            called <emphasis>token</emphasis>.
             The value of this parameter is a single-use token that can be
             used for authenticated access.
             This token can be converted into a multi-use token and stored

documentation/manual/en/module_specs/Zend_Gdata_Docs.xml

@@ -21,7 +21,7 @@
         <title>Get a List of Documents</title>
         <para>
             You can get a list of the Google Documents for a particular user by using
-            the <code>getDocumentListFeed</code> method of the docs
+            the <methodname>getDocumentListFeed()</methodname> method of the docs
             service. The service will return a
             <classname>Zend_Gdata_Docs_DocumentListFeed</classname> object
             containing a list of documents associated with the authenticated
@@ -39,7 +39,7 @@ $feed = $docs->getDocumentListFeed();
         The resulting <classname>Zend_Gdata_Docs_DocumentListFeed</classname> object
         represents the response from the server. This feed contains a list of
         <classname>Zend_Gdata_Docs_DocumentListEntry</classname> objects
-        (<code>$feed->entries</code>), each of which represents a single
+        (<command>$feed->entries</command>), each of which represents a single
         Google Document.
         </para>
     </sect2>

documentation/manual/en/module_specs/Zend_Gdata_Exception.xml

@@ -43,7 +43,7 @@ try {
                     indicates that an <acronym>HTTP</acronym> request was not successful.
                     Provides the ability to get the full <classname>Zend_Http_Response</classname>
                     object to determine the exact cause of the failure in
-                    cases where <code>$e->getMessage()</code> does not provide
+                    cases where <command>$e->getMessage()</command> does not provide
                     enough details.
                 </para>
             </listitem>