diff --git a/backup_and_restore/graceful-cluster-shutdown.adoc b/backup_and_restore/graceful-cluster-shutdown.adoc
index be7762a79f..d5fc8860f7 100644
--- a/backup_and_restore/graceful-cluster-shutdown.adoc
+++ b/backup_and_restore/graceful-cluster-shutdown.adoc
@@ -16,6 +16,9 @@ This document describes the process to gracefully shut down your cluster. You mi
 include::modules/graceful-shutdown.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
-.Additional resources
+[id="additional-resources_restarting-restoring-cluster"]
+== Additional resources
 
 * xref:../backup_and_restore/graceful-cluster-restart.adoc#graceful-restart-cluster[Restarting the cluster gracefully]
+
+* xref:../backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.adoc#dr-restoring-cluster-state[Restore to a previous cluster state]
\ No newline at end of file
diff --git a/modules/graceful-shutdown.adoc b/modules/graceful-shutdown.adoc
index 6b9b91cb04..cf7f035156 100644
--- a/modules/graceful-shutdown.adoc
+++ b/modules/graceful-shutdown.adoc
@@ -21,6 +21,14 @@ You can shut down a cluster until a year from the installation date and expect i
 [IMPORTANT]
 ====
 It is important to take an etcd backup before performing this procedure so that your cluster can be restored if you encounter any issues when restarting the cluster.
+
+For example, the following conditions can cause the restarted cluster to malfunction:
+
+* etcd data corruption during shutdown
+* Node failure due to hardware
+* Network connectivity issues
+
+If your cluster fails to recover, follow the steps to restore to a previous cluster state.
 ====
 
 .Procedure