diff --git a/proposals/20201026-creating-control-plane-components.md b/proposals/20201026-creating-control-plane-components.md
index 823d9814..115f6dbf 100644
--- a/proposals/20201026-creating-control-plane-components.md
+++ b/proposals/20201026-creating-control-plane-components.md
@@ -59,7 +59,7 @@ To better illustrate the creation process, we define two Roles with different re
 
 * **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
@@ -194,6 +194,7 @@ We will host sets of default templates in this repositor. Users can specify whic
 Each component's controller will generate necessary certificates for the component and store them to the [secret resources](https://cluster-api.sigs.k8s.io/tasks/certs/using-custom-certificates.html) defined by CAPI. Also, The KAS controller will store the content of the kubeconfig file in a secret named `[clustername]-kubeconfig`.
 
 ![Control Plane Creating Process](nativeway.png)
+
 The creating process will include six steps:
 
 1. The user generates all CRs, i.e., NCP, Etcd, APIServer, ControllerManager, with the same namespace, and apply them.