[DOCUMENTATION] English:

 - manual fixes: <code>constant name </code> => <constant>constant name</constant>

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

documentation/manual/en/module_specs/Zend_Date-Creation.xml

@@ -106,7 +106,7 @@ $date = new Zend_Date($unixtimestamp, Zend_Date::TIMESTAMP);
 
             <para>
                 The standard output of all databases is quite different even if it looks the same on
-                the first eyecatch. But all are part of the <code>ISO</code> Standard and explained
+                the first eyecatch. But all are part of the <acronym>ISO</acronym> Standard and explained
                 through it. So the easiest way of date creation is the usage of
                 <classname>Zend_Date::ISO_8601</classname>. Databases which are known to be
                 recognised by <classname>Zend_Date::ISO_8601</classname> are <code>MySQL</code>,

documentation/manual/en/module_specs/Zend_Db_Select.xml

@@ -947,10 +947,10 @@ $select = $db->select()
             <title>Adding a HAVING Clause</title>
 
             <para>
-                In SQL, the <code>HAVING</code> clause applies a restriction condition on groups of
-                rows. This is similar to how a <code>WHERE</code> clause applies a restriction
-                condition on rows. But the two clauses are different because <code>WHERE</code>
-                conditions are applied before groups are defined, whereas <code>HAVING</code>
+                In SQL, the <constant>HAVING</constant> clause applies a restriction condition on groups of
+                rows. This is similar to how a <constant>WHERE</constant> clause applies a restriction
+                condition on rows. But the two clauses are different because <constant>WHERE</constant>
+                conditions are applied before groups are defined, whereas <constant>HAVING</constant>
                 conditions are applied after groups are defined.
             </para>
 
@@ -961,7 +961,7 @@ $select = $db->select()
                 expression. The optional second argument is a value that is used to replace a
                 positional parameter placeholder in the SQL expression. Expressions given in
                 multiple invocations of the <methodname>having()</methodname> method are combined using the
-                Boolean <code>AND</code> operator, or the <code>OR</code> operator if you use the
+                Boolean <constant>AND</constant> operator, or the <code>OR</code> operator if you use the
                 <methodname>orHaving()</methodname> method.
             </para>
 
@@ -1013,14 +1013,14 @@ $select = $db->select()
                 determined by the secondary columns if the preceding columns contain identical
                 values. The default sorting is from least value to greatest value. You can also
                 sort by greatest value to least value for a given column in the list by specifying
-                the keyword <code>DESC</code> after that column.
+                the keyword <constant>DESC</constant> after that column.
             </para>
 
             <para>
                 In <classname>Zend_Db_Select</classname>, you can use the <methodname>order()</methodname>
                 method to specify a column or an array of columns by which to sort. Each element of
-                the array is a string naming a column. Optionally with the <code>ASC</code>
-                <code>DESC</code> keyword following it, separated by a space.
+                the array is a string naming a column. Optionally with the <constant>ASC</constant>
+                <constant>DESC</constant> keyword following it, separated by a space.
             </para>
 
             <para>
@@ -1061,7 +1061,7 @@ $select = $db->select()
             <title>Adding a LIMIT Clause</title>
 
             <para>
-                Some RDBMS brands extend SQL with a query clause known as the <code>LIMIT</code>
+                Some RDBMS brands extend SQL with a query clause known as the <constant>LIMIT</constant>
                 clause. This clause reduces the number of rows in the result set to at most a
                 number you specify. You can also specify to skip a number of rows before starting
                 to output. This feature makes it easy to take a subset of a result set, for example
@@ -1096,7 +1096,7 @@ $select = $db->select()
             <note>
 
                 <para>
-                    The <code>LIMIT</code> syntax is not supported by all RDBMS brands. Some RDBMS
+                    The <constant>LIMIT</constant> syntax is not supported by all RDBMS brands. Some RDBMS
                     require different syntax to support similar functionality. Each
                     <classname>Zend_Db_Adapter_Abstract</classname> class includes a method to
                     produce SQL appropriate for that RDBMS.
@@ -1139,7 +1139,7 @@ $select = $db->select()
             <title>Adding the DISTINCT Query Modifier</title>
 
             <para>
-                The <methodname>distinct()</methodname> method enables you to add the <code>DISTINCT</code>
+                The <methodname>distinct()</methodname> method enables you to add the <constant>DISTINCT</constant>
                 keyword to your SQL query.
             </para>
 
@@ -1307,9 +1307,9 @@ echo "$sql\n";
             <para>
                 The <methodname>getPart()</methodname> method returns a representation of one part of your SQL
                 query. For example, you can use this method to return the array of expressions for
-                the <code>WHERE</code> clause, or the array of columns (or column expressions) that
-                are in the <code>SELECT</code> list, or the values of the count and offset for the
-                <code>LIMIT</code> clause.
+                the <constant>WHERE</constant> clause, or the array of columns (or column expressions) that
+                are in the <constant>SELECT</constant> list, or the values of the count and offset for the
+                <constant>LIMIT</constant> clause.
             </para>
 
             <para>
@@ -1323,7 +1323,7 @@ echo "$sql\n";
                 The single argument to the <methodname>getPart()</methodname> method is a string that
                 identifies which part of the Select query to return. For example, the string
                 <code>'from'</code> identifies the part of the Select object that stores
-                information about the tables in the <code>FROM</code> clause, including joined
+                information about the tables in the <constant>FROM</constant> clause, including joined
                 tables.
             </para>
 

documentation/manual/en/module_specs/Zend_Db_Table-Relationships.xml

@@ -744,7 +744,7 @@ $products = $bug1234->findProductsViaBugsProductsByBug();
 
         <para>
             You can declare cascading operations to execute against a dependent table when you
-            apply an <code>UPDATE</code> or a <code>DELETE</code> to a row in a parent table.
+            apply an <constant>UPDATE</constant> or a <constant>DELETE</constant> to a row in a parent table.
         </para>
 
         <example id="zend.db.table.relationships.cascading.example-delete">
@@ -769,7 +769,7 @@ $product1234->delete();
         </example>
 
         <para>
-            Similarly, if you use <code>UPDATE</code> to change the value of a primary key in a
+            Similarly, if you use <constant>UPDATE</constant> to change the value of a primary key in a
             parent table, you may want the value in foreign keys of dependent tables to be updated
             automatically to match the new value, so that such references are kept up to date.
         </para>
@@ -785,7 +785,7 @@ $product1234->delete();
             To declare a cascading relationship in the <classname>Zend_Db_Table</classname>, edit
             the rules in the <varname>$_referenceMap</varname>. Set the associative array keys
             <code>'onDelete'</code> and <code>'onUpdate'</code> to the string 'cascade' (or the
-            constant <code>self::CASCADE</code>). Before a row is deleted from the parent table, or
+            constant <constant>self::CASCADE</constant>). Before a row is deleted from the parent table, or
             its primary key values updated, any rows in the dependent table that refer to the
             parent's row are deleted or updated first.
         </para>
@@ -798,13 +798,13 @@ $product1234->delete();
                 In the example below, rows in the <code>Bugs</code> table are automatically deleted
                 if the row in the <code>Products</code> table to which they refer is deleted. The
                 <code>'onDelete'</code> element of the reference map entry is set to
-                <code>self::CASCADE</code>.
+                <constant>self::CASCADE</constant>.
             </para>
 
             <para>
                 No cascading update is done in the example below if the primary key value in the
                 parent class is changed. The <code>'onUpdate'</code> element of the reference map
-                entry is <code>self::RESTRICT</code>. You can get the same result by omitting
+                entry is <constant>self::RESTRICT</constant>. You can get the same result by omitting
                 the <code>'onUpdate'</code> entry.
             </para>
 
@@ -838,22 +838,22 @@ class BugsProducts extends Zend_Db_Table_Abstract
 
             <para>
                 This means that if your database implements and enforces referential integrity
-                constraints, a cascading <code>UPDATE</code> executed by a
+                constraints, a cascading <constant>UPDATE</constant> executed by a
                 <classname>Zend_Db_Table</classname> class conflicts with the constraint, and
                 results in a referential integrity violation. You can use cascading
-                <code>UPDATE</code> in <classname>Zend_Db_Table</classname>
+                <constant>UPDATE</constant> in <classname>Zend_Db_Table</classname>
                 <emphasis>only</emphasis> if your database does not enforce that referential
                 integrity constraint.
             </para>
 
             <para>
-                Cascading <code>DELETE</code> suffers less from the problem of referential
+                Cascading <constant>DELETE</constant> suffers less from the problem of referential
                 integrity violations. You can delete dependent rows as a non-atomic action before
                 deleting the parent row that they reference.
             </para>
 
             <para>
-                However, for both <code>UPDATE</code> and <code>DELETE</code>, changing the
+                However, for both <constant>UPDATE</constant> and <constant>DELETE</constant>, changing the
                 database in a non-atomic way also creates the risk that another database user can
                 see the data in an inconsistent state. For example, if you delete a row and all its
                 dependent rows, there is a small chance that another database client program can
@@ -885,11 +885,11 @@ class BugsProducts extends Zend_Db_Table_Abstract
             </para>
 
             <para>
-                <emphasis>No Cascading <code>INSERT</code>.</emphasis>
+                <emphasis>No Cascading <constant>INSERT</constant>.</emphasis>
             </para>
 
             <para>
-                There is no support for a cascading <code>INSERT</code>. You must insert a row to a
+                There is no support for a cascading <constant>INSERT</constant>. You must insert a row to a
                 parent table in one operation, and insert row(s) to a dependent table in a separate
                 operation.
             </para>

documentation/manual/en/module_specs/Zend_Db_Table.xml

@@ -513,7 +513,7 @@ $data = array(
 
             <para>
                 An auto-incrementing primary key generates a unique integer value for you if you
-                omit the primary key column from your SQL <code>INSERT</code> statement.
+                omit the primary key column from your SQL <constant>INSERT</constant> statement.
             </para>
 
             <para>
@@ -546,9 +546,9 @@ class Bugs extends Zend_Db_Table_Abstract
             </para>
 
             <para>
-                PostgreSQL has a <code>SERIAL</code> notation that implicitly defines a sequence
+                PostgreSQL has a <constant>SERIAL</constant> notation that implicitly defines a sequence
                 based on the table and column name, and uses the sequence to generate key values
-                for new rows. IBM DB2 has an <code>IDENTITY</code> notation that works similarly.
+                for new rows. IBM DB2 has an <constant>IDENTITY</constant> notation that works similarly.
                 If you use either of these notations, treat your
                 <classname>Zend_Db_Table</classname> class as having an auto-incrementing column
                 with respect to declaring the <varname>$_sequence</varname> member as
@@ -570,7 +570,7 @@ class Bugs extends Zend_Db_Table_Abstract
                 If you define <varname>$_sequence</varname> to be a string, then
                 <classname>Zend_Db_Table_Abstract</classname> assumes the string to name a sequence
                 object in the database. The sequence is invoked to generate a new value, and this
-                value is used in the <code>INSERT</code> operation.
+                value is used in the <constant>INSERT</constant> operation.
             </para>
 
             <example id="zend.db.table.insert.key-sequence.example">
@@ -657,8 +657,8 @@ class BugStatus extends Zend_Db_Table_Abstract
             You can update rows in a database table using the <code>update</code> method of a Table
             class. This method takes two arguments: an associative array of columns to change and
             new values to assign to these columns; and an SQL expression that is used in a
-            <code>WHERE</code> clause, as criteria for the rows to change in the
-            <code>UPDATE</code> operation.
+            <constant>WHERE</constant> clause, as criteria for the rows to change in the
+            <constant>UPDATE</constant> operation.
         </para>
 
         <example id="zend.db.table.update.example">
@@ -684,7 +684,7 @@ $table->update($data, $where);
             Since the table <methodname>update()</methodname> method proxies to the database adapter
             <link linkend="zend.db.adapter.write.update"><methodname>update()</methodname></link> method, the
             second argument can be an array of SQL expressions. The expressions are combined as
-            Boolean terms using an <code>AND</code> operator.
+            Boolean terms using an <constant>AND</constant> operator.
         </para>
 
         <note>
@@ -707,7 +707,7 @@ $table->update($data, $where);
         <para>
             You can delete rows from a database table using the <methodname>delete()</methodname> method. This
             method takes one argument, which is an SQL expression that is used in a
-            <code>WHERE</code> clause, as criteria for the rows to delete.
+            <constant>WHERE</constant> clause, as criteria for the rows to delete.
         </para>
 
         <example id="zend.db.table.delete.example">
@@ -728,7 +728,7 @@ $table->delete($where);
             Since the table <methodname>delete()</methodname> method proxies to the database adapter
             <link linkend="zend.db.adapter.write.delete"><methodname>delete()</methodname></link> method, the
             argument can also be an array of SQL expressions. The expressions are combined as
-            Boolean terms using an <code>AND</code> operator.
+            Boolean terms using an <constant>AND</constant> operator.
         </para>
 
         <note>
@@ -1008,8 +1008,8 @@ $rows = $table->fetchAll($select);
             <para>
                 You may also pass sorting criteria in an <code>ORDER BY</code> clause, as well as
                 count and offset integer values, used to make the query return a specific subset of
-                rows. These values are used in a <code>LIMIT</code> clause, or in equivalent logic
-                for RDBMS brands that do not support the <code>LIMIT</code> syntax.
+                rows. These values are used in a <constant>LIMIT</constant> clause, or in equivalent logic
+                for RDBMS brands that do not support the <constant>LIMIT</constant> syntax.
             </para>
 
             <example id="zend.db.table.fetch-all.example2">

documentation/manual/en/module_specs/Zend_Db_Table_Row.xml

@@ -531,8 +531,8 @@ class MyApplicationRow extends Zend_Db_Table_Row_Abstract
             <para>
                 The Row class calls protected methods <methodname>_insert()</methodname>,
                 <methodname>_update()</methodname>, and <methodname>_delete()</methodname> before performing the
-                corresponding operations <code>INSERT</code>, <code>UPDATE</code>, and
-                <code>DELETE</code>. You can add logic to these methods in your custom Row
+                corresponding operations <constant>INSERT</constant>, <constant>UPDATE</constant>, and
+                <constant>DELETE</constant>. You can add logic to these methods in your custom Row
                 subclass.
             </para>
 

documentation/manual/en/module_specs/Zend_Debug.xml

@@ -59,7 +59,7 @@ Zend_Debug::dump($var, $label=null, $echo=true);
         <para>
             Also consider the <link linkend="zend.log.overview">Zend_Log</link>
             component when writing more permanent debugging code.
-            For example, you can use the <code>DEBUG</code> log level and the
+            For example, you can use the <constant>DEBUG</constant> log level and the
             Stream log writer, to output the string returned by
             <methodname>Zend_Debug::dump()</methodname>.
         </para>

documentation/manual/en/module_specs/Zend_Dom-Query.xml

@@ -205,8 +205,8 @@ foreach ($results as $result) {
                 <listitem><para>
                     <methodname>getDocumentType()</methodname>: retrieve the document
                     type of the document provided to the object; will be one of
-                    the <code>DOC_XML</code>, <code>DOC_XHTML</code>, or
-                    <code>DOC_HTML</code> class constants.
+                    the <constant>DOC_XML</constant>, <constant>DOC_XHTML</constant>, or
+                    <constant>DOC_HTML</constant> class constants.
                 </para></listitem>
 
                 <listitem><para>

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

@@ -367,15 +367,15 @@ $names = $upload->getMimeType('foo');
 
         <para>
             <classname>Zend_File_Transfer</classname> can give you the actual state of a fileupload
-            in progress. To use this feature you need either the <code>APC</code> extension which is
+            in progress. To use this feature you need either the <acronym>APC</acronym> extension which is
             provided with most default PHP installations, or the <code>uploadprogress</code>
             extension. Both extensions are detected and used automatically. To be able to get the
             progress you need to meet some prerequisites.
         </para>
 
         <para>
-            First, you need to have either <code>APC</code> or <code>uploadprogress</code> to be
-            enabled. Note that you can disable this feature of <code>APC</code> within your php.ini.
+            First, you need to have either <acronym>APC</acronym> or <code>uploadprogress</code> to be
+            enabled. Note that you can disable this feature of <acronym>APC</acronym> within your php.ini.
         </para>
 
         <para>

documentation/manual/en/module_specs/Zend_Filter_Input.xml

@@ -651,12 +651,12 @@ echo $input->month; // echoes 1
 ]]></programlisting>
 
             <para>
-                If your rule uses the <code>FIELDS</code> metacommand
+                If your rule uses the <constant>FIELDS</constant> metacommand
                 to define an array of multiple fields, you can define
-                an array for the <code>DEFAULT_VALUE</code> metacommand
+                an array for the <constant>DEFAULT_VALUE</constant> metacommand
                 and the defaults of corresponding keys are used for any
-                missing fields. If <code>FIELDS</code> defines multiple
-                fields but <code>DEFAULT_VALUE</code> is a scalar, then
+                missing fields. If <constant>FIELDS</constant> defines multiple
+                fields but <constant>DEFAULT_VALUE</constant> is a scalar, then
                 that default value is used as the value for any missing
                 fields in the array.
             </para>

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

@@ -68,7 +68,7 @@
                     decorator (e.g. FormElements uses the separator between each
                     item rendered). In the case that a decorator replaces the
                     content, this setting may be ignored. The default value is
-                    <code>PHP_EOL</code>.
+                    <constant>PHP_EOL</constant>.
             </para></listitem>
         </itemizedlist>
 

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

@@ -417,7 +417,7 @@ $form->addElement($element, 'foo');
 
         <para>
             To limit the size of the file uploaded, you can
-            specify the maximum file size by setting the <code>MAX_FILE_SIZE</code>
+            specify the maximum file size by setting the <constant>MAX_FILE_SIZE</constant>
             option on the form. When you set this value by using the
             <methodname>setMaxFileSize($size)</methodname> method, it will be rendered with the
             file element.
@@ -437,7 +437,7 @@ $form->addElement($element, 'foo');
 
             <para>
                 When you use multiple file elements in your form you should set
-                the <code>MAX_FILE_SIZE</code> only once. Setting it again will
+                the <constant>MAX_FILE_SIZE</constant> only once. Setting it again will
                 overwrite the previous value.
             </para>
 

documentation/manual/en/module_specs/Zend_Gdata_Books.xml

@@ -311,7 +311,7 @@ $books->updateVolume($entry, $entryUrl);
 
                 <para>
                     To submit labels, add a <code>Category</code> object
-                    with the scheme <code>LABELS_SCHEME</code> to a
+                    with the scheme <constant>LABELS_SCHEME</constant> to a
                     <code>VolumeEntry</code> and post it to the annotation feed.
                 </para>
 
@@ -421,7 +421,7 @@ $books->deleteVolume($entry);
                 <para>
                     To retrieve the user's books, send a query to the
                     My Library feed. To get the library of the authenticated
-                    user, use <code>me</code> in place of <code>USER_ID</code>.
+                    user, use <code>me</code> in place of <constant>USER_ID</constant>.
                 </para>
 
                 <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Gdata_Health.xml

@@ -296,7 +296,7 @@ foreach ($entries as $entry) {
             <para>
               Here, the <methodname>getCcr()</methodname> method is used in conjunction with a magic helper to drill down and extract just the
               medication data from the entry's CCR. The formentioned magic helper takes the form <methodname>getCATEGORYNAME()</methodname>, where
-              <code>CATEGORYNAME</code> is a supported Google Health category. See the
+              <constant>CATEGORYNAME</constant> is a supported Google Health category. See the
               <ulink url="http://code.google.com/apis/health/reference.html#CatQueries">Google Health reference Guide</ulink> for the possible categories.
             </para>
             <para>

documentation/manual/en/module_specs/Zend_InfoCard-Basics.xml

@@ -60,7 +60,7 @@
             them which information cards meet the requirements of the site, but
             also allows them to select which information card to use if multiple
             meet the criteria. This information card is transmitted as an XML
-            document to the specified <code>POST</code> URL and is ready to be
+            document to the specified POST URL and is ready to be
             processed by the <classname>Zend_InfoCard</classname> component.
         </para>
 

documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Attribute.xml

@@ -201,8 +201,8 @@
                         <varname>$attribName</varname> defaults to <code>'userPassword'</code>
                         which is the standard password attribute. The password hash can be
                         specified with <varname>$hashType</varname>. The default value here is
-                        <code>Zend_Ldap_Attribute::PASSWORD_HASH_MD5</code> with
-                        <code>Zend_Ldap_Attribute::PASSWORD_HASH_SHA</code> as the other
+                        <constant>Zend_Ldap_Attribute::PASSWORD_HASH_MD5</constant> with
+                        <constant>Zend_Ldap_Attribute::PASSWORD_HASH_SHA</constant> as the other
                         possibilty.
                     </entry>
                 </row>
@@ -214,8 +214,8 @@
                     <entry>
                         Creates a <acronym>LDAP</acronym> password. The password hash can be specified
                         with <varname>$hashType</varname>. The default value here is
-                        <code>Zend_Ldap_Attribute::PASSWORD_HASH_MD5</code> with
-                        <code>Zend_Ldap_Attribute::PASSWORD_HASH_SHA</code> as the other
+                        <constant>Zend_Ldap_Attribute::PASSWORD_HASH_MD5</constant> with
+                        <constant>Zend_Ldap_Attribute::PASSWORD_HASH_SHA</constant> as the other
                         possibilty.
                     </entry>
                 </row>

documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Dn.xml

@@ -12,23 +12,23 @@
 
     <variablelist>
         <varlistentry>
-            <term><code>Zend_Ldap_Dn::ATTR_CASEFOLD_NONE</code></term>
+            <term><constant>Zend_Ldap_Dn::ATTR_CASEFOLD_NONE</constant></term>
             <listitem><para>No case-folding will be done.</para></listitem>
         </varlistentry>
 
         <varlistentry>
-            <term><code>Zend_Ldap_Dn::ATTR_CASEFOLD_UPPER</code></term>
+            <term><constant>Zend_Ldap_Dn::ATTR_CASEFOLD_UPPER</constant></term>
             <listitem><para>All attributes will be converted to upper-case.</para></listitem>
         </varlistentry>
 
         <varlistentry>
-            <term><code>Zend_Ldap_Dn::ATTR_CASEFOLD_LOWER</code></term>
+            <term><constant>Zend_Ldap_Dn::ATTR_CASEFOLD_LOWER</constant></term>
             <listitem><para>All attributes will be converted to lower-case.</para></listitem>
         </varlistentry>
     </variablelist>
 
     <para>
-        The default case-folding is <code>Zend_Ldap_Dn::ATTR_CASEFOLD_NONE</code> and
+        The default case-folding is <constant>Zend_Ldap_Dn::ATTR_CASEFOLD_NONE</constant> and
         can be set with <methodname>Zend_Ldap_Dn::setDefaultCaseFold()</methodname>. Each instance of
         <classname>Zend_Ldap_Dn</classname> can have its own case-folding-setting. If the
         <varname>$caseFold</varname> parameter is ommitted in method-calls it defaults to the
@@ -179,7 +179,7 @@
                     <entry>
                         Sets the case-folding option to the current DN instance. If
                         <varname>$caseFold</varname> is null the default case-folding setting
-                        (<code>Zend_Ldap_Dn::ATTR_CASEFOLD_NONE</code> by default or set
+                        (<constant>Zend_Ldap_Dn::ATTR_CASEFOLD_NONE</constant> by default or set
                         via <methodname>Zend_Ldap_Dn::setDefaultCaseFold()</methodname> will be set for
                         the current instance.
                     </entry>

documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node-RootDse.xml

@@ -214,25 +214,25 @@
                         <variablelist>
                             <varlistentry>
                                 <term>
-                                <code>Zend_Ldap_Node_RootDse::SERVER_TYPE_GENERIC</code></term>
+                                <constant>Zend_Ldap_Node_RootDse::SERVER_TYPE_GENERIC</constant></term>
                                 <listitem><para>for unknown <acronym>LDAP</acronym> servers</para></listitem>
                             </varlistentry>
 
                             <varlistentry>
                                 <term>
-                                <code>Zend_Ldap_Node_RootDse::SERVER_TYPE_OPENLDAP</code></term>
+                                <constant>Zend_Ldap_Node_RootDse::SERVER_TYPE_OPENLDAP</constant></term>
                                 <listitem><para>for OpenLDAP servers</para></listitem>
                             </varlistentry>
 
                             <varlistentry>
                                 <term>
-                                <code>Zend_Ldap_Node_RootDse::SERVER_TYPE_ACTIVEDIRECTORY</code></term>
+                                <constant>Zend_Ldap_Node_RootDse::SERVER_TYPE_ACTIVEDIRECTORY</constant></term>
                                 <listitem><para>for Microsoft ActiveDirectory servers</para></listitem>
                             </varlistentry>
 
                             <varlistentry>
                                 <term>
-                                <code>Zend_Ldap_Node_RootDse::SERVER_TYPE_EDIRECTORY</code></term>
+                                <constant>Zend_Ldap_Node_RootDse::SERVER_TYPE_EDIRECTORY</constant></term>
                                 <listitem><para>For Novell eDirectory servers</para></listitem>
                             </varlistentry>
                         </variablelist>
@@ -280,7 +280,7 @@
                         <entry><code>integer getServerType()</code></entry>
                         <entry>
                             Gets the server type. Returns
-                            <code>Zend_Ldap_Node_RootDse::SERVER_TYPE_OPENLDAP</code>
+                            <constant>Zend_Ldap_Node_RootDse::SERVER_TYPE_OPENLDAP</constant>
                         </entry>
                     </row>
                     <row>
@@ -349,7 +349,7 @@
                         <entry><code>integer getServerType()</code></entry>
                         <entry>
                             Gets the server type. Returns
-                            <code>Zend_Ldap_Node_RootDse::SERVER_TYPE_ACTIVEDIRECTORY</code>
+                            <constant>Zend_Ldap_Node_RootDse::SERVER_TYPE_ACTIVEDIRECTORY</constant>
                         </entry>
                     </row>
                     <row>
@@ -497,7 +497,7 @@
                         <entry><code>integer getServerType()</code></entry>
                         <entry>
                             Gets the server type. Returns
-                            <code>Zend_Ldap_Node_RootDse::SERVER_TYPE_EDIRECTORY</code>
+                            <constant>Zend_Ldap_Node_RootDse::SERVER_TYPE_EDIRECTORY</constant>
                         </entry>
                     </row>
                     <row>

documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node.xml

@@ -417,7 +417,7 @@
                         Sets a <acronym>LDAP</acronym> password on <varname>$attribName</varname> (defaults
                         to <code>'userPassword'</code>) to <varname>$password</varname> with the
                         hash type <varname>$hashType</varname> (defaults to
-                        <code>Zend_Ldap_Attribute::PASSWORD_HASH_MD5</code>).
+                        <constant>Zend_Ldap_Attribute::PASSWORD_HASH_MD5</constant>).
                     </entry>
                 </row>
                 <row>

documentation/manual/en/module_specs/Zend_Ldap-API-Ldap.xml

@@ -191,15 +191,15 @@
                                 <listitem>
                                     <para>
                                         The search scope.
-                                        <code>Zend_Ldap::SEARCH_SCOPE_SUB</code> searches the
+                                        <constant>Zend_Ldap::SEARCH_SCOPE_SUB</constant> searches the
                                         complete subtree including the <varname>$baseDn</varname> node.
-                                        <code>Zend_Ldap::SEARCH_SCOPE_ONE</code> restricts search
+                                        <constant>Zend_Ldap::SEARCH_SCOPE_ONE</constant> restricts search
                                         to one level below <varname>$baseDn</varname>.
-                                        <code>Zend_Ldap::SEARCH_SCOPE_BASE</code> restricts search
+                                        <constant>Zend_Ldap::SEARCH_SCOPE_BASE</constant> restricts search
                                         to the <varname>$baseDn</varname> itself; this can be used to
                                         efficiently retrieve a single entry by its DN. The default
                                         value is
-                                        <code>Zend_Ldap::SEARCH_SCOPE_SUB</code>.
+                                        <constant>Zend_Ldap::SEARCH_SCOPE_SUB</constant>.
                                     </para>
                                 </listitem>
                             </varlistentry>

documentation/manual/en/module_specs/Zend_Locale-Functions.xml

@@ -79,7 +79,7 @@ if ($locale->equals($mylocale)) {
             environment of the host server, and Zend Framework settings. As with the constructor
             for <classname>Zend_Locale</classname>, the first parameter selects a preference of
             which information to consider <link
-                linkend="zend.locale.selection">(<code>BROWSER</code>, <code>ENVIRONMENT</code>, or
+                linkend="zend.locale.selection">(<constant>BROWSER</constant>, <constant>ENVIRONMENT</constant>, or
                 <code>FRAMEWORK)</code></link> first. The second parameter toggles between
             returning all matching locales or only the first/best match. Locale-aware components
             normally use only the first locale. A quality rating is included, when available.
@@ -102,7 +102,7 @@ print_r($found2);
 
         <para>
             To obtain only the default locales relevant to the
-            <link linkend="zend.locale.selection"><code>BROWSER</code>, <code>ENVIRONMENT</code>, or <code>FRAMEWORK</code>
+            <link linkend="zend.locale.selection"><constant>BROWSER</constant>, <constant>ENVIRONMENT</constant>, or <constant>FRAMEWORK</constant>
             </link>
             , use the corresponding method:
             <itemizedlist>

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

@@ -143,7 +143,7 @@
         </note>
 
         <para>
-            A user from USA would expect the language <code>English</code> and the region <code>USA</code>, yielding the
+            A user from USA would expect the language <code>English</code> and the region <constant>USA</constant>, yielding the
             locale identifier "en_US". A user in Germany would expect the language <code>German</code> and the region
             <code>Germany</code>, yielding the locale identifier "de_DE". See the
             <ulink url="http://unicode.org/cldr/data/diff/supplemental/languages_and_territories.html">list of pre-defined locale and region combinations</ulink>, if you need to select a specific locale within Zend Framework.
@@ -157,7 +157,7 @@ $locale = new Zend_Locale('de_DE'); // German language _ Germany
         </example>
 
         <para>
-            A German user in America might expect the language <code>German</code> and the region <code>USA</code>, but
+            A German user in America might expect the language <code>German</code> and the region <constant>USA</constant>, but
             these non-standard mixes are not supported directly as recognized "locales". Instead, if an invalid
             combination is used, then it will automatically be truncated by dropping the region code. For example,
             "de_IS" would be truncated to "de", and "xh_RU" would be truncated to "xh", because neither of these
@@ -216,16 +216,16 @@ $locale3 = new Zend_Locale(Zend_Locale::FRAMEWORK);
                 <listitem>
                     <para>
                         const <classname>Zend_Locale::BROWSER</classname> - The user's Web browser provides information with each
-                        request, which is published by PHP in the global variable <code>HTTP_ACCEPT_LANGUAGE</code>. If
-                        no matching locale can be found, then preference is given to <code>ENVIRONMENT</code> and lastly
-                        <code>FRAMEWORK</code>.
+                        request, which is published by PHP in the global variable <constant>HTTP_ACCEPT_LANGUAGE</constant>. If
+                        no matching locale can be found, then preference is given to <constant>ENVIRONMENT</constant> and lastly
+                        <constant>FRAMEWORK</constant>.
                     </para>
                 </listitem>
                 <listitem>
                     <para>
                         const <classname>Zend_Locale::ENVIRONMENT</classname> - PHP publishes the host server's locale via the PHP
                         internal function <methodname>setlocale()</methodname>. If no matching locale can be found, then preference
-                        is given to <code>FRAMEWORK</code> and lastly <code>BROWSER</code>.
+                        is given to <constant>FRAMEWORK</constant> and lastly <constant>BROWSER</constant>.
                     </para>
                 </listitem>
                 <listitem>
@@ -233,8 +233,8 @@ $locale3 = new Zend_Locale(Zend_Locale::FRAMEWORK);
                         const <classname>Zend_Locale::FRAMEWORK</classname> - When Zend Framework has a standardized way of
                         specifying component defaults (planned, but not yet available), then using this constant during
                         instantiation will give preference to choosing a locale based on these defaults. If no matching
-                        locale can be found, then preference is given to <code>ENVIRONMENT</code> and lastly
-                        <code>BROWSER</code>.
+                        locale can be found, then preference is given to <constant>ENVIRONMENT</constant> and lastly
+                        <constant>BROWSER</constant>.
                     </para>
                 </listitem>
             </orderedlist>
@@ -263,7 +263,7 @@ $locale3 = new Zend_Locale(Zend_Locale::FRAMEWORK);
                     <para>
                         <code>'browser'</code> - <classname>Zend_Locale</classname> should work with the information
                         which is provided by the user's Web browser. It is published by PHP in the global
-                        variable <code>HTTP_ACCEPT_LANGUAGE</code>.
+                        variable <constant>HTTP_ACCEPT_LANGUAGE</constant>.
                     </para>
                     <para>
                         If a user provides more than one locale within his browser, <classname>Zend_Locale</classname>

documentation/manual/en/module_specs/Zend_Log-Overview.xml

@@ -147,10 +147,10 @@ DEBUG   = 7;  // Debug: debug messages
     </para>
 
     <para>
-      Priority numbers descend in order of importance. <code>EMERG</code> (0)
-      is the most important priority. <code>DEBUG</code> (7) is the least
+      Priority numbers descend in order of importance. <constant>EMERG</constant> (0)
+      is the most important priority. <constant>DEBUG</constant> (7) is the least
       important priority of the built-in priorities. You may define priorities
-      of lower importance than <code>DEBUG</code>. When
+      of lower importance than <constant>DEBUG</constant>. When
       selecting the priority for your log message, be aware of this priority
       hierarchy and choose appropriately.
     </para>
@@ -167,7 +167,7 @@ DEBUG   = 7;  // Debug: debug messages
 $logger->addPriority('FOO', 8);
 ]]></programlisting>
 
-      The snippet above creates a new priority, <code>FOO</code>, whose
+      The snippet above creates a new priority, <constant>FOO</constant>, whose
       value is <code>8</code>. The new priority is then available for logging:
 
       <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Log-Writers-Firebug.xml

@@ -108,31 +108,31 @@ $writer->setDefaultPriorityStyle('TRACE');
                 </thead>
                 <tbody>
                     <row>
-                        <entry><code>LOG</code></entry>
+                        <entry><constant>LOG</constant></entry>
                         <entry>Displays a plain log message</entry>
                     </row>
                     <row>
-                        <entry><code>INFO</code></entry>
+                        <entry><constant>INFO</constant></entry>
                         <entry>Displays an info log message</entry>
                     </row>
                     <row>
-                        <entry><code>WARN</code></entry>
+                        <entry><constant>WARN</constant></entry>
                         <entry>Displays a warning log message</entry>
                     </row>
                     <row>
-                        <entry><code>ERROR</code></entry>
+                        <entry><constant>ERROR</constant></entry>
                         <entry>Displays an error log message that increments Firebug's error count</entry>
                     </row>
                     <row>
-                        <entry><code>TRACE</code></entry>
+                        <entry><constant>TRACE</constant></entry>
                         <entry>Displays a log message with an expandable stack trace</entry>
                     </row>
                     <row>
-                        <entry><code>EXCEPTION</code></entry>
+                        <entry><constant>EXCEPTION</constant></entry>
                         <entry>Displays an error long message with an expandable stack trace</entry>
                     </row>
                     <row>
-                        <entry><code>TABLE</code></entry>
+                        <entry><constant>TABLE</constant></entry>
                         <entry>Displays a log message with an expandable table</entry>
                     </row>
                 </tbody>
@@ -150,8 +150,8 @@ $writer->setDefaultPriorityStyle('TRACE');
         is required if using some of the more specialized log styles.
       </para>
       <para>
-        The <code>LOG</code>, <code>INFO</code>, <code>WARN</code>, <code>ERROR</code>
-        and <code>TRACE</code> styles require no special formatting.
+        The <constant>LOG</constant>, <constant>INFO</constant>, <constant>WARN</constant>, <constant>ERROR</constant>
+        and <constant>TRACE</constant> styles require no special formatting.
       </para>
     </sect3>
 

documentation/manual/en/module_specs/Zend_Log-Writers.xml

@@ -16,7 +16,7 @@
 
     <para>
       To write log data to the PHP output buffer, use the URL <code>php://output</code>. Alternatively,
-      you can send log data directly to a stream like <code>STDERR</code>
+      you can send log data directly to a stream like <constant>STDERR</constant>
       (<code>php://stderr</code>).
 
       <programlisting language="php"><![CDATA[

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

@@ -42,7 +42,7 @@ echo $unit->convertTo(Zend_Measure_Length::YARD);
         <title>The meter measurement</title>
         <para>
             The <code>meter</code> is used for measuring lengths, so its type constant can be found in the
-            <code>Length</code> class. To refer to this unit of measurement, the notation <code>Length::METER</code>
+            <code>Length</code> class. To refer to this unit of measurement, the notation <constant>Length::METER</constant>
             must be used. The display unit is <code>m</code>.
         </para>
         <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_ProgressBar_Adapter_Console.xml

@@ -32,7 +32,7 @@
         </listitem>
         <listitem>
             <para>
-                <code>width</code>: Either an integer or the <code>AUTO</code>
+                <code>width</code>: Either an integer or the <constant>AUTO</constant>
                 constant of <classname>Zend_Console_ProgressBar</classname>.
             </para>
         </listitem>
@@ -46,18 +46,18 @@
             <itemizedlist>
                 <listitem>
                     <para>
-                        <code>ELEMENT_PERCENT</code>: The current value in percent.
+                        <constant>ELEMENT_PERCENT</constant>: The current value in percent.
                     </para>
                 </listitem>
                 <listitem>
                     <para>
-                        <code>ELEMENT_BAR</code>: The visual bar which display
+                        <constant>ELEMENT_BAR</constant>: The visual bar which display
                         the percentage.
                     </para>
                 </listitem>
                 <listitem>
                     <para>
-                        <code>ELEMENT_ETA</code>: The automatic calculated ETA.
+                        <constant>ELEMENT_ETA</constant>: The automatic calculated ETA.
                         This element is firstly displayed after five seconds,
                         because in this time, it is not able to calculate
                         accurate results.
@@ -65,7 +65,7 @@
                 </listitem>
                 <listitem>
                     <para>
-                        <code>ELEMENT_TEXT</code>: An optional status message
+                        <constant>ELEMENT_TEXT</constant>: An optional status message
                         about the current process.
                     </para>
                 </listitem>
@@ -74,13 +74,13 @@
         <listitem>
             <para>
                 <code>textWidth</code>: Width in characters of the
-                <code>ELEMENT_TEXT</code> element. Default is 20.
+                <constant>ELEMENT_TEXT</constant> element. Default is 20.
             </para>
         </listitem>
         <listitem>
             <para>
                 <code>charset</code>: Charset of the
-                <code>ELEMENT_TEXT</code> element. Default is utf-8.
+                <constant>ELEMENT_TEXT</constant> element. Default is utf-8.
             </para>
         </listitem>
         <listitem>

documentation/manual/en/module_specs/Zend_Registry.xml

@@ -165,10 +165,10 @@ var_dump( $registry['index'] );
             in an object-oriented fashion by using index names as object
             properties.
             You must specifically construct the registry
-            object using the <code>ArrayObject::ARRAY_AS_PROPS</code> option
+            object using the <constant>ArrayObject::ARRAY_AS_PROPS</constant> option
             and initialize the static instance to enable this functionality.
             <note>
-                <para>You must set the <code>ArrayObject::ARRAY_AS_PROPS</code> option
+                <para>You must set the <constant>ArrayObject::ARRAY_AS_PROPS</constant> option
                 <emphasis>before</emphasis> the static registry has been accessed for
                 the first time.</para>
             </note>
@@ -177,7 +177,7 @@ var_dump( $registry['index'] );
                 <title>Known Issues with the ArrayObject::ARRAY_AS_PROPS Option</title>
 
                 <para>
-                    Some versions of PHP have proven very buggy when using the registry with the <code>ArrayObject::ARRAY_AS_PROPS</code> option.
+                    Some versions of PHP have proven very buggy when using the registry with the <constant>ArrayObject::ARRAY_AS_PROPS</constant> option.
                 </para>
             </warning>
 

documentation/manual/en/module_specs/Zend_Search_Lucene-Searching.xml

@@ -295,15 +295,15 @@ $index->find($query [, $sortField [, $sortType [, $sortOrder]]]
 
         <para>
             <varname>$sortType</varname> may be omitted or take the following enumerated values:
-            <code>SORT_REGULAR</code> (compare items normally- default value),
-            <code>SORT_NUMERIC</code> (compare items numerically),
-            <code>SORT_STRING</code> (compare items as strings).
+            <constant>SORT_REGULAR</constant> (compare items normally- default value),
+            <constant>SORT_NUMERIC</constant> (compare items numerically),
+            <constant>SORT_STRING</constant> (compare items as strings).
         </para>
 
         <para>
             <varname>$sortOrder</varname> may be omitted or take the following enumerated values:
-            <code>SORT_ASC</code> (sort in ascending order- default value),
-            <code>SORT_DESC</code> (sort in descending order).
+            <constant>SORT_ASC</constant> (sort in ascending order- default value),
+            <constant>SORT_DESC</constant> (sort in descending order).
         </para>
 
         <para>

documentation/manual/en/module_specs/Zend_Service_Amazon_S3.xml

@@ -235,7 +235,7 @@ foreach($list as $bucket) {
                 following parameters as keys:
                 </para>
                 <variablelist>
-                <varlistentry><term><code>S3_CONTENT_TYPE_HEADER</code></term>
+                <varlistentry><term><constant>S3_CONTENT_TYPE_HEADER</constant></term>
                     <listitem>
                     <para>
                     MIME content type of the data. If not specified, the type will be guessed according
@@ -243,28 +243,28 @@ foreach($list as $bucket) {
                     </para>
                     </listitem>
                 </varlistentry>
-                <varlistentry><term><code>S3_ACL_HEADER</code></term>
+                <varlistentry><term><constant>S3_ACL_HEADER</constant></term>
                     <listitem>
                     <para>
                     The access to the item. Following access constants can be used:
                         <variablelist>
-                        <varlistentry><term><code>S3_ACL_PRIVATE</code></term>
+                        <varlistentry><term><constant>S3_ACL_PRIVATE</constant></term>
                             <listitem>
                             <para>Only the owner has access to the item.</para>
                             </listitem>
                         </varlistentry>
-                        <varlistentry><term><code>S3_ACL_PUBLIC_READ</code></term>
+                        <varlistentry><term><constant>S3_ACL_PUBLIC_READ</constant></term>
                             <listitem>
                             <para>Anybody can read the object, but only owner can write.
                             This is setting may be used to store publicly accessible content.</para>
                             </listitem>
                         </varlistentry>
-                        <varlistentry><term><code>S3_ACL_PUBLIC_WRITE</code></term>
+                        <varlistentry><term><constant>S3_ACL_PUBLIC_WRITE</constant></term>
                             <listitem>
                             <para>Anybody can read or write the object. This policy is rarely useful.</para>
                             </listitem>
                         </varlistentry>
-                        <varlistentry><term><code>S3_ACL_AUTH_READ</code></term>
+                        <varlistentry><term><constant>S3_ACL_AUTH_READ</constant></term>
                             <listitem>
                             <para>Only the owner has write access to the item, and other authenticated S3
                             users have read access. This is useful for sharing data between S3 accounts without

documentation/manual/en/module_specs/Zend_Service_Nirvanix.xml

@@ -148,7 +148,7 @@ $imfs->unlink('/foo.txt');
             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
-            you want to use. Above, a proxy for the <code>IMFS</code> namespace is created.
+            you want to use. Above, a proxy for the <constant>IMFS</constant> namespace is created.
         </para>
 
         <para>
@@ -165,7 +165,7 @@ $imfs->unlink('/foo.txt');
 
         <para>
             In the previous example, we used the <methodname>getService()</methodname> method to return
-            a proxy object to the <code>IMFS</code> namespace. The proxy object allows
+            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
             PHP method call, as opposed to constructing your own HTTP request objects.
         </para>
@@ -206,7 +206,7 @@ $result = $imfs->renameFile(array('filePath' => '/path/to/foo.txt',
 ]]></programlisting>
 
         <para>
-            Above, a proxy for the <code>IMFS</code> namespace is created. A method,
+            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 PHP code, so it is trapped by
             <methodname>__call()</methodname> and converted into a POST request to the REST API where

documentation/manual/en/module_specs/Zend_Service_StrikeIron-Overview.xml

@@ -211,7 +211,7 @@ echo $rateInfo->GST;
       <para>
         The result from <methodname>getTaxRateCanada()</methodname> is stored in
         <varname>$rateInfo</varname> and has properties like <code>province</code>
-        and <code>GST</code>.
+        and <constant>GST</constant>.
       </para>
 
       <para>
@@ -269,7 +269,7 @@ Zend_Service_StrikeIron_Decorator Object
 
       <para>
         This means that <varname>$rateInfo</varname> has public properties like <code>abbreviation</code>,
-        <code>province</code>, and <code>GST</code>. These are accessed like <code>$rateInfo->province</code>.
+        <code>province</code>, and <constant>GST</constant>. These are accessed like <code>$rateInfo->province</code>.
       </para>
 
       <tip>

documentation/manual/en/module_specs/Zend_Session-AdvancedUsage.xml

@@ -63,7 +63,7 @@ php_value session.auto_start 0
                     <classname>Zend_Session_Namespace</classname>, an exception will be thrown by
                     <methodname>Zend_Session::start()</methodname> ("session has already been started"). If you call
                     <methodname>session_start()</methodname> after using <classname>Zend_Session_Namespace</classname> or calling
-                    <methodname>Zend_Session::start()</methodname>, an error of level <code>E_NOTICE</code> will be generated, and
+                    <methodname>Zend_Session::start()</methodname>, an error of level <constant>E_NOTICE</constant> will be generated, and
                     the call will be ignored.
                 </para>
             </listitem>

documentation/manual/en/module_specs/Zend_Soap_Client.xml

@@ -92,13 +92,13 @@
                 </listitem>
                 <listitem>
                     <para>
-                        'style' - request style (doesn't work for WSDL mode): <code>SOAP_RPC</code> or <code>SOAP_DOCUMENT</code>.
+                        'style' - request style (doesn't work for WSDL mode): <constant>SOAP_RPC</constant> or <constant>SOAP_DOCUMENT</constant>.
                     </para>
                 </listitem>
                 <listitem>
                     <para>
-                        'use' - method to encode messages (doesn't work for WSDL mode): <code>SOAP_ENCODED</code> or
-                        <code>SOAP_LITERAL</code>.
+                        'use' - method to encode messages (doesn't work for WSDL mode): <constant>SOAP_ENCODED</constant> or
+                        <constant>SOAP_LITERAL</constant>.
                     </para>
                 </listitem>
                 <listitem>
@@ -118,8 +118,8 @@
                 </listitem>
                 <listitem>
                     <para>
-                        'compression' - compression options; it's a combination of <code>SOAP_COMPRESSION_ACCEPT</code>,
-                        <code>SOAP_COMPRESSION_GZIP</code> and <code>SOAP_COMPRESSION_DEFLATE</code> options which
+                        'compression' - compression options; it's a combination of <constant>SOAP_COMPRESSION_ACCEPT</constant>,
+                        <constant>SOAP_COMPRESSION_GZIP</constant> and <constant>SOAP_COMPRESSION_DEFLATE</constant> options which
                         may be used like this:
                         <programlisting language="php"><![CDATA[
 // Accept response compression

documentation/manual/en/module_specs/Zend_Text_Figlet.xml

@@ -62,8 +62,8 @@
                 <para>
                     <code>justification</code> - May be one of the values of
                     <classname>Zend_Text_Figlet::JUSTIFICATION_*</classname>. There is
-                    <code>JUSTIFICATION_LEFT</code>, <code>JUSTIFICATION_CENTER</code>
-                    and <code>JUSTIFICATION_RIGHT</code> The default justification
+                    <constant>JUSTIFICATION_LEFT</constant>, <constant>JUSTIFICATION_CENTER</constant>
+                    and <constant>JUSTIFICATION_RIGHT</constant> The default justification
                     is defined by the <code>rightToLeft</code> value.
                 </para>
             </listitem>

documentation/manual/en/module_specs/Zend_Text_Table.xml

@@ -99,17 +99,17 @@
         <itemizedlist>
             <listitem>
                 <para>
-                    <code>ALIGN_LEFT</code>
+                    <constant>ALIGN_LEFT</constant>
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <code>ALIGN_CENTER</code>
+                    <constant>ALIGN_CENTER</constant>
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <code>ALIGN_RIGHT</code>
+                    <constant>ALIGN_RIGHT</constant>
                 </para>
             </listitem>
         </itemizedlist>

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

@@ -47,9 +47,9 @@ if ($validator->isValid($hostname)) {
     </para>
 
     <para>
-        The Zend_Validate_Hostname constants are: <code>ALLOW_DNS</code> to allow only DNS
-        hostnames, <code>ALLOW_IP</code> to allow IP addresses, <code>ALLOW_LOCAL</code> to allow
-        local network names, and <code>ALLOW_ALL</code> to allow all three types. To just check for
+        The Zend_Validate_Hostname constants are: <constant>ALLOW_DNS</constant> to allow only DNS
+        hostnames, <constant>ALLOW_IP</constant> to allow IP addresses, <constant>ALLOW_LOCAL</constant> to allow
+        local network names, and <constant>ALLOW_ALL</constant> to allow all three types. To just check for
         IP addresses you can use the example below:
         <programlisting language="php"><![CDATA[
 $validator = new Zend_Validate_Hostname(Zend_Validate_Hostname::ALLOW_IP);
@@ -65,7 +65,7 @@ if ($validator->isValid($hostname)) {
     </para>
 
     <para>
-        As well as using <code>ALLOW_ALL</code> to accept all hostnames types you can combine
+        As well as using <constant>ALLOW_ALL</constant> to accept all hostnames types you can combine
         these types to allow for combinations. For example, to accept DNS and Local hostnames
         instantiate your Zend_Validate_Hostname object as so:
         <programlisting language="php"><![CDATA[

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

@@ -4,7 +4,7 @@
     <title>Doctype Helper</title>
 
     <para>
-        Valid HTML and XHTML documents should include a <code>DOCTYPE</code>
+        Valid HTML and XHTML documents should include a <constant>DOCTYPE</constant>
         declaration. Besides being difficult to remember, these can also affect
         how certain elements in your document should be rendered (for instance,
         CDATA escaping in <code>&lt;script&gt;</code> and
@@ -17,15 +17,15 @@
     </para>
 
     <itemizedlist>
-        <listitem><para><code>XHTML11</code></para></listitem>
-        <listitem><para><code>XHTML1_STRICT</code></para></listitem>
-        <listitem><para><code>XHTML1_TRANSITIONAL</code></para></listitem>
-        <listitem><para><code>XHTML1_FRAMESET</code></para></listitem>
-        <listitem><para><code>XHTML_BASIC1</code></para></listitem>
-        <listitem><para><code>HTML4_STRICT</code></para></listitem>
-        <listitem><para><code>HTML4_LOOSE</code></para></listitem>
-        <listitem><para><code>HTML4_FRAMESET</code></para></listitem>
-        <listitem><para><code>HTML5</code></para></listitem>
+        <listitem><para><constant>XHTML11</constant></para></listitem>
+        <listitem><para><constant>XHTML1_STRICT</constant></para></listitem>
+        <listitem><para><constant>XHTML1_TRANSITIONAL</constant></para></listitem>
+        <listitem><para><constant>XHTML1_FRAMESET</constant></para></listitem>
+        <listitem><para><constant>XHTML_BASIC1</constant></para></listitem>
+        <listitem><para><constant>HTML4_STRICT</constant></para></listitem>
+        <listitem><para><constant>HTML4_LOOSE</constant></para></listitem>
+        <listitem><para><constant>HTML4_FRAMESET</constant></para></listitem>
+        <listitem><para><constant>HTML5</constant></para></listitem>
     </itemizedlist>
 
     <para>

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

@@ -319,7 +319,7 @@ $this->navigation()->addPage(array(
                     Unless otherwise is stated in other examples, the user
                     is requesting the URL
                     <code>http://www.example.com/products/server/faq/</code>,
-                    which translates to the page labeled <code>FAQ</code>
+                    which translates to the page labeled <constant>FAQ</constant>
                     under <code>Foo Server</code>.
                 </para>
             </listitem>
@@ -754,7 +754,7 @@ Products, Foo Server, FAQ
         <title>Links Helper</title>
 
         <para>
-            The links helper is used for rendering HTML <code>LINK</code>
+            The links helper is used for rendering HTML <constant>LINK</constant>
             elements. Links are used for describing document relationships
             of the currently active page. Read more about links and link
             types at <ulink url="http://www.w3.org/TR/html4/struct/links.html#h-12.3">Document

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

@@ -134,13 +134,13 @@ echo $foo['bar'];
 
                 <para>
                     <varname>$type</varname> should be one of the
-                    <code>Placeholder</code> constants <code>APPEND</code> or
-                    <code>SET</code>. If <code>APPEND</code>, captured content
+                    <code>Placeholder</code> constants <constant>APPEND</constant> or
+                    <constant>SET</constant>. If <constant>APPEND</constant>, captured content
                     is appended to the list of current content in the
-                    placeholder; if <code>SET</code>, captured content is used
+                    placeholder; if <constant>SET</constant>, captured content is used
                     as the sole value of the placeholder (potentially replacing
                     any previous content). By default, <varname>$type</varname> is
-                    <code>APPEND</code>.
+                    <constant>APPEND</constant>.
                 </para>
 
                 <para>