diff --git a/src/current/_includes/v22.2/backups/serverless-locality-aware.md b/src/current/_includes/v22.2/backups/serverless-locality-aware.md
index a5661dc1806..95cbaa7ad70 100644
--- a/src/current/_includes/v22.2/backups/serverless-locality-aware.md
+++ b/src/current/_includes/v22.2/backups/serverless-locality-aware.md
@@ -1 +1 @@
-CockroachDB {{ site.data.products.serverless }} clusters operate with a [different architecture](https://www.cockroachlabs.com/docs/cockroachcloud/architecture#cockroachdb-serverless) compared to CockroachDB {{ site.data.products.core }} and CockroachDB {{ site.data.products.dedicated }} clusters. These architectural differences have implications for how locality-aware backups can run. Serverless clusters will scale resources depending on whether they are actively in use, which means that it is less likely to have a SQL pod available in every locality. As a result, Serverless clusters are more likely to have ranges that do not match with any of the cluster's localities, which can lead to more ranges backed up to a storage bucket in a different locality. You should consider this as you plan a backup strategy that must comply with [data domiciling](data-domiciling.html) requirements.
\ No newline at end of file
+CockroachDB {{ site.data.products.serverless }} clusters operate with a [different architecture](https://www.cockroachlabs.com/docs/cockroachcloud/architecture#cockroachdb-serverless) compared to CockroachDB {{ site.data.products.core }} and CockroachDB {{ site.data.products.dedicated }} clusters. These architectural differences have implications for how locality-aware backups can run. Serverless clusters will scale resources depending on whether they are actively in use, which means that it is less likely to have a SQL pod available in every locality. As a result, your Serverless cluster may not have a SQL pod in the locality where the data resides, resulting in that data being uploaded to a storage bucket in a locality where you do have active SQL pods. You should consider this as you plan a backup strategy that must comply with [data domiciling](data-domiciling.html) requirements.
\ No newline at end of file
diff --git a/src/current/_includes/v23.1/backups/serverless-locality-aware.md b/src/current/_includes/v23.1/backups/serverless-locality-aware.md
index 25b22f1f00c..1183decc63f 100644
--- a/src/current/_includes/v23.1/backups/serverless-locality-aware.md
+++ b/src/current/_includes/v23.1/backups/serverless-locality-aware.md
@@ -1 +1 @@
-CockroachDB {{ site.data.products.serverless }} clusters operate with a [different architecture]({% link cockroachcloud/architecture.md %}#cockroachdb-serverless) compared to CockroachDB {{ site.data.products.core }} and CockroachDB {{ site.data.products.dedicated }} clusters. These architectural differences have implications for how locality-aware backups can run. Serverless clusters will scale resources depending on whether they are actively in use, which means that it is less likely to have a SQL pod available in every locality. As a result, Serverless clusters are more likely to have ranges that do not match with any of the cluster's localities, which can lead to more ranges backed up to a storage bucket in a different locality. You should consider this as you plan a backup strategy that must comply with [data domiciling]({% link v23.1/data-domiciling.md %}) requirements.
\ No newline at end of file
+CockroachDB {{ site.data.products.serverless }} clusters operate with a [different architecture]({% link cockroachcloud/architecture.md %}#cockroachdb-serverless) compared to CockroachDB {{ site.data.products.core }} and CockroachDB {{ site.data.products.dedicated }} clusters. These architectural differences have implications for how locality-aware backups can run. Serverless clusters will scale resources depending on whether they are actively in use, which means that it is less likely to have a SQL pod available in every locality. As a result, your Serverless cluster may not have a SQL pod in the locality where the data resides, resulting in that data being uploaded to a storage bucket in a locality where you do have active SQL pods. You should consider this as you plan a backup strategy that must comply with [data domiciling]({% link v23.1/data-domiciling.md %}) requirements.
\ No newline at end of file
diff --git a/src/current/_includes/v23.2/backups/serverless-locality-aware.md b/src/current/_includes/v23.2/backups/serverless-locality-aware.md
index e5da195923a..ee054067df7 100644
--- a/src/current/_includes/v23.2/backups/serverless-locality-aware.md
+++ b/src/current/_includes/v23.2/backups/serverless-locality-aware.md
@@ -1 +1 @@
-CockroachDB {{ site.data.products.serverless }} clusters operate with a [different architecture]({% link cockroachcloud/architecture.md %}#cockroachdb-serverless) compared to CockroachDB {{ site.data.products.core }} and CockroachDB {{ site.data.products.dedicated }} clusters. These architectural differences have implications for how locality-aware backups can run. Serverless clusters will scale resources depending on whether they are actively in use, which means that it is less likely to have a SQL pod available in every locality. As a result, Serverless clusters are more likely to have ranges that do not match with any of the cluster's localities, which can lead to more ranges backed up to a storage bucket in a different locality. You should consider this as you plan a backup strategy that must comply with [data domiciling]({% link v23.2/data-domiciling.md %}) requirements.
\ No newline at end of file
+CockroachDB {{ site.data.products.serverless }} clusters operate with a [different architecture]({% link cockroachcloud/architecture.md %}#cockroachdb-serverless) compared to CockroachDB {{ site.data.products.core }} and CockroachDB {{ site.data.products.dedicated }} clusters. These architectural differences have implications for how locality-aware backups can run. Serverless clusters will scale resources depending on whether they are actively in use, which means that it is less likely to have a SQL pod available in every locality. As a result, your Serverless cluster may not have a SQL pod in the locality where the data resides, resulting in that data being uploaded to a storage bucket in a locality where you do have active SQL pods. You should consider this as you plan a backup strategy that must comply with [data domiciling]({% link v23.2/data-domiciling.md %}) requirements.
\ No newline at end of file