Final small changes

peachdawnleach · peachdawnleach · commit c129f84025be · 2025-10-28T14:35:18.000-04:00
Added some links
diff --git a/src/current/v24.3/physical-cluster-replication-overview.md b/src/current/v24.3/physical-cluster-replication-overview.md
@@ -71,7 +71,9 @@ Statement | Action
 
 ## Cluster versions and upgrades
 
-To safely perform a major version upgrade on a cluster with PCR, you must upgrade the standby cluster before the primary cluster to avoid version incompatibility. If you are using a reader virtual cluster (reader VC), you must upgrade it separately from the primary and standby clusters. For information about the upgrade process, refer to [Upgrade a Cluster Running PCR]({% link {{ page.version.version }}/upgrade-with-pcr.md %}).
+To safely perform a major version upgrade on a cluster with PCR, you must upgrade the standby cluster before the primary cluster to avoid version incompatibility. If you are using a reader virtual cluster (reader VC), you must upgrade it separately from the primary and standby clusters. 
+
+Follow the process described in [Upgrade a Cluster Running PCR]({% link {{ page.version.version }}/upgrade-with-pcr.md %}).
 
 ## Demo video
 
diff --git a/src/current/v24.3/upgrade-cockroach-version.md b/src/current/v24.3/upgrade-cockroach-version.md
@@ -5,7 +5,11 @@ toc: true
 docs_area: manage
 ---
 
-This page describes how major-version and patch upgrades work and shows how to upgrade a self-hosted CockroachDB. To upgrade a cluster in CockroachDB {{ site.data.products.cloud }}, refer to [Upgrade a cluster in CockroachDB {{ site.data.products.cloud }}]({% link cockroachcloud/upgrade-cockroach-version.md %}) instead.
+This page describes how major-version and patch upgrades work and shows how to upgrade a self-hosted CockroachDB. 
+
+To upgrade a cluster in CockroachDB {{ site.data.products.cloud }}, refer to [Upgrade a cluster in CockroachDB {{ site.data.products.cloud }}]({% link cockroachcloud/upgrade-cockroach-version.md %}) instead.
+
+To upgrade a cluster with with [physical cluster replication (PCR)]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}), refer to [Upgrade a Cluster Running PCR]({% link cockroachcloud/upgrade-with-pcr.md %}).
 
 ## Overview
 
diff --git a/src/current/v24.3/upgrade-with-pcr.md b/src/current/v24.3/upgrade-with-pcr.md
@@ -15,7 +15,7 @@ The entire standby cluster must be on the same major version as the primary clus
 
 ## Minor version upgrades
 
-Minor versions are not relevant when determining PCR compatibility. There is no need to consider PCR compatibility when upgrading to a specific minor version within a major version.
+Minor versions are not relevant when determining PCR compatibility. There is no need to consider PCR compatibility when upgrading to a specific minor version within a major version, so you can follow the normal [patch upgrade process]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#perform-a-patch-upgrade).
 
 ## Upgrade primary and standby clusters
 
diff --git a/src/current/v25.2/physical-cluster-replication-overview.md b/src/current/v25.2/physical-cluster-replication-overview.md
@@ -69,7 +69,9 @@ Statement | Action
 
 ## Cluster versions and upgrades
 
-To safely perform a major version upgrade on a cluster with PCR, you must upgrade the standby cluster before the primary cluster to avoid version incompatibility. If you are using a reader virtual cluster (reader VC), you must upgrade it separately from the primary and standby clusters. For information about the upgrade process, refer to [Upgrade a Cluster Running PCR]({% link {{ page.version.version }}/upgrade-with-pcr.md %}).
+To safely perform a major version upgrade on a cluster with PCR, you must upgrade the standby cluster before the primary cluster to avoid version incompatibility. If you are using a reader virtual cluster (reader VC), you must upgrade it separately from the primary and standby clusters. 
+
+Follow the process described in [Upgrade a Cluster Running PCR]({% link {{ page.version.version }}/upgrade-with-pcr.md %}).
 
 ## Demo video
 
diff --git a/src/current/v25.2/upgrade-cockroach-version.md b/src/current/v25.2/upgrade-cockroach-version.md
@@ -5,7 +5,11 @@ toc: true
 docs_area: manage
 ---
 
-This page describes how major-version and patch upgrades work and shows how to upgrade a self-hosted CockroachDB. To upgrade a cluster in CockroachDB {{ site.data.products.cloud }}, refer to [Upgrade a cluster in CockroachDB {{ site.data.products.cloud }}]({% link cockroachcloud/upgrade-cockroach-version.md %}) instead.
+This page describes how major-version and patch upgrades work and shows how to upgrade a self-hosted CockroachDB. 
+
+To upgrade a cluster in CockroachDB {{ site.data.products.cloud }}, refer to [Upgrade a cluster in CockroachDB {{ site.data.products.cloud }}]({% link cockroachcloud/upgrade-cockroach-version.md %}) instead.
+
+To upgrade a cluster with with [physical cluster replication (PCR)]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}), refer to [Upgrade a Cluster Running PCR]({% link cockroachcloud/upgrade-with-pcr.md %}).
 
 ## Overview
 
diff --git a/src/current/v25.2/upgrade-with-pcr.md b/src/current/v25.2/upgrade-with-pcr.md
@@ -15,7 +15,7 @@ The entire standby cluster must be on the same major version as the primary clus
 
 ## Minor version upgrades
 
-Minor versions are not relevant when determining PCR compatibility. There is no need to consider PCR compatibility when upgrading to a specific minor version within a major version.
+Minor versions are not relevant when determining PCR compatibility. There is no need to consider PCR compatibility when upgrading to a specific minor version within a major version, so you can follow the normal [patch upgrade process]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#perform-a-patch-upgrade).
 
 ## Upgrade primary and standby clusters
 
diff --git a/src/current/v25.3/physical-cluster-replication-overview.md b/src/current/v25.3/physical-cluster-replication-overview.md
@@ -69,7 +69,9 @@ Statement | Action
 
 ## Cluster versions and upgrades
 
-To safely perform a major version upgrade on a cluster with PCR, you must upgrade the standby cluster before the primary cluster to avoid version incompatibility. If you are using a reader virtual cluster (reader VC), you must upgrade it separately from the primary and standby clusters. For information about the upgrade process, refer to [Upgrade a Cluster Running PCR]({% link {{ page.version.version }}/upgrade-with-pcr.md %}).
+To safely perform a major version upgrade on a cluster with PCR, you must upgrade the standby cluster before the primary cluster to avoid version incompatibility. If you are using a reader virtual cluster (reader VC), you must upgrade it separately from the primary and standby clusters. 
+
+Follow the process described in [Upgrade a Cluster Running PCR]({% link {{ page.version.version }}/upgrade-with-pcr.md %}).
 
 ## Demo video
 
diff --git a/src/current/v25.3/upgrade-cockroach-version.md b/src/current/v25.3/upgrade-cockroach-version.md
@@ -5,7 +5,11 @@ toc: true
 docs_area: manage
 ---
 
-This page describes how major-version and patch upgrades work and shows how to upgrade a self-hosted CockroachDB. To upgrade a cluster in CockroachDB {{ site.data.products.cloud }}, refer to [Upgrade a cluster in CockroachDB {{ site.data.products.cloud }}]({% link cockroachcloud/upgrade-cockroach-version.md %}) instead.
+This page describes how major-version and patch upgrades work and shows how to upgrade a self-hosted CockroachDB. 
+
+To upgrade a cluster in CockroachDB {{ site.data.products.cloud }}, refer to [Upgrade a cluster in CockroachDB {{ site.data.products.cloud }}]({% link cockroachcloud/upgrade-cockroach-version.md %}) instead.
+
+To upgrade a cluster with with [physical cluster replication (PCR)]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}), refer to [Upgrade a Cluster Running PCR]({% link cockroachcloud/upgrade-with-pcr.md %}).
 
 ## Overview
 
diff --git a/src/current/v25.3/upgrade-with-pcr.md b/src/current/v25.3/upgrade-with-pcr.md
@@ -15,7 +15,7 @@ The entire standby cluster must be on the same major version as the primary clus
 
 ## Minor version upgrades
 
-Minor versions are not relevant when determining PCR compatibility. There is no need to consider PCR compatibility when upgrading to a specific minor version within a major version.
+Minor versions are not relevant when determining PCR compatibility. There is no need to consider PCR compatibility when upgrading to a specific minor version within a major version, so you can follow the normal [patch upgrade process]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#perform-a-patch-upgrade).
 
 ## Upgrade primary and standby clusters
 
diff --git a/src/current/v25.4/physical-cluster-replication-overview.md b/src/current/v25.4/physical-cluster-replication-overview.md
@@ -69,7 +69,9 @@ Statement | Action
 
 ## Cluster versions and upgrades
 
-To safely perform a major version upgrade on a cluster with PCR, you must upgrade the standby cluster before the primary cluster to avoid version incompatibility. If you are using a reader virtual cluster (reader VC), you must upgrade it separately from the primary and standby clusters. For information about the upgrade process, refer to [Upgrade a Cluster Running PCR]({% link {{ page.version.version }}/upgrade-with-pcr.md %}).
+To safely perform a major version upgrade on a cluster with PCR, you must upgrade the standby cluster before the primary cluster to avoid version incompatibility. If you are using a reader virtual cluster (reader VC), you must upgrade it separately from the primary and standby clusters. 
+
+Follow the process described in [Upgrade a Cluster Running PCR]({% link {{ page.version.version }}/upgrade-with-pcr.md %}).
 
 ## Demo video
 
diff --git a/src/current/v25.4/upgrade-cockroach-version.md b/src/current/v25.4/upgrade-cockroach-version.md
@@ -5,7 +5,11 @@ toc: true
 docs_area: manage
 ---
 
-This page describes how major-version and patch upgrades work and shows how to upgrade a self-hosted CockroachDB. To upgrade a cluster in CockroachDB {{ site.data.products.cloud }}, refer to [Upgrade a cluster in CockroachDB {{ site.data.products.cloud }}]({% link cockroachcloud/upgrade-cockroach-version.md %}) instead.
+This page describes how major-version and patch upgrades work and shows how to upgrade a self-hosted CockroachDB. 
+
+To upgrade a cluster in CockroachDB {{ site.data.products.cloud }}, refer to [Upgrade a cluster in CockroachDB {{ site.data.products.cloud }}]({% link cockroachcloud/upgrade-cockroach-version.md %}) instead.
+
+To upgrade a cluster with with [physical cluster replication (PCR)]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}), refer to [Upgrade a Cluster Running PCR]({% link cockroachcloud/upgrade-with-pcr.md %}).
 
 ## Overview
 
diff --git a/src/current/v25.4/upgrade-with-pcr.md b/src/current/v25.4/upgrade-with-pcr.md
@@ -15,7 +15,7 @@ The entire standby cluster must be on the same major version as the primary clus
 
 ## Minor version upgrades
 
-Minor versions are not relevant when determining PCR compatibility. There is no need to consider PCR compatibility when upgrading to a specific minor version within a major version.
+Minor versions are not relevant when determining PCR compatibility. There is no need to consider PCR compatibility when upgrading to a specific minor version within a major version, so you can follow the normal [patch upgrade process]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#perform-a-patch-upgrade).
 
 ## Upgrade primary and standby clusters
 
