doc/issue_tracker: remove more mentions of patches

Signed-off-by: Michael Niedermayer <michaelni@gmx.at>

doc/issue_tracker.txt

-FFmpeg's bug/patch/feature request tracker manual
+FFmpeg's bug/feature request tracker manual
 =================================================
 
 NOTE: This is a draft.
@@ -11,7 +11,7 @@ existing issues can be done through a web interface.
 
 Issues can be different kinds of things we want to keep track of
 but that do not belong into the source tree itself. This includes
-bug reports, patches, feature requests and license violations. We
+bug reports, feature requests and license violations. We
 might add more items to this list in the future, so feel free to
 propose a new `type of issue' on the ffmpeg-devel mailing list if
 you feel it is worth tracking.
@@ -45,12 +45,11 @@ license violation
 Priority:
 ---------
 critical
-    Bugs and patches which deal with data loss and security issues.
+    Bugs about data loss and security issues.
     No feature request can be critical.
 
 important
-    Bugs which make FFmpeg unusable for a significant number of users, and
-    patches fixing them.
+    Bugs which make FFmpeg unusable for a significant number of users.
     Examples here might be completely broken MPEG-4 decoding or a build issue
     on Linux.
     While broken 4xm decoding or a broken OS/2 build would not be important,
@@ -64,7 +63,7 @@ normal
 
 
 minor
-    Bugs and patches about things like spelling errors, "mp2" instead of
+    Bugs about things like spelling errors, "mp2" instead of
     "mp3" being shown and such.
     Feature requests about things few people want or which do not make a big
     difference.
@@ -102,7 +101,7 @@ reproduction is not needed as the bug is already understood.
 Type/Status:
 ----------
 */new
-    Initial state of new bugs, patches and feature requests submitted by
+    Initial state of new bugs and feature requests submitted by
     users.
 
 */open
@@ -113,9 +112,7 @@ Type/Status:
     looked at.
 
 */closed/duplicate
-    Bugs, patches or feature requests which are duplicates.
-    Note that patches dealing with the same thing in a different way are not
-    duplicates.
+    Bugs or feature requests which are duplicates.
     Note, if you mark something as duplicate, do not forget setting the
     superseder so bug reports are properly linked.