Added glue text between the tutorials.

docs/basics.rst

@@ -348,3 +348,7 @@ one option is to raise an :class:`ArgumentError` from within your function:
 
 If you would like the usage line not to be printed, raise :class:`UserError`
 instead.
+
+
+Next up, we will look at how you can have Clize :ref:`dispatch to multiple
+functions<dispatching>` for you.

docs/compositing.rst

@@ -225,3 +225,8 @@ names of the composited parameters must not conflict:
     Connecting to (('abc', 80, True), ('def', 80, False)) to get /eggs
     $ python argdeco.py /eggs -6 abc def --port 8080 cheese
     Connecting to (('abc', 80, True), ('def', 80, False), ('cheese', 8080, False)) to get /eggs
+
+
+Congratulations, you've reached the end of the tutorials! You can check out the
+:ref:`parameter reference<parameter-reference>` or see how you can :ref:`extend
+the parser<extending parser>`.

docs/multicommands.rst

@@ -72,5 +72,9 @@ feature.
     Sorry I forgot it all :(
 
 Alternatively, you can pass any iterable of functions or a mapping(`dict` or
-`collections.OrderedDict`) to `.run` like with :ref:`the alt parameter explained earlier <command-list>`.
+`collections.OrderedDict`) to `.run` like with :ref:`the alt parameter
+explained earlier <command-list>`.
 
+
+You'll often need to share a few characteristics between each function. See how
+Clize helps you do that in :ref:`function-compositing`.