Update daprdocs/content/en/reference/components-reference/supported-s…

…tate-stores/setup-etcd.md Co-authored-by: Hannah Hunter <[email protected]> Signed-off-by: Josh van Leeuwen <[email protected]>
dapr · Jun 28, 2023 · 4a58c18 · 4a58c18
1 parent efb3468
commit 4a58c18
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/.../content/en/reference/components-reference/supported-state-stores/setup-etcd.md b/.../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