X-Git-Url: https://review.openocd.org/gitweb?a=blobdiff_plain;f=BUGS;h=961b33940a4b5f6f31a2b3c2f8d2e03d436c7bc2;hb=7c5acf8660ddfce4746152e03749b699532f513f;hp=69675256cade19e608253af9570d846b87f3bf01;hpb=17fb7ead4b901f10c01c0824f594d91775b012b3;p=openocd.git

diff --git a/BUGS b/BUGS
index 69675256ca..961b33940a 100644
--- a/BUGS
+++ b/BUGS
@@ -22,7 +22,7 @@ that may be important.
 - If the report is for a regression:
   - Include logs for both working and broken versions.
   - Find the precise version that caused the regression by binary search.
-    You can use "git bisect" to expedite this binary search:  
+    You can use "git bisect" to expedite this binary search:
     http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
 
 If possible, please develop and attach a patch that helps to expose or
@@ -36,7 +36,7 @@ in total.
 @section bugscrashdump Obtaining Crash Backtraces
 
 If OpenOCD is crashing, there are two very effective things you can do to
-improve your chances of getting help on the development mailing list. 
+improve your chances of getting help on the development mailing list.
 
 Try to reproduce the problem using the dummy JTAG interface to allow other developers to replicate
 your problem robustly and use GDB to get a trace:@par