[DOCUMENTATION] English:

-  manual fixes

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

documentation/manual/en/module_specs/Zend_Amf-Server.xml

@@ -163,18 +163,19 @@ class World
             <filename>service-config.xml</filename> to find the RemoteObject endpoint. To do this
             open your project properties panel again by right clicking on the project folder from
             your Navigator and selecting properties. From the properties popup select 'Flex
-            Compiler' and add the string: -services "services-config.xml". Press Apply then OK to
-            return to update the option. What you have just done is told the Flex compiler to look
-            to the <filename>services-config.xml</filename> file for runtime variables that will be
-            used by the RemotingObject class.
+            Compiler' and add the string: <command>-services "services-config.xml"</command>. Press
+            Apply then OK to return to update the option. What you have just done is told the Flex
+            compiler to look to the <filename>services-config.xml</filename> file for runtime
+            variables that will be used by the RemotingObject class.
         </para>
 
         <para>
             We now need to tell Flex which services configuration file to use for connecting to
-            our remote methods. For this reason create a new 'services-config.xml' file into your
-            Flex project src folder. To do this right click on the project folder and select
-            'new' 'File' which will popup a new window. Select the project folder and then name
-            the file 'services-config.xml' and press finish.
+            our remote methods. For this reason create a new
+            '<filename>services-config.xml</filename>' file into your Flex project src folder. To
+            do this right click on the project folder and select 'new' 'File' which will popup a
+            new window. Select the project folder and then name the file
+            '<filename>services-config.xml</filename>' and press finish.
         </para>
 
         <para>

documentation/manual/en/module_specs/Zend_Application-AvailableResources-Session.xml

@@ -77,9 +77,9 @@ resources.session.saveHandler.options.lifetimeColumn = "lifetime"
             handler, you must first configure your database connection for it to
             work. Do this by either using the <link
                 linkend="zend.application.available-resources.db">Db</link>
-            resource -- and make sure the "resources.db" key comes prior to the
-            "resources.session" key -- or by writing your own resource that
-            initializes the database, and specifically sets the default
+            resource -- and make sure the "<emphasis>resources.db</emphasis>" key comes prior to
+            the "<emphasis>resources.session</emphasis>" key -- or by writing your own resource
+            that initializes the database, and specifically sets the default
             <classname>Zend_Db_Table</classname> adapter.
         </para>
     </note>

documentation/manual/en/module_specs/Zend_Auth_Adapter_Http.xml

@@ -136,9 +136,9 @@
                             <emphasis>'digest'</emphasis>
                         </entry>
                         <entry>
-                            Space-separated list of URIs for which the same authentication
-                            information is valid. The URIs need not all point to the same
-                            server.
+                            Space-separated list of <acronym>URI</acronym>s for which the same
+                            authentication information is valid. The <acronym>URI</acronym>s need
+                            not all point to the same server.
                         </entry>
                     </row>
                     <row>

documentation/manual/en/module_specs/Zend_Auth_Adapter_Ldap.xml

@@ -239,7 +239,7 @@ Array
                 the username is qualified with a domain (e.g., has a domain component like
                 <filename>alice@foo.net</filename> or <filename>FOO\alice</filename>). If a domain
                 is present, but does not match either of the server's domain names
-                (<filename>foo.net</filename> or <emphasis>FOO</emphasis>), a special exception is
+                (<filename>foo.net</filename> or <acronym>FOO</acronym>), a special exception is
                 thrown and caught by <classname>Zend_Auth_Adapter_Ldap</classname> that causes that
                 server to be ignored and the next set of server options is selected. If a domain
                 <emphasis>does</emphasis> match, or if the user did not supply a qualified username,
@@ -422,26 +422,26 @@ Array
                     <row>
                         <entry><emphasis>accountDomainName</emphasis></entry>
                         <entry>
-                            The FQDN domain name for which the target <acronym>LDAP</acronym>
-                            server is an authority (e.g., <filename>example.com</filename>). This
-                            option is used to canonicalize names so that the username supplied by
-                            the user can be converted as necessary for binding. It is also used to
-                            determine if the server is an authority for the supplied username
-                            (e.g., if <emphasis>accountDomainName</emphasis> is
-                            <filename>foo.net</filename> and the user supplies
-                            <filename>bob@bar.net</filename>, the server will not be queried, and a
-                            failure will result). This option is not required, but if it is not
-                            supplied, usernames in principal name form (e.g.,
-                            <filename>alice@foo.net</filename>) are not supported. It is strongly
-                            recommended that you supply this option, as there are many use-cases
-                            that require generating the principal name form.
+                            The <acronym>FQDN</acronym> domain name for which the target
+                            <acronym>LDAP</acronym> server is an authority (e.g.,
+                            <filename>example.com</filename>). This option is used to canonicalize
+                            names so that the username supplied by the user can be converted as
+                            necessary for binding. It is also used to determine if the server is an
+                            authority for the supplied username (e.g., if
+                            <emphasis>accountDomainName</emphasis> is <filename>foo.net</filename>
+                            and the user supplies <filename>bob@bar.net</filename>, the server will
+                            not be queried, and a failure will result). This option is not
+                            required, but if it is not supplied, usernames in principal name form
+                            (e.g., <filename>alice@foo.net</filename>) are not supported. It is
+                            strongly recommended that you supply this option, as there are many
+                            use-cases that require generating the principal name form.
                         </entry>
                     </row>
                     <row>
                         <entry><emphasis>accountDomainNameShort</emphasis></entry>
                         <entry>
                             The 'short' domain for which the target <acronym>LDAP</acronym> server
-                            is an authority (e.g., <emphasis>FOO</emphasis>). Note that there is a
+                            is an authority (e.g., <acronym>FOO</acronym>). Note that there is a
                             1:1 mapping between the <emphasis>accountDomainName</emphasis> and
                             <emphasis>accountDomainNameShort</emphasis>. This option should be used
                             to specify the NetBIOS domain name for Windows networks, but may also
@@ -449,7 +449,7 @@ Array
                             server options with the backslash style
                             <emphasis>accountCanonicalForm</emphasis>). This option is not required
                             but if it is not supplied, usernames in backslash form (e.g.,
-                            <emphasis>FOO\alice</emphasis>) are not supported.
+                            <filename>FOO\alice</filename>) are not supported.
                         </entry>
                     </row>
                     <row>
@@ -489,7 +489,7 @@ Array
                 client generates an error claiming that it cannot validate the server's
                 certificate. Assuming the <acronym>PHP</acronym> <acronym>LDAP</acronym> extension
                 is ultimately linked to the OpenLDAP client libraries, to resolve this issue you
-                can set "<emphasis>TLS_REQCERT never</emphasis>" in the OpenLDAP client
+                can set "<command>TLS_REQCERT never</command>" in the OpenLDAP client
                 <filename>ldap.conf</filename> (and restart the web server) to indicate to the
                 OpenLDAP client library that you trust the server. Alternatively, if you are
                 concerned that the server could be spoofed, you can export the
@@ -568,7 +568,8 @@ Array
                 For <acronym>ADS</acronym>, the following options are noteworthy:
             </para>
 
-            <table id="zend.auth.adapter.ldap.options-common-server-specific.active-directory.table">
+            <table
+                id="zend.auth.adapter.ldap.options-common-server-specific.active-directory.table">
                 <title>Options for Active Directory</title>
                 <tgroup cols="2">
                     <thead>
@@ -752,7 +753,7 @@ Array
                                 your <emphasis>accountDomainName</emphasis> is
                                 <filename>foo.net</filename>, a good
                                 <emphasis>accountDomainNameShort</emphasis> value might be
-                                <emphasis>FOO</emphasis>).
+                                <acronym>FOO</acronym>).
                             </entry>
                       </row>
                     </tbody>