diff --git a/modules/migration-debugging-velero-resources.adoc b/modules/migration-debugging-velero-resources.adoc
index ed071e166679..a02ec77df14b 100644
--- a/modules/migration-debugging-velero-resources.adoc
+++ b/modules/migration-debugging-velero-resources.adoc
@@ -71,7 +71,12 @@ One or more errors in any of the above categories causes a `Restore` operation t
 
 [NOTE]
 ====
-If there are `Velero` errors but no resource-specific errors in the output of a `describe` command, it is possible that the restore completed without any actual problems in restoring workloads, but carefully validate post-restore applications.
+For resource-specific errors, that is, `Cluster` and `Namespaces` errors, the `restore describe --details` output includes a resource list that lists all resources that Velero succeeded in restoring. For any resource that has such an error, check to see if the resource is actually in the cluster.
+====
+
+[NOTE]
+====
+If there are `Velero` errors, but no resource-specific errors, in the output of a `describe` command, it is possible that the restore completed without any actual problems in restoring workloads, but carefully validate post-restore applications.
 For example, if the output contains `PodVolumeRestore` or Node Agent-related errors, check the status of `PodVolumeRestores` and `DataDownloads`. If none of these are failed or still running, then volume data might have been fully restored.
 ====