[DOCUMENTATION] English:

-  manual fixes

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

documentation/manual/en/module_specs/Zend_Controller-ActionHelpers-FlashMessenger.xml

@@ -6,14 +6,14 @@
     <sect4 id="zend.controller.actionhelper.flashmessenger.introduction">
         <title>Introduction</title>
         <para>
-            The <code>FlashMessenger</code> helper allows you to pass messages
+            The <emphasis>FlashMessenger</emphasis> helper allows you to pass messages
             that the user may need to see on the next request. To accomplish
-            this, <code>FlashMessenger</code> uses
+            this, <emphasis>FlashMessenger</emphasis> uses
             <classname>Zend_Session_Namespace</classname> to store messages for future or
             next request retrieval. It is generally a good idea that if you
             plan on using <classname>Zend_Session</classname> or
             <classname>Zend_Session_Namespace</classname>, that you initialize with
-            <classname>Zend_Session::start()</classname> in your bootstrap file. (See the
+            <methodname>Zend_Session::start()</methodname> in your bootstrap file. (See the
             <link linkend="zend.session.advanced_usage.starting_a_session">Zend_Session</link>
             documentation for more details on its usage.)
         </para>
@@ -24,9 +24,9 @@
         <title>Basic Usage Example</title>
         <para>
             The usage example below shows the use of the flash messenger at its
-            most basic. When the action <code>/some/my</code> is called, it adds
+            most basic. When the action <filename>/some/my</filename> is called, it adds
             the flash message "Record Saved!" A subsequent request to the action
-            <code>/some/my-next-request</code> will retrieve it (and thus delete
+            <filename>/some/my-next-request</filename> will retrieve it (and thus delete
             it as well).
         </para>