fix: Fix v2store and v3store

Signed-off-by: Wendy Ha <[email protected]>

Author: wendy-ha18

content/en/docs/v3.4/how-to-migrate.md

@@ -1,44 +1,44 @@
 ---
-title: How to migrate etcd from v2 store to v3
+title: How to migrate etcd from v2store to v3store
 description: etcd v2 to v3 migration guide
 weight: 1200
 ---
 
-`migrate` to transform etcd v2 to v3 data.
+`migrate` to transform etcd v2store to v3store.
 
 {{% alert color="warning" %}}
 ⚠️ **Deprecated functionality:**
 
-The `etcdctl migrate` command was removed in etcd v3.5.0 ([pull/12971](https://github.com/etcd-io/etcd/pull/12971)). If your etcd cluster is already running v3.5 or higher, you can no longer migrate v2 data to v3 using this method.  
+The `etcdctl migrate` command was removed in etcd v3.5.0 ([pull/12971](https://github.com/etcd-io/etcd/pull/12971)). If your etcd cluster is already running v3.5 or higher, you can no longer migrate v2store to v3store using this method.  
 
 You **must use etcdctl v3.4 or earlier** to perform the migration (View note from  [CHANGELOG-3.5](https://github.com/ahrtr/etcd/blob/main/CHANGELOG/CHANGELOG-3.5.md#etcdctl-v3-3)). However please take appropriate precautions when using it, as it is no longer officially supported or tested in recent releases.  
 {{% /alert %}}
 
 ## Pre-requisites
 
-Before migrating from etcd v2 to v3, ensure the following:
+Before migrating from etcd v2store to v3store, make sure you have:
 
-- A currently running etcd v2 cluster.
-- The `etcdctl` CLI tool version <= v3.4.
+- An etcd cluster that still contains v2store data.
+- The `etcdctl` CLI version 3.4 or earlier.
 - Access to each etcd node and their data directories.
 - A working backup of your etcd data before performing the migration.
 
 ## Migrate a cluster
 
-The following steps show how to migrate your etcd data from v2 to v3 using `etcdctl migrate`.
+The following steps show how to migrate your etcd data stored from v2store to v3store using `etcdctl migrate`.
 
 ### Variables and Flags Used
 
 - `--endpoints`: Specifies the etcd cluster endpoint(s).
 - `--output`: Output format (e.g., `"json"`).
 - `--data-dir`: Path to the data directory (default: `default.etcd`). View more at [etcd flags](https://etcd.io/docs/v3.6/op-guide/configuration/#member).
-- `--wal-dir`: The write-ahead log directory inside `data-dir` (default: `default.etcd/member/wal`). View more at [etcd flags](https://etcd.io/docs/v3.6/op-guide/configuration/#member).
-- `set`: Command to set a key-value pair in etcd v2 (View [READMEv2](https://github.com/etcd-io/etcd/blob/main/etcdctl/READMEv2.md#setting-key-values) for more details. In etcd v3, the equivalent command is `put` instead of `set`, see the [READMEv3](https://github.com/etcd-io/etcd/tree/main/etcdctl#key-value-commands)) for reference.
+- `--wal-dir`: The write-ahead log (WAL) directory inside `data-dir` (default: `default.etcd/member/wal`). View more at [etcd flags](https://etcd.io/docs/v3.6/op-guide/configuration/#member).
+- `set`: Command to set a key-value pair in etcd v2store (View [READMEv2](https://github.com/etcd-io/etcd/blob/main/etcdctl/READMEv2.md#setting-key-values) for more details. In etcd v3, the equivalent command is `put` instead of `set`, see the [READMEv3](https://github.com/etcd-io/etcd/tree/main/etcdctl#key-value-commands)) for reference.
 - `get`: Command to retrieve a key-value pair (View [Read keys](https://etcd.io/docs/v3.6/dev-guide/interacting_v3/#read-keys)).
 
 ### Migration Process
 
-- Step 1: Set up test key using v2 API
+- Step 1: Write a test key into the v2store and confirm that key exists
 
 ```sh
 export ETCDCTL_API=2
@@ -50,9 +50,9 @@ etcdctl --endpoints=http://$ENDPOINT --output="json" get foo
 
 Before running the migration, stop your etcd node to ensure data consistency.
 
-- Step 3: Run the migration tool
+- Step 3: Run the migration tool to convert v2store to v3store
 
-Switch to API v3 and use `etcdctl migrate` command to transform the v2 store. Please review the deprecation alert on top of the page, you must use etcdctl v3.4 or earlier to be able to perform this command.
+Switch to v3 API and use `etcdctl migrate` command to transform the v2store data into v3store. Please review the deprecation alert on top of the page, you must use etcdctl v3.4 or earlier to be able to perform this command.
 
 ```sh
 export ETCDCTL_API=3
@@ -65,31 +65,35 @@ etcdctl --endpoints=http://$ENDPOINT migrate \
 
 Repeat steps 2–4 for each etcd node one at a time in your cluster.
 
-- Step 5: Confirm the data is accessible via v3 API
+- Step 5: Confirm the key is now stored in v3store
+
+Use the v3 API to check:
 
 ```sh
 etcdctl --endpoints=$ENDPOINTS get /foo
 ```
 
+If the migration succeeded, you should see the value previously stored in v2store.
+
 Summary full process:
 
 ```shell
-# write key in etcd version 2 store
+# Write key in etcd version 2store
 export ETCDCTL_API=2
 etcdctl --endpoints=http://$ENDPOINT set foo bar
 
-# read key in etcd v2
+# Confirm key exists in v2store
 etcdctl --endpoints=$ENDPOINTS --output="json" get foo
 
-# stop etcd node to migrate, one by one
+# Stop etcd node to migrate, one by one
 
-# migrate v2 data
+# Migrate v2store to v3store
 export ETCDCTL_API=3
 etcdctl --endpoints=$ENDPOINT migrate --data-dir="default.etcd" --wal-dir="default.etcd/member/wal"
 
-# restart etcd node after migrate, one by one
+# Restart etcd node after migrate, one by one and repeat the previous process for each node.
 
-# confirm that the key got migrated
+# Confirm the key was migrated into v3store
 etcdctl --endpoints=$ENDPOINTS get /foo
 ```