[MANUAL] English:

- manual fixes

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

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

@@ -45,8 +45,8 @@ resources.cachemanager.database.frontendBackendAutoload = false
             calling <methodname>Zend_Cache_Manager::getCache('database')</methodname>. The example
             below is taken from a controller where the bootstrap class can be accessed as
             a Front Controller parameter (which is automatically assigned during bootstrapping).
-            As you can see, the Cache Manager Resource implements a <methodname>
-            getCacheManager()</methodname> method to retrieve the bootstrapped instance
+            As you can see, the Cache Manager Resource implements a
+            <methodname>getCacheManager()</methodname> method to retrieve the bootstrapped instance
             of <classname>Zend_Cache_Manager</classname>.
         </para>
 
@@ -61,7 +61,7 @@ $dbCache = $manager->getCache('database');
         <para>
             See <methodname>Zend_Cache::factory()</methodname> method to get a
             description of the default values you can assign when configuring a
-            cache via a configuration file such as out example INI file above.
+            cache via a configuration file such as out example <acronym>INI</acronym> file above.
         </para>
     </example>
 </sect2>

documentation/manual/en/module_specs/Zend_Cache-Backends.xml

@@ -579,8 +579,8 @@ $cache = Zend_Cache::factory('Core', 'Zend_Cache_Backend_ZendServer_Disk',
                     by registering a callback function to be called
                     when the output buffering it uses is cleaned. In order for this to operate
                     correctly, it must be the final output buffer in the request. To guarantee
-                    this, the output buffering used by the Dispatcher MUST be disabled by
-                    calling <classname>Zend_Controller_Front</classname>'s
+                    this, the output buffering used by the Dispatcher <emphasis>must</emphasis> be
+                    disabled by calling <classname>Zend_Controller_Front</classname>'s
                     <methodname>setParam()</methodname> method, for example,
                     <command>$front->setParam('disableOutputBuffering', true);</command> or adding
                     "resources.frontcontroller.params.disableOutputBuffering = true"

documentation/manual/en/module_specs/Zend_Cache-Frontends.xml

@@ -661,8 +661,8 @@ $result = $cache->foobar2('1', '2');
                     This frontend operates by registering a callback function to be called
                     when the output buffering it uses is cleaned. In order for this to operate
                     correctly, it must be the final output buffer in the request. To guarantee
-                    this, the output buffering used by the Dispatcher MUST be disabled by
-                    calling <classname>Zend_Controller_Front</classname>'s
+                    this, the output buffering used by the Dispatcher <emphasis>must</emphasis> be
+                    disabled by calling <classname>Zend_Controller_Front</classname>'s
                     <methodname>setParam()</methodname> method, for example,
                     <command>$front->setParam('disableOutputBuffering', true);</command> or adding
                     "resources.frontcontroller.params.disableOutputBuffering = true"
@@ -999,16 +999,17 @@ if ($someTest) {
             <para>
                 <classname>Zend_Cache_Frontend_Capture</classname> is like
                 <classname>Zend_Cache_Frontend_Output</classname> but designed for a complete page.
-                It's impossible to use <classname>Zend_Cache_Frontend_Capture</classname> for caching
-                only a single block. This class is specifically designed to operate in concert
-                only with the <classname>Zend_Cache_Backend_Static</classname> backend to
-                assist in caching entire pages of HTML/XML or other content to a physical static
-                file on the local filesystem.
+                It's impossible to use <classname>Zend_Cache_Frontend_Capture</classname> for
+                caching only a single block. This class is specifically designed to operate in
+                concert only with the <classname>Zend_Cache_Backend_Static</classname> backend to
+                assist in caching entire pages of <acronym>HTML</acronym> / <acronym>XML</acronym>
+                or other content to a physical static file on the local filesystem.
             </para>
 
             <para>
-                Please refer to the documentation on <classname>Zend_Cache_Backend_Static</classname>
-                for all use cases pertaining to this class.
+                Please refer to the documentation on
+                <classname>Zend_Cache_Backend_Static</classname> for all use cases pertaining to
+                this class.
             </para>
 
             <note>
@@ -1016,8 +1017,8 @@ if ($someTest) {
                     This frontend operates by registering a callback function to be called
                     when the output buffering it uses is cleaned. In order for this to operate
                     correctly, it must be the final output buffer in the request. To guarantee
-                    this, the output buffering used by the Dispatcher MUST be disabled by
-                    calling <classname>Zend_Controller_Front</classname>'s
+                    this, the output buffering used by the Dispatcher <emphasis>must</emphasis> be
+                    disabled by calling <classname>Zend_Controller_Front</classname>'s
                     <methodname>setParam()</methodname> method, for example,
                     <command>$front->setParam('disableOutputBuffering', true);</command> or adding
                     "resources.frontcontroller.params.disableOutputBuffering = true"