fix language issues

Author: charleszheng44

proposals/20201026-creating-control-plane-components.md

@@ -53,13 +53,13 @@ The followings are terms that will be used in the proposal. Whether including th
 
 * **NestedControllerManager(NKCM)** - The kube-control-manager which belongs to the control plane of the nested cluster.
 
-* **Component Controller** - Operators that create components of the NCP, including the Etcd controller, KAS controller and KCM controller.
+* **Component Controller** - Operators that create the NCP components, including the Etcd controller, KAS controller and KCM controller.
 
 To better illustrate the creation process, we define two Roles with different responsibilities:
 
 * **Cluster Admin** - Responsible for creating the underlying super cluster and in-charge of creating Nested clusters.
 
-* **End User** - Represents a nested cluster user, these users have limited access to the super cluster.
+* **End User** - Represents a nested cluster user. These users have limited access to the super cluster.
 
 
 ## Summary
@@ -73,7 +73,7 @@ CAPN aims at providing control plane level isolation while sharing physical reso
 ### Goals
 
 - Define the CRD that represents each control plane component. The CRD needs to meet two requirements:
-    * Portable - the CRD should hold information that are required by different component controllers, e.g., [etcd-operator](https://github.com/coreos/etcd-operator), [etcd-cluster-operator](https://github.com/improbable-eng/etcd-cluster-operator/blob/f84abc6561735814debd67d45bb62d2d2ed8cf4a/api/v1alpha1/etcdcluster_types.go#L31-L47)
+    * Portable - the CRD should hold information that is required by different component controllers, e.g., [etcd-operator](https://github.com/coreos/etcd-operator), [etcd-cluster-operator](https://github.com/improbable-eng/etcd-cluster-operator/blob/f84abc6561735814debd67d45bb62d2d2ed8cf4a/api/v1alpha1/etcdcluster_types.go#L31-L47)
     * Customizable - the CRD should allow end-users to customize each component, i.e., specify the image, component version, and command-line options.
 
 - Define a standard process of creating control plane components for NCP.
@@ -136,7 +136,7 @@ type PatchSpec struct {
 
 #### Create prerequisites 
 
-We assume that the APIServer, ContollerManager, Etcd and the NCP CR are located in the same namespace. To create an NCP, we need to first create APIserver CR, ControllerManager CR, Etcd CR, NCP CR, and a namespace that holds all the CRs, then the component controller can cooperate with each other to create components for the NCP. 
+We assume that the APIServer, ContollerManager, Etcd, and the NCP CR are located in the same namespace. To create an NCP, we need first to create APIserver CR, ControllerManager CR, Etcd CR, NCP CR, and a namespace that holds all the CRs, then the component controller can cooperate to create components for the NCP. 
 
 As there exist dependencies between components, i.e., KAS cannot run without Etcd, KCM cannot work without KAS, when creating NCP components, component controllers will need to get information and status of other CRs. To achieve this, we will add three `ObjectReference` to the `NestedControlPlaneSpec` with each `ObjectReference` points to a component.
 
@@ -159,7 +159,7 @@ After applying the NCP CR, the NCP controller will find the three associated com
 
 ### Creation
 
-End-users can create component CRs manually and apply them to the cluster with an NCP to create the resources. In the future, we might introduce the `Template` CR, which will handle the creation of the component CRs in it's controller. We assume that at any given time, there will be only component controller for each component, and it is cluster administrator's responsibility to setup the proper component controllers. 
+End-users can create component CRs manually and apply them to the cluster with an NCP to create the resources. In the future, we might introduce the `Template` CR, which will handle the creation of the component CRs in it's controller. We assume that there will be only one component controller for each component at any given time, and it is the cluster administrator's responsibility to set up the proper component controllers.
 
 #### In-tree
 
@@ -183,11 +183,11 @@ The creating process will include six steps:
 
 #### Using out-of-tree provisioners
 
-If users intend to use an external component controller, they can disable any or all of the component controllers within the CAPN Manager. For example, if you wanted to use the [etcd-cluster-operator](https://github.com/improbable-eng/etcd-cluster-operator) this requires the [EtcdCluster](https://github.com/improbable-eng/etcd-cluster-operator/blob/master/api/v1alpha1/etcdcluster_types.go) CR. To support this you would implement a custom controller that listens for `NestedEtcd` resource and will create the necessary CRs for that implementation and update the required status fields on `NestedEtcd` to allow dependent services to be provisioned. This can be done using the [kubebuilder-declarative-pattern](https://github.com/kubernetes-sigs/kubebuilder-declarative-pattern) like is done for in-tree component controllers.
+If users intend to use an external component controller, they can ask the cluster administrator to disable any component controllers within the CAPN Manager. For example, if you wanted to use the [etcd-cluster-operator](https://github.com/improbable-eng/etcd-cluster-operator) this requires the [EtcdCluster](https://github.com/improbable-eng/etcd-cluster-operator/blob/master/api/v1alpha1/etcdcluster_types.go) CR. To support this, you would implement a custom controller that listens for `NestedEtcd` resource and will create the necessary CRs for that implementation and update the required status fields on `NestedEtcd` to allow dependent services to be provisioned. This can be done using the [kubebuilder-declarative-pattern](https://github.com/kubernetes-sigs/kubebuilder-declarative-pattern) like is done for in-tree component controllers.
 
 ![Creating a Control Plane using out-of-tree provisioners](out-of-tree.png)
 
-In the following example, we assume that the user intend to use Etcd-cluster-operator(ECO) as the Etcd controller. The creating process will include seven steps:
+In the following example, we assume that the user intends to use Etcd-cluster-operator(ECO) as the Etcd controller. The creating process will include seven steps:
 
 1. The cluster administrator deletes the in-tree Etcd controller and deploys the custom Etcd controller (ECO controller).
 
@@ -345,7 +345,7 @@ There is no need to worry about malicious users to manipulate other users' resou
 A malicious user can still skew the system by creating a massive amount of resources. 
 To avoid this, we need to enhance the syncer component; however, this topic is 
 beyond this proposal's scope. The proposed mechanism will not lead to any 
-severe security issue.
+severe security issues.
 
 ## Implementation History