From 3439ee1e7f16064058d218d19c4046813c346e38 Mon Sep 17 00:00:00 2001
From: Kathryn Hancox <kathryn@cockroachlabs.com>
Date: Tue, 27 Feb 2024 13:31:45 -0500
Subject: [PATCH] Corrections

---
 src/current/cockroachcloud/backup-and-restore-overview.md | 4 ++--
 src/current/v23.2/backup-and-restore-overview.md          | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/current/cockroachcloud/backup-and-restore-overview.md b/src/current/cockroachcloud/backup-and-restore-overview.md
index 76ce2e886c1..9db9b64f24b 100644
--- a/src/current/cockroachcloud/backup-and-restore-overview.md
+++ b/src/current/cockroachcloud/backup-and-restore-overview.md
@@ -108,7 +108,7 @@ You can take manual backups and store them in your [cloud storage buckets](https
       <td>
         <a href="https://www.cockroachlabs.com/docs/{{site.current_cloud_version}}/take-and-restore-locality-aware-backups">Locality-aware backup and restore</a>
       </td>
-      <td>A backup where each node writes files only to the backup destination that matches the node locality configured at node startup.</td>
+      <td>A backup where each node writes files to the backup destination that matches the node locality configured at node startup.</td>
       <td>
         <ul>
           <li>Customer-owned backups in CockroachDB {{ site.data.products.serverless }} and CockroachDB {{ site.data.products.dedicated }}.</li>
@@ -197,7 +197,7 @@ You can track backup jobs using metrics that cover scheduled backups, status of
 CockroachDB supports two backup features that use a node's locality to determine how a backup job runs or where the backup data is stored:
 
 - [Locality-restricted backup execution](https://www.cockroachlabs.com/docs/{{site.current_cloud_version}}/take-locality-restricted-backups): Specify a set of locality filters for a backup job in order to restrict the nodes that can participate in the backup process to that locality. This ensures that the backup job is executed by nodes that meet certain requirements, such as being located in a specific region or having access to a certain storage bucket.
-- [Locality-aware backup](https://www.cockroachlabs.com/docs/{{site.current_cloud_version}}/take-and-restore-locality-aware-backups): Partition and store backup data in a way that is optimized for locality. This means that nodes write backup data to the cloud storage bucket that is closest to the node's locality. This is helpful if you want to reduce network costs or have data domiciling needs.
+- [Locality-aware backup](https://www.cockroachlabs.com/docs/{{site.current_cloud_version}}/take-and-restore-locality-aware-backups): Partition and store backup data in a way that is optimized for locality. When you run a locality-aware backup, nodes write backup data to the [cloud storage](https://www.cockroachlabs.com/docs/{{site.current_cloud_version}}/use-cloud-storage) bucket that is closest to the node locality configured at [node startup](https://www.cockroachlabs.com/docs/{{site.current_cloud_version}}/cockroach-start).
 
 ## Video demo
 
diff --git a/src/current/v23.2/backup-and-restore-overview.md b/src/current/v23.2/backup-and-restore-overview.md
index 435badadd66..b419188923a 100644
--- a/src/current/v23.2/backup-and-restore-overview.md
+++ b/src/current/v23.2/backup-and-restore-overview.md
@@ -99,7 +99,7 @@ This table outlines the level of product support for backup and restore features
       <td>
         <a href="{% link {{ page.version.version }}/take-and-restore-locality-aware-backups.md %}">Locality-aware backup and restore</a>
       </td>
-      <td>A backup where each node writes files only to the backup destination that matches the node locality configured at node startup.</td>
+      <td>A backup where each node writes files to the backup destination that matches the node locality configured at node startup.</td>
       <td>
         <ul>
           <li>Requires an Enterprise license - <a href="{% link {{ page.version.version }}/enterprise-licensing.md %}">Learn more</a></li>