Add section identifiers to developer scripting introduction.

git-svn-id: svn://svn.berlios.de/openocd/trunk@1898 b42882b7-edfa-0310-969c-e2dbd0fdcd60

diff --git a/doc/manual/scripting.txt b/doc/manual/scripting.txt
index e62cba6df42c76f5b494d08d743e9929c7fe8d07..a4629bac462dd808f210c266e46f5439789f9e6b 100644 (file)
--- a/doc/manual/scripting.txt
+++ b/doc/manual/scripting.txt
@@ -1,6 +1,6 @@
 /** @page scripting OpenOCD Scripting Overview
 
-@section What scripting will not do
+@section scriptingisnt What scripting will not do
 
 The scripting support is intended for developers of OpenOCD.
 It is not the intention that normal OpenOCD users will
@@ -18,7 +18,7 @@ Jim Tcl was chosen as it was easy to integrate, works
 great in an embedded environment and Øyvind Harboe
 had experience with it.
 
-@section Uses of scripting
+@section scriptinguses Uses of scripting
 
 Default implementation of procedures in tcl/procedures.tcl.
 
@@ -52,7 +52,7 @@ Default implementation of procedures in tcl/procedures.tcl.
   be simpler.
   
   
-@section External scripting
+@section scriptingexternal External scripting
 
 The embedded Jim Tcl interpreter in OpenOCD is very limited
 compared to any full scale PC hosted scripting language.