More updates

Author: hyunsun

design-proposals/cluster-orch-integrating-k8s-into-emt.md

@@ -168,7 +168,7 @@ Clusters for a specific host can be created in two ways:
 
 **1. Automatically during host registration**: This new option is designed for users with simple use cases who want Kubernetes to be available with a pre-defined template, reducing user interactions during onboarding and cluster creation.
 
-**2. Manually through a direct request to the Cluster Manager**: This method allows users to create a cluster dynamically on hosts that are already onboarded or provisioned (pending final design decisions). It is particularly useful for scenarios where a pool of hosts is available but not yet assigned specific workloads. Users can register hosts with the auto-onboard option (and potentially auto-provision, depending on the finalized design) and later create clusters using Kubernetes flavors and templates that align with their workload requirements.
+**2. Manually through a direct request to the Cluster Manager**: This method enables users to create clusters dynamically on hosts that are already onboarded (or provisioned, depending on the finalized design). It is particularly beneficial in scenarios where hosts are onboarded before their workloads are defined or assigned. The Onboarding Manager can register hosts with auto-onboard (and potentially auto-provision, based on the final design) option enabled, allowing Edge Operators or users to later install operating system and create clusters using OS profile, Kubernetes flavor and template that work best for specific workload requirements. This approach is well-suited for cloud-like edge usage, offering flexibility and adaptability.
 
 Before diving into workflow changes, it is essential to understand the coupling introduced by this design change between the following components: