[MANUAL] English:

- several manual fixes

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

documentation/manual/en/module_specs/Zend_Mail-CharacterSets.xml

@@ -6,9 +6,10 @@
     <para>
         <classname>Zend_Mail</classname> does not check for the correct character set of the mail
         parts. When instantiating <classname>Zend_Mail</classname>, a charset for the e-mail itself
-        may be given. It defaults to <code>iso-8859-1</code>. The application has to make sure that
-        all parts added to that mail object have their content encoded in the correct character set.
-        When creating a new mail part, a different charset can be given for each part.
+        may be given. It defaults to <emphasis>iso-8859-1</emphasis>. The application has to make
+        sure that all parts added to that mail object have their content encoded in the correct
+        character set. When creating a new mail part, a different charset can be given for each
+        part.
     </para>
 
     <note>

documentation/manual/en/module_specs/Zend_Mail-HtmlMails.xml

@@ -6,9 +6,10 @@
     <para>
         To send an e-mail in <acronym>HTML</acronym> format, set the body using the method
         <methodname>setBodyHTML()</methodname> instead of <methodname>setBodyText()</methodname>.
-        The <acronym>MIME</acronym> content type will automatically be set to <code>text/html</code>
-        then. If you use both <acronym>HTML</acronym> and Text bodies, a multipart/alternative
-        <acronym>MIME</acronym> message will automatically be generated:
+        The <acronym>MIME</acronym> content type will automatically be set to
+        <property>text/html</property> then. If you use both <acronym>HTML</acronym> and Text
+        bodies, a multipart/alternative <acronym>MIME</acronym> message will automatically be
+        generated:
     </para>
 
     <example id="zend.mail.html-mails.example-1">

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

@@ -52,7 +52,7 @@ $mail->send();
 
         <para>
             For security reasons, <classname>Zend_Mail</classname> filters all header fields to
-            prevent header injection with newline (<code>\n</code>) characters.
+            prevent header injection with newline (<emphasis>\n</emphasis>) characters.
             Double quotation is changed to single quotation and angle brackets to square brackets in
             the name of sender and recipients. If the marks are in email address, the marks will be
             removed.

documentation/manual/en/module_specs/Zend_Pdf-Drawing.xml

@@ -258,7 +258,7 @@ $pdfPage->drawText('Hello world!', 72, 720);
             database), you can indicate the character encoding at draw time and
             <classname>Zend_Pdf</classname> will handle the conversion for you. You can supply
             source strings in any encoding method supported by <acronym>PHP</acronym>'s
-            <code><ulink url="http://www.php.net/manual/function.iconv.php">iconv()</ulink></code>
+            <ulink url="http://www.php.net/manual/function.iconv.php">iconv()</ulink>
             function:
         </para>
 

documentation/manual/en/module_specs/Zend_Pdf-Properties.xml

@@ -11,8 +11,8 @@
 
     <para>
         Historically this information is stored using special Info structure. This structure
-        is available for read and writing as an associative array using <code>properties</code>
-        public property of <classname>Zend_Pdf</classname> objects:
+        is available for read and writing as an associative array using
+        <property>properties</property> public property of <classname>Zend_Pdf</classname> objects:
     </para>
 
     <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Registry.xml

@@ -98,7 +98,7 @@ foreach ($registry as $index => $value) {
         </para>
 
         <para>
-            Use the traditional <code>new</code> operator to instantiate
+            Use the traditional <emphasis>new</emphasis> operator to instantiate
             <classname>Zend_Registry</classname>. Instantiating <classname>Zend_Registry</classname>
             using its constructor also makes initializing the entries in the registry simple by
             taking an associative array as an argument.

documentation/manual/en/module_specs/Zend_Service_LiveDocx.xml

@@ -328,7 +328,7 @@
             <para>
                 Using this dialog, you can insert the required merge fields into your document.
                 Below is a screenshot of a license agreement in Microsoft Word 2007. The merge
-                fields are marked as <code>{ MERGEFIELD FieldName }</code>:
+                fields are marked as <command>{ MERGEFIELD FieldName }</command>:
             </para>
 
             <para>

documentation/manual/en/module_specs/Zend_Service_WindowsAzure_Blob.xml

@@ -173,7 +173,7 @@ $storageClient->setContainerAcl(
         <para>
             Windows Azure Blob Storage provides support to work with a "root container".
             This means that a blob can be stored in the root of your storage account,
-            i.e. <code>http://myaccount.blob.core.windows.net/somefile.txt</code>.
+            i.e. <filename>http://myaccount.blob.core.windows.net/somefile.txt</filename>.
         </para>
 
         <para>

documentation/manual/en/module_specs/Zend_Tool-Extending.xml

@@ -861,10 +861,10 @@ class Zend_Tool_Framework_Client_Storage
             <para>
                 Project specific providers are created in the same fashion as plain framework
                 providers, with one exception: project providers must extend the
-                <code>Zend_Tool_Project_Provider_Abstract</code>. This class comes with some
-                significant functionality that helps developers load existing project, obtian the
-                profile object, and be able to search the profile, then later store any changes to
-                the current project profile.
+                <classname>Zend_Tool_Project_Provider_Abstract</classname>. This class comes with
+                some significant functionality that helps developers load existing project, obtian
+                the profile object, and be able to search the profile, then later store any changes
+                to the current project profile.
             </para>
 
             <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Tool-Usage-CLI.xml

@@ -457,7 +457,7 @@ zf --setup storage-directory
 
             <para>
                 This will create the proper zf.ini file. This <emphasis>should</emphasis>
-                be run after <code>zf --setup storage-directory</code>. If it is not, it will
+                be run after <command>zf --setup storage-directory</command>. If it is not, it will
                 be located inside the users home directory. If it is, it will be located inside
                 the users storage directory.
             </para>