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 allows users to create clusters on hosts that have already been onboarded or provisioned, depending on the finalized design. It is particularly useful in scenarios where host onboarding and workload creation occur independently by different users or at different times. For instance, an Onboarding Manager may register a pool of hosts with only the auto-onboard option enabled (and potentially auto-provision, based on the final design), and later Edge Operators or Users select an operating system and create clusters using an OS profile, Kubernetes flavor, and template that best align with specific workload requirements. This approach offers flexibility and adaptability, making it well-suited for cloud-like edge usage.
 
 Before diving into workflow changes, it is essential to understand the coupling introduced by this design change between the following components: