David Brownell <david-b@pacbell.net>:

[fw/openocd] / doc / manual / scripting.txt

diff --git a/doc/manual/scripting.txt b/doc/manual/scripting.txt
index e62cba6df42c76f5b494d08d743e9929c7fe8d07..09b69d38b7ca2fc28878395313b9cbe301501112 100644 (file)
--- a/doc/manual/scripting.txt
+++ b/doc/manual/scripting.txt
@@ -1,6 +1,6 @@
-/** @page scripting OpenOCD Scripting Overview
+/** @page scripting 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,14 +18,14 @@ 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.
 
 - Polymorphic commands for target scripts.
   - there will be added some commands in Tcl that the target
     scripts can replace.
-  - produce <productionfile> <serialnumber>. Default implementation
+  - produce \<productionfile\> \<serialnumber\>. Default implementation
     is to ignore serial number and write a raw binary file
     to beginning of first flash. Target script can dictate
     file format and structure of serialnumber. Tcl allows
@@ -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.