doc: remove duplicated words

Remove occurrences of duplicated words in the documentation.

Change-Id: Ib6ef1607fc5e6387764be108b2b9c0c93ac10a62
Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com>
Reviewed-on: http://openocd.zylin.com/5754
Tested-by: jenkins
Reviewed-by: Tarek BOCHKATI <tarek.bouchkati@gmail.com>
Reviewed-by: Tomas Vanek <vanekt@fbl.cz>

diff --git a/README b/README
index 2ff0329ed29c2c36ed4b1409556a1d3d2c857da3..fe70e725fc85101b8a59feae4e0daae61f239340 100644 (file)
--- a/README
+++ b/README
@@ -288,7 +288,7 @@ Parallel Port Dongles
 ---------------------
 
 If you want to access the parallel port using the PPDEV interface you
-have to specify both --enable-parport AND --enable-parport-ppdev, since the
+have to specify both --enable-parport AND --enable-parport-ppdev, since
 the later option is an option to the parport driver.
 
 The same is true for the --enable-parport-giveio option, you have to

diff --git a/doc/manual/release.txt b/doc/manual/release.txt
index 44de4464f5c059e368da283b9ab3dfa1c5d24582..d1a6c62507828c6d3bd868e194e936325f028189 100644 (file)
--- a/doc/manual/release.txt
+++ b/doc/manual/release.txt
@@ -82,7 +82,7 @@ number will be zero (<code>z = 0</code>).  For a <i>major releases</i>,
 the minor version will @a also be zero (<code>y = 0, z = 0</code>).
 
 After these required numeric components, release version strings
-may contain tags such as as <em>-rc1</em> or <em>-rc2</em>.
+may contain tags such as <em>-rc1</em> or <em>-rc2</em>.
 These 'rc' tags indicate "release candidate" versions of the package.
 Like major/minor/micro numbers, these are updated
 as part of the release process.

diff --git a/doc/manual/server.txt b/doc/manual/server.txt
index 50fcac75ed36151cd47bee599da4ac3e6e0f92f5..8041c3df3d1a39d560fc949771ccf78a23f7845a 100644 (file)
--- a/doc/manual/server.txt
+++ b/doc/manual/server.txt
@@ -23,7 +23,7 @@ In early 2008, Oyvind Harboe and Duane Ellis had talked about how to
 create a reasonable GUI for OpenOCD - something that is non-invasive,
 simple to use and maintain, and does not tie OpenOCD to many other
 packages.  It would be wrong to "spider web" requirements into other
-external external packages.  That makes it difficult for developers to
+external packages.  That makes it difficult for developers to
 write new code and creates a support nightmare.
 
 In many ways, people had talked about the need for some type of
@@ -67,7 +67,7 @@ write scripts internally to help things, or we can write "C" code  that
 interfaces well with TCL.
 
 From there, the developers wanted to create an external front-end that
-would be @a very usable and that that @a any language could utilize,
+would be @a very usable and that @a any language could utilize,
 allowing simple front-ends to be (a) cross-platform (b) language
 agnostic, and (c) easy to develop and use.
 

diff --git a/doc/manual/style.txt b/doc/manual/style.txt
index e654be9c3414986d533dca76ea47a593634815bf..7191a4b0e6975b518b49a19319cc1aa70fcd3cfb 100644 (file)
--- a/doc/manual/style.txt
+++ b/doc/manual/style.txt
@@ -52,7 +52,7 @@ OpenOCD project.
   -# remove it entirely (git can retrieve the old version), or
   -# use an @c \#if/\#endif block.
 
-Finally, try to avoid lines of code that are longer than than 72-80 columns:
+Finally, try to avoid lines of code that are longer than 72-80 columns:
 
 - long lines frequently indicate other style problems:
   - insufficient use of static functions, macros, or temporary variables

diff --git a/doc/openocd.texi b/doc/openocd.texi
index 9f20e391d272230c199f2c77ced75213d85ab1f3..6b461a30eb1959c33a68ecd9cb302a2606265eff 100644 (file)
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -1020,7 +1020,7 @@ will help support users of any board using that chip.
 @end quotation
 
 @item
-You may may need to write some C code.
+You may need to write some C code.
 It may be as simple as supporting a new FT2232 or parport
 based adapter; a bit more involved, like a NAND or NOR flash
 controller driver; or a big piece of work like supporting
@@ -5661,7 +5661,7 @@ at91samd bootloader 16384
 @deffn Command {at91samd dsu_reset_deassert}
 This command releases internal reset held by DSU
 and prepares reset vector catch in case of reset halt.
-Command is used internally in event event reset-deassert-post.
+Command is used internally in event reset-deassert-post.
 @end deffn
 
 @deffn Command {at91samd nvmuserrow}
@@ -5768,7 +5768,7 @@ The AT91SAM4L driver adds some additional commands:
 @deffn Command {at91sam4l smap_reset_deassert}
 This command releases internal reset held by SMAP
 and prepares reset vector catch in case of reset halt.
-Command is used internally in event event reset-deassert-post.
+Command is used internally in event reset-deassert-post.
 @end deffn
 @end deffn
 
@@ -5809,7 +5809,7 @@ processor to be halted.
 @deffn Command {atsame5 dsu_reset_deassert}
 This command releases internal reset held by DSU
 and prepares reset vector catch in case of reset halt.
-Command is used internally in event event reset-deassert-post.
+Command is used internally in event reset-deassert-post.
 @end deffn
 
 @deffn Command {atsame5 userpage}
@@ -8392,7 +8392,7 @@ and any buffered trace data is invalidated.
 
 @itemize
 @item @var{type} ... describing how data accesses are traced,
-when they pass any ViewData filtering that that was set up.
+when they pass any ViewData filtering that was set up.
 The value is one of
 @option{none} (save nothing),
 @option{data} (save data),
@@ -8740,7 +8740,7 @@ and any other core-specific commands that may be available.
 
 @deffn Command {arm7_9 dbgrq} [@option{enable}|@option{disable}]
 Displays the value of the flag controlling use of the
-the EmbeddedIce DBGRQ signal to force entry into debug mode,
+EmbeddedIce DBGRQ signal to force entry into debug mode,
 instead of breakpoints.
 If a boolean parameter is provided, first assigns that flag.