From 0be35d69dd927a283ec7444a3df1a502bab6f228 Mon Sep 17 00:00:00 2001
From: Ajay <217481+ajaygm@users.noreply.github.com>
Date: Fri, 8 Jan 2021 07:37:03 +0530
Subject: [PATCH] Update garbage-collection.md

---
 .../workloads/controllers/garbage-collection.md        | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/concepts/workloads/controllers/garbage-collection.md b/content/en/docs/concepts/workloads/controllers/garbage-collection.md
index 0e9b4f746a..aaf9cd08ac 100644
--- a/content/en/docs/concepts/workloads/controllers/garbage-collection.md
+++ b/content/en/docs/concepts/workloads/controllers/garbage-collection.md
@@ -150,14 +150,16 @@ curl -X DELETE localhost:8080/apis/apps/v1/namespaces/default/replicasets/my-rep
 ```
 
 kubectl also supports cascading deletion.
-To delete dependents automatically using kubectl, set `--cascade` to true.  To
-orphan dependents, set `--cascade` to false. The default value for `--cascade`
-is true.
+
+To delete dependents in the foreground using kubectl, set `--cascade=foreground`.  To
+orphan dependents, set `--cascade=orphan`. 
+
+The default behavior is to delete dependents in the background i.e. no `--cascade` option or `--cascade=background`.
 
 Here's an example that orphans the dependents of a ReplicaSet:
 
 ```shell
-kubectl delete replicaset my-repset --cascade=false
+kubectl delete replicaset my-repset --cascade=orphan
 ```
 
 ### Additional note on Deployments