diff --git a/docs/advanced.rst b/docs/advanced.rst
index 5f17cd3ed4b3907b8dd5c0b350af10d193af45ad..c5eebbd4eebe14f3bcd67abb8c59a5b8f1909f8b 100644
--- a/docs/advanced.rst
+++ b/docs/advanced.rst
@@ -150,7 +150,8 @@ Fireworks and workflows are stored on the LaunchPad during their full life cycle
 *RUNNING* state until they reach the *COMPLETED* state. Completed workflows
 hold not only the input parameters and the results but also provenence metadata
 that help the further use of the workflows. The life cycle of a workflow continues
-when it is extended using for example the *append_wflow* command (see exercise 4).
+when it is extended using for example the *append_wflow* command (see *Exercise 4: 
+Extending a workflow*).
 
 Another further use of the stored workflows is to collect, reorganize, analyse
 and visualize their stored data programatically. To show how data can be extracted
@@ -257,12 +258,14 @@ Building up a workflow as you go
 --------------------------------
 
 Very often in a research project one does not know the workflow final structure
-at the beginning. In FireWorks one can extend exiting workflows on the LaunchPad
+at the beginning. In FireWorks one can extend existing workflows on the LaunchPad
 during their whole lifetime, i.e. it does not matter whether the workflow has
 been just added, is running or completed. A simple example for extending a
-workflow is given in __ Exercise 4: Extending a workflow __. Here, the
-example shows how a workflow with a single Firework performing a structure
-relaxation can be exteded with a Firework performing normal mode analysis::
+workflow is given in *Exercise 4: Extending a workflow*.
+
+Here, the example shows how a workflow with a single Firework performing a
+structure relaxation can be exteded with a Firework performing normal mode
+analysis::
 
   cd inputs
   lpad add -c water-turbomole_relax.yaml