diff --git a/content/en/docs/reference/glossary/finalizer.md b/content/en/docs/reference/glossary/finalizer.md
index c44386fbf3..e01f66d7f2 100644
--- a/content/en/docs/reference/glossary/finalizer.md
+++ b/content/en/docs/reference/glossary/finalizer.md
@@ -19,12 +19,12 @@ to clean up resources the deleted object owned.
 <!--more-->
 
 When you tell Kubernetes to delete an object that has finalizers specified for
-it, the Kubernetes API marks the object for deletion, putting it into a
-read-only state. The target object remains in a terminating state while the
+it, the Kubernetes API marks the object for deletion by populating `.metadata.deletionTimestamp`,
+and returns a `202` status code (HTTP "Accepted"). The target object remains in a terminating state while the
 control plane, or other components, take the actions defined by the finalizers.
 After these actions are complete, the controller removes the relevant finalizers
 from the target object. When the `metadata.finalizers` field is empty,
-Kubernetes considers the deletion complete.
+Kubernetes considers the deletion complete and deletes the object.
 
 You can use finalizers to control {{<glossary_tooltip text="garbage collection" term_id="garbage-collection">}}
 of resources. For example, you can define a finalizer to clean up related resources or