Thomas Kindler <mail+ocd@t-kindler.de> typos

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

1 files changed, 340 insertions, 342 deletions

diff --git a/doc/openocd.texi b/doc/openocd.texi
index 66f8b128..cd32a69e 100644
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -70,11 +70,11 @@ This manual documents edition @value{EDITION} of the Open On-Chip Debugger
 * Sample Scripts::                   Sample Target Scripts
 * TFTP::                             TFTP
 * GDB and OpenOCD::                  Using GDB and OpenOCD
-* TCL scripting API::                Tcl scripting API
+* Tcl scripting API::                Tcl scripting API
 * Upgrading::                        Deprecated/Removed Commands
 * Target library::                   Target library
 * FAQ::                              Frequently Asked Questions
-* TCL Crash Course::                 TCL Crash Course
+* Tcl Crash Course::                 Tcl Crash Course
 * License::                          GNU Free Documentation License
 @comment DO NOT use the plain word ``Index'', reason: CYGWIN filename
 @comment case issue with ``Index.html'' and ``index.html''
@@ -92,14 +92,14 @@ in-system programming and boundary-scan testing for embedded target
 devices.
 
 @b{JTAG:} OpenOCD uses a ``hardware interface dongle'' to communicate
-with the JTAG (IEEE 1149.1) complient taps on your target board.
+with the JTAG (IEEE 1149.1) compliant taps on your target board.
 
-@b{Dongles:} OpenOCD currently many types of hardware dongles: USB
+@b{Dongles:} OpenOCD currently supports many types of hardware dongles: USB
 Based, Parallel Port Based, and other standalone boxes that run
 OpenOCD internally. See the section titled: @xref{JTAG Hardware Dongles}.
 
-@b{GDB Debug:} It allows ARM7 (ARM7TDMI and ARM720t), ARM9 (ARM920t,
-ARM922t, ARM926ej--s, ARM966e--s), XScale (PXA25x, IXP42x) and
+@b{GDB Debug:} It allows ARM7 (ARM7TDMI and ARM720t), ARM9 (ARM920T,
+ARM922T, ARM926EJ--S, ARM966E--S), XScale (PXA25x, IXP42x) and
 Cortex-M3 (Luminary Stellaris LM3 and ST STM32) based cores to be
 debugged via the GDB Protocol.
 
@@ -139,9 +139,9 @@ If you are a @b{PACKAGER} of OpenOCD if you
 
 @enumerate
 @item @b{Sell dongles} and include pre-built binaries
-@item @b{Supply tools} ie: A complete development solution
+@item @b{Supply tools} i.e.: A complete development solution
 @item @b{Supply IDEs} like Eclipse, or RHIDE, etc.
-@item @b{Build packages} ie: RPM files, or DEB files for a Linux Distro
+@item @b{Build packages} i.e.: RPM files, or DEB files for a Linux Distro
 @end enumerate
 
 As a @b{PACKAGER} - you are at the top of the food chain. You solve
@@ -151,8 +151,8 @@ please let us know. That said, would also like you to follow a few
 suggestions:
 
 @enumerate
-@item @b{Always build with Printer Ports Enabled}
-@item @b{Try where possible to use LIBFTDI + LIBUSB} You cover more bases
+@item @b{Always build with printer ports enabled}.
+@item @b{Try to use LIBFTDI + LIBUSB where possible}. You cover more bases.
 @end enumerate
 
 It is your decision..
@@ -166,7 +166,7 @@ It is your decision..
 @item @b{MORE} platforms are supported
 @item @b{MORE} complete solution
 @end itemize
-@item @b{Why not LIBFTDI + LIBUSB} (ie: ftd2xx instead)
+@item @b{Why not LIBFTDI + LIBUSB} (i.e.: ftd2xx instead)
 @itemize @bullet
 @item @b{LESS} Some say it is slower.
 @item @b{LESS} complex to distribute (external dependencies)
@@ -208,7 +208,7 @@ a FTDI FT2232 based interface:
 homepage (@uref{www.amontec.com}), as the JTAGkey uses a non-standard VID/PID. 
 @end itemize
 
-libftdi is supported under windows. Do not use versions earlier then 0.14.
+libftdi is supported under Windows. Do not use versions earlier then 0.14.
 
 In general, the D2XX driver provides superior performance (several times as fast),
 but has the draw-back of being binary-only - though that isn't that bad, as it isn't
@@ -282,7 +282,7 @@ There are 2 methods of using the FTD2232, either (1) using the
 FTDICHIP.COM closed source driver, or (2) the open (and free) driver
 libftdi. Some claim the (closed) FTDICHIP.COM solution is faster.
 
-The FTDICHIP drivers come as either a (win32) ZIP file, or a (linux)
+The FTDICHIP drivers come as either a (win32) ZIP file, or a (Linux)
 TAR.GZ file. You must unpack them ``some where'' convient. As of this
 writing (12/26/2008) FTDICHIP does not supply means to install these
 files ``in an appropriate place'' As a result, there are two
@@ -315,7 +315,7 @@ Linux FTDICHIP solution
 
 Cygwin/Linux LIBFTDI solution
     Assumes: 
-    1a) For Windows: The windows port of LIBUSB is in place.
+    1a) For Windows: The Windows port of LIBUSB is in place.
     1b) For Linux: libusb has been built and is inplace.
 
     2) And libftdi has been built and installed
@@ -344,11 +344,11 @@ openocd @option{-v} is executed.
 @node JTAG Hardware Dongles
 @chapter JTAG Hardware Dongles
 @cindex dongles
-@cindex ftdi
+@cindex FTDI
 @cindex wiggler
 @cindex zy1000
 @cindex printer port
-@cindex usb adapter
+@cindex USB adapter
 @cindex rtck
 
 Defined: @b{dongle}: A small device that plugins into a computer and serves as
@@ -378,7 +378,7 @@ dongle, but a standalone box.
 
 @section USB FT2232 Based
 
-There are many USB jtag dongles on the market, many of them are based
+There are many USB JTAG dongles on the market, many of them are based
 on a chip from ``Future Technology Devices International'' (FTDI)
 known as the FTDI FT2232.
 
@@ -505,7 +505,7 @@ Title: FlashLINK JTAG programing cable for PSD and uPSD
 @itemize @bullet
 
 @item @b{ep93xx}
-@* An EP93xx based linux machine using the GPIO pins directly.
+@* An EP93xx based Linux machine using the GPIO pins directly.
 
 @item @b{at91rm9200}
 @* Like the EP93xx - but an ATMEL AT91RM9200 based solution using the GPIO pins on the chip.
@@ -589,8 +589,8 @@ There are 4 basic ways of ``configurating'' OpenOCD to run, they are:
 
 @section Small configuration file method
 
-This is the prefered method, it is simple and is works well for many
-people.  The developers of OpenOCD would encourage you to use this
+This is the preferred method. It is simple and works well for many
+people. The developers of OpenOCD would encourage you to use this
 method. If you create a new configuration please email new
 configurations to the development list.
 
@@ -663,10 +663,10 @@ standard distribution configuration files as needed.
 Some key things you should look at and understand are:
 
 @enumerate
-@item The RESET configuration of your debug environment as a hole
+@item The RESET configuration of your debug environment as a whole
 @item Is there a ``work area'' that OpenOCD can use?
 @* For ARM - work areas mean up to 10x faster downloads.
-@item For MMU/MPU based ARM chips (ie: ARM9 and later) will that work area still be available?
+@item For MMU/MPU based ARM chips (i.e.: ARM9 and later) will that work area still be available?
 @item For complex targets (multiple chips) the JTAG SPEED becomes an issue.
 @end enumerate
 
@@ -679,26 +679,25 @@ This section/chapter is aimed at developers and integrators of
 OpenOCD. These are guidelines for creating new boards and new target
 configurations as of 28/Nov/2008.
 
-However, you the user of OpenOCD should be some what familiar with
+However, you, the user of OpenOCD, should be somewhat familiar with
 this section as it should help explain some of the internals of what
 you might be looking at.
 
-The user should find under @t{$(INSTALLDIR)/lib/openocd} the
-following directories:
+The user should find the following directories under @t{$(INSTALLDIR)/lib/openocd} :
 
 @itemize @bullet
 @item @b{interface}
-@*Think JTAG Dongle. Files that configure the jtag dongle go here.
+@*Think JTAG Dongle. Files that configure the JTAG dongle go here.
 @item @b{board}
-@* Thing Circuit Board, PWA, PCB, they go by many names.  Board files
+@* Think Circuit Board, PWA, PCB, they go by many names.  Board files
 contain initialization items that are specific to a board - for
 example: The SDRAM initialization sequence for the board, or the type
 of external flash and what address it is found at. Any initialization
-sequence to enable that external flash or sdram should be found in the
-board file. Boards may also contain multiple targets, ie: Two cpus, or
+sequence to enable that external flash or SDRAM should be found in the
+board file. Boards may also contain multiple targets, i.e.: Two CPUs, or
 a CPU and an FPGA or CPLD.
 @item @b{target}
-@* Think CHIP. The ``target'' directory represents a jtag tap (or
+@* Think chip. The ``target'' directory represents a JTAG tap (or
 chip) OpenOCD should control, not a board. Two common types of targets
 are ARM chips and FPGA or CPLD chips.
 @end itemize
@@ -722,7 +721,7 @@ A preconfigured interface file should exist for every interface in use
 today, that said, perhaps some interfaces have only been used by the
 sole developer who created it.
 
-@b{FIXME/NOTE:} We need to add support for a variable like TCL variable
+@b{FIXME/NOTE:} We need to add support for a variable like Tcl variable
 tcl_platform(platform), it should be called jim_platform (because it
 is jim, not real tcl) and it should contain 1 of 3 words: ``linux'',
 ``cygwin'' or ``mingw''
@@ -745,12 +744,12 @@ Or:
 The board file should contain one or more @t{source [find
 target/FOO.cfg]} statements along with any board specific things.
 
-In summery the board files should contain (if present)
+In summary the board files should contain (if present)
 
 @enumerate
-@item External flash configuration (ie: the flash on CS0)
-@item SDRAM configuration (size, speed, etc)
-@item Board specific IO configuration (ie: GPIO pins might disable a 2nd flash)
+@item External flash configuration (i.e.: the flash on CS0)
+@item SDRAM configuration (size, speed, etc.
+@item Board specific IO configuration (i.e.: GPIO pins might disable a 2nd flash)
 @item Multiple TARGET source statements
 @item All things that are not ``inside a chip''
 @item Things inside a chip go in a 'target' file
@@ -766,7 +765,7 @@ Or:
   openocd -f target/FOOBAR.cfg
 @end example
 
-In summery the target files should contain
+In summary the target files should contain
 
 @enumerate 
 @item Set Defaults
@@ -793,8 +792,8 @@ tap identifier dotted name.
 @* When OpenOCD examines the JTAG chain, it will attempt to identify
 every chip. If the @t{-expected-id} is nonzero, OpenOCD attempts
 to verify the tap id number verses configuration file and may issue an
-error or warning like this. The hope is this will help pin point
-problem OpenOCD configurations.
+error or warning like this. The hope is that this will help to pinpoint
+problems in OpenOCD configurations.
 
 @example
 Info:   JTAG tap: sam7x256.cpu tap/device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)
@@ -830,12 +829,12 @@ The user (or board file) should reasonably be able to:
 
 @end itemize
 
-@subsection TCL Variables Guide Line
+@subsection Tcl Variables Guide Line
 The Full Tcl/Tk language supports ``namespaces'' - JIM-Tcl does not.
 
 Thus the rule we follow in OpenOCD is this: Variables that begin with
-a leading underscore are temporal in nature, and can be modified and
-used at will within a ?TARGET? configuration file
+a leading underscore are temporary in nature, and can be modified and
+used at will within a ?TARGET? configuration file.
 
 @b{EXAMPLE:} The user should be able to do this:
 
@@ -849,14 +848,14 @@ used at will within a ?TARGET? configuration file
    source [find target/pxa270.cfg]
    # variable: _TARGETNAME = network.cpu
    # other commands can refer to the "network.cpu" tap.
-   $_TARGETNAME configure .... params for this cpu..
+   $_TARGETNAME configure .... params for this CPU..
    
    set ENDIAN little
    set CHIPNAME video
    source [find target/pxa270.cfg]
    # variable: _TARGETNAME = video.cpu
    # other commands can refer to the "video.cpu" tap.
-   $_TARGETNAME configure .... params for this cpu..
+   $_TARGETNAME configure .... params for this CPU..
    
    unset ENDIAN
    set CHIPNAME xilinx
@@ -896,7 +895,7 @@ if @{ [info exists CPUTAPID ] @} @{
 @end example
 
 @subsection Creating Taps
-After the ``defaults'' are choosen, [see above], the taps are created.
+After the ``defaults'' are choosen [see above] the taps are created.
 
 @b{SIMPLE example:} such as an Atmel AT91SAM7X256
 
@@ -943,7 +942,7 @@ set _TARGETNAME [format "%s.cpu" $_CHIPNAME]
 
 @b{Tap Naming Convention}
 
-See the command ``jtag newtap'' for detail, but in breif the names you should use are:
+See the command ``jtag newtap'' for detail, but in brief the names you should use are:
 
 @itemize @bullet
 @item @b{tap}
@@ -963,20 +962,20 @@ managed. If these are @b{CHIP SPECIFIC} they go here, if they are
 @subsection Work Areas
 
 Work areas are small RAM areas used by OpenOCD to speed up downloads,
-and to download small snippits of code to program flash chips.  
+and to download small snippets of code to program flash chips.  
 
-If the chip includes an form of ``on-chip-ram'' - and many do - define
+If the chip includes a form of ``on-chip-ram'' - and many do - define
 a reasonable work area and use the ``backup'' option.
 
 @b{PROBLEMS:} On more complex chips, this ``work area'' may become
-inaccessable if/when the application code enables or disables the MMU.
+inaccessible if/when the application code enables or disables the MMU.
 
 @subsection ARM Core Specific Hacks
 
-If the chip has a DCC, enable it. If the chip is an arm9 with some
-special high speed download - enable it.
+If the chip has a DCC, enable it. If the chip is an ARM9 with some
+special high speed download features - enable it.
 
-If the chip has an ARM ``vector catch'' feature - by defeault enable
+If the chip has an ARM ``vector catch'' feature - by default enable
 it for Undefined Instructions, Data Abort, and Prefetch Abort, if the
 user is really writing a handler for those situations - they can
 easily disable it.  Experiance has shown the ``vector catch'' is
@@ -1010,31 +1009,31 @@ OpenOCD includes a small ``TCL Interpreter'' known as JIM-TCL. You can
 learn more about JIM here: @url{http://jim.berlios.de}
 
 @itemize @bullet
-@item @b{JIM vrs TCL}
+@item @b{JIM vs. Tcl}
 @* JIM-TCL is a stripped down version of the well known Tcl language,
 which can be found here: @url{http://www.tcl.tk}. JIM-Tcl has far
 fewer features. JIM-Tcl is a single .C file and a single .H file and
-impliments the basic TCL command set along. In contrast: Tcl 8.6 is a
-4.2MEG zip file containing 1540 files.
+impliments the basic Tcl command set along. In contrast: Tcl 8.6 is a
+4.2 MB .zip file containing 1540 files.
 
 @item @b{Missing Features}
-@* Our practice has been: Add/clone the Real TCL feature if/when
+@* Our practice has been: Add/clone the real Tcl feature if/when
 needed. We welcome JIM Tcl improvements, not bloat.
 
 @item @b{Scripts}
 @* OpenOCD configuration scripts are JIM Tcl Scripts. OpenOCD's
-command interpretor today (28/nov/2008) is a mixture of (newer)
-JIM-Tcl commands, and (older) the orginal command interpretor.
+command interpreter today (28/nov/2008) is a mixture of (newer)
+JIM-Tcl commands, and (older) the orginal command interpreter.
 
 @item @b{Commands}
 @* At the OpenOCD telnet command line (or via the GDB mon command) one
 can type a Tcl for() loop, set variables, etc.
 
 @item @b{Historical Note}
-@* JIM-Tcl was introduced to OpenOCD in Spring 2008.
+@* JIM-Tcl was introduced to OpenOCD in spring 2008.
 
-@item @b{Need a Crash Course In TCL?}
-@* See: @xref{TCL Crash Course}.
+@item @b{Need a Crash Course In Tcl?}
+@* See: @xref{Tcl Crash Course}.
 @end itemize
 
 
@@ -1071,9 +1070,9 @@ the memory read/write commands.
 @item @b{tcl_port} <@var{number}>
 @cindex tcl_port
 @*Intended as a machine interface. Port on which to listen for
-incoming TCL syntax. This port is intended as a simplified RPC
+incoming Tcl syntax. This port is intended as a simplified RPC
 connection that can be used by clients to issue commands and get the
-output from the TCL engine.
+output from the Tcl engine.
 
 @item @b{gdb_port} <@var{number}>
 @cindex gdb_port
@@ -1089,7 +1088,7 @@ first target will be gdb_port, the second target will listen on gdb_port + 1, an
 @*Force breakpoint type for gdb 'break' commands.
 The raison d'etre for this option is to support GDB GUI's without 
 a hard/soft breakpoint concept where the default OpenOCD and
-GDB behaviour is not sufficient. Note that GDB will use hardware
+GDB behavior is not sufficient. Note that GDB will use hardware
 breakpoints if the memory map has been set up for flash regions.
 
 This option replaces older arm7_9 target commands that addressed
@@ -1097,16 +1096,16 @@ the same issue.
 
 @item @b{gdb_detach} <@var{resume|reset|halt|nothing}>
 @cindex gdb_detach
-@*Configures what OpenOCD will do when gdb detaches from the daemon.
-Default behaviour is <@var{resume}>
+@*Configures what OpenOCD will do when GDB detaches from the daemon.
+Default behavior is <@var{resume}>
 
 @item @b{gdb_memory_map} <@var{enable|disable}>
 @cindex gdb_memory_map
-@*Set to <@var{enable}> to cause OpenOCD to send the memory configuration to gdb when
-requested. gdb will then know when to set hardware breakpoints, and program flash
-using the gdb load command. @option{gdb_flash_program enable} will also need enabling
+@*Set to <@var{enable}> to cause OpenOCD to send the memory configuration to GDB when
+requested. GDB will then know when to set hardware breakpoints, and program flash
+using the GDB load command. @option{gdb_flash_program enable} must also be enabled 
 for flash programming to work.
-Default behaviour is <@var{enable}>
+Default behavior is <@var{enable}>
 @xref{gdb_flash_program}.
 
 @item @b{gdb_flash_program} <@var{enable|disable}>
@@ -1114,7 +1113,7 @@ Default behaviour is <@var{enable}>
 @anchor{gdb_flash_program}
 @*Set to <@var{enable}> to cause OpenOCD to program the flash memory when a
 vFlash packet is received.
-Default behaviour is <@var{enable}>
+Default behavior is <@var{enable}>
 @comment END GDB Items
 @end itemize
 
@@ -1153,10 +1152,10 @@ jtag_speed 0
 @verbatim
 interface arm-jtag-ew
 @end verbatim
-@section Interface Conmmand
+@section Interface Command
 
-The interface command tells OpenOCD what type of jtag dongle you are
-using. Depending upon the type of dongle, you may need to have one or
+The interface command tells OpenOCD what type of JTAG dongle you are
+using. Depending on the type of dongle, you may need to have one or
 more additional commands.
 
 @itemize @bullet
@@ -1194,16 +1193,16 @@ libusb.
 @* Gateworks GW16012 JTAG programmer.
 
 @item @b{jlink}
-@* Segger jlink usb adapter
+@* Segger jlink USB adapter
 
 @item @b{rlink}
-@* Raisonance RLink usb adapter
+@* Raisonance RLink USB adapter
 
 @item @b{vsllink}
 @* vsllink is part of Versaloon which is a versatile USB programmer.
 
 @item @b{arm-jtag-ew}
-@* Olimex ARM-JTAG-EW usb adapter
+@* Olimex ARM-JTAG-EW USB adapter
 @comment - End parameters
 @end itemize
 @comment - End Interface
@@ -1283,7 +1282,7 @@ interface on exiting OpenOCD
 specified, the FTDI default value is used. This setting is only valid
 if compiled with FTD2XX support.
 
-@b{TODO:} Confirm the following: On windows the name needs to end with
+@b{TODO:} Confirm the following: On Windows the name needs to end with
 a ``space A''? Or not? It has to do with the FTD2xx driver. When must
 this be added and when must it not be added? Why can't the code in the
 interface or in OpenOCD automatically add this if needed? -- Duane.
@@ -1300,7 +1299,7 @@ signals. Valid layouts are
 @item @b{usbjtag}
 "USBJTAG-1" layout described in the original OpenOCD diploma thesis
 @item @b{jtagkey}
-Amontec JTAGkey and JTAGkey-tiny
+Amontec JTAGkey and JTAGkey-Tiny
 @item @b{signalyzer}
 Signalyzer
 @item @b{olimex-jtag}
@@ -1326,17 +1325,17 @@ Axiom AXM-0432
 
 @item @b{ft2232_vid_pid} <@var{vid}> <@var{pid}>
 @*The vendor ID and product ID of the FTDI FT2232 device. If not specified, the FTDI
-default values are used. Multiple <@var{vid}>, <@var{pid}> pairs may be given, eg.
+default values are used. Multiple <@var{vid}>, <@var{pid}> pairs may be given, e.g.
 @example
 ft2232_vid_pid 0x0403 0xcff8 0x15ba 0x0003
 @end example
 @item @b{ft2232_latency} <@var{ms}>
-@*On some systems using ft2232 based JTAG interfaces the FT_Read function call in
+@*On some systems using FT2232 based JTAG interfaces the FT_Read function call in
 ft2232_read() fails to return the expected number of bytes. This can be caused by
 USB communication delays and has proved hard to reproduce and debug. Setting the
-FT2232 latency timer to a larger value increases delays for short USB packages but it
+FT2232 latency timer to a larger value increases delays for short USB packets but it
 also reduces the risk of timeouts before receiving the expected number of bytes.
-The OpenOCD default value is 2 and for some systems a value of 10 has proved useful. 
+The OpenOCD default value is 2 and for some systems a value of 10 has proved useful.
 @end itemize
 
 @subsection ep93xx options
@@ -1349,9 +1348,9 @@ Currently, there are no options available for the ep93xx interface.
 @cindex jtag_khz
 
 It is debatable if this command belongs here - or in a board
-configuration file. In fact, in some situations the jtag speed is
-changed during the target initialization process (ie: (1) slow at
-reset, (2) program the cpu clocks, (3) run fast)
+configuration file. In fact, in some situations the JTAG speed is
+changed during the target initialization process (i.e.: (1) slow at
+reset, (2) program the CPU clocks, (3) run fast)
 
 Speed 0 (khz) selects RTCK method. A non-zero speed is in KHZ. Hence: 3000 is 3mhz. 
 
@@ -1359,11 +1358,11 @@ Not all interfaces support ``rtck''. If the interface device can not
 support the rate asked for, or can not translate from kHz to
 jtag_speed, then an error is returned.
 
-Make sure the jtag clock is no more than @math{1/6th × CPU-Clock}. This is
+Make sure the JTAG clock is no more than @math{1/6th × CPU-Clock}. This is
 especially true for synthesized cores (-S). Also see RTCK.
 
 @b{NOTE: Script writers} If the target chip requires/uses RTCK -
-please use the command: 'jtag_rclk FREQ'. This TCL proc (in
+please use the command: 'jtag_rclk FREQ'. This Tcl proc (in
 startup.tcl) attempts to enable RTCK, if that fails it falls back to
 the specified frequency.
 
@@ -1372,7 +1371,7 @@ the specified frequency.
     jtag_rclk 3000
 @end example
 
-@item @b{DEPRICATED} @b{jtag_speed} - please use jtag_khz above.
+@item @b{DEPRECATED} @b{jtag_speed} - please use jtag_khz above.
 @cindex jtag_speed
 @*Limit the maximum speed of the JTAG interface. Usually, a value of zero means maximum
 speed. The actual effect of this option depends on the JTAG interface used. 
@@ -1416,7 +1415,7 @@ deasserted.
 
 @section reset_config
 
-@b{Note:} To maintainer types and integrators. Where exactly the
+@b{Note:} To maintainer and integrators: Where exactly the
 ``reset configuration'' goes is a good question. It touches several
 things at once. In the end, if you have a board file - the board file
 should define it and assume 100% that the DONGLE supports
@@ -1426,17 +1425,17 @@ chip. @i{Grr.... nothing is every pretty.}
 
 @* @b{Problems:} 
 @enumerate
-@item Every JTAG Dongle is slightly different, some dongles impliment reset differently.
+@item Every JTAG Dongle is slightly different, some dongles implement reset differently.
 @item Every board is also slightly different; some boards tie TRST and SRST together.
 @item Every chip is slightly different; some chips internally tie the two signals together.
-@item Some may not impliment all of the signals the same way.
+@item Some may not implement all of the signals the same way.
 @item Some signals might be push-pull, others open-drain/collector.
 @end enumerate
 @b{Best Case:} OpenOCD can hold the SRST (push-button-reset), then
 reset the TAP via TRST and send commands through the JTAG tap to halt
 the CPU at the reset vector before the 1st instruction is executed,
 and finally release the SRST signal.
-@*Depending upon your board vendor, your chip vendor, etc, these
+@*Depending on your board vendor, chip vendor, etc., these
 signals may have slightly different names. 
 
 OpenOCD defines these signals in these terms:
@@ -1459,12 +1458,12 @@ be @option{none}, @option{trst_only}, @option{srst_only} or
 
 [@var{combination}] is an optional value specifying broken reset
 signal implementations.  @option{srst_pulls_trst} states that the
-testlogic is reset together with the reset of the system (e.g. Philips
+test logic is reset together with the reset of the system (e.g. Philips
 LPC2000, "broken" board layout), @option{trst_pulls_srst} says that
 the system is reset together with the test logic (only hypothetical, I
 haven't seen hardware with such a bug, and can be worked around).
-@option{combined} imples both @option{srst_pulls_trst} and
-@option{trst_pulls_srst}.  The default behaviour if no option given is
+@option{combined} implies both @option{srst_pulls_trst} and
+@option{trst_pulls_srst}.  The default behavior if no option given is
 @option{separate}.
 
 The [@var{trst_type}] and [@var{srst_type}] parameters allow the
@@ -1498,7 +1497,7 @@ Tap Uses:
 @itemize @bullet
 @item @b{Debug Target} A tap can be used by a GDB debug target
 @item @b{Flash Programing} Some chips program the flash via JTAG
-@item @b{Boundry Scan} Some chips support boundry scan.
+@item @b{Boundry Scan} Some chips support boundary scan.
 @end itemize
 
 
@@ -1529,7 +1528,7 @@ them off when doing comparisons.  In general, this should just be all ones for
 the size of the IR.
 @comment END REQUIRED
 @end itemize
-An example of a FOOBAR Tap
+An example of a FOOBAR tap
 @example
 jtag newtap foobar tap -irlen 7 -ircapture 0x42 -irmask 0x55
 @end example
@@ -1542,12 +1541,12 @@ bits long, during Capture-IR 0x42 is loaded into the IR, and bits
 @itemize @bullet
 @item @b{-expected-id NUMBER}
 @* By default it is zero. If non-zero represents the
-expected tap ID used when the Jtag Chain is examined. See below.
+expected tap ID used when the JTAG chain is examined. See below.
 @item @b{-disable}
 @item @b{-enable}
 @* By default not specified the tap is enabled. Some chips have a
-jtag route controller (JRC) that is used to enable and/or disable
-specific jtag taps. You can later enable or disable any JTAG tap via
+JTAG route controller (JRC) that is used to enable and/or disable
+specific JTAG taps. You can later enable or disable any JTAG tap via
 the command @b{jtag tapenable DOTTED.NAME} or @b{jtag tapdisable 
 DOTTED.NAME}
 @comment END Optional
@@ -1562,22 +1561,22 @@ DOTTED.NAME}
 @* newtap is a sub command of the ``jtag'' command
 @item @b{Big Picture Background}
 @*GDB Talks to OpenOCD using the GDB protocol via
-tcpip. OpenOCD then uses the JTAG interface (the dongle) to
+TCP/IP. OpenOCD then uses the JTAG interface (the dongle) to
 control the JTAG chain on your board. Your board has one or more chips
 in a @i{daisy chain configuration}. Each chip may have one or more
-jtag taps. GDB ends up talking via OpenOCD to one of the taps.
+JTAG taps. GDB ends up talking via OpenOCD to one of the taps.
 @item @b{NAME Rules}
 @*Names follow ``C'' symbol name rules (start with alpha ...)
 @item @b{TAPNAME - Conventions}
 @itemize @bullet
 @item @b{tap} - should be used only FPGA or CPLD like devices with a single tap.
-@item @b{cpu} - the main cpu of the chip, alternatively @b{foo.arm} and @b{foo.dsp}
+@item @b{cpu} - the main CPU of the chip, alternatively @b{foo.arm} and @b{foo.dsp}
 @item @b{flash} - if the chip has a flash tap, example: str912.flash
 @item @b{bs} - for boundary scan if this is a seperate tap.
-@item @b{jrc} - for jtag route controller (example: OMAP3530 found on Beagleboards)
+@item @b{jrc} - for JTAG route controller (example: OMAP3530 found on Beagleboards)
 @item @b{unknownN} - where N is a number if you have no idea what the tap is for
 @item @b{Other names} - Freescale IMX31 has a SDMA (smart dma) with a JTAG tap, that tap should be called the ``sdma'' tap.
-@item @b{When in doubt} - use the chip makers name in their data sheet.
+@item @b{When in doubt} - use the chip maker's name in their data sheet.
 @end itemize
 @item @b{DOTTED.NAME}
 @* @b{CHIPNAME}.@b{TAPNAME} creates the tap name, aka: the
@@ -1591,12 +1590,12 @@ important.
 @item @b{Multi Tap Example}
 @* This example is based on the ST Microsystems STR912. See the ST
 document titled: @b{STR91xFAxxx, Section 3.15 Jtag Interface, Page:
-28/102, Figure 3: Jtag chaining inside the STR91xFA}.
+28/102, Figure 3: JTAG chaining inside the STR91xFA}.
 
 @url{http://eu.st.com/stonline/products/literature/ds/13495.pdf}
 @*@b{checked: 28/nov/2008}
 
-The diagram shows the TDO pin connects to the flash tap, flash TDI
+The diagram shows that the TDO pin connects to the flash tap, flash TDI
 connects to the CPU debug tap, CPU TDI connects to the boundary scan
 tap which then connects to the TDI pin.
 
@@ -1631,7 +1630,7 @@ have the taps created in the proper order.
 @* @b{Removed: 28/nov/2008} This command has been removed and replaced
 by the ``jtag newtap'' command. The documentation remains here so that
 one can easily convert the old syntax to the new syntax. About the old
-syntax: The old syntax is positional, ie: The 3rd parameter is the
+syntax: The old syntax is positional, i.e.: The 3rd parameter is the
 ``irmask''. The new syntax requires named prefixes, and supports
 additional options, for example ``-expected-id 0x3f0f0f0f''. Please refer to the
 @b{jtag newtap} command for details.
@@ -1657,20 +1656,20 @@ when querying the state of the JTAG taps.
 @cindex JRC
 @cindex route controller
 
-These commands are used when your target has a JTAG Route controller
-that effectively adds or removes a tap from the jtag chain in a
+These commands are used when your target has a JTAG route controller
+that effectively adds or removes a tap from the JTAG chain in a
 non-standard way.
 
 The ``standard way'' to remove a tap would be to place the tap in
 bypass mode. But with the advent of modern chips, this is not always a
 good solution. Some taps operate slowly, others operate fast, and
-there are other JTAG clock syncronization problems one must face. To
-solve that problem, the JTAG Route controller was introduced. Rather
-then ``bypass'' the tap, the tap is completely removed from the
+there are other JTAG clock synchronization problems one must face. To
+solve that problem, the JTAG route controller was introduced. Rather
+than ``bypass'' the tap, the tap is completely removed from the
 circuit and skipped.
 
 
-From OpenOCD's view point, a JTAG TAP is in one of 3 states:
+From OpenOCD's point of view, a JTAG tap is in one of 3 states:
 
 @itemize @bullet
 @item @b{Enabled - Not In ByPass} and has a variable bit length
@@ -1685,15 +1684,15 @@ The IEEE JTAG definition has no concept of a ``disabled'' tap.
 
 This command returns 1 if the named tap is currently enabled, 0 if not.
 This command exists so that scripts that manipulate a JRC (like the
-Omap3530 has) can determine if OpenOCD thinks a tap is presently
-enabled, or disabled.
+OMAP3530 has) can determine if OpenOCD thinks a tap is presently
+enabled or disabled.
 
 @page
 @node Target Configuration
 @chapter Target Configuration
 
-This chapter discusses how to create a GDB Debug Target.  Before
-creating a ``target'' a JTAG Tap DOTTED.NAME must exist first.
+This chapter discusses how to create a GDB debug target.  Before
+creating a ``target'' a JTAG tap DOTTED.NAME must exist first.
 
 @section targets [NAME]
 @b{Note:} This command name is PLURAL - not singular.  
@@ -1701,8 +1700,8 @@ creating a ``target'' a JTAG Tap DOTTED.NAME must exist first.
 With NO parameter, this plural @b{targets} command lists all known
 targets in a human friendly form.
 
-With a parameter, this pural @b{targets} command sets the current
-target to the given name. (ie: If there are multiple debug targets)
+With a parameter, this plural @b{targets} command sets the current
+target to the given name. (i.e.: If there are multiple debug targets)
 
 Example:
 @verbatim
@@ -1722,7 +1721,7 @@ see below for details.
 The TARGET command accepts these sub-commands:
 @itemize @bullet
 @item @b{create} .. parameters ..
-@* creates a new target, See below for details.
+@* creates a new target, see below for details.
 @item @b{types}
 @* Lists all supported target types (perhaps some are not yet in this document).
 @item @b{names}
@@ -1768,8 +1767,8 @@ commands with a specific target name and effect only that target.
 
 @b{Model:} The Tcl/Tk language has the concept of object commands. A
 good example is a on screen button, once a button is created a button
-has a name (a path in TK terms) and that name is useable as a 1st
-class command. For example in TK, one can create a button and later
+has a name (a path in Tk terms) and that name is useable as a 1st
+class command. For example in Tk, one can create a button and later
 configure it like this:
 
 @example
@@ -1784,13 +1783,13 @@ configure it like this:
 @end example
     
 In OpenOCD's terms, the ``target'' is an object just like a Tcl/Tk
-button. Commands avaialble as a ``target object'' are:
+button. Commands available as a ``target object'' are:
 
 @comment START targetobj commands.
 @itemize @bullet
 @item @b{configure} - configure the target; see Target Config/Cget Options below
 @item @b{cget} - query the target configuration; see Target Config/Cget Options below
-@item @b{curstate} - current target state (running, halt, etc)
+@item @b{curstate} - current target state (running, halt, etc.
 @item @b{eventlist}
 @* Intended for a human to see/read the currently configure target events.
 @item @b{Various Memory Commands} See the ``mww'' command elsewhere.
@@ -1845,7 +1844,7 @@ To specify an event action, either during target creation, or later
 via ``$_TARGETNAME configure'' see this example.
 
 Syntactially, the option is: ``-event NAME BODY'' where NAME is a
-target event name, and BODY is a tcl procedure or string of commands
+target event name, and BODY is a Tcl procedure or string of commands
 to execute. 
 
 The programmers model is the ``-command'' option used in Tcl/Tk
@@ -1865,9 +1864,9 @@ creates and invokes small procedure. The second inlines the procedure.
 The following events are available:
 @itemize @bullet
 @item @b{debug-halted}
-@* The target has halted for debug reasons (ie: breakpoint)
+@* The target has halted for debug reasons (i.e.: breakpoint)
 @item @b{debug-resumed}
-@* The target has resumed (ie: gdb said run)
+@* The target has resumed (i.e.: gdb said run)
 @item @b{early-halted}
 @* Occurs early in the halt process
 @item @b{examine-end}
@@ -1889,7 +1888,7 @@ The following events are available:
 @item @b{gdb-flash-write-end}
 @* After GDB writes to the flash
 @item @b{gdb-start}
-@* Before the taret steps, gdb is trying to start/resume the tarfget
+@* Before the taret steps, gdb is trying to start/resume the target
 @item @b{halted}
 @* The target has halted
 @item @b{old-gdb_program_config}
@@ -1960,7 +1959,7 @@ jtag configure DOTTED.NAME -event tap-disable @{
 DOTTED.NAME, this name is also used to create the target object
 command.
 @item @b{TYPE}
-@* Specifies the target type, ie: arm7tdmi, or cortexM3. Currently supported targes are:
+@* Specifies the target type, i.e.: ARM7TDMI, or Cortex-M3. Currently supported targets are:
 @comment START types
 @itemize @minus
 @item @b{arm7tdmi}
@@ -1978,8 +1977,7 @@ command.
 @comment end TYPES
 @end itemize
 @item @b{PARAMS}
-@*PARAMs are various target configure parameters, the following are mandatory
-at configuration:
+@*PARAMs are various target configuration parameters. The following ones are mandatory:
 @comment START mandatory
 @itemize @bullet
 @item @b{-endian big|little}
@@ -2000,7 +1998,7 @@ via the configure option or to query the target via cget.
 @item @b{-work-area-size [ADDRESS]} specify/set the work area
 @item @b{-work-area-backup [0|1]} does the work area get backed up
 @item @b{-endian  [big|little]} 
-@item @b{-variant [NAME]} some chips have varients OpenOCD needs to know about
+@item @b{-variant [NAME]} some chips have variants OpenOCD needs to know about
 @item @b{-chain-position DOTTED.NAME} the tap name this target refers to.
 @end itemize
 Example:
@@ -2013,14 +2011,14 @@ Example:
   @}
 @end example
 
-@section Target Varients
+@section Target Variants
 @itemize @bullet
 @item @b{arm7tdmi}
 @* Unknown (please write me)
 @item @b{arm720t}
-@* Unknown (please write me) (simular to arm7tdmi)
+@* Unknown (please write me) (similar to arm7tdmi)
 @item @b{arm9tdmi}
-@* Varients: @option{arm920t}, @option{arm922t} and @option{arm940t}
+@* Variants: @option{arm920t}, @option{arm922t} and @option{arm940t}
 This enables the hardware single-stepping support found on these
 cores.
 @item @b{arm920t}
@@ -2028,10 +2026,10 @@ cores.
 @item @b{arm966e}
 @* None (this is also used as the ARM946)
 @item @b{cortex_m3}
-@* use variant <@var{-variant lm3s}> when debugging luminary lm3s targets. This will cause
+@* use variant <@var{-variant lm3s}> when debugging Luminary lm3s targets. This will cause
 OpenOCD to use a software reset rather than asserting SRST to avoid a issue with clearing
 the debug registers. This is fixed in Fury Rev B, DustDevil Rev B, Tempest, these revisions will
-be detected and the normal reset behaviour used.
+be detected and the normal reset behavior used.
 @item @b{xscale}
 @* Supported variants are @option{ixp42x}, @option{ixp45x}, @option{ixp46x},@option{pxa250}, @option{pxa255}, @option{pxa26x}.
 @item @b{arm11}
@@ -2042,7 +2040,7 @@ provide a functional SRST line on the EJTAG connector.  This causes
 OpenOCD to instead use an EJTAG software reset command to reset the
 processor.  You still need to enable @option{srst} on the reset
 configuration command to enable OpenOCD hardware reset functionality.
-@comment END varients
+@comment END variants
 @end itemize
 @section working_area - Command Removed
 @cindex working_area
@@ -2068,7 +2066,7 @@ performing a backup slows down operation.
 @cindex Flash Configuration
 
 @b{Note:} As of 28/nov/2008 OpenOCD does not know how to program a SPI
-flash that a micro may boot from. Perhaps you the reader would like to
+flash that a micro may boot from. Perhaps you, the reader, would like to
 contribute support for this.
 
 Flash Steps:
@@ -2081,7 +2079,7 @@ via a script in some automated way. For example: To program the boot
 flash on your board.
 @item GDB Flashing
 @* Flashing via GDB requires the flash be configured via ``flash
-bank'', and the GDB flash features be enabled. See the Daemon
+bank'', and the GDB flash features be enabled. See the daemon
 configuration section for more details.
 @end enumerate
 
@@ -2175,16 +2173,16 @@ and <@var{bus_width}> bytes using the selected flash <driver>.
 
 @subsection External Flash - cfi options
 @cindex cfi options
-CFI flash are external flash chips - often they are connected to a
-specific chip select on the micro. By default at hard reset most
-micros have the ablity to ``boot'' from some flash chip - typically
-attached to the chips CS0 pin.
+CFI flashes are external flash chips - often they are connected to a
+specific chip select on the CPU. By default, at hard reset, most
+CPUs have the ablity to ``boot'' from some flash chip - typically
+attached to the CPU's CS0 pin.
 
 For other chip selects: OpenOCD does not know how to configure, or
-access a specific chip select. Instead you the human might need to via