internal/bisect: fix doc comment api links

Change-Id: I586dfdf79272c488eff2a374f24d3f4392176f91
Reviewed-on: https://go-review.googlesource.com/c/tools/+/599156
Auto-Submit: Russ Cox <rsc@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: David Chase <drchase@google.com>

internal/bisect/bisect.go

diff --git a/internal/bisect/bisect.go b/internal/bisect/bisect.go
index 50cf53b..5a7da48 100644
--- a/internal/bisect/bisect.go
+++ b/internal/bisect/bisect.go
@@ -119,7 +119,7 @@
 //
 // Finally, a leading “v” in the pattern indicates that the reports will be shown
 // to the user of bisect to describe the changes involved in a failure.
-// At the API level, the leading “v” causes [Matcher.Visible] to return true.
+// At the API level, the leading “v” causes [Matcher.Verbose] to return true.
 // See the next section for details.
 //
 // # Match Reports
@@ -136,12 +136,12 @@
 // 0x1234 is the change ID in hexadecimal.
 // An alternate form is “[bisect-match 010101]”, giving the change ID in binary.
 //
-// When [Matcher.Visible] returns false, the match reports are only
+// When [Matcher.Verbose] returns false, the match reports are only
 // being processed by bisect to learn the set of enabled changes,
 // not shown to the user, meaning that each report can be a match
 // marker on a line by itself, eliding the usual textual description.
 // When the textual description is expensive to compute,
-// checking [Matcher.Visible] can help the avoid that expense
+// checking [Matcher.Verbose] can help the avoid that expense
 // in most runs.
 package bisect