diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-etcd.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-etcd.md
index f700af0eb9d..63ee61ac2d0 100644
--- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-etcd.md
+++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-etcd.md
@@ -47,7 +47,7 @@ Dapr has 2 versions of the Etcd state store component: `v1` and `v2`. It is reco
 
 While `v1` and `v2` have the same metadata fields, `v1` causes data inconsistencies in apps when using [Actor TTLs]({{< ref "actors_api.md#ttl" >}}) from Dapr v1.12.
 `v1` and `v2` are incompatible with no data migration path for `v1` to `v2` on an existing active Etcd cluster and `keyPrefixPath`.
-If you are using `v1`, you should continue to use `v1` until you create a new Etcd cluster or use a different `keyPrefixPath`, then use `v2`.
+If you are using `v1`, you should continue to use `v1` until you create a new Etcd cluster or use a different `keyPrefixPath`.
 
 ## Spec metadata fields