[DOCUMENTATION] [ZF-5446] [ZF-5471] }checked spelling

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

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

@@ -12,7 +12,7 @@
         <title>Zend_Cache_Backend_File</title>
 
         <para>
-            This (extended) backends stores cache records into files (in a choosen directory).
+            This (extended) backends stores cache records into files (in a chosen directory).
         </para>
 
         <para>

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

@@ -84,7 +84,7 @@ $databaseCache = $manager->getCache('database');
     <para>
         If for any reason, you are unsure where the Cache Manager contains a
         pre-instantiated cache or a relevant option cache template to create one
-        on request, you can check for the existance of a name cache configuration
+        on request, you can check for the existence of a name cache configuration
         or instance using the method <methodname>Zend_Cache_Manager::hasCache()</methodname>.
     </para>
 

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

@@ -833,7 +833,7 @@ $result = $cache->foobar2('1', '2');
                                             <emphasis>(int, <constant>FALSE</constant> by
                                                 default) specific_lifetime</emphasis>: if not
                                             <constant>FALSE</constant>, the
-                                            given lifetime will be used for the choosen regexp
+                                            given lifetime will be used for the chosen regexp
                                         </para>
                                     </listitem>
 

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

@@ -9,13 +9,13 @@
         <emphasis>'lifetime'</emphasis> directive as seen in the examples; it defines for how long
         the cached resource is considered 'fresh'. The third key concept is conditional execution so
         that parts of your code can be skipped entirely, boosting performance. The main frontend
-        function (eg. <methodname>Zend_Cache_Core::get()</methodname>) is always designed to return
+        function (e.g. <methodname>Zend_Cache_Core::get()</methodname>) is always designed to return
         <constant>FALSE</constant> for a cache miss if that makes sense for the nature of a
         frontend. That enables
         end-users to wrap parts of the code they would like to cache (and skip) in
         <emphasis><methodname>if()</methodname>{ ... }</emphasis> statements where the condition is
         a <classname>Zend_Cache</classname> method itself. On the end if these blocks you must save
-        what you've generated, however (eg. <methodname>Zend_Cache_Core::save()</methodname>).
+        what you've generated, however (e.g. <methodname>Zend_Cache_Core::save()</methodname>).
     </para>
 
     <note>
@@ -51,10 +51,10 @@ $backendName = '[...]';
 // We choose a frontend (for example 'Core', 'Output', 'Page'...)
 $frontendName = '[...]';
 
-// We set an array of options for the choosen frontend
+// We set an array of options for the chosen frontend
 $frontendOptions = array([...]);
 
-// We set an array of options for the choosen backend
+// We set an array of options for the chosen backend
 $backendOptions = array([...]);
 
 // We create an instance of Zend_Cache

documentation/manual/en/module_specs/Zend_Mail_Read.xml

@@ -6,7 +6,7 @@
     <para>
         <classname>Zend_Mail</classname> can read mail messages from several local or remote mail storages. All of them have the
         same basic <acronym>API</acronym> to count and fetch messages and some of them implement additional interfaces for not so common
-        features. For a feature overview of the implemented storages see the following table.
+        features. For a feature overview of the implemented storages, see the following table.
     </para>
 
     <table id="zend.mail.read.table-1">
@@ -230,7 +230,7 @@ unset($mail[$messageNum]);
         <methodname>getHeader()</methodname> if you want more control or have unusual header names. The header names are
         lower-cased internally, thus the case of the header name in the mail message doesn't matter. Also headers
         with a dash can be written in camel-case. If no header is found for both notations an exception is thrown.
-        To encounter this the method <methodname>headerExists()</methodname> can be used to check the existance of a header.</para>
+        To encounter this the method <methodname>headerExists()</methodname> can be used to check the existence of a header.</para>
 
         <programlisting language="php"><![CDATA[
 // get the message object