Docs review changes

Changes from docs review- still need to add code snippets

Author: peachdawnleach

src/current/_includes/v24.3/sidebar-data/cross-cluster-replication.json

@@ -47,7 +47,7 @@
             ]
           },
           {
-            "title": "Upgrade with Physical Cluster Replication Enabled",
+            "title": "Upgrade a Cluster Running PCR",
             "urls": [
               "/${VERSION}/upgrade-with-pcr.html"
             ]

src/current/_includes/v25.2/sidebar-data/cross-cluster-replication.json

@@ -47,7 +47,7 @@
             ]
           },
           {
-            "title": "Upgrade with Physical Cluster Replication Enabled",
+            "title": "Upgrade a Cluster Running PCR",
             "urls": [
               "/${VERSION}/upgrade-with-pcr.html"
             ]

src/current/_includes/v25.3/sidebar-data/cross-cluster-replication.json

@@ -47,7 +47,7 @@
             ]
           },
           {
-            "title": "Upgrade with Physical Cluster Replication Enabled",
+            "title": "Upgrade a Cluster Running PCR",
             "urls": [
               "/${VERSION}/upgrade-with-pcr.html"
             ]

src/current/_includes/v25.4/sidebar-data/cross-cluster-replication.json

@@ -47,7 +47,7 @@
             ]
           },
           {
-            "title": "Upgrade with Physical Cluster Replication Enabled",
+            "title": "Upgrade a Cluster Running PCR",
             "urls": [
               "/${VERSION}/upgrade-with-pcr.html"
             ]

src/current/v24.3/upgrade-with-pcr.md

@@ -1,21 +1,27 @@
 ---
-title: Upgrade with Physical Cluster Replication Enabled
+title: Upgrade a Cluster Running PCR
 summary: Upgrade your primary and standby clusters when using PCR.
 toc: true
 docs_area: manage
 ---
 
-When [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) is enabled, you must use the process on this page to upgrade your clusters. This process ensures that the standby cluster safely upgrades before the primary cluster, preventing any version incompatibility. You cannot replicate data from a cluster on a newer version to a cluster on an older version. 
+To safely perform a major version upgrade on a cluster with [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}), you must upgrade the standby cluster before the primary cluster to avoid version incompatibility. You cannot replicate data from a cluster on a newer version to a cluster on an older version. 
+
+This page describes the process for safely performing a major version upgrade on a pair of clusters that have PCR enabled.
 
 {{site.data.alerts.callout_info}}
 The entire standby cluster must be on the same major version as the primary cluster or a major version the primary cluster [can directly upgrade to]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#compatible-versions). Within the primary and standby CockroachDB clusters, the _system virtual cluster (system VC)_ must be at a cluster major version greater than or equal to the _application virtual cluster (app VC)_.
 {{site.data.alerts.end}}
 
+## 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.
+
 ## Upgrade primary and standby clusters
 
 To upgrade your primary and standby clusters:
 
-1. Ensure that the virtual clusters on both your primary cluster and your standby cluster are finalized on the current version. If their versions have not been finalized, [finalize]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#finalize-a-major-version-upgrade-manually) them before beginning the upgrade process.
+1. Ensure that the virtual clusters on both your primary cluster and your standby cluster are [finalized]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#finalize-a-major-version-upgrade-manually) on the current version before beginning the upgrade process.
 
 1. [Upgrade the binaries]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#perform-a-major-version-upgrade) on the standby cluster. Replace the binary on each node of the cluster and restart the node.
 
@@ -39,7 +45,7 @@ To upgrade your primary and standby clusters:
 
 ## Upgrade reader VC
 
-If you have a _reader virtual cluster (reader VC)_, you must upgrade it independently from the primary and standby clusters, after completing the main upgrade process. Use the following steps to upgrade your reader VC by dropping and re-creating it:
+If you have a [_reader virtual cluster (reader VC)_]({% link {{ page.version.version }}/read-from-standby.md %}), you must drop and recreate it to upgrade after completing the main upgrade process on the primary and standby clusters. Follow these steps to upgrade your reader VC:
 
 1. After upgrading the app VC on your primary cluster, wait for the replicated time to pass the time at which the upgrade completed.
 1. On the standby cluster, stop the reader VC service:
@@ -67,10 +73,6 @@ At this point, the reader VC is on the same version as the standby cluster.
 
 ## Failover and fast failback during upgrade
 
-If you need to, you can still perform a [failover]({% link {{ page.version.version }}/failover-replication.md %}) while upgrading your clusters.
-
-However, after performing a failover you cannot perform a [fast failback]({% link {{ page.version.version }}/failover-replication.md %}#failback) to the original primary cluster while the standby cluster version is newer than the primary cluster version. This is because you cannot replicate data from a cluster on a newer version to a cluster on an older version. 
-
-## Minor version upgrades
+If needed, you can perform a [failover]({% link {{ page.version.version }}/failover-replication.md %}) while upgrading your clusters.
 
-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.
+However, after performing a failover you cannot perform a [fast failback]({% link {{ page.version.version }}/failover-replication.md %}#failback) to the original primary cluster while the standby cluster version is newer than the primary cluster version. This is because you cannot replicate data from a cluster on a newer version to a cluster on an older version. 

src/current/v25.2/upgrade-with-pcr.md

@@ -1,21 +1,27 @@
 ---
-title: Upgrade with Physical Cluster Replication Enabled
+title: Upgrade a Cluster Running PCR
 summary: Upgrade your primary and standby clusters when using PCR.
 toc: true
 docs_area: manage
 ---
 
-When [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) is enabled, you must use the process on this page to upgrade your clusters. This process ensures that the standby cluster safely upgrades before the primary cluster, preventing any version incompatibility. You cannot replicate data from a cluster on a newer version to a cluster on an older version. 
+To safely perform a major version upgrade on a cluster with [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}), you must upgrade the standby cluster before the primary cluster to avoid version incompatibility. You cannot replicate data from a cluster on a newer version to a cluster on an older version. 
+
+This page describes the process for safely performing a major version upgrade on a pair of clusters that have PCR enabled.
 
 {{site.data.alerts.callout_info}}
 The entire standby cluster must be on the same major version as the primary cluster or a major version the primary cluster [can directly upgrade to]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#compatible-versions). Within the primary and standby CockroachDB clusters, the _system virtual cluster (system VC)_ must be at a cluster major version greater than or equal to the _application virtual cluster (app VC)_.
 {{site.data.alerts.end}}
 
+## 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.
+
 ## Upgrade primary and standby clusters
 
 To upgrade your primary and standby clusters:
 
-1. Ensure that the virtual clusters on both your primary cluster and your standby cluster are finalized on the current version. If their versions have not been finalized, [finalize]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#finalize-a-major-version-upgrade-manually) them before beginning the upgrade process.
+1. Ensure that the virtual clusters on both your primary cluster and your standby cluster are [finalized]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#finalize-a-major-version-upgrade-manually) on the current version before beginning the upgrade process.
 
 1. [Upgrade the binaries]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#perform-a-major-version-upgrade) on the standby cluster. Replace the binary on each node of the cluster and restart the node.
 
@@ -39,7 +45,7 @@ To upgrade your primary and standby clusters:
 
 ## Upgrade reader VC
 
-If you have a _reader virtual cluster (reader VC)_, you must upgrade it independently from the primary and standby clusters, after completing the main upgrade process. Use the following steps to upgrade your reader VC by dropping and re-creating it:
+If you have a [_reader virtual cluster (reader VC)_]({% link {{ page.version.version }}/read-from-standby.md %}), you must drop and recreate it to upgrade after completing the main upgrade process on the primary and standby clusters. Follow these steps to upgrade your reader VC:
 
 1. After upgrading the app VC on your primary cluster, wait for the replicated time to pass the time at which the upgrade completed.
 1. On the standby cluster, stop the reader VC service:
@@ -67,10 +73,6 @@ At this point, the reader VC is on the same version as the standby cluster.
 
 ## Failover and fast failback during upgrade
 
-If you need to, you can still perform a [failover]({% link {{ page.version.version }}/failover-replication.md %}) while upgrading your clusters.
-
-However, after performing a failover you cannot perform a [fast failback]({% link {{ page.version.version }}/failover-replication.md %}#failback) to the original primary cluster while the standby cluster version is newer than the primary cluster version. This is because you cannot replicate data from a cluster on a newer version to a cluster on an older version. 
-
-## Minor version upgrades
+If needed, you can perform a [failover]({% link {{ page.version.version }}/failover-replication.md %}) while upgrading your clusters.
 
-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.
+However, after performing a failover you cannot perform a [fast failback]({% link {{ page.version.version }}/failover-replication.md %}#failback) to the original primary cluster while the standby cluster version is newer than the primary cluster version. This is because you cannot replicate data from a cluster on a newer version to a cluster on an older version. 

src/current/v25.3/upgrade-with-pcr.md

@@ -1,21 +1,27 @@
 ---
-title: Upgrade with Physical Cluster Replication Enabled
+title: Upgrade a Cluster Running PCR
 summary: Upgrade your primary and standby clusters when using PCR.
 toc: true
 docs_area: manage
 ---
 
-When [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) is enabled, you must use the process on this page to upgrade your clusters. This process ensures that the standby cluster safely upgrades before the primary cluster, preventing any version incompatibility. You cannot replicate data from a cluster on a newer version to a cluster on an older version. 
+To safely perform a major version upgrade on a cluster with [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}), you must upgrade the standby cluster before the primary cluster to avoid version incompatibility. You cannot replicate data from a cluster on a newer version to a cluster on an older version. 
+
+This page describes the process for safely performing a major version upgrade on a pair of clusters that have PCR enabled.
 
 {{site.data.alerts.callout_info}}
 The entire standby cluster must be on the same major version as the primary cluster or a major version the primary cluster [can directly upgrade to]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#compatible-versions). Within the primary and standby CockroachDB clusters, the _system virtual cluster (system VC)_ must be at a cluster major version greater than or equal to the _application virtual cluster (app VC)_.
 {{site.data.alerts.end}}
 
+## 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.
+
 ## Upgrade primary and standby clusters
 
 To upgrade your primary and standby clusters:
 
-1. Ensure that the virtual clusters on both your primary cluster and your standby cluster are finalized on the current version. If their versions have not been finalized, [finalize]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#finalize-a-major-version-upgrade-manually) them before beginning the upgrade process.
+1. Ensure that the virtual clusters on both your primary cluster and your standby cluster are [finalized]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#finalize-a-major-version-upgrade-manually) on the current version before beginning the upgrade process.
 
 1. [Upgrade the binaries]({% link {{ page.version.version }}/upgrade-cockroach-version.md %}#perform-a-major-version-upgrade) on the standby cluster. Replace the binary on each node of the cluster and restart the node.
 
@@ -39,7 +45,7 @@ To upgrade your primary and standby clusters:
 
 ## Upgrade reader VC
 
-If you have a [_reader virtual cluster (reader VC)_]({% link {{ page.version.version }}/read-from-standby.md %}), you must upgrade it independently from the primary and standby clusters, after completing the main upgrade process. Use the following steps to upgrade your reader VC by dropping and re-creating it:
+If you have a [_reader virtual cluster (reader VC)_]({% link {{ page.version.version }}/read-from-standby.md %}), you must drop and recreate it to upgrade after completing the main upgrade process on the primary and standby clusters. Follow these steps to upgrade your reader VC:
 
 1. After upgrading the app VC on your primary cluster, wait for the replicated time to pass the time at which the upgrade completed.
 1. On the standby cluster, stop the reader VC service:
@@ -67,10 +73,6 @@ At this point, the reader VC is on the same version as the standby cluster.
 
 ## Failover and fast failback during upgrade
 
-If you need to, you can still perform a [failover]({% link {{ page.version.version }}/failover-replication.md %}) while upgrading your clusters.
-
-However, after performing a failover you cannot perform a [fast failback]({% link {{ page.version.version }}/failover-replication.md %}#failback) to the original primary cluster while the standby cluster version is newer than the primary cluster version. This is because you cannot replicate data from a cluster on a newer version to a cluster on an older version. 
-
-## Minor version upgrades
+If needed, you can perform a [failover]({% link {{ page.version.version }}/failover-replication.md %}) while upgrading your clusters.
 
-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.
+However, after performing a failover you cannot perform a [fast failback]({% link {{ page.version.version }}/failover-replication.md %}#failback) to the original primary cluster while the standby cluster version is newer than the primary cluster version. This is because you cannot replicate data from a cluster on a newer version to a cluster on an older version.