Updated fork project info for Rolf and my branches in doc/install.txt.

[hooke.git] / doc / hacking.txt

diff --git a/doc/hacking.txt b/doc/hacking.txt
index b671e0572bda6fb6a5344172350aad1baa225ac0..fb9a7d444ff571d4f5e49b145d54d62937e51b33 100644 (file)
--- a/doc/hacking.txt
+++ b/doc/hacking.txt
@@ -1,11 +1,11 @@
-*************
-Hacking Hooke
-*************
+*******
+Hacking
+*******
 
 .. toctree::
    :maxdepth: 2
 
-   testing.txt
+   testing
 
 Dependencies
 ============
@@ -31,10 +31,9 @@ standard library, we use configparser_ for the config files.
 
 On the testing side, the need to stick to the standard library relaxes
 (developers can install extra packages), so we can use nose_.  See
-the Testing_ section for more information.
+the :doc:`testing` section for more information.
 
 .. _nose: http://somethingaboutorange.com/mrl/projects/nose/0.11.3/
-.. _Testing: testing.txt
 
 
 Architecture
@@ -49,7 +48,7 @@ and a :class:`~hooke.ui.UserInterface` instance to connect the
 :class:`~hooke.engine.CommandEngine` runs in a subprocess, which
 allows command execution to occur in parallel with
 :class:`~hooke.ui.UserInterface` interaction.  The two processes
-communicate via two :class:`~multiprocessing.Queue`\s.
+communicate via two :class:`multiprocessing.Queue`\s.
 
 There are a number of special classes availiable to structure queue
 communications.  See :mod:`~hooke.interaction` and
@@ -111,7 +110,7 @@ Experiments_ tags need a data-holding container to tag, and
 :class:`~hooke.curve.Data` (for example approach and retract curves in
 a :class:`~hooke.experiment.VelocityClamp` experiment would be
 seperate blocks).  :class:`~hooke.curve.Curve`\s also have an
-:attr:`~~hooke.curve.Curve.info` attribute for persistently storing
+:attr:`~hooke.curve.Curve.info` attribute for persistently storing
 arbitrary data.
 
 Playlists