diff --git a/src/current/advisories/a101963.md b/src/current/advisories/a101963.md
index f404a8a28d1..75a292f38bc 100644
--- a/src/current/advisories/a101963.md
+++ b/src/current/advisories/a101963.md
@@ -19,13 +19,13 @@ In the following circumstances, backups that include [revision history](https://
 
 ## Statement
 
-This is resolved in CockroachDB by [#102179](https://github.com/cockroachdb/cockroach/pull/102179), which ensures that `RESTORE` operations can correctly restore from backups that include this incorrect metadata.
+This is resolved in CockroachDB by #102179, which ensures that `RESTORE` operations can correctly restore from backups that include this incorrect metadata.
 
 The fix has been applied to maintenance releases of CockroachDB: [v22.2.9](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-9).
 
 This fix will be applied to maintenance releases of CockroachDB: v22.1.20. Until that version is available, refer to [Mitigation](#mitigation) for a suggested workaround.
 
-This public issue is tracked by [#101963](https://github.com/cockroachdb/cockroach/issues/101963).
+This public issue is tracked by #101963.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a102375.md b/src/current/advisories/a102375.md
index ec031327deb..1ac6d7165d3 100644
--- a/src/current/advisories/a102375.md
+++ b/src/current/advisories/a102375.md
@@ -16,13 +16,13 @@ In CockroachDB versions v22.1.19 and v22.2.8, some customers may experience spur
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#102405](https://github.com/cockroachdb/cockroach/issues/102405) which ensures that privilege checks happen after staleness checks when attempting to use the query cache.
+This is resolved in CockroachDB by PR #102405 which ensures that privilege checks happen after staleness checks when attempting to use the query cache.
 
 The fix has been applied to the maintenance release of CockroachDB [v22.2.9](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-9).
 
 This fix will be applied to the maintenance release of CockroachDB v22.1.20.
 
-This public issue is tracked by [#102375](https://github.com/cockroachdb/cockroach/issues/102375).
+This public issue is tracked by #102375.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a103220.md b/src/current/advisories/a103220.md
index 877b5b6695f..b7a59712884 100644
--- a/src/current/advisories/a103220.md
+++ b/src/current/advisories/a103220.md
@@ -15,11 +15,11 @@ In CockroachDB v23.1.0 and its testing versions, inserting rows into a multi-[co
 
 ## Statement
 
-This is resolved in CockroachDB by PR [103323](https://github.com/cockroachdb/cockroach/pull/103323).
+This is resolved in CockroachDB by PR 103323.
 
 This fix has been applied to maintenance releases of CockroachDB [v23.1.1](https://www.cockroachlabs.com/docs/releases/v23.1#v23-1-1) and later.
 
-This public issue is tracked by [#103220](https://github.com/cockroachdb/cockroach/issues/103220).
+This public issue is tracked by #103220.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a104309.md b/src/current/advisories/a104309.md
index 7fd8b7b5feb..e5ba1bf5c4a 100644
--- a/src/current/advisories/a104309.md
+++ b/src/current/advisories/a104309.md
@@ -47,7 +47,7 @@ Versions prior to 22.2 are no longer eligible for [maintenance support](https://
 
 ## Statement
 
-This is resolved in CockroachDB by [PR #117612](https://github.com/cockroachdb/cockroach/pull/117612), which uses a barrier command to ensure that all historical and ongoing range writes have been applied to the local replica and emitted before the resolved timestamp is advanced and a checkpoint is emitted.
+This is resolved in CockroachDB by PR #117612, which uses a barrier command to ensure that all historical and ongoing range writes have been applied to the local replica and emitted before the resolved timestamp is advanced and a checkpoint is emitted.
 
 The fix has been applied to maintenance releases of CockroachDB:
 
@@ -63,7 +63,7 @@ However, the initial fix introduced a bug that could cause a rangefeed’s resol
 
 Users are encouraged to upgrade to a version that contains both fixes.
 
-This public issue is tracked by [Issue #104309](https://github.com/cockroachdb/cockroach/issues/104309).
+This public issue is tracked by Issue #104309.
 
 ## Mitigation
 
@@ -90,7 +90,7 @@ If data is found, it can be re-emitted in two ways:
 
 <a id="issue_110536"></a>
 {{site.data.alerts.callout_info}}
-This fix introduces a [bug](https://github.com/cockroachdb/cockroach/issues/119536) that could cause a rangefeed’s resolved timestamp to stop advancing. The corresponding changefeed will appear to be stalled in `RUNNING` state in certain conditions: If a rangefeed is running on a follower on a recently-merged range, and the rangefeed encounters an aborted transaction, then the resolved timestamp may stall. Events such as row updates will still be emitted as normal, but new checkpoints will not be emitted.
+This fix introduces a bug that could cause a rangefeed’s resolved timestamp to stop advancing. The corresponding changefeed will appear to be stalled in `RUNNING` state in certain conditions: If a rangefeed is running on a follower on a recently-merged range, and the rangefeed encounters an aborted transaction, then the resolved timestamp may stall. Events such as row updates will still be emitted as normal, but new checkpoints will not be emitted.
 
 That bug is fixed in the following versions:
 
@@ -120,7 +120,7 @@ If your cluster experiences a stalled rangefeed or changefeed after upgrading, y
 
 As an alternative to avoid disruption to the changefeed, you can temporarily disable `kv.rangefeed.push_txns.barrier.enabled` to disable the fix to this advisory, **a104309**, until a fix to the stalled rangefeed bug is available.
 
-This issue is tracked by [Issue #119536](https://github.com/cockroachdb/cockroach/issues/119536).
+This issue is tracked by Issue #119536.
 {{site.data.alerts.end}}
 
 ## Impact
diff --git a/src/current/advisories/a106617.md b/src/current/advisories/a106617.md
index 43ce154346e..5eb69e00da5 100644
--- a/src/current/advisories/a106617.md
+++ b/src/current/advisories/a106617.md
@@ -20,11 +20,11 @@ The corruption is limited to a single store, allowing recovery through [decommis
 
 ## Statement
 
-This is resolved in CockroachDB by [#107249](https://github.com/cockroachdb/cockroach/pull/107249), which fixes the ordering of steps during encryption-at-rest log rotation. 
+This is resolved in CockroachDB by #107249, which fixes the ordering of steps during encryption-at-rest log rotation. 
 
 The fix has been applied to maintenance releases of CockroachDB [v23.1.8](../releases/v23.1.html#v23-1-8), [v22.2.13](../releases/v22.2.html#v22-2-13), v22.1.22.
 
-This public issue is tracked by [#106617](https://github.com/cockroachdb/cockroach/issues/106617).
+This public issue is tracked by #106617.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a110363.md b/src/current/advisories/a110363.md
index 0d3e04692c2..bf4450a9c3d 100644
--- a/src/current/advisories/a110363.md
+++ b/src/current/advisories/a110363.md
@@ -22,11 +22,11 @@ This issue affects clusters that meet all of the following conditions:
 
 ## Statement
 
-This is resolved in CockroachDB by [#110364](https://github.com/cockroachdb/cockroach/pull/110364), which prevents deletion of the TTL field upon upgrade.
+This is resolved in CockroachDB by #110364, which prevents deletion of the TTL field upon upgrade.
 
 The fix will be available in CockroachDB v23.1.10.
 
-This public issue is tracked by [#110363](https://github.com/cockroachdb/cockroach/issues/110363).
+This public issue is tracked by #110363.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a114393.md b/src/current/advisories/a114393.md
index 139cb8a57d6..adbda2e6b4c 100644
--- a/src/current/advisories/a114393.md
+++ b/src/current/advisories/a114393.md
@@ -20,11 +20,11 @@ A critical bug has been identified in the [optimizer](../v23.1/cost-based-optimi
 
 ## Statement
 
-This is resolved in CockroachDB by [#114394](https://github.com/cockroachdb/cockroach/pull/114394).
+This is resolved in CockroachDB by #114394.
 
 This fix has been applied to maintenance release of CockroachDB [v23.1.13](../releases/v23.1.html#v23-1-13), which fixes a bug that could cause a query plan to skip scanning rows from the local region when performing a lookup join with a `REGIONAL BY ROW` table as the input.
 
-This public issue is tracked by [#114393](https://github.com/cockroachdb/cockroach/issues/114393).
+This public issue is tracked by #114393.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a122372.md b/src/current/advisories/a122372.md
index 4bc217b89c4..e4c677c3a63 100644
--- a/src/current/advisories/a122372.md
+++ b/src/current/advisories/a122372.md
@@ -14,15 +14,15 @@ Publication date: {{ page.advisory_date | date: "%B %e, %Y" }}
 
 In all versions of CockroachDB v23.1, v23.2.0 to v23.2.9, v24.1.0 to v24.1.3, and testing versions of v24.2 through v24.2.0-beta.3, [changefeeds]({% link v24.2/change-data-capture-overview.md %}) could emit events on the same row out of order in some cases, which violates [changefeed ordering guarantees]({% link v24.2/changefeed-messages.md %}#per-key-ordering). This issue was caused by a [bug in the sarama Kafka client library](https://github.com/IBM/sarama/issues/2619), a third-party library that CockroachDB uses to talk to Kafka clusters. The bug manifested when a workload had mutations to the same key in rapid succession, because it was possible for [sarama](https://github.com/IBM/sarama) to re-order the messages if it encountered a retryable Kafka error.
 
-To resolve this issue, CockroachDB now uses a new version of the Kafka sink that uses [franz-go](https://github.com/twmb/franz-go), a different third-party Kafka client library that does not have this bug. The new Kafka sink can be enabled using the cluster setting [`changefeed.new_kafka_sink.enabled`]({% link v24.2/show-cluster-setting.md %}). The new Kafka sink was added in PR [#126213](https://github.com/cockroachdb/cockroach/pull/126213).
+To resolve this issue, CockroachDB now uses a new version of the Kafka sink that uses [franz-go](https://github.com/twmb/franz-go), a different third-party Kafka client library that does not have this bug. The new Kafka sink can be enabled using the cluster setting [`changefeed.new_kafka_sink.enabled`]({% link v24.2/show-cluster-setting.md %}). The new Kafka sink was added in PR #126213.
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#126213](https://github.com/cockroachdb/cockroach/pull/126213), which replaces the Kafka client library [sarama](https://github.com/IBM/sarama) with [franz-go](https://github.com/twmb/franz-go).
+This is resolved in CockroachDB by PR #126213, which replaces the Kafka client library [sarama](https://github.com/IBM/sarama) with [franz-go](https://github.com/twmb/franz-go).
 
 The fix has been applied to maintenance releases of CockroachDB v23.2.10, v24.1.4, and v24.2.0-rc.1.
 
-This public issue is tracked by issue [#122372](https://github.com/cockroachdb/cockroach/issues/122372).
+This public issue is tracked by issue #122372.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a123371.md b/src/current/advisories/a123371.md
index ee5c9ad2a14..af0e353bd4e 100644
--- a/src/current/advisories/a123371.md
+++ b/src/current/advisories/a123371.md
@@ -12,7 +12,7 @@ Publication date: {{ page.advisory_date | date: "%B %e, %Y" }}
 
 ## Description
 
-In all versions of CockroachDB v22.2, v23.1.0 to v23.1.21, v23.2.0 to v23.2.5, and testing versions of v24.1 through v24.1.0-rc.1, changefeeds could drop events during the initial scan in some cases, causing changefeed consumers to receive incomplete data. This bug was caused by a [code change](https://github.com/cockroachdb/cockroach/commit/0eda54018b9676f855efcd90bfdd0c486c97bfdd) to reduce the number of duplicates sent during an initial scan if the changefeed needed to restart by using the checkpoint to determine which spans could be skipped when the job resumed. This change led to some non-determinism in another part of the codebase that would sometimes incorrectly forward the progress of every span a node was tracking to the lowest checkpoint timestamp when some spans may not have been scanned yet. This bug is now fixed by [PR #123625](https://github.com/cockroachdb/cockroach/pull/123625).
+In all versions of CockroachDB v22.2, v23.1.0 to v23.1.21, v23.2.0 to v23.2.5, and testing versions of v24.1 through v24.1.0-rc.1, changefeeds could drop events during the initial scan in some cases, causing changefeed consumers to receive incomplete data. This bug was caused by a code change to reduce the number of duplicates sent during an initial scan if the changefeed needed to restart by using the checkpoint to determine which spans could be skipped when the job resumed. This change led to some non-determinism in another part of the codebase that would sometimes incorrectly forward the progress of every span a node was tracking to the lowest checkpoint timestamp when some spans may not have been scanned yet. This bug is now fixed by PR #123625.
 
 Symptoms of the bug:
 
@@ -35,9 +35,9 @@ Factors that increase the likelihood the bug occurring:
 
 ## Statement
 
-This is resolved in CockroachDB by [PR #123625](https://github.com/cockroachdb/cockroach/pull/123625) which prevents incorrect forwarding of progress for spans that have not been scanned yet by the initial scan.
+This is resolved in CockroachDB by PR #123625 which prevents incorrect forwarding of progress for spans that have not been scanned yet by the initial scan.
 The fix has been applied to maintenance releases of CockroachDB v23.1.22, v23.2.6, and v24.1.0-rc.2.
-This public issue is tracked by [#123371](https://github.com/cockroachdb/cockroach/issues/123371).
+This public issue is tracked by #123371.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a131639.md b/src/current/advisories/a131639.md
index 6564386f581..0550531bcb5 100644
--- a/src/current/advisories/a131639.md
+++ b/src/current/advisories/a131639.md
@@ -35,7 +35,7 @@ Versions prior to 23.1 are no longer eligible for [maintenance support]({% link
 
 ## Statement
 
-[In #123442](https://github.com/cockroachdb/cockroach/commit/6dd54b46cc56b7d2b302e0d5ec1509658a1c86f7), we resolved an issue with CockroachDB in the expiration-to-epoch lease promotion transition process, where a lease's effective expiration could be allowed to regress, resulting in two nodes believing they are the leaseholder for a range.
+In #123442, we resolved an issue with CockroachDB in the expiration-to-epoch lease promotion transition process, where a lease's effective expiration could be allowed to regress, resulting in two nodes believing they are the leaseholder for a range.
 
 The patch has been applied to maintenance releases of CockroachDB:
 
@@ -43,7 +43,7 @@ The patch has been applied to maintenance releases of CockroachDB:
 - [v23.2.11]({% link releases/v23.2.md%}#v23-2-11)
 - [v24.1.1]({% link releases/v24.1.md%}#v24-1-1)
 
-This public issue is tracked by [131639](https://github.com/cockroachdb/cockroach/issues/131639).
+This public issue is tracked by 131639.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a144650.md b/src/current/advisories/a144650.md
index 969f5c24488..0c79fd10c01 100644
--- a/src/current/advisories/a144650.md
+++ b/src/current/advisories/a144650.md
@@ -28,9 +28,9 @@ For steps to identify and mitigate affected operations, refer to [Mitigation](#m
 
 ## Statement
 
-This issue is resolved in CockroachDB by [#144646](https://github.com/cockroachdb/cockroach/pull/144646), which disables the rare (async flush) code path for bulk write operations. The fix has been applied to the v23.2.24, v24.1.17, v24.3.11, and v25.1.5 production releases, and to the v25.2.0-beta.2 testing release.
+This issue is resolved in CockroachDB by #144646, which disables the rare (async flush) code path for bulk write operations. The fix has been applied to the v23.2.24, v24.1.17, v24.3.11, and v25.1.5 production releases, and to the v25.2.0-beta.2 testing release.
 
-The issue is tracked publicly by [#144650](https://github.com/cockroachdb/cockroach/issues/144650).
+The issue is tracked publicly by #144650.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a151050.md b/src/current/advisories/a151050.md
index e259bbad3c3..d737bdde87d 100644
--- a/src/current/advisories/a151050.md
+++ b/src/current/advisories/a151050.md
@@ -20,11 +20,11 @@ While this issue is expected to occur rarely, we recommend upgrading to the next
 
 ## Statement
 
-This issue is resolved in CockroachDB by PR [#151058](https://github.com/cockroachdb/cockroach/pull/151058) which ensures errors encountered during all buffer flushes - even those caused by intermittent object storage provider errors - are correctly reported to the backup job. 
+This issue is resolved in CockroachDB by PR #151058 which ensures errors encountered during all buffer flushes - even those caused by intermittent object storage provider errors - are correctly reported to the backup job. 
 
 The fix has been applied to the following versions of CockroachDB: v24.1.22, v24.3.17, v25.1.10, v25.2.4, and the testing version of v25.3, v25.3.0-rc.2.
 
-This issue is tracked publicly by [#151050](https://github.com/cockroachdb/cockroach/issues/151050).
+This issue is tracked publicly by #151050.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a161317.md b/src/current/advisories/a161317.md
index f39aeb1e4c9..2a2990ad293 100644
--- a/src/current/advisories/a161317.md
+++ b/src/current/advisories/a161317.md
@@ -26,7 +26,7 @@ This advisory applies to the following versions of CockroachDB:
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#161318](https://github.com/cockroachdb/cockroach/pull/161318) which fixes the improper error handling in the Avro OCF reader implementation.
+This is resolved in CockroachDB by PR #161318 which fixes the improper error handling in the Avro OCF reader implementation.
 
 This fix has been applied to the following maintenance releases of CockroachDB:
 
@@ -35,7 +35,7 @@ This fix has been applied to the following maintenance releases of CockroachDB:
 - v25.4.4
 - Testing release v26.1.0-rc.1
 
-This public issue is tracked in [#161317](https://github.com/cockroachdb/cockroach/issues/161317).
+This public issue is tracked in #161317.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a162085.md b/src/current/advisories/a162085.md
index 35f6e48093d..6d32870ffad 100644
--- a/src/current/advisories/a162085.md
+++ b/src/current/advisories/a162085.md
@@ -16,7 +16,7 @@ A race condition between MVCC garbage collection and range splits in CockroachDB
 
 Most workloads are unlikely to be affected by this issue. The conditions that precipitate data loss are narrow and require a specific combination of data lifecycle patterns and timing. Details on how to assess your risk are provided in the *Am I Affected?* section below.
 
-This public issue is tracked by [#162085](https://github.com/cockroachdb/cockroach/issues/162085).
+This public issue is tracked by #162085.
 
 ## Action Required
 
@@ -140,7 +140,7 @@ This section provides a detailed technical explanation of the underlying issue f
 
 ### Background
 
-CockroachDB v23.1 (PR [#90830](https://github.com/cockroachdb/cockroach/pull/90830)) added an optimization to the garbage collection process. When there is a contiguous span of at least 2,000 non-live (obsolete) keys in a range, the GC process writes a Pebble range tombstone using a ClearRange request to efficiently delete this span of data, rather than deleting each key individually.
+CockroachDB v23.1 (PR #90830) added an optimization to the garbage collection process. When there is a contiguous span of at least 2,000 non-live (obsolete) keys in a range, the GC process writes a Pebble range tombstone using a ClearRange request to efficiently delete this span of data, rather than deleting each key individually.
 
 ### The race condition
 
diff --git a/src/current/advisories/a166122.md b/src/current/advisories/a166122.md
index 45100e6e961..60be0858600 100644
--- a/src/current/advisories/a166122.md
+++ b/src/current/advisories/a166122.md
@@ -37,7 +37,7 @@ The root cause is in the SQL optimizer, which incorrectly applies two optimizati
 
 ## Statement
 
-This is resolved in CockroachDB by [PR #166123](https://github.com/cockroachdb/cockroach/pull/166123), which fixes the optimizer to always fetch the required columns and avoid simplifying predicate evaluation for mutation indexes.
+This is resolved in CockroachDB by PR #166123, which fixes the optimizer to always fetch the required columns and avoid simplifying predicate evaluation for mutation indexes.
 
 A fix has been applied to the following maintenance releases of CockroachDB:
 
@@ -47,7 +47,7 @@ A fix has been applied to the following maintenance releases of CockroachDB:
 - v26.1.3
 - Testing release v26.2.0-beta.2
 
-This public issue is tracked by [#166122](https://github.com/cockroachdb/cockroach/issues/166122).
+This public issue is tracked by #166122.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a190483.md b/src/current/advisories/a190483.md
index 9aaf0412c90..70eb4132a29 100644
--- a/src/current/advisories/a190483.md
+++ b/src/current/advisories/a190483.md
@@ -34,11 +34,11 @@ If the result set is empty, no further action is required. If the result set is
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#109713](https://github.com/cockroachdb/cockroach/pull/109713) for v23.1 and PR [#109750](https://github.com/cockroachdb/cockroach/pull/109750) for v22.2. The PRs update the method used to select the boundaries at which ranges of data are split during `RESTORE` to avoid splitting between two column families of the same row.
+This is resolved in CockroachDB by PR #109713 for v23.1 and PR #109750 for v22.2. The PRs update the method used to select the boundaries at which ranges of data are split during `RESTORE` to avoid splitting between two column families of the same row.
 
 These fixes are available in CockroachDB maintenance releases v23.1.9 and v22.2.14.
 
-This public issue is tracked in [109483](https://github.com/cockroachdb/cockroach/issues/109483).
+This public issue is tracked in 109483.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a30821.md b/src/current/advisories/a30821.md
index cce37051a4b..b5aaab62464 100644
--- a/src/current/advisories/a30821.md
+++ b/src/current/advisories/a30821.md
@@ -20,7 +20,7 @@ On October 23rd, 2018, an internal review uncovered a security vulnerability wit
 
 Registered users were informed privately of the issue and provided with early access to the fix, ahead of the public advisory.
 
-This issue is tracked internally as [#30821](https://github.com/cockroachdb/cockroach/issues/30821).
+This issue is tracked internally as #30821.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a42567.md b/src/current/advisories/a42567.md
index fd2fe281ea0..8d4dad2fb54 100644
--- a/src/current/advisories/a42567.md
+++ b/src/current/advisories/a42567.md
@@ -26,7 +26,7 @@ This issue was fixed in patch revisions v2.1.10, v19.1.6, and v19.2.2 by requiri
 The issue also exists in versions v2.0.x and prior. However, up to and including version v2.0.x, the HTTP endpoint was not advertised safe for use on non-privileged networks. Additionally, versions v2.0 and prior have reached end-of-life. All users are invited to upgrade to v2.1.10 or, preferably, a later version.
 
 This issue is tracked internally as
-[#42567](https://github.com/cockroachdb/cockroach/issues/42567).
+#42567.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a43870.md b/src/current/advisories/a43870.md
index c02b470c322..a1c38c3b41c 100644
--- a/src/current/advisories/a43870.md
+++ b/src/current/advisories/a43870.md
@@ -26,7 +26,7 @@ Additionally, CockroachDB v19.2.3 and v20.1 include a way to create an HTTP auth
 
 Starting in v20.1, the `root` user will also be able to use a password and log in via HTTP interactively.
 
-This issue is tracked internally as [#43870](https://github.com/cockroachdb/cockroach/issues/43870).
+This issue is tracked internally as #43870.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a44166.md b/src/current/advisories/a44166.md
index dfb7a7450a0..17b6e1e62c8 100644
--- a/src/current/advisories/a44166.md
+++ b/src/current/advisories/a44166.md
@@ -22,7 +22,7 @@ Under reasonable production settings, a single backup job payload may exceed 5MB
 
 Starting in CockroachDB v19.2.3, new jobs payloads are reduced in size. A later version will also avoid loading old job entries in memory when viewing recent jobs.
 
-This public issue is tracked as [#44166](https://github.com/cockroachdb/cockroach/issues/44166).
+This public issue is tracked as #44166.
 
 
 ## Mitigation
diff --git a/src/current/advisories/a44299.md b/src/current/advisories/a44299.md
index 13e359a70a1..3b7cb3fa5e1 100644
--- a/src/current/advisories/a44299.md
+++ b/src/current/advisories/a44299.md
@@ -24,7 +24,7 @@ An identifying symptom is frequent log messages of the format: `job with ID <job
 This condition has been eliminated in CockroachDB versions v19.1.8 and v19.2.4. All deployments are strongly recommended to upgrade as preventative measure. A cluster already affected by the symptoms is also expected to recover automatically after upgrading to these patch revisions.
 
 The public issue is tracked as
-[#44299](https://github.com/cockroachdb/cockroach/issues/44299).
+#44299.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a44348.md b/src/current/advisories/a44348.md
index 8225d49d146..7488d96817e 100644
--- a/src/current/advisories/a44348.md
+++ b/src/current/advisories/a44348.md
@@ -22,7 +22,7 @@ Starting in CockroachDB v19.2.4, v19.1.8 and v2.1.12, admin privileges will be r
 
 A new feature to enable access to their own statement details by non-admin users is being considered for inclusion in CockroachDB v20.1 or later.
 
-This public issue is tracked as [#44348](https://github.com/cockroachdb/cockroach/issues/44348).
+This public issue is tracked as #44348.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a48860.md b/src/current/advisories/a48860.md
index a360bbc47ff..e368ebfc071 100644
--- a/src/current/advisories/a48860.md
+++ b/src/current/advisories/a48860.md
@@ -20,7 +20,7 @@ A defect in RocksDB allowed it to violate its guarantees for snapshots, causing
 
 This bug has been fixed in versions v19.1.9, v19.2.7, and v20.1.0. All users are encouraged to upgrade (see [Mitigation](#mitigation) below).
 
-The public issue is tracked as [#48860](https://github.com/cockroachdb/cockroach/issues/48860).
+The public issue is tracked as #48860.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a50587.md b/src/current/advisories/a50587.md
index b1ceff9babc..4aba06017eb 100644
--- a/src/current/advisories/a50587.md
+++ b/src/current/advisories/a50587.md
@@ -18,7 +18,7 @@ When executing a [`TRUNCATE`](https://www.cockroachlabs.com/docs/v19.2/truncate)
 
 This bug has been fixed in versions v19.1.11 and v19.2.9. All users are encouraged to upgrade to the latest maintenance release (see [Mitigation](#mitigation) below).
 
-The public issue is tracked as [#50587](https://github.com/cockroachdb/cockroach/issues/50587).
+The public issue is tracked as #50587.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a54418.md b/src/current/advisories/a54418.md
index c4e60009bae..ea46164fe1c 100644
--- a/src/current/advisories/a54418.md
+++ b/src/current/advisories/a54418.md
@@ -17,11 +17,11 @@ CockroachDB introduced a bug in the [v20.1.4 release](https://www.cockroachlabs.
 - The execution of a single `UPSERT` statement will stop, without a visible error, after reaching 10,000 rows. The reported number of affected rows will be incorrect, reported as 0.
 - Executing a single `UPSERT … RETURNING` statement will return at most 10,000 rows.
 
-This bug was introduced in [#51944][#51944], which was intended to correct a previously-identified error in `UPSERT` handling. A fix ([#54418][#54418]) is available in the [v20.1.6 release](https://www.cockroachlabs.com/docs/releases/v20.1#v20-1-6).
+This bug was introduced in #51944, which was intended to correct a previously-identified error in `UPSERT` handling. A fix (#54418) is available in the [v20.1.6 release](https://www.cockroachlabs.com/docs/releases/v20.1#v20-1-6).
 
 ## Statement
 
-To track this issue, see [#54418][#54418], the pull request correcting the aforementioned bugs.
+To track this issue, see #54418, the pull request correcting the aforementioned bugs.
 
 ## Mitigation
 
@@ -33,5 +33,3 @@ All deployments running CockroachDB [v20.1.4 release](https://www.cockroachlabs.
 
 Questions about any technical alert can be directed to our [support team](https://support.cockroachlabs.com/).
 
-[#51944]: https://github.com/cockroachdb/cockroach/pull/51944
-[#54418]: https://github.com/cockroachdb/cockroach/pull/54418
diff --git a/src/current/advisories/a56116.md b/src/current/advisories/a56116.md
index dfb8d553e3b..a307fc126d6 100644
--- a/src/current/advisories/a56116.md
+++ b/src/current/advisories/a56116.md
@@ -20,7 +20,7 @@ All currently-released versions of the Go runtime [incorrectly interpret](https:
 
 ## Statement
 
-This public issue is tracked as [#56116][#56116].
+This public issue is tracked as #56116.
 
 ## Mitigation
 
@@ -44,4 +44,3 @@ Any clusters impacted by this issue may produce incorrect results when performin
 
 Questions about any technical alert can be directed to our [support team](https://support.cockroachlabs.com/).
 
-[#56116]: https://github.com/cockroachdb/cockroach/issues/56116
diff --git a/src/current/advisories/a58932.md b/src/current/advisories/a58932.md
index efc319c799d..17c24de45fc 100644
--- a/src/current/advisories/a58932.md
+++ b/src/current/advisories/a58932.md
@@ -16,11 +16,11 @@ A bug in the [protobuf](https://github.com/gogo/protobuf) binary decode function
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#58716] which fixes the decoding routine of protobuf payloads.
+This is resolved in CockroachDB by PR #58716 which fixes the decoding routine of protobuf payloads.
 
 The fix has been applied to maintenance releases of CockroachDB v19.2, v20.1, and v21.1.
 
-This public issue is tracked as [#58932].
+This public issue is tracked as #58932.
 
 ## Mitigation
 
@@ -39,5 +39,3 @@ Questions about any technical alert can be directed to our [Support team](https:
 
 We thank Kirk Baird for reporting this issue to Cockroach Labs.
 
-[#58716]: https://github.com/cockroachdb/cockroach/pull/58716
-[#58932]: https://github.com/cockroachdb/cockroach/issues/58932
diff --git a/src/current/advisories/a62842.md b/src/current/advisories/a62842.md
index 6367267520f..ff593a90175 100644
--- a/src/current/advisories/a62842.md
+++ b/src/current/advisories/a62842.md
@@ -21,11 +21,11 @@ This issue affects CockroachDB [v20.2.0 to v20.2.8.](https://www.cockroachlabs.c
 
 ## Statement
 
-This bug was resolved by [#62944].
+This bug was resolved by #62944.
 
-The fix has been applied to the maintenance release v20.2.9 of CockroachDB by PR [#63153].
+The fix has been applied to the maintenance release v20.2.9 of CockroachDB by PR #63153.
 
-This public issue is tracked by [#62842].
+This public issue is tracked by #62842.
 
 ## Detection
 
@@ -92,6 +92,3 @@ Users of CockroachDB v20.2 are encouraged to upgrade to v20.2.9 or a later versi
 All deployments running CockroachDB versions 20.2.0 up to and including 20.2.8 are affected.
 Cockroach Labs acknowledges the issue and has applied a fix that is available in subsequent maintenance releases for 20.2 (20.2.9 and later).
 
-[#62842]: https://github.com/cockroachdb/cockroach/issues/62842
-[#62944]: https://github.com/cockroachdb/cockroach/pull/62944
-[#63153]: https://github.com/cockroachdb/cockroach/pull/63153
diff --git a/src/current/advisories/a63162.md b/src/current/advisories/a63162.md
index 54563620db0..d73a7dc1d0a 100644
--- a/src/current/advisories/a63162.md
+++ b/src/current/advisories/a63162.md
@@ -31,10 +31,10 @@ In addition to resolving the issue when creating incremental backups, these fixe
 
 The following GitHub issues and pull requests describe the issues and fixes:
 
-- [#63162](https://github.com/cockroachdb/cockroach/issues/63162)
-- [#62564](https://github.com/cockroachdb/cockroach/issues/62564)
-- [#62565](https://github.com/cockroachdb/cockroach/issues/62565)
-- [#62572](https://github.com/cockroachdb/cockroach/pull/62572)
+- #63162
+- #62564
+- #62565
+- #62572
 
 Questions about this technical alert can be directed to our [support team](https://support.cockroachlabs.com/), or to your customer success contact at Cockroach Labs.
 
diff --git a/src/current/advisories/a64325.md b/src/current/advisories/a64325.md
index 3a21a330f68..aa1cb35c38a 100644
--- a/src/current/advisories/a64325.md
+++ b/src/current/advisories/a64325.md
@@ -28,11 +28,11 @@ This is a rare scenario that can only be encountered if a number of conditions a
 This issue affects CockroachDB [versions](/docs/releases/) 20.1 and later.
 
 ## Statement
-This is resolved in CockroachDB by PR [#64324], which fixes the race condition between read requests and replica removal.
+This is resolved in CockroachDB by PR #64324, which fixes the race condition between read requests and replica removal.
 
 The fix has been applied to maintenance releases of CockroachDB v20.1, v20.2, and v21.1.
 
-This public issue is tracked by [#64325].
+This public issue is tracked by #64325.
 
 ## Mitigation
 
@@ -42,5 +42,3 @@ Users of CockroachDB v20.1 or v20.2 are encouraged to upgrade to v20.1.16, v20.2
 
 This issue may impact all read operations, while the window of opportunity to see is very limited it may have happened to without your knowledge. Because this issue affects reads, it may impact backups. Our [support team](https://support.cockroachlabs.com/) has tools to detect and troubleshoot this condition. If you would like help to check this in your environment, please contact them.
 
-[#64324]: https://github.com/cockroachdb/cockroach/pull/64324
-[#64325]: https://github.com/cockroachdb/cockroach/issues/64325
diff --git a/src/current/advisories/a68005.md b/src/current/advisories/a68005.md
index 3d08966caea..003a5268a86 100644
--- a/src/current/advisories/a68005.md
+++ b/src/current/advisories/a68005.md
@@ -16,11 +16,11 @@ Cockroach Labs has discovered a bug in which setting the `sql.trace.txn.enable_t
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#68002], which fixes the miuse of the tracing API.
+This is resolved in CockroachDB by PR #68002, which fixes the miuse of the tracing API.
 
 The fix has been applied to maintenance releases of CockroachDB v21.1, and is available in v21.1.7+.
 
-This bug is publicly tracked as [#68005].
+This bug is publicly tracked as #68005.
 
 ## Mitigation
 
@@ -32,5 +32,3 @@ Setting the `sql.trace.txn.enable_threshold` cluster setting to a non-0 value ca
 
 All deployments running CockroachDB v21.1.0 to v21.1.6 are affected. Upgrading a v20.2 cluster to an affected version of v21.1 that has the cluster already set will also be affected by the bug. Such an upgrade can be mitigated by rolling back to v20.2 unless the version upgrade was finalized. Cockroach Labs acknowledges the issue and has issued a fix that is available in v21.1.7.
 
-[#68002]: https://github.com/cockroachdb/cockroach/pull/68002
-[#68005]: https://github.com/cockroachdb/cockroach/issues/68005
diff --git a/src/current/advisories/a69874.md b/src/current/advisories/a69874.md
index 95510c36a97..bf8a68b575d 100644
--- a/src/current/advisories/a69874.md
+++ b/src/current/advisories/a69874.md
@@ -18,7 +18,7 @@ A bug was introduced in CockroachDB v21.1.8 which would prevent downgrading to e
 
 Patch releases are expected to maintain upgrade/downgrade/mixed-version compatibility, so a user can upgrade (for example) from v21.1.3 to v21.1.7 and back down to v21.1.5 at will.
 
-A recent change was [backported to the release-21.1 branch](https://github.com/cockroachdb/cockroach/pull/69157/files#diff-8f32466c40e6960b988c87d7e2453c01a591d420af123f0963959da8e580f2e4), that included a new cluster version, which was then included in the v21.1.8 release. This means a cluster that deploys v21.1.8 (and has the default automatic finalization enabled) will be unable to downgrade to v21.1.7 or earlier.
+A recent change was backported to the release-21.1 branch, that included a new cluster version, which was then included in the v21.1.8 release. This means a cluster that deploys v21.1.8 (and has the default automatic finalization enabled) will be unable to downgrade to v21.1.7 or earlier.
 
 A future release, currently in development, will resolve this issue.
 
@@ -34,4 +34,4 @@ If you are running v21.1.7 or earlier, no action is necessary.
 
 Users who are running v21.1.8 cannot downgrade to a previous patch release.
 
-Tracking issue: [#69874](https://github.com/cockroachdb/cockroach/issues/69874)
+Tracking issue: #69874
diff --git a/src/current/advisories/a71002.md b/src/current/advisories/a71002.md
index 9d927cc6600..5522d0f118e 100644
--- a/src/current/advisories/a71002.md
+++ b/src/current/advisories/a71002.md
@@ -21,9 +21,9 @@ Only CockroachDB version 21.1.9 is affected by this bug.
 
 ## Statement
 
-This bug was resolved in CockroachDB by PR [71035](https://github.com/cockroachdb/cockroach/pull/71035).
+This bug was resolved in CockroachDB by PR 71035.
 The fix has been applied to CockroachDB 21.1.10.
-This public issue is tracked by [71002](https://github.com/cockroachdb/cockroach/issues/71002).
+This public issue is tracked by 71002.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a71553.md b/src/current/advisories/a71553.md
index e079508e28f..5dcd0c3c48a 100644
--- a/src/current/advisories/a71553.md
+++ b/src/current/advisories/a71553.md
@@ -19,11 +19,11 @@ CockroachDB versions 20.2 and 21.1 are affected by this bug, until maintenance v
 
 ## Statement
 
-This bug was resolved in CockroachDB by PR [71545](https://github.com/cockroachdb/cockroach/pull/71545), which corrects the bug in the vectorized engine that caused the database to return incorrect results when reading unique secondary indexes that were created as a result of an `ALTER PRIMARY KEY`.
+This bug was resolved in CockroachDB by PR 71545, which corrects the bug in the vectorized engine that caused the database to return incorrect results when reading unique secondary indexes that were created as a result of an `ALTER PRIMARY KEY`.
 
 The fix has been applied to maintenance versions 20.2.18 and 21.1.12 of CockroachDB.
 
-This public issue is tracked by issue [71553](https://github.com/cockroachdb/cockroach/issues/71553).
+This public issue is tracked by issue 71553.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a71655.md b/src/current/advisories/a71655.md
index 6ce627e6d6c..571af292182 100644
--- a/src/current/advisories/a71655.md
+++ b/src/current/advisories/a71655.md
@@ -20,11 +20,11 @@ CockroachDB versions 19.2, 20.1, 20.2, and 21.1 are affected by this bug. Versio
 
 ## Statement
 
-This bug was resolved in CockroachDB by PR [71758](https://github.com/cockroachdb/cockroach/pull/71758), which corrects the bug by no longer planning zigzag joins when they produce incorrect results.
+This bug was resolved in CockroachDB by PR 71758, which corrects the bug by no longer planning zigzag joins when they produce incorrect results.
 
 The fix has been applied to maintenance release 20.2.18. The fix will be applied to an upcoming maintenance version for 21.1. See [Mitigation](#mitigation) for the steps to avoid the issue until a patch is released.
 
-This public issue is tracked by [71655](https://github.com/cockroachdb/cockroach/pull/71758).
+This public issue is tracked by 71655.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a72839.md b/src/current/advisories/a72839.md
index 0b517be01d2..a016f3f23e9 100644
--- a/src/current/advisories/a72839.md
+++ b/src/current/advisories/a72839.md
@@ -24,7 +24,7 @@ Newly created (non-upgrade) clusters are unaffected.
 
 ## Statement
 
-Cockroach Labs has diagnosed the above-described problem, and is tracking progress in GitHub issue [#72839](https://github.com/cockroachdb/cockroach/issues/72839).
+Cockroach Labs has diagnosed the above-described problem, and is tracking progress in GitHub issue #72839.
 
 We plan to improve this issue in an expedited patch version v21.2.1 in the coming days. This advisory will be updated after that release.
 
diff --git a/src/current/advisories/a73024.md b/src/current/advisories/a73024.md
index c95f511e574..d09f69df2fd 100644
--- a/src/current/advisories/a73024.md
+++ b/src/current/advisories/a73024.md
@@ -18,11 +18,11 @@ This issue only occurs against `REGIONAL BY ROW` tables in CockroachDB 21.2.0.
 
 ## Statement
 
-This is resolved in CockroachDB by PR [73040](https://github.com/cockroachdb/cockroach/pull/73040), which disables the incorrect planning of locality-optimized semi-joins with ON-conditions.
+This is resolved in CockroachDB by PR 73040, which disables the incorrect planning of locality-optimized semi-joins with ON-conditions.
 
 The fix has been applied to [21.2.1](https://www.cockroachlabs.com/docs/releases/v21.2#v21-2-1).
 
-This issue is tracked by public issue [73024](https://github.com/cockroachdb/cockroach/issues/73024).
+This issue is tracked by public issue 73024.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a73629.md b/src/current/advisories/a73629.md
index 8fb64494143..ab2f5e30d45 100644
--- a/src/current/advisories/a73629.md
+++ b/src/current/advisories/a73629.md
@@ -18,11 +18,11 @@ The issue does not exist on 20.2 and prior versions.
 
 ## Statement
 
-This is resolved in CockroachDB by PR [73630](https://github.com/cockroachdb/cockroach/pull/73630), which prevents queries over tables with a `DEFAULT` partition from causing the internal error “empty Datums being compared to other”.
+This is resolved in CockroachDB by PR 73630, which prevents queries over tables with a `DEFAULT` partition from causing the internal error “empty Datums being compared to other”.
 
 The fix has been applied to maintenance releases of CockroachDB 21.1.13 and 21.2.3.
 
-This issue is tracked by public issue [73629](https://github.com/cockroachdb/cockroach/issues/73629).
+This issue is tracked by public issue 73629.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a74385.md b/src/current/advisories/a74385.md
index 85cff2a1855..138e91792a2 100644
--- a/src/current/advisories/a74385.md
+++ b/src/current/advisories/a74385.md
@@ -22,15 +22,15 @@ CockroachDB versions 21.1 and 21.2 are affected by this bug until maintenance ve
 
 ## Statement
 
-This bug was resolved in CockroachDB by [PR 74431](https://github.com/cockroachdb/cockroach/pull/74431).
+This bug was resolved in CockroachDB by PR 74431.
 The fix has been applied to maintenance versions 21.1.13 and 21.2.4 of CockroachDB.
-The public issue is tracked by issue [74385](https://github.com/cockroachdb/cockroach/issues/74385).
+The public issue is tracked by issue 74385.
 
 ## Mitigation
 
 Users of CockroachDB are encouraged to upgrade to a maintenance version with the fix applied. Once the upgrade is complete, all partial indexes should be dropped and recreated to ensure that no indexes remain corrupt.
 
-To avoid the issue without upgrading, users should remove or alter the `WHERE` clause of partial indexes such that no table has two or more partial indexes with the same `WHERE` clause. Be aware that removing or altering unique partial indexes can change their uniqueness guarantees. Workarounds are discussed in more detail in issue [74385](https://github.com/cockroachdb/cockroach/issues/74385).
+To avoid the issue without upgrading, users should remove or alter the `WHERE` clause of partial indexes such that no table has two or more partial indexes with the same `WHERE` clause. Be aware that removing or altering unique partial indexes can change their uniqueness guarantees. Workarounds are discussed in more detail in issue 74385.
 
 ## Impact
 
diff --git a/src/current/advisories/a74736.md b/src/current/advisories/a74736.md
index f4a12f17d0f..5238fda0086 100644
--- a/src/current/advisories/a74736.md
+++ b/src/current/advisories/a74736.md
@@ -24,11 +24,11 @@ Versions affected: v21.2.0 - v21.2.4
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#75475](https://github.com/cockroachdb/cockroach/pull/75475) which fixes the metadata returned by the KV layer when some of the isolated key spans are not scanned.
+This is resolved in CockroachDB by PR #75475 which fixes the metadata returned by the KV layer when some of the isolated key spans are not scanned.
 
 The fix has been applied to maintenance release v21.2.5.
 
-This public issue is tracked by [#74736](https://github.com/cockroachdb/cockroach/issues/74736).
+This public issue is tracked by #74736.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a75758.md b/src/current/advisories/a75758.md
index 14779e99049..b4b2b7f1d45 100644
--- a/src/current/advisories/a75758.md
+++ b/src/current/advisories/a75758.md
@@ -18,9 +18,9 @@ This issue is fixed in [v20.2.19](https://www.cockroachlabs.com/docs/releases/v2
 
 ## Statement
 
-This issue is resolved in CockroachDB by [#75814](https://github.com/cockroachdb/cockroach/pull/75814). The fix has been applied to maintenance versions [v20.2.19](https://www.cockroachlabs.com/docs/releases/v20.2#v20-2-19), [v21.1.14](https://www.cockroachlabs.com/docs/releases/v21.1#v21-1-14), and [v21.2.5](https://www.cockroachlabs.com/docs/releases/v21.2#v21-2-5) of CockroachDB.
+This issue is resolved in CockroachDB by #75814. The fix has been applied to maintenance versions [v20.2.19](https://www.cockroachlabs.com/docs/releases/v20.2#v20-2-19), [v21.1.14](https://www.cockroachlabs.com/docs/releases/v21.1#v21-1-14), and [v21.2.5](https://www.cockroachlabs.com/docs/releases/v21.2#v21-2-5) of CockroachDB.
 
-This public issue is tracked as [#75758](https://github.com/cockroachdb/cockroach/issues/75758).
+This public issue is tracked as #75758.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a76522.md b/src/current/advisories/a76522.md
index 9cfb09b8346..6ffc3f3f46f 100644
--- a/src/current/advisories/a76522.md
+++ b/src/current/advisories/a76522.md
@@ -20,9 +20,9 @@ This issue is fixed in [v21.1.16](https://www.cockroachlabs.com/docs/releases/v2
 
 ## Statement
 
-This issue is resolved in CockroachDB by [#76334](https://github.com/cockroachdb/cockroach/pull/76334). The fix has been applied to maintenance versions [v21.1.16](https://www.cockroachlabs.com/docs/releases/v21.1#v21-1-16) and v21.2.7 of CockroachDB.
+This issue is resolved in CockroachDB by #76334. The fix has been applied to maintenance versions [v21.1.16](https://www.cockroachlabs.com/docs/releases/v21.1#v21-1-16) and v21.2.7 of CockroachDB.
 
-This public issue is tracked as [#76522](https://github.com/cockroachdb/cockroach/issues/76522).
+This public issue is tracked as #76522.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a78681.md b/src/current/advisories/a78681.md
index 9aee6383e6a..9722a17cf2c 100644
--- a/src/current/advisories/a78681.md
+++ b/src/current/advisories/a78681.md
@@ -21,11 +21,11 @@ The optimizer has been found to create logically incorrect query plans in some c
 
 ## Statement
 
-The bug is resolved in CockroachDB PR [78685](https://github.com/cockroachdb/cockroach/pull/78685).
+The bug is resolved in CockroachDB PR 78685.
 
 The fix has been applied to maintenance versions 21.1.17 and 21.2.8 of CockroachDB.
 
-This public issue is tracked by [78681](https://github.com/cockroachdb/cockroach/issues/78681).
+This public issue is tracked by 78681.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a79066.md b/src/current/advisories/a79066.md
index 217ffa7f51d..99181d937a8 100644
--- a/src/current/advisories/a79066.md
+++ b/src/current/advisories/a79066.md
@@ -18,11 +18,11 @@ A bug in initialization of store and data keys on node restart led to data key r
 
 ## Statement
 
-This is resolved in CockroachDB by [PR 80114](https://github.com/cockroachdb/cockroach/pull/80114).
+This is resolved in CockroachDB by PR 80114.
 
 The fix has been applied to maintenance versions v21.1.19 and v21.2.10 of CockroachDB.
 
-This public issue is tracked by [79066](https://github.com/cockroachdb/cockroach/issues/79066).
+This public issue is tracked by 79066.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a79281.md b/src/current/advisories/a79281.md
index 6ae64379bdd..91f0439c4b4 100644
--- a/src/current/advisories/a79281.md
+++ b/src/current/advisories/a79281.md
@@ -18,10 +18,10 @@ Affected versions: v21.2.0 to v21.2.7
 
 ## Statement
 
-This is resolved in CockroachDB by [PR 79293](https://github.com/cockroachdb/cockroach/pull/79293).
+This is resolved in CockroachDB by PR 79293.
 The fix was applied in the maintenance release of [CockroachDB v21.2.8](https://www.cockroachlabs.com/docs/releases/v21.2#v21-2-8).
 
-This public issue is tracked by [79281](https://github.com/cockroachdb/cockroach/issues/79281).
+This public issue is tracked by 79281.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a79384.md b/src/current/advisories/a79384.md
index f3d1983adc9..6a8fbfb4cd0 100644
--- a/src/current/advisories/a79384.md
+++ b/src/current/advisories/a79384.md
@@ -21,11 +21,11 @@ The optimizer has been found to create logically incorrect query plans in some c
 
 ## Statement
 
-This is resolved in CockroachDB by [PR 79389](https://github.com/cockroachdb/cockroach/pull/79389).
+This is resolved in CockroachDB by PR 79389.
 
 The fix has been applied to maintenance versions [v21.1.18](https://www.cockroachlabs.com/docs/releases/v21.1#v21-1-18) and [v21.2.9](https://www.cockroachlabs.com/docs/releases/v21.2#v21-2-9) of CockroachDB.
 
-This public issue is tracked by [79384](https://github.com/cockroachdb/cockroach/issues/79384).
+This public issue is tracked by 79384.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a81315.md b/src/current/advisories/a81315.md
index 7e8e17ee673..55881d68804 100644
--- a/src/current/advisories/a81315.md
+++ b/src/current/advisories/a81315.md
@@ -18,11 +18,11 @@ For example, executing a prepared statement of the form `SELECT ... FROM ... WHE
 
 ## Statement
 
-This is resolved in CockroachDB by [PR 81331](https://github.com/cockroachdb/cockroach/pull/81331).
+This is resolved in CockroachDB by PR 81331.
 
 The fix has been applied to maintenance versions [v21.2.11](https://www.cockroachlabs.com/docs/releases/v21.2#v21-2-11) and [v22.1.1](https://www.cockroachlabs.com/docs/releases/v22.1#v22-1-1) of CockroachDB.
 
-This public issue is tracked by [81315](https://github.com/cockroachdb/cockroach/issues/81315).
+This public issue is tracked by 81315.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a81448.md b/src/current/advisories/a81448.md
index 30a58211e5e..bddb1bc7e7e 100644
--- a/src/current/advisories/a81448.md
+++ b/src/current/advisories/a81448.md
@@ -32,11 +32,11 @@ This is evidenced by executing the queries `SELECT b FROM t@t_pkey` and `SELECT
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#81486](https://github.com/cockroachdb/cockroach/pull/81486), which fixes the incorrect backfill logic.
+This is resolved in CockroachDB by PR #81486, which fixes the incorrect backfill logic.
 
 The fix is applied to CockroachDB maintenance version v22.1.1, and is expected to be applied to maintenance version v21.2.13.
 
-This public issue is tracked by [#81448](https://github.com/cockroachdb/cockroach/issues/81448).
+This public issue is tracked by #81448.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a81968.md b/src/current/advisories/a81968.md
index c09856bd37b..23933ee76a7 100644
--- a/src/current/advisories/a81968.md
+++ b/src/current/advisories/a81968.md
@@ -16,11 +16,11 @@ In CockroachDB v22.1.0, executing a [left outer join](https://www.cockroachlabs.
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#82054](https://github.com/cockroachdb/cockroach/pull/82054).
+This is resolved in CockroachDB by PR #82054.
 
 The fix has been applied to the maintenance release of CockroachDB [v22.1.1](https://www.cockroachlabs.com/docs/releases/v22.1#v22-1-1).
 
-This issue is tracked by [#81968](https://github.com/cockroachdb/cockroach/issues/81968).
+This issue is tracked by #81968.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a82079.md b/src/current/advisories/a82079.md
index 0d94889943e..9b593281dc1 100644
--- a/src/current/advisories/a82079.md
+++ b/src/current/advisories/a82079.md
@@ -66,9 +66,9 @@ If you get back a non-zero result, your cluster has the problem described in thi
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#82087](https://github.com/cockroachdb/cockroach/pull/82087) which fixes the missing removal of back-references to the materialized view.
+This is resolved in CockroachDB by PR #82087 which fixes the missing removal of back-references to the materialized view.
 
-The fix has been applied to maintenance releases of CockroachDB v21.2.13 and v22.1.1. This public issue is tracked by [#82079](https://github.com/cockroachdb/cockroach/pull/82079).
+The fix has been applied to maintenance releases of CockroachDB v21.2.13 and v22.1.1. This public issue is tracked by #82079.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a82309.md b/src/current/advisories/a82309.md
index 18dd8b52e6d..9fe4043f1d7 100644
--- a/src/current/advisories/a82309.md
+++ b/src/current/advisories/a82309.md
@@ -30,11 +30,11 @@ If you had changefeeds running in v21.2.x, and have already upgraded to v22.1.0,
 
 If the changefeeds run with the [`resolved` option](https://www.cockroachlabs.com/docs/v22.1/create-changefeed#resolved-option), your sink will continue receiving `RESOLVED` messages but will not receive any data messages. Although changefeeds will **appear** to be up to date, these `RESOLVED` messages are incorrect and should be disregarded.
 
-This is resolved in CockroachDB by PR [#82312](https://github.com/cockroachdb/cockroach/pull/82312).
+This is resolved in CockroachDB by PR #82312.
 
 The fix has been applied to maintenance version [v22.1.1](https://www.cockroachlabs.com/docs/releases/v22.1#v22-1-1) of CockroachDB.
 
-This public issue is tracked by [#82309](https://github.com/cockroachdb/cockroach/issues/82309).
+This public issue is tracked by #82309.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a82576.md b/src/current/advisories/a82576.md
index e1812df142d..25fdc32c2bb 100644
--- a/src/current/advisories/a82576.md
+++ b/src/current/advisories/a82576.md
@@ -98,11 +98,11 @@ If you get back a non-zero result, your cluster has the problem described in thi
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#82833](https://github.com/cockroachdb/cockroach/pull/82833) which relaxes the validation checks which detect descriptor corruption.
+This is resolved in CockroachDB by PR #82833 which relaxes the validation checks which detect descriptor corruption.
 
 The fix has been applied to maintenance release [v22.1.3](https://www.cockroachlabs.com/docs/releases/v22.1#v22-1-3) of CockroachDB.
 
-This public issue is tracked by [#82576](https://github.com/cockroachdb/cockroach/issues/82576).
+This public issue is tracked by #82576.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a84144.md b/src/current/advisories/a84144.md
index a5e0271a51c..26b04780a94 100644
--- a/src/current/advisories/a84144.md
+++ b/src/current/advisories/a84144.md
@@ -40,12 +40,12 @@ ERROR: failed to construct index entries during backfill: error decoding 4 bytes
 
 ## Statement
 
-This is resolved in CockroachDB by PRs [#84339](https://github.com/cockroachdb/cockroach/pull/84339) and [#84349](https://github.com/cockroachdb/cockroach/pull/84349) which ensure, respectively, that:
+This is resolved in CockroachDB by PRs #84339 and #84349 which ensure, respectively, that:
 back-references to tables using the [region enum](https://www.cockroachlabs.com/docs/v22.1/alter-table#crdb_region) type are correctly updated in the region enum type descriptor when performing `ALTER TABLE … SET LOCALITY REGIONAL BY ROW;` any existing type descriptors which are already missing these back-references are updated prior to `ALTER DATABASE … DROP [SUPER] REGION` so as to ensure its correct behavior.
 
 The fix has been applied to the maintenance release of CockroachDB [v22.1.4](https://www.cockroachlabs.com/docs/releases/v22.1#v22-1-4).
 
-This public issue is tracked by [#84144](https://github.com/cockroachdb/cockroach/issues/84144).
+This public issue is tracked by #84144.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a88042.md b/src/current/advisories/a88042.md
index 3f5dc8b21a0..df28e306eb4 100644
--- a/src/current/advisories/a88042.md
+++ b/src/current/advisories/a88042.md
@@ -26,17 +26,17 @@ If a backup chain starts from a full backup subsequent to the `IMPORT INTO` job
 
 The technical details can be found in the following GitHub issues:
 
-- [#88042](https://github.com/cockroachdb/cockroach/issues/88042)
-- [#88043](https://github.com/cockroachdb/cockroach/issues/88043)
+- #88042
+- #88043
 
 
 ## Statement
 
-This is resolved in CockroachDB by [#87312](https://github.com/cockroachdb/cockroach/pull/87312).
+This is resolved in CockroachDB by #87312.
 
 The fix has been applied to the maintenance release of CockroachDB [v22.1.9](https://www.cockroachlabs.com/docs/releases/v22.1#v22-1-9) and CockroachDB [v21.2.17](https://www.cockroachlabs.com/docs/releases/v21.2#v21-2-17).
 
-This public issue is tracked by [#87305](https://github.com/cockroachdb/cockroach/issues/87305).
+This public issue is tracked by #87305.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a88407.md b/src/current/advisories/a88407.md
index 1b63499cf42..5cb433029f9 100644
--- a/src/current/advisories/a88407.md
+++ b/src/current/advisories/a88407.md
@@ -16,11 +16,11 @@ In CockroachDB [v22.1.0](https://www.cockroachlabs.com/docs/releases/v22.1#v22-1
 
 ## Statement
 
-This is resolved in CockroachDB by [#88079](https://github.com/cockroachdb/cockroach/pull/88079).
+This is resolved in CockroachDB by #88079.
 
 The fix has been applied to the maintenance release of CockroachDB [v22.1.8](https://www.cockroachlabs.com/docs/releases/v22.1#v22-1-8).
 
-This public issue is tracked by [#88047](https://github.com/cockroachdb/cockroach/pull/88047).
+This public issue is tracked by #88047.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a88993.md b/src/current/advisories/a88993.md
index f3c072a9f14..f9fc5a5d7c0 100644
--- a/src/current/advisories/a88993.md
+++ b/src/current/advisories/a88993.md
@@ -22,11 +22,11 @@ This issue could also cause a query that performs an aggregation with min or max
 
 ## Statement
 
-This is resolved in CockroachDB by [#89113](https://github.com/cockroachdb/cockroach/pull/89113).
+This is resolved in CockroachDB by #89113.
 
 The fix has been applied to the maintenance release of CockroachDB [v22.1.9](https://www.cockroachlabs.com/docs/releases/v22.1#v22-1-9).
 
-This public issue is tracked by [#88993](https://github.com/cockroachdb/cockroach/pull/88993).
+This public issue is tracked by #88993.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a90146.md b/src/current/advisories/a90146.md
index 478f8948881..bc67dcb9a6a 100644
--- a/src/current/advisories/a90146.md
+++ b/src/current/advisories/a90146.md
@@ -18,11 +18,11 @@ The same issue may occur if a changefeed with [`schema_change_policy='stop'`](ht
 
 ## Statement
 
-This is resolved in CockroachDB by [#90241](https://github.com/cockroachdb/cockroach/pull/90241), which ensures all events correctly flush out of all buffers prior to the changefeed exiting.
+This is resolved in CockroachDB by #90241, which ensures all events correctly flush out of all buffers prior to the changefeed exiting.
 
 The fix has been applied to maintenance releases of CockroachDB [v22.1.10](https://www.cockroachlabs.com/docs/releases/v22.1#v22-1-10) and later.
 
-This public issue is tracked by [#90146](https://github.com/cockroachdb/cockroach/issues/90146).
+This public issue is tracked by #90146.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a93314.md b/src/current/advisories/a93314.md
index a1afcc9ce80..97ee35823af 100644
--- a/src/current/advisories/a93314.md
+++ b/src/current/advisories/a93314.md
@@ -29,11 +29,11 @@ $$ LANGUAGE SQL; -- CockroachDB cluster crashes when this query is run
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#94106](https://github.com/cockroachdb/cockroach/pull/94106) which fixes infinite recursion during the type hydration for catalog descriptors.
+This is resolved in CockroachDB by PR #94106 which fixes infinite recursion during the type hydration for catalog descriptors.
 
 The fix has been applied to maintenance releases of CockroachDB [v22.2.2](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-2) and later.
 
-This public issue is tracked by [#93314](https://github.com/cockroachdb/cockroach/issues/93314).
+This public issue is tracked by #93314.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a93398.md b/src/current/advisories/a93398.md
index 0bd40204aee..f1ff76ff64c 100644
--- a/src/current/advisories/a93398.md
+++ b/src/current/advisories/a93398.md
@@ -16,11 +16,11 @@ In all versions of CockroachDB from [v22.2.0-alpha.1](https://www.cockroachlabs.
 
 ## Statement
 
-This is resolved in CockroachDB by [#95398](https://github.com/cockroachdb/cockroach/pull/95398), which casts the `DEFAULT` expression to the correct type when backfilling a new column.
+This is resolved in CockroachDB by #95398, which casts the `DEFAULT` expression to the correct type when backfilling a new column.
 
 The fix has been applied to the maintenance release of CockroachDB [v22.2.5](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-5).
 
-This public issue is tracked by [#93398](https://github.com/cockroachdb/cockroach/issues/93398).
+This public issue is tracked by #93398.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a96465.md b/src/current/advisories/a96465.md
index d115480db6e..0b56ceadb9b 100644
--- a/src/current/advisories/a96465.md
+++ b/src/current/advisories/a96465.md
@@ -16,12 +16,12 @@ The global [`NOSQLLOGIN` privilege](https://www.cockroachlabs.com/docs/v22.2/sec
 
 ## Statement
 
-This is resolved in CockroachDB by [#96466](https://github.com/cockroachdb/cockroach/pull/96466)
-and backported in [#96520](https://github.com/cockroachdb/cockroach/pull/96520)) by fixing the logic that inspects the `NOSQLLOGIN` privilege.
+This is resolved in CockroachDB by #96466
+and backported in #96520) by fixing the logic that inspects the `NOSQLLOGIN` privilege.
 
 The fix has been applied to maintenance releases of CockroachDB [v22.2.4](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-4).
 
-This public issue is tracked by https://github.com/cockroachdb/cockroach/issues/96465. 
+This public issue is tracked by cockroach#96465. 
 
 ## Mitigation
 
diff --git a/src/current/advisories/a96924.md b/src/current/advisories/a96924.md
index 6007d5448ed..c783d647dae 100644
--- a/src/current/advisories/a96924.md
+++ b/src/current/advisories/a96924.md
@@ -18,11 +18,11 @@ This problem exists in all versions of CockroachDB since the introduction of [pa
 
 ## Statement
 
-This is resolved in CockroachDB by [#97372](https://github.com/cockroachdb/cockroach/pull/97372), which disallows dropping columns that are referenced by a partial index.
+This is resolved in CockroachDB by #97372, which disallows dropping columns that are referenced by a partial index.
 
 This fix has been applied to maintenance releases of CockroachDB [v22.1.16](https://www.cockroachlabs.com/docs/releases/v22.1#v22-1-16) and [v22.2.6](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-6)).
 
-This public issue is tracked by [#96924](https://github.com/cockroachdb/cockroach/issues/96924).
+This public issue is tracked by #96924.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a97090.md b/src/current/advisories/a97090.md
index ec1d0a42361..93bd41d5c07 100644
--- a/src/current/advisories/a97090.md
+++ b/src/current/advisories/a97090.md
@@ -19,11 +19,11 @@ For example, if a table `t` contained indexes `INDEX (a ASC, c DESC)` and `INDEX
 
 ## Statement
 
-This is resolved in CockroachDB by [#97151](https://github.com/cockroachdb/cockroach/pull/97151), which prevents the [optimizer](https://www.cockroachlabs.com/docs/v22.2/cost-based-optimizer) from planning zigzag joins when any columns in the matching suffix between two candidate indexes have different directions.
+This is resolved in CockroachDB by #97151, which prevents the [optimizer](https://www.cockroachlabs.com/docs/v22.2/cost-based-optimizer) from planning zigzag joins when any columns in the matching suffix between two candidate indexes have different directions.
 
 The fix has been applied to maintenance releases of CockroachDB [v22.1.16](https://www.cockroachlabs.com/docs/releases/v22.1#v22-1-16) and [v22.2.6](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-6).
 
-This public issue is tracked by [#97090](https://github.com/cockroachdb/cockroach/issues/97090).
+This public issue is tracked by #97090.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a97178.md b/src/current/advisories/a97178.md
index 22238ffde6b..eb474f34704 100644
--- a/src/current/advisories/a97178.md
+++ b/src/current/advisories/a97178.md
@@ -21,9 +21,9 @@ This issue affects only v22.2.4 clusters.
 
 Cockroach Labs has withdrawn v22.2.4, and it can no longer be downloaded.
 
-The issue is resolved in CockroachDB v22.2.5 by PR [#97183](https://github.com/cockroachdb/cockroach/pull/97183).
+The issue is resolved in CockroachDB v22.2.5 by PR #97183.
 
-This public issue is tracked by [#97178](https://github.com/cockroachdb/cockroach/issues/97178).
+This public issue is tracked by #97178.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a97932.md b/src/current/advisories/a97932.md
index 4f2cdfd2e57..21f56dcd340 100644
--- a/src/current/advisories/a97932.md
+++ b/src/current/advisories/a97932.md
@@ -16,9 +16,9 @@ Starting in CockroachDB v22.2.0 and above, CockroachDB switched to using the [SC
 
 ## Statement
 
-This is resolved in CockroachDB by PR [98254](https://github.com/cockroachdb/cockroach/pull/98254), which sets the default hash cost value to `10610` using the cluster setting `server.user_login.password_hashes.default_cost.scram_sha_256`. This fix has been released in [22.2.7](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-7). 
+This is resolved in CockroachDB by PR 98254, which sets the default hash cost value to `10610` using the cluster setting `server.user_login.password_hashes.default_cost.scram_sha_256`. This fix has been released in [22.2.7](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-7). 
 
-The public issue is tracked by [97932](https://github.com/cockroachdb/cockroach/issues/97932).
+The public issue is tracked by 97932.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a98779.md b/src/current/advisories/a98779.md
index 9a71753fe59..143aeba51c8 100644
--- a/src/current/advisories/a98779.md
+++ b/src/current/advisories/a98779.md
@@ -18,11 +18,11 @@ A resumption could occur due to manual user action, such as [pausing](https://ww
 
 ## Statement
 
-This is resolved in CockroachDB by [#99066](https://github.com/cockroachdb/cockroach/pull/99066), which removes the incorrect optimization, and reverts back to the behavior of v22.2.5.
+This is resolved in CockroachDB by #99066, which removes the incorrect optimization, and reverts back to the behavior of v22.2.5.
 
 The fix has been applied to maintenance releases of CockroachDB [v22.2.7](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-7) and later. This problem can also be mitigated immediately by updating the `bulkio.restore.use_simple_import_spans` cluster setting. See the following [Mitigation](#mitigation) section for details.
 
-This public issue is tracked by [#98779](https://github.com/cockroachdb/cockroach/issues/98779).
+This public issue is tracked by #98779.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a99049.md b/src/current/advisories/a99049.md
index d68f6030604..83fa1a49a9b 100644
--- a/src/current/advisories/a99049.md
+++ b/src/current/advisories/a99049.md
@@ -20,11 +20,11 @@ This vulnerability affects all of the following CockroachDB versions with this f
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#99051](https://github.com/cockroachdb/cockroach/pull/99051), which fixes privilege escalation by correctly checking the SQL user’s privileges before granting access to the statement diagnostic bundle.
+This is resolved in CockroachDB by PR #99051, which fixes privilege escalation by correctly checking the SQL user’s privileges before granting access to the statement diagnostic bundle.
 
 The fix has been applied to maintenance releases of CockroachDB: [v22.1.18](https://www.cockroachlabs.com/docs/releases/v22.1#v22-1-18) and [v22.2.7](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-7).
 
-This public issue is tracked by [#99049](https://github.com/cockroachdb/cockroach/issues/99049).
+This public issue is tracked by #99049.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a99561.md b/src/current/advisories/a99561.md
index e83273d55fd..7dd2b85f876 100644
--- a/src/current/advisories/a99561.md
+++ b/src/current/advisories/a99561.md
@@ -24,11 +24,11 @@ If you have gone through the following sequence of steps, you are potentially at
 
 ## Statement
 
-This is resolved in CockroachDB by [#105828](https://github.com/cockroachdb/cockroach/pull/105828), which makes CockroachDB automatically repair the encoding type for secondary indexes when accessing the table. In summary, this encoding type fix will prevent this issue from occurring, and additional validation will be added to prevent data loss.
+This is resolved in CockroachDB by #105828, which makes CockroachDB automatically repair the encoding type for secondary indexes when accessing the table. In summary, this encoding type fix will prevent this issue from occurring, and additional validation will be added to prevent data loss.
 
 The fix has been applied to [v22.2.12](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-12) and [v23.1.6](https://www.cockroachlabs.com/docs/releases/v23.1#v23-1-6).
 
-This public issue is tracked by [#99561](https://github.com/cockroachdb/cockroach/issues/99561).
+This public issue is tracked by #99561.
 
 ## Mitigation
 
diff --git a/src/current/advisories/a99796.md b/src/current/advisories/a99796.md
index 146c1b0bde2..0a6cde9b43f 100644
--- a/src/current/advisories/a99796.md
+++ b/src/current/advisories/a99796.md
@@ -20,11 +20,11 @@ This vulnerability affects all of the following CockroachDB versions: v22.2.0 to
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#99953](https://github.com/cockroachdb/cockroach/pull/99953), which adds validation to rollback operations to account for this situation.
+This is resolved in CockroachDB by PR #99953, which adds validation to rollback operations to account for this situation.
 
 The fix has been applied to maintenance releases of CockroachDB: [v22.2.8](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-8).
 
-This public issue is tracked by [#99796](https://github.com/cockroachdb/cockroach/issues/99796).
+This public issue is tracked by #99796.
 
 ## Mitigation