refactor: address pr feedback

Author: Piotr1215

vcluster/configure/vcluster-yaml/control-plane/components/backing-store/etcd/embedded.mdx

@@ -158,11 +158,15 @@ kubectl logs [[VAR:VCLUSTER NAME:my-vcluster]]-0 -n [[VAR:NAMESPACE:vcluster-my-
 <TabItem value="first-replica-failing" label="First replica is failing">
 
 :::warning
-Before attempting any recovery procedure, create a backup of the virtual cluster namespace on the host cluster. If using namespace syncing, back up all synced namespaces as well.
+Before attempting any recovery procedure, create a backup of your virtual cluster using `vcluster snapshot create` or manually backup the virtual cluster namespace on the host cluster. If using namespace syncing, back up all synced namespaces as well.
 :::
 
 The recovery procedure depends on your StatefulSet `podManagementPolicy` configuration. vCluster version 0.20 and later use `Parallel` by default. Earlier versions used `OrderedReady`.
 
+:::info
+If more than one pod is down with `podManagementPolicy: OrderedReady`, you must first [migrate to `Parallel`](#migrate-to-parallel) before attempting recovery.
+:::
+
 Check your configuration:
 
 <InterpolatedCodeBlock
@@ -175,7 +179,16 @@ Check your configuration:
 
 <Flow>
 <Step title="Delete the failed pod and PVC">
-Delete the corrupted pod and PVC for replica-0:
+First, identify the PVC for replica-0:
+
+<InterpolatedCodeBlock
+  code={`kubectl get pvc -l [[VAR:VCLUSTER LABEL:app=vcluster]] -n [[VAR:NAMESPACE:vcluster-my-team]]`}
+  language="bash"
+/>
+
+<br />
+
+Delete the corrupted pod and its PVC:
 
 <InterpolatedCodeBlock
   code={`kubectl delete pod [[VAR:VCLUSTER NAME:my-vcluster]]-0 -n [[VAR:NAMESPACE:vcluster-my-team]]
@@ -185,7 +198,7 @@ kubectl delete pvc [[VAR:PVC PREFIX:data]]-[[VAR:VCLUSTER NAME:my-vcluster]]-0 -
 
 <br />
 
-The pod restarts with a new empty PVC. After 1-3 pod restarts, the automatic recovery adds it back to the etcd cluster.
+The pod restarts with a new empty PVC. The initial attempts fail because the new member tries to join the existing etcd cluster but lacks the required data. After 1-3 pod restarts, vCluster's automatic recovery detects the empty member and properly adds it as a new learner, allowing it to sync data from healthy members and join the cluster.
 </Step>
 
 <Step title="Monitor recovery">
@@ -239,29 +252,21 @@ Delete the StatefulSet without deleting the pods:
 </Step>
 
 <Step title="Update configuration to Parallel">
+<a id="migrate-to-parallel"></a>
+
 Update your virtual cluster configuration to use `Parallel` pod management policy.
 
 If using a VirtualClusterInstance:
 
 <InterpolatedCodeBlock
-  code={`kubectl edit virtualclusterinstance [[VAR:VCLUSTER NAME:my-vcluster]] -n [[VAR:NAMESPACE:vcluster-my-team]]`}
+  code={`kubectl patch virtualclusterinstance [[VAR:VCLUSTER NAME:my-vcluster]] -n [[VAR:NAMESPACE:vcluster-my-team]] \\
+  --type merge \\
+  -p '{"spec":{"controlPlane":{"statefulSet":{"scheduling":{"podManagementPolicy":"Parallel"}}}}}'`}
   language="bash"
 />
 
 <br />
 
-Add or update the following configuration:
-
-<InterpolatedCodeBlock
-  code={`controlPlane:
-  statefulSet:
-    scheduling:
-      podManagementPolicy: Parallel`}
-  language="yaml"
-/>
-
-<br />
-
 If using Helm, update your `values.yaml` and run:
 
 <InterpolatedCodeBlock
@@ -279,7 +284,18 @@ The StatefulSet is recreated with `Parallel` policy and pods pick up the existin
 </Step>
 
 <Step title="Delete the failed pod and PVC">
-Now follow the same procedure as for `Parallel` mode:
+Now follow the same procedure as for `Parallel` mode.
+
+First, identify the PVC for replica-0:
+
+<InterpolatedCodeBlock
+  code={`kubectl get pvc -l [[VAR:VCLUSTER LABEL:app=vcluster]] -n [[VAR:NAMESPACE:vcluster-my-team]]`}
+  language="bash"
+/>
+
+<br />
+
+Delete the corrupted pod and its PVC:
 
 <InterpolatedCodeBlock
   code={`kubectl delete pod [[VAR:VCLUSTER NAME:my-vcluster]]-0 -n [[VAR:NAMESPACE:vcluster-my-team]]
@@ -289,7 +305,7 @@ kubectl delete pvc [[VAR:PVC PREFIX:data]]-[[VAR:VCLUSTER NAME:my-vcluster]]-0 -
 
 <br />
 
-The pod restarts with a new empty PVC and automatic recovery adds it back to the cluster after 1-3 pod restarts.
+The pod restarts with a new empty PVC. The initial attempts fail because the new member tries to join the existing etcd cluster but lacks the required data. After 1-3 pod restarts, vCluster's automatic recovery detects the empty member and properly adds it as a new learner, allowing it to sync data from healthy members and join the cluster.
 </Step>
 </Flow>