Tried to be even clearer.

1 files changed, 9 insertions, 10 deletions

diff --git a/generic/tkText.c b/generic/tkText.c
index 5042582..eb2d77a 100644
--- a/generic/tkText.c
+++ b/generic/tkText.c
@@ -3000,16 +3000,15 @@ DeleteIndexRange(
      * dummy empty line at the end of the text. If the final newline of the
      * file (just before the dummy line) is being deleted, then back up index
      * to just before the newline. If there is a newline just before the first
-     * character being deleted, then back up the first index too, so that an
-     * even number of lines gets deleted. The idea is that a deletion
-     * involving a range starting at a line start and including the final \n
-     * (i.e. index2 is "end") is an attempt to delete complete lines, so the
-     * \n before the deleted block shall become the new final \n. Furthermore,
-     * remove any tags that are present on the newline that isn't going to be
-     * deleted after all (this simulates deleting the newline and then adding
-     * a "clean" one back again). Note that index1 and index2 might now be
-     * equal again which means that no text will be deleted but tags might be
-     * removed.
+     * character being deleted, then back up the first index too. The idea is
+     * that a deletion involving a range starting at a line start and
+     * including the final \n (i.e. index2 is "end") is an attempt to delete
+     * complete lines, so the \n before the deleted block shall become the new
+     * final \n. Furthermore, remove any tags that are present on the newline
+     * that isn't going to be deleted after all (this simulates deleting the
+     * newline and then adding a "clean" one back again). Note that index1 and
+     * index2 might now be equal again which means that no text will be
+     * deleted but tags might be removed.
      */
 
     line1 = TkBTreeLinesTo(textPtr, index1.linePtr);