whitespace cleanup, mostly for docs

Remove useless space/tab at end of lines.
Remove spaces in indentation and replace with tab.

Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com>
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>

5 files changed, 8 insertions, 9 deletions

diff --git a/testing/examples/PIC32/readme.txt b/testing/examples/PIC32/readme.txt
index cb32ac2e..8a5ac3b4 100644
--- a/testing/examples/PIC32/readme.txt
+++ b/testing/examples/PIC32/readme.txt
@@ -1,4 +1,3 @@
 Here you'll find a simple example tested with PIC32 Starter kit (source code and .elf file). It will blink repeatedly the LEDs on the board.
-The program was compiled and written on the target using MPLAB IDE v 8.0 that comes with the kit because openocd is missing currently the ability 
-to program the flash for this specific target. It is possible in the future this limitation to be removed. 
- 
\ No newline at end of file
+The program was compiled and written on the target using MPLAB IDE v 8.0 that comes with the kit because openocd is missing currently the ability
+to program the flash for this specific target. It is possible in the future this limitation to be removed.
diff --git a/testing/index.html b/testing/index.html
index 7e5fcb03..af3ce934 100644
--- a/testing/index.html
+++ b/testing/index.html
@@ -7,7 +7,7 @@
 		A release test must be done on code committed to git.
 		Commit, then test. That way one can know for sure *what* code was actually tested.
 		<p>
-		Note that this testing document does not have anything to do with testing that is done 
+		Note that this testing document does not have anything to do with testing that is done
 		before committing to git. It is a test document for released code. Pre-commit testing
 		is done mostly by the developer who has written the change. Sometimes code is committed
 		to synchronize work, even if it has known problems. Release testing is
@@ -16,7 +16,7 @@
 		and test setup. Also the testing will take place over an extended period of time.
 		<p>
 		All of the above makes it imperative that there can be no doubt about *which* code
-		is tested and thus all tests refer to committed code by subversion number.  
+		is tested and thus all tests refer to committed code by subversion number.
 		<h1>Release procedure</h1>
 		OpenOCD mainline is work in progress.
 		Expect it to change daily and to have some quirks.
@@ -35,7 +35,7 @@
 		<h2>Test cases</h2>
 		Additionally OpenOCD has test cases that target specific functionality more precisely.
 		<p>
-		A full release test must include both smoketests and unit testing. 
+		A full release test must include both smoketests and unit testing.
 		<p>
 		<a href="testcases.html">Test cases</a>
 	</body>
diff --git a/testing/profile_stm32.txt b/testing/profile_stm32.txt
index 3328e5db..a7e03b08 100644
--- a/testing/profile_stm32.txt
+++ b/testing/profile_stm32.txt
@@ -33,7 +33,7 @@ set before [flush_count]
 flash fillb 0x8000000 0x55 0x10000
 set flash_fill_count [expr [flush_count]-$before]
 
-puts "counts" ; puts "step       $step_count" ; puts "mem        $mem_count" ; puts "erase      $erase_count" ; puts "flash fill $flash_fill_count" 
+puts "counts" ; puts "step       $step_count" ; puts "mem        $mem_count" ; puts "erase      $erase_count" ; puts "flash fill $flash_fill_count"
 
 parport trunk rev 1675
 ======================
diff --git a/testing/smoketests.html b/testing/smoketests.html
index 459f8bf6..7d5efc1c 100644
--- a/testing/smoketests.html
+++ b/testing/smoketests.html
@@ -183,7 +183,7 @@
 		<hr>
 		<h1>OpenOCD JTAG device test results</h1>
 		Each JTAG device must be tested
-		
+
 		<table border="1">
 			<tr>
 				<th align="center" width="40">ID</th>
diff --git a/testing/testcases.html b/testing/testcases.html
index 3c1a0242..a3d65b91 100644
--- a/testing/testcases.html
+++ b/testing/testcases.html
@@ -12,7 +12,7 @@ each subversion number.
        <tr><td>Test results</td><td>comment</td></tr>
 	<tr><td><a href="examples/SAM7S256Test/results/607.html">SAM7 R607</a></td><td>PASS</td></tr>
 	<tr><td><a href="examples/STR710Test/results/607.html">STR710 R607</a></td><td>PASS</td></tr>
-	
+
        <tr><td><a href="results/template.html">template</a></td><td>Test results template</td></tr>
 </table>