fix comments

Author: Elimpizza

src/annotator/anchoring/rendered-text.ts

@@ -15,9 +15,10 @@ function substituteBrs(root: Element): string {
 /**
  * Return the text within `range` with each `<br>` replaced by a space.
  *
- * Same as `range.toString()` otherwise — no whitespace collapsing, no
- * block-tag handling. The `<br>` → space substitution exists so that
- * selections spanning a line break aren't reported as run-together words.
+ * Unlike block tags (which almost always have whitespace between them in
+ * the HTML source), `<br>` elements are written inline with no surrounding
+ * whitespace, so `textContent` produces no separation. Each `<br>` is
+ * replaced by a space so the quote reflects what the user sees on screen.
  */
 export function renderedTextFromRange(range: Range): string {
   const container = document.createElement('div');

src/annotator/anchoring/test/html-boundary-test.js

@@ -42,10 +42,9 @@ describe('annotator/anchoring/html boundary handling', () => {
   });
 
   it('describes selection spanning <br> with a space in exact', () => {
-    // This is the bug the PR fixes: a selection that crosses a `<br>` used
-    // to produce `exact: "foobar"` because `textContent` doesn't include a
-    // character for the `<br>`. With the substitution, the stored quote
-    // reflects what the user actually sees in the rendered page.
+    // A selection crossing a `<br>` should produce `exact: "foo bar"` (with
+    // a space), not `"foobar"`, so the stored quote reflects what the user
+    // sees on the rendered page.
     const range = document.createRange();
     range.selectNodeContents(container.querySelector('p'));