Resolve comments

docs/content/en/docs/clustermgmt/cluster-backup-restore/backup-cluster.md

@@ -17,7 +17,7 @@ For optimal cluster maintenance, it is crucial to perform regular etcd backups o
 
 ## Cluster API backup
 
-Since cluster failures primarily occur following unsuccessful cluster upgrades, EKS Anywhere takes the proactive step of automatically creating backups for the Cluster API objects that capture the states of both the management cluster and its workload clusters. These backups are stored within the management cluster folder, where the upgrade command is initiated from the Admin machine, and are generated before each management cluster upgrade process. For example, after executing a cluster upgrade command on `mgmt-cluster`, a backup folder is generated with the naming convention of `cluster-state-backup-${timestamp}`:
+Since cluster failures primarily occur following unsuccessful cluster upgrades, EKS Anywhere takes the proactive step of automatically creating backups for the Cluster API objects that capture the states of both the management cluster and its workload clusters if all the clusters are in ready state. If one of the workload clusters is not ready, EKS Anywhere takes the best effort to backup the management cluster itself. These backups are stored within the management cluster folder, where the upgrade command is initiated from the Admin machine, and are generated before each management cluster upgrade process. For example, after executing a cluster upgrade command on `mgmt-cluster`, a backup folder is generated with the naming convention of `cluster-state-backup-${timestamp}`:
 
 ```bash
 mgmt-cluster/ 

docs/content/en/docs/clustermgmt/cluster-backup-restore/restore-cluster.md

@@ -36,7 +36,7 @@ If the cluster is no longer accessible in any means, or the infrastructure machi
 
 1. Create a new management cluster to which you will be migrating your workload clusters later.
 
-    You can define a cluster config similar to your old management cluster, with a different cluster name, and run cluster creation of the new management cluster.
+    You can define a cluster config similar to your old management cluster, with a different cluster name (if the old management cluster still exists), and run cluster creation of the new management cluster with the **exact same EKS Anywhere version** used to create the old management cluster.
 
     ```sh
     eksctl anywhere create cluster -f mgmt-new.yaml
@@ -56,10 +56,13 @@ If the cluster is no longer accessible in any means, or the infrastructure machi
 
     # Substitute the workspace path with the workspace you are using
     WORKSPACE_PATH="/home/ec2-user/eks-a"
+    
+    # Retrieve the Cluster API backup folder path that are automatically generated during the cluster upgrade
+    # This folder contains all the resources that represent the cluster state of the old management cluster along with its workload clusters
     CLUSTER_STATE_BACKUP_LATEST=$(ls -Art ${WORKSPACE_PATH}/${MGMT_CLUSTER_OLD} | grep 'cluster-state-backup' | tail -1)
     CLUSTER_STATE_BACKUP_LATEST_PATH=${WORKSPACE_PATH}/${MGMT_CLUSTER_OLD}/${CLUSTER_STATE_BACKUP_LATEST}/
 
-    # Substitute the EKS Anywhere release version with whatever CLI version you are using
+    # Substitute the EKS Anywhere release version with the EKS Anywhere version of the original management cluster
     EKSA_RELEASE_VERSION=v0.17.3
     BUNDLE_MANIFEST_URL=$(curl -s https://anywhere-assets.eks.amazonaws.com/releases/eks-a/manifest.yaml | yq ".spec.releases[] | select(.version==\"$EKSA_RELEASE_VERSION\").bundleManifestUrl")
     CLI_TOOLS_IMAGE=$(curl -s $BUNDLE_MANIFEST_URL | yq ".spec.versionsBundles[0].eksa.cliTools.uri")