diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 96ed079a25..2655b5a04c 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -4438,7 +4438,8 @@
                 </para>
 
                 <para>
-                    Downloaded archives reside in the Build Directory in
+                    Downloaded archives reside in the 
+                    <link linkend='build-directory'>Build Directory</link> in
                     <filename>/tmp</filename> and are cleared up when they are no longer in use.
                 </para>
 
@@ -4451,7 +4452,7 @@
                     The OpenEmbedded build system generates separate <filename>vmlinux</filename>
                     packages for each kernel it builds.
                     Thus, it should just be a question of making sure a matching package is
-                    installed (e.g. <filename>opkg install kernel-vmlinux</filename>.
+                    installed (e.g. <filename>opkg install kernel-vmlinux</filename>).
                     The files are automatically installed into development and profiling images
                     alongside OProfile.
                     A configuration option exists within the OProfileUI settings page that you can use to
@@ -4463,9 +4464,10 @@
                     is not always necessary to actually have them on the device for OProfile use.
                     All that is needed is a copy of the filesystem with the debug symbols present
                     on the viewer system.
-                    The "<link linkend='platdev-gdb-remotedebug-launch-gdb'>Launching GDB on the Host Computer</link>"
+                    The "<link linkend='platdev-gdb-remotedebug-launch-gdb'>Launch GDB on the Host Computer</link>"
                     section covers how to create such a directory with
-                    the source directory and how to use the OProfileUI Settings dialog to specify the location.
+                    the <link linkend='source-directory'>Source Directory</link>
+                    and how to use the OProfileUI Settings Dialog to specify the location.
                     If you specify the directory, it will be used when the file checksums
                     match those on the system you are profiling.
                 </para>