diff --git a/build.sh b/build.sh
index 4fc65b0d..b91db496 100755
--- a/build.sh
+++ b/build.sh
@@ -86,7 +86,7 @@ case "$1" in
    man7)
       for man in cdist.text cdist-best-practice.text cdist-hacker.text         \
       cdist-quickstart.text cdist-reference.text cdist-stages.text             \
-      cdist-type.text
+      cdist-type.text cdist-cache.text
          do
          ln -sf ../$man ${MAN7DSTDIR}
       done
diff --git a/doc/changelog b/doc/changelog
index 5cfae26f..93d0f7e4 100644
--- a/doc/changelog
+++ b/doc/changelog
@@ -1,3 +1,6 @@
+1.5.0:
+	* Add cache functionality
+
 1.4.1: 2011-03-25
 	* New type __key_value (Steven Armstrong)
 	* New type __apt_ppa (Steven Armstrong)
@@ -41,7 +44,6 @@
 	* Document cdist-object-gencode-all
 	* Document cdist-manifest-run
 
-
 1.1.0: 2011-03-16
 	* Replace type __file with __file, __directory, __link
 	* Document cdist-env
diff --git a/doc/man/cdist-cache.text b/doc/man/cdist-cache.text
index cbf4c9d7..54619199 100644
--- a/doc/man/cdist-cache.text
+++ b/doc/man/cdist-cache.text
@@ -15,25 +15,9 @@ cdist-cache TARGET_HOST
 
 DESCRIPTION
 -----------
-
-   Assume you want to configure stuff one host ("monitor node"),
-   depending on the configuration of other hosts ("cluster nodes").
-
-   For instance, the monitor host would like to know,
-   which hosts are configured with the provider
-   "apache" and option --start true.
-
-   This requires the monitor node to be able to
-   query all other configured nodes. It can't
-   ask for all hosts, because cdist does not 
-   know which hosts are configured or may exist.
-
-   Example implementation
-
-   If cdist keeps ("caches") the configuration of every
-   node it configures, each new node can query the 
-   cache for existing nodes that acquired the given
-   configuration.
+cdist-cache moves away the objects created during last run so the
+next run can use the previous information and compare them with
+the current status.
 
 
 SEE ALSO