[DOCUMENTATION] English:

 - manual fixes: 'ZF' by 'Zend Framework' in text

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

documentation/manual/en/module_specs/Zend_Db_Table.xml

@@ -28,7 +28,7 @@
         <title>Using Zend_Db_Table as a concrete class</title>
 
         <para>
-            As of ZF 1.9, you can instantiate <classname>Zend_Db_Table</classname>. This added benefit is that
+            As of Zend Framework 1.9, you can instantiate <classname>Zend_Db_Table</classname>. This added benefit is that
             you do not have to extend a base class and configure it to do simple operations
             such as selecting, inserting, updating and deleteing on a single table. Below
             is an example of the simplest of use cases.

documentation/manual/en/module_specs/Zend_Dojo.xml

@@ -27,7 +27,7 @@
         javascript source, unit tests, and build tools. You can symlink this
         into your javascript directory, copy it, or use the build tool to create
         your own custom build to include in your project. Alternatively, you can
-        use one of the Content Delivery Networks that offer Dojo (ZF supports
+        use one of the Content Delivery Networks that offer Dojo (Zend Framework supports
         both the official AOL CDN as well as the Google CDN).
     </para>
 </sect1>

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

@@ -380,7 +380,7 @@ $date = new Zend_Date();
         <title>ZF Locale-Aware Classes</title>
 
         <para>
-            In the ZF, locale-aware classes rely on <classname>Zend_Locale</classname> to
+            In the Zend Framework, locale-aware classes rely on <classname>Zend_Locale</classname> to
             automatically select a locale, as explained above. For example, in a Zend Framework web
             application, constructing a date using <classname>Zend_Date</classname> without
             specifying a locale results in an object with a locale based on information provided by

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

@@ -20,7 +20,7 @@
             but they are somewhat more performant.
             <footnote>
                 <para>
-                It's a limitation of current ZF version. It will be eliminated in future versions.
+                It's a limitation of current Zend Framework version. It will be eliminated in future versions.
                 But unattached pages will always give better (more optimal) result for sharing pages between documents.
                 </para>
             </footnote>

documentation/manual/en/module_specs/Zend_Search_Lucene-Charset.xml

@@ -81,7 +81,7 @@ Zend_Search_Lucene_Analysis_Analyzer::setDefault(
         <warning>
             <title/>
             <para>
-                UTF-8 compatible analyzers were improved in ZF 1.5. Early versions of analyzers assumed
+                UTF-8 compatible analyzers were improved in Zend Framework 1.5. Early versions of analyzers assumed
                 all non-ascii characters are letters. New analyzers implementation has more accurate behavior.
             </para>
             <para>

documentation/manual/en/module_specs/Zend_Search_Lucene-IndexCreation.xml

@@ -134,7 +134,7 @@ for ($count = 0; $count < $index->maxDoc(); $count++) {
             reorganization. See Lucene index file formats for details
             (<ulink url="http://lucene.apache.org/java/docs/fileformats.html">http://lucene.apache.org/java/docs/fileformats.html</ulink>)
             <footnote>
-                <para>The currently supported Lucene index file format is version 2.3 (starting from ZF 1.6).</para>
+                <para>The currently supported Lucene index file format is version 2.3 (starting from Zend Framework 1.6).</para>
             </footnote>.
             New documents are added to the index by creating new segment.
         </para>
@@ -220,14 +220,14 @@ $index->optimize();
             <para>
                 Lucene Java and Luke (Lucene Index Toolbox - <ulink url="http://www.getopt.org/luke/">http://www.getopt.org/luke/</ulink>)
                 can also be used to optimize an index. Latest Luke release (v0.8) is based on Lucene v2.3 and compatible with
-                current implementation of <classname>Zend_Search_Lucene</classname> component (ZF 1.6). Earlier versions of <classname>Zend_Search_Lucene</classname> implementations
+                current implementation of <classname>Zend_Search_Lucene</classname> component (Zend Framework 1.6). Earlier versions of <classname>Zend_Search_Lucene</classname> implementations
                 need another versions of Java Lucene tools to be compatible:
                 <itemizedlist>
                     <listitem>
-                        <para>ZF 1.5 - Java Lucene 2.1 (Luke tool v0.7.1 - <ulink url="http://www.getopt.org/luke/luke-0.7.1/"/>)</para>
+                        <para>Zend Framework 1.5 - Java Lucene 2.1 (Luke tool v0.7.1 - <ulink url="http://www.getopt.org/luke/luke-0.7.1/"/>)</para>
                     </listitem>
                     <listitem>
-                        <para>ZF 1.0 - Java Lucene 1.4 - 2.1 (Luke tool v0.6 - <ulink url="http://www.getopt.org/luke/luke-0.6/"/>)</para>
+                        <para>Zend Framework 1.0 - Java Lucene 1.4 - 2.1 (Luke tool v0.6 - <ulink url="http://www.getopt.org/luke/luke-0.6/"/>)</para>
                     </listitem>
                 </itemizedlist>
             </para>

documentation/manual/en/module_specs/Zend_Search_Lucene-JavaLucene.xml

@@ -13,7 +13,7 @@
         <para>
           A detailed description of this format is available here:
           <ulink url="http://lucene.apache.org/java/docs/fileformats.html"/>
-          <footnote><para>The currently supported Lucene index file format version is 2.3 (starting from ZF 1.6).</para></footnote>.
+          <footnote><para>The currently supported Lucene index file format version is 2.3 (starting from Zend Framework 1.6).</para></footnote>.
         </para>
     </sect2>
 

documentation/manual/en/module_specs/Zend_Search_Lucene-Overview.xml

@@ -33,8 +33,8 @@
                 Previous <classname>Zend_Search_Lucene</classname> implementations support the Lucene 1.4 (1.9) - 2.1 index formats.
             </para>
             <para>
-                Starting from ZF 1.5 any index created using pre-2.1 index format is automatically upgraded to Lucene 2.1 format
-                after the <classname>Zend_Search_Lucene</classname> update and will not be compatible with <classname>Zend_Search_Lucene</classname> implementations included into ZF 1.0.x.
+                Starting from Zend Framework 1.5 any index created using pre-2.1 index format is automatically upgraded to Lucene 2.1 format
+                after the <classname>Zend_Search_Lucene</classname> update and will not be compatible with <classname>Zend_Search_Lucene</classname> implementations included into Zend Framework 1.0.x.
             </para>
         </note>
     </sect2>
@@ -314,7 +314,7 @@ $headerLinksArray = $doc->getHeaderLinks();
         </para>
 
         <para>
-            Starting from ZF 1.6 it's also possible to exclude links with <code>rel</code> attribute set to <code>'nofollow'</code>.
+            Starting from Zend Framework 1.6 it's also possible to exclude links with <code>rel</code> attribute set to <code>'nofollow'</code>.
             Use <methodname>Zend_Search_Lucene_Document_Html::setExcludeNoFollowLinks($true)</methodname> to turn on this option.
         </para>
         <para>

documentation/manual/en/module_specs/Zend_Session-GlobalSessionManagement.xml

@@ -249,7 +249,7 @@ Zend_Session::setOptions($config->toArray());
         <title>Session Identifiers</title>
 
         <para>
-            Introduction: Best practice in relation to using sessions with ZF calls for using a browser cookie (i.e.
+            Introduction: Best practice in relation to using sessions with Zend Framework calls for using a browser cookie (i.e.
             a normal cookie stored in your web browser), instead of embedding a unique session identifier in URLs as
             a means to track individual users. By default this component uses only cookies to maintain session
             identifiers. The cookie's value is the unique identifier of your browser's session. PHP's ext/session