ZF-10818: removed marker of the pre-defined cache manager template 'skeleton' and renamed template 'tagcache' to 'pagetag' as defined in Zend_Cache_Manager

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

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

@@ -186,16 +186,13 @@ $databaseCache = $manager->getCache('database');
 
     <para>
         Out of the box, <classname>Zend_Cache_Manager</classname> already includes
-        four pre-defined cache templates called "skeleton", "default", "page" and
-        "tagcache". The default cache is a simple File based cache using the Core
-        frontend which assumes a cache_dir called "cache" exists at the same
-        level as the conventional "public" directory of a Zend Framework application.
-        The skeleton cache is actually a <constant>NULL</constant> cache, i.e. it contains no
-        options. The remaining two caches are used to implement a default Static Page Cache
+        three pre-defined cache templates called "default", "page" and "pagetag".
+        The default cache is a simple File based cache using the Core frontend.
+        The remaining two caches are used to implement a default Static Page Cache
         where static <acronym>HTML</acronym>, <acronym>XML</acronym> or even <acronym>JSON</acronym>
         may be written to static files in <filename>/public</filename>. Control over a Static Page
         Cache is offered via <classname>Zend_Controller_Action_Helper_Cache</classname>, though you
-        may alter the settings of this "page" the "tagcache" it uses to track tags using
+        may alter the settings of this "page" the "pagetag" it uses to track tags using
         <methodname>Zend_Cache_Manager::setTemplateOptions()</methodname> or even
         <methodname>Zend_Cache_Manager::setCacheTemplate()</methodname> if overloading
         all of their options.