diff --git a/developer-doc/AddingAMeasure.txt b/developer-doc/AddingAMeasure.txt
index d883b5d1a186cc2d1705b5aa0fdb17635d9a7ded..cb2e6f50797e7e05c3059dc681231aa71d9a2ec7 100644
--- a/developer-doc/AddingAMeasure.txt
+++ b/developer-doc/AddingAMeasure.txt
@@ -99,7 +99,7 @@ It is useful to think carefully about how you can reuse other parts of the code
 how PLMD::OptimalRMSD and PLMD::SimpleRMSD make extensive use of the PLMD::RMSD class.  Similarly notice how the PLMD::OptimalRMSD,
 PLMD::SimpleRMSD and PLMD::DRMSD classes are reused in PLMD::MultiDomainRMSD.
 
-\section docs Adding documentation for your measure
+\section AddingAMeasureDocs Adding documentation for your measure
 
 To test whether you have implemented you new measure correctly you should implement a small Action that calculates the
 distance between the instantaneous positions of the atoms and some read in reference configuration.  The methods
diff --git a/developer-doc/AddingAMultColvar.txt b/developer-doc/AddingAMultColvar.txt
index 73be9f60a40459d057141540659b5091feab1adb..66381e6b3a5156623ef5ec750645520289127fac 100644
--- a/developer-doc/AddingAMultColvar.txt
+++ b/developer-doc/AddingAMultColvar.txt
@@ -39,7 +39,7 @@ through these classes and attempt to understand the code contained within them.
 provides a rather prescriptive description as to how to implement a new multicolvar.  I hope this helps but I am keenly
 aware that any description is bound to be incomplete so if you have questions please do email the user list to ask.
 
-\section docs Creating documentation  
+\section AddingAMultColvarDocs Creating documentation  
 
 The first thing you will have to change is the documentation.  As discussed on the \ref usingDoxygen page
 of this manual the documentation is created using Doxygen.  You are implementing a cv so your PLMEDOC line