[MANUAL] English:

- unified classnames

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

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

@@ -679,10 +679,10 @@ private function onFault(fault:Object):void {
 
         <para>
             Adding in the ActionScript to make the remoting connection is now complete. Running the
-            ZendExample file now makes a connection to Zend Amf. In review you have added the
-            required variables to open a connection to the remote server, defined what methods
-            should be used when your application receives a response from the server, and finally
-            displayed the returned data to output via <methodname>trace()</methodname>.
+            ZendExample file now makes a connection to <classname>Zend_Amf</classname>. In review
+            you have added the required variables to open a connection to the remote server, defined
+            what methods should be used when your application receives a response from the server,
+            and finally displayed the returned data to output via <methodname>trace()</methodname>.
         </para>
     </sect2>
 

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

@@ -420,10 +420,10 @@ C:\WAMP\PHP\bin
             </para>
 
             <sect4 id="zend.tool.extending.zend-tool-framework.providers-and-manifests.loading">
-                <title>How Zend Tool finds your Providers</title>
+                <title>How Zend_Tool finds your Providers</title>
 
                 <para>
-                    By default Zend Tool uses the BasicLoader to find all
+                    By default <classname>Zend_Tool</classname> uses the BasicLoader to find all
                     the providers that you can run. It recursivly iterates all
                     include path directories and opens all files that end
                     with "Manifest.php" or "Provider.php". All classes in these
@@ -479,8 +479,8 @@ C:\WAMP\PHP\bin
                     <title>Exposing Your Providers with a Manifest</title>
 
                     <para>
-                        You can expose your providers to Zend Tool by offering a manifest
-                        with a special filename ending with "Manifest.php".
+                        You can expose your providers to <classname>Zend_Tool</classname> by
+                        offering a manifest with a special filename ending with "Manifest.php".
                         A Provider Manifest is an implementation of the
                         <interface>Zend_Tool_Framework_Manifest_ProviderManifestable</interface>
                         and requires the <methodname>getProviders()</methodname> method to return
@@ -546,11 +546,12 @@ Hello from my provider!
                 <title>The response object</title>
 
                 <para>
-                    As discussed in the architecture section Zend Tool allows to hook different
-                    clients for using your Zend Tool providers. To keep compliant with different
-                    clients you should use the response object to return messages from your
-                    providers instead of using <methodname>echo()</methodname> or a similiar output
-                    mechanism. Rewritting our hello provider with this knowledge it looks like:
+                    As discussed in the architecture section <classname>Zend_Tool</classname> allows
+                    to hook different clients for using your <classname>Zend_Tool</classname>
+                    providers. To keep compliant with different clients you should use the response
+                    object to return messages from your providers instead of using
+                    <methodname>echo()</methodname> or a similiar output mechanism. Rewritting our
+                    hello provider with this knowledge it looks like:
                 </para>
 
                 <programlisting language="php"><![CDATA[
@@ -736,8 +737,8 @@ class My_Component_HelloProvider
                     <para>
                         Using the Enviroment variable <property>ZF_CONFIG_FILE</property> or the
                         .zf.ini in your home directory you can inject configuration parameters into
-                        any Zend Tool provider. Access to this configuration is available via the
-                        registry that is passed to your provider if you extend
+                        any <classname>Zend_Tool</classname> provider. Access to this configuration
+                        is available via the registry that is passed to your provider if you extend
                         <classname>Zend_Tool_Framework_Provider_Abstract</classname>.
                     </para>
 

documentation/manual/en/module_specs/Zend_Tool_Framework-WritingProviders.xml

@@ -11,10 +11,10 @@
     </para>
 
     <sect2 id="zend.tool.framework.writing-providers.loading">
-        <title>How Zend Tool finds your Providers</title>
+        <title>How Zend_Tool finds your Providers</title>
 
         <para>
-            By default Zend Tool uses the IncludePathLoader to find all
+            By default <classname>Zend_Tool</classname> uses the IncludePathLoader to find all
             the providers that you can run. It recursivly iterates all
             include path directories and opens all files that end
             with "Manifest.php" or "Provider.php". All classes in these
@@ -71,8 +71,8 @@
             <title>Exposing Your Providers with a Manifest</title>
 
             <para>
-                You can expose your providers to Zend Tool by offering a manifest
-                with a special filename ending with "Manifest.php".
+                You can expose your providers to <classname>Zend_Tool</classname> by offering a
+                manifest with a special filename ending with "Manifest.php".
                 A Provider Manifest is an implementation of the
                 <interface>Zend_Tool_Framework_Manifest_ProviderManifestable</interface>
                 and requires the <methodname>getProviders()</methodname> method to return
@@ -138,11 +138,11 @@ Hello from my provider!
         <title>The response object</title>
 
         <para>
-            As discussed in the architecture section Zend Tool allows to hook different clients for
-            using your Zend Tool providers. To keep compliant with different clients you should
-            use the response object to return messages from your providers instead of using
-            <methodname>echo()</methodname> or a similiar output mechanism. Rewritting our hello
-            provider with this knowledge it looks like:
+            As discussed in the architecture section <classname>Zend_Tool</classname> allows to hook
+            different clients for using your <classname>Zend_Tool</classname> providers. To keep
+            compliant with different clients you should use the response object to return messages
+            from your providers instead of using <methodname>echo()</methodname> or a similiar
+            output mechanism. Rewritting our hello provider with this knowledge it looks like:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -323,8 +323,8 @@ class My_Component_HelloProvider
             <para>
                 Using the Enviroment variable <property>ZF_CONFIG_FILE</property> or the
                 .zf.ini in your home directory you can inject configuration parameters into
-                any Zend Tool provider. Access to this configuration is available via the
-                registry that is passed to your provider if you extend
+                any <classname>Zend_Tool</classname> provider. Access to this configuration is
+                available via the registry that is passed to your provider if you extend
                 <classname>Zend_Tool_Framework_Provider_Abstract</classname>.
             </para>
 

documentation/manual/en/module_specs/Zend_Tool_Project-Providers.xml

@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
 <sect1 id="zend.tool.project.providers">
-    <title>Zend Tool Project Providers</title>
+    <title>Zend_Tool Project Providers</title>
 
     <para>
         Below is a table of all of the providers shipped with

documentation/manual/en/module_specs/Zend_Translate-Using.xml

@@ -27,7 +27,7 @@ print "Here is line two\n";
     </para>
 
     <para>
-        The next step is to integrate Zend Translate into your existing code.
+        The next step is to integrate <classname>Zend_Translate</classname> into your existing code.
         Of course it is much easier if you had already written your code with
         translation in mind, than changing your code afterwards.
     </para>

documentation/manual/en/module_specs/Zend_View-Helpers-Currency.xml

@@ -6,7 +6,7 @@
     <para>
         Displaying localized currency values is a common task; the
         <classname>Zend_Currency</classname> view helper is intended to simply this task.  See the
-        <link linkend="zend.currency.introduction">Zend Currency documentation</link> for specifics
+        <link linkend="zend.currency.introduction">Zend_Currency documentation</link> for specifics
         on this localization feature. In this section, we will focus simply on usage of the view
         helper.
     </para>

documentation/manual/en/module_specs/Zend_View-Helpers-Translate.xml

@@ -6,8 +6,8 @@
     <para>
         Often web sites are available in several languages. To translate the
         content of a site you should simply use <link
-            linkend="zend.translate.introduction">Zend Translate</link> and to
-        integrate <classname>Zend Translate</classname> within your view you should use
+            linkend="zend.translate.introduction">Zend_Translate</link> and to
+        integrate <classname>Zend_Translate</classname> within your view you should use
         the <emphasis>Translate</emphasis> View Helper.
     </para>