Description: <short summary of the patch>
 TODO: Put a short summary on the line above and replace this paragraph
 with a longer explanation of this change. Complete the meta-information
 with other relevant fields (see below for details). To make it easier, the
 information below has been extracted from the changelog. Adjust it or drop
 it.
 .
 bedtools (2.21.0-1) unstable; urgency=medium
 .
   856a5fd Merge tag 'v2.21.0' into debian/unstable
   a4f6ab7 Merge corrections on version number.
Author: Charles Plessy <plessy@debian.org>

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: <vendor|upstream|other>, <url of original patch>
Bug: <url in upstream bugtracker>
Bug-Debian: https://bugs.debian.org/<bugnumber>
Bug-Ubuntu: https://launchpad.net/bugs/<bugnumber>
Forwarded: <no|not-needed|url proving that it has been forwarded>
Reviewed-By: <name and email of someone who approved the patch>
Last-Update: <YYYY-MM-DD>

--- bedtools-2.21.0.orig/README.md
+++ bedtools-2.21.0/README.md
@@ -1,7 +1,7 @@
 bedtools - a swiss army knife for genome arithmetic         
 ===================================================
 
-**Current version**: 2.20.1
+**Current version**: 2.21.1
 
 Note
 -------
--- bedtools-2.21.0.orig/docs/conf.py
+++ bedtools-2.21.0/docs/conf.py
@@ -51,9 +51,9 @@ copyright = u'2009 - 2014, Aaron R. Quin
 # built documents.
 #
 # The short X.Y version.
-version = '2.20.1'
+version = '2.21.1'
 # The full version, including alpha/beta/rc tags.
-release = '2.20.1'
+release = '2.21.1'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
--- bedtools-2.21.0.orig/docs/content/tools/intersect.rst
+++ bedtools-2.21.0/docs/content/tools/intersect.rst
@@ -751,7 +751,7 @@ We can now compare query.bed to all thre
   chr3  110 120
   chr3  105 115
 
-Clearly this is completely informative because we cannot tell from which file each intersection came. However, if we use `-wa` and `-wb`, this becomes abundantly clear. When these options are used, the first column after the complete `-a` record lists the file number from which the overlap came. The number corresponds to the order in which the files were given on the command line. 
+Clearly this is not completely informative because we cannot tell from which file each intersection came. However, if we use `-wa` and `-wb`, this becomes abundantly clear. When these options are used, the first column after the complete `-a` record lists the file number from which the overlap came. The number corresponds to the order in which the files were given on the command line. 
 
 .. code-block:: bash
 
