[DOCUMENTATION] English:

 - manual fixes

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

documentation/manual/en/module_specs/Zend_Application-CoreFunctionality-Resource_ResourceAbstract.xml

@@ -191,7 +191,7 @@ class My_Resource_View extends Zend_Application_Resource_ResourceAbstract
 
         <para>
             We can then bootstrap that resource or retrieve it by the name
-            "My_View":
+            "<classname>My_View</classname>":
         </para>
 
         <programlisting language="php"><![CDATA[

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

@@ -387,8 +387,8 @@ $cache = Zend_Cache::factory('Core', 'Zend Platform');
                           <entry><constant>FALSE</constant></entry>
                           <entry>
                               if <constant>TRUE</constant>, the slow_backend argument is used as a
-                              complete class name ;
-                              if <constant>FALSE</constant>, the frontend argument is used as the end of
+                              complete class name; if <constant>FALSE</constant>,
+                              the frontend argument is used as the end of
                               "<classname>Zend_Cache_Backend_</classname>[...]" class name
                           </entry>
                       </row>
@@ -398,8 +398,8 @@ $cache = Zend_Cache::factory('Core', 'Zend Platform');
                           <entry><constant>FALSE</constant></entry>
                           <entry>
                               if <constant>TRUE</constant>, the fast_backend argument is used as a
-                              complete class name ;
-                              if <constant>FALSE</constant>, the frontend argument is used as the end of
+                              complete class name; if <constant>FALSE</constant>,
+                              the frontend argument is used as the end of
                               "<classname>Zend_Cache_Backend_</classname>[...]" class name
                           </entry>
                       </row>

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

@@ -755,7 +755,7 @@ $result = $cache->foobar2('1', '2');
                               <entry><methodname>array()</methodname></entry>
                               <entry>
                                   an associative array to set options only for some
-                                  <acronym>REQUEST_URI</acronym>, keys are
+                                  <constant>REQUEST_URI</constant>, keys are
                                   (<acronym>PCRE</acronym>) regexps, values are associative arrays
                                   with specific options to set if the regexp matchs on
                                   <varname>$_SERVER['REQUEST_URI']</varname> (see default_options

documentation/manual/en/module_specs/Zend_Controller-ActionController.xml

@@ -313,10 +313,10 @@ applicationOrModule/
 
             <para>
                 In other words, view scripts are assumed to be in the
-                <filename>views/scripts/</filename> subdirectory, and the
-                <filename>views/</filename> subdirectory is assumed to contain sibling
+                <filename>/views/scripts/</filename> subdirectory, and the
+                <filename>/views/</filename> subdirectory is assumed to contain sibling
                 functionality (helpers, filters). When determining the view
-                script name and path, the <filename>views/scripts/</filename> directory
+                script name and path, the <filename>/views/scripts/</filename> directory
                 will be used as the base path, with directories named after the
                 individual controllers providing a hierarchy of view scripts.
             </para>
@@ -341,8 +341,8 @@ string render(string $action = null,
                 <filename>[controller]/[action].phtml</filename> (where
                 <filename>.phtml</filename> is the value of the <varname>$viewSuffix</varname>
                 property). Passing a value for <varname>$action</varname> will render
-                that template in the <filename>[controller]/</filename> subdirectory. To
-                override using the <filename>[controller]/</filename> subdirectory, pass
+                that template in the <filename>/[controller]/</filename> subdirectory. To
+                override using the <filename>/[controller]/</filename> subdirectory, pass
                 a <constant>TRUE</constant> value for <varname>$noController</varname>. Finally,
                 templates are rendered into the response object; if you wish to render to
                 a specific <link