X-Git-Url: https://review.openocd.org/gitweb?a=blobdiff_plain;f=BUGS;h=36a7da376f05af4743838bdad2fe44a5fba7fd56;hb=44aaba3d08bebbd809aabbe1c05d5aecb54eff12;hp=69675256cade19e608253af9570d846b87f3bf01;hpb=cfc02ccca25b7883ad761123faf207df0df4ad06;p=openocd.git

diff --git a/BUGS b/BUGS
index 69675256ca..36a7da376f 100644
--- a/BUGS
+++ b/BUGS
@@ -22,12 +22,12 @@ 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
-solve the reported problem.  See the PATCHES file for more information
-for that process.
+solve the reported problem.  See the PATCHES.txt file for information
+about that process.
 
 Attach all files directly to your posting.  The mailing list knows to
 transform attachments to links, but attachments must be less than 300KB
@@ -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