diff --git a/docs/en/programmers/caching/caching-cacheable.xml b/docs/en/programmers/caching/caching-cacheable.xml
index 49aa697f..48cbb1c2 100644
--- a/docs/en/programmers/caching/caching-cacheable.xml
+++ b/docs/en/programmers/caching/caching-cacheable.xml
@@ -2,26 +2,22 @@
 <!-- $Revision$ -->
  <sect1 id="caching.cacheable">
   <title>Controlling Cacheability of Plugins' Output</title>
-   <para>
-   Since Smarty-2.6.0 plugins the cacheability of plugins can be declared
-   when registering them. The third parameter to
-   <link linkend="api.register.block">register_block()</link>,
-   <link
+  <para>
+   Since Smarty-2.6.0 plugins the cacheability of plugins can be
+   declared when registering them. The third parameter to <link
+   linkend="api.register.block">register_block()</link>, <link
    linkend="api.register.compiler.function">register_compiler_function()
-   </link> and
-   <link linkend="api.register.block">register_function()</link> is called
-   <parameter>$cacheable</parameter> and defaults to true which is also
-   the behaviour of plugins in Smarty versions before 2.6.0
+   </link> and <link
+   linkend="api.register.function">register_function()</link> is
+   called <parameter>$cacheable</parameter> and defaults to true which
+   is also the behaviour of plugins in Smarty versions before 2.6.0
   </para>
-
-
   <para>
    When registering a plugin with $cacheable=false the plugin is
    called everytime the page is displayed, even if the page comes
    from the cache. The plugin function behaves a little like an
    <link linkend="plugins.inserts">insert</link> function.
   </para>
-
   <para>
    In contrast to <link linkend="plugins.inserts">insert</link>
    the attributes to the plugins are not cached by default. They can be