diff --git a/docs/landing-zone-v2/README.md b/docs/landing-zone-v2/README.md
index 302d3bdb7..c3fe59162 100644
--- a/docs/landing-zone-v2/README.md
+++ b/docs/landing-zone-v2/README.md
@@ -633,13 +633,17 @@ To reacquire the resources you will need to redeploy a new instance and deploy t
 First delete the Rootsync deployment. This will prevent the resources from self-healing.
 
 ```shell
-kubectl delete root-sync landing-zone -n config-management-system
+kubectl delete RootSync root-sync -n config-management-system
 ```
 
 Now we can delete our KCC resources from the Config Controller instance.
 
 ```shell
-kubectl delete gcp --all
+kubectl delete gcp -n projects --all
+kubectl delete gcp -n networking --all
+kubectl delete gcp -n hierarchy --all
+kubectl delete gcp -n policies --all
+kubectl delete gcp -n logging --all
 ```
 
 Once the resources have been deleted you can delete the config controller instance .