diff --git a/doc/man/cdist-stages.text b/doc/man/cdist-stages.text
index 465a7fc8..279e1d5f 100644
--- a/doc/man/cdist-stages.text
+++ b/doc/man/cdist-stages.text
@@ -23,7 +23,7 @@ Before running the user facing stages, cdist prepares the target host
 to contain cdist binaries and creates a clean environment for the
 configuration run.
 
-Related manpages:
+Related documentation:
    - cdist-bin-transfer(1) FIXME: does not exist
 
 
@@ -34,7 +34,7 @@ explorers. Every existing explorer is run on the target and the output of all
 explorers are copied back into the local cache. The results can be used by 
 manifests and types.
 
-Related manpages:
+Related documentation:
    - cdist-explorer-run-global(1)
    - cdist-remote-explorer-run(1)
    - cdist-explorer(7)
@@ -48,7 +48,7 @@ the objects as defined in the manifest for the specific host. In this stage,
 no conflicts may occur, i.e. no object of the same type with the same id may
 be created.
 
-Related manpages: 
+Related documentation: 
    - cdist-manifest-run-init(1)
    - cdist-manifest-run(1)
    - cdist-manifest(7)
@@ -61,7 +61,7 @@ transfered to the target host and executed. The results are transfered back
 and can be used in the following stages to decide what changes need to made
 on the target to implement the desired state.
 
-Related manpages:
+Related documentation:
    - cdist-object-explorer-run(1)
    - cdist-remote-explorer-run(1)
    - cdist-type(7) 
@@ -82,7 +82,7 @@ The newly created objects are merged back into the existing tree. No conflicts
 may occur during the merge. A conflict would mean that two different objects
 try to create the same object, which indicates a broken configuration.
 
-Related manpages:
+Related documentation:
    - cdist-object-manifest-run(1)
    - cdist-manifest-run(1)
    - cdist-type(7) 
@@ -96,7 +96,7 @@ be executed. This executable should create code to be executed on the target
 on stdout. If the gencode executable fails, it must print diagnostic messages
 on stderr and exit non-zero.
 
-Related manpages:
+Related documentation:
    - cdist-object-gencode-run(1)
    - cdist-object-gencode(1)
    - cdist-type(7) 
@@ -107,7 +107,7 @@ STAGE 6: CODE EXECUTION
 For every object the resulting code from the previous stage is transferred to
 the target host and executed there to apply the configuration changes.
 
-Related manpages:
+Related documentation:
    - cdist-object-code-run(1)
    - cdist-code-run(1)
 
@@ -116,7 +116,7 @@ STAGE 7: CACHE
 --------------
 The cache stores the information from the current run for later use.
 
-Related manpages:
+Related documentation:
    - cdist-cache(1)