From 4371e47930b3d1f28ba5a99d59a26ce2a241b89c Mon Sep 17 00:00:00 2001 From: Siyuan Zhang <10984162+siyuanfoundation@users.noreply.github.com> Date: Tue, 14 May 2024 13:14:03 -0700 Subject: [PATCH] Update content/en/docs/v3.5/downgrades/downgrade_3_5.md Co-authored-by: Marek Siarkowicz --- content/en/docs/v3.5/downgrades/downgrade_3_5.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/v3.5/downgrades/downgrade_3_5.md b/content/en/docs/v3.5/downgrades/downgrade_3_5.md index 6d1ef40e..55c3e0d3 100644 --- a/content/en/docs/v3.5/downgrades/downgrade_3_5.md +++ b/content/en/docs/v3.5/downgrades/downgrade_3_5.md @@ -99,7 +99,7 @@ For a much larger total data size, 100MB or more , this one-time process might t #### Rollback -If any member has been downgraded to v3.4, the cluster will be downgraded to v3.4, and the cluster and its operations will be "v3.4". You would need to follow the [Upgrade etcd from 3.4 to 3.5](../../upgrades/upgrade_3_5/) instructions to rollback. +If any member has been downgraded to v3.4, the cluster version will be downgraded to v3.4, and operations will be "v3.4" compatible. You would need to follow the [Upgrade etcd from 3.4 to 3.5](../../upgrades/upgrade_3_5/) instructions to rollback. Please [download the snapshot backup](../../op-guide/maintenance/#snapshot-backup) to make downgrading the cluster possible even after it has been completely downgraded.