diff --git a/src/content/docs/quick-installation-new-operator.md b/src/content/docs/quick-installation-new-operator.md
index 139bc69def..529e228e21 100644
--- a/src/content/docs/quick-installation-new-operator.md
+++ b/src/content/docs/quick-installation-new-operator.md
@@ -60,17 +60,17 @@ After completing these steps, please refer to the installation guide to proceed
    spec:
       components:
          codeflare:
-            managementState: Managed
+            managementState: Removed
          dashboard:
             managementState: Managed
          datasciencepipelines:
             managementState: Managed
          kserve:
-            managementState: Managed
+            managementState: Removed
          modelmeshserving:
             managementState: Managed
          ray:
-            managementState: Managed
+            managementState: Removed
          workbenches:
             managementState: Managed
    ```
@@ -152,5 +152,5 @@ We offer a feature that allows users to configure the namespace for their applic
 
 There are two scenarios in which this feature can be utilized:
 
-- Assigning a New Namespace: Users can set a new namespace immediately after creating the `DSCInitialization` instance, before creating the `DataScienceCluster` instance.
+- Assigning a New Namespace: Users can set a new namespace using `DSCInitialization` instance before creating the `DataScienceCluster` instance.
 - Switching to a New Namespace: Users have the option to switch to a new namespace after resources have already been established in the application's current namespace. It's important to note that in this scenario, only specific resources (such as deployments, configmaps, networkpolicies, roles, rolebindings, secrets etc) will be removed from the old application namespace during cleanup. For namespace-scoped CRD instances, users will be responsible to cleanup themselves.