David Brownell <david-b@pacbell.net> Fix two texinfo formatting bugs. The first...

reading the output, and both were reported in openocd.log
after making the PDF.

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

diff --git a/doc/openocd.texi b/doc/openocd.texi
index 363165be07e0b1af05a00e00421a6ca25eb4dade..12827cd23cc4115614b7b8771979dceb862ea694 100644 (file)
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -176,9 +176,11 @@ or expand the OpenOCD source code.
 You can download the current SVN version with an SVN client of your
 choice from the following repositories:
 
-   svn://svn.berlios.de/openocd/trunk
+   @uref{svn://svn.berlios.de/openocd/trunk}
+
 or
-   http://svn.berlios.de/svnroot/repos/openocd/trunk
+
+   @uref{http://svn.berlios.de/svnroot/repos/openocd/trunk}
 
 Using the SVN command line client, you can use the following command to
 fetch the latest version (make sure there is no (non-svn) directory
@@ -716,7 +718,7 @@ will help support users of any board using that chip.
 
 @item
 You may may need to write some C code.
-It may be as simple as a supporting a new new ft2232 or parport
+It may be as simple as a supporting a new ft2232 or parport
 based dongle; a bit more involved, like a NAND or NOR flash
 controller driver; or a big piece of work like supporting
 a new chip architecture.
@@ -3155,8 +3157,8 @@ the family was cribbed from the data sheet. @emph{Note to future
 readers/updaters: Please remove this worrysome comment after other
 chips are confirmed.}
 
-The AT91SAM3U4[E/C] (256K) chips have 2 flash banks, the other chips
-(3U[1/2][E/C]) have 1 flash bank.  In all cases the flash banks are at
+The AT91SAM3U4[E/C] (256K) chips have two flash banks; most other chips
+have one flash bank.  In all cases the flash banks are at
 the following fixed locations:
 
 @example