Merge pull request kubernetes#1812 from soltysh/kui_typos

Fix typos and formatting

Author: k8s-ci-robot

keps/sig-cli/20191111-kui.md

@@ -7,9 +7,11 @@ owning-sig: sig-cli
 participating-sigs:
   - sig-cli
 reviewers:
-  - TBD
+  - "@pwittrock"
+  - "@soltysh"
 approvers:
-  - TBD
+  - "@pwittrock"
+  - "@soltysh"
 editor: TBD
 creation-date: 2019-11-14
 last-updated: 2020-01-30
@@ -19,7 +21,7 @@ see-also:
 replaces:
 
 superseded-by:
- 
+
 ---
 
 # Kubectl Graphical Plugins
@@ -105,14 +107,16 @@ refer to as producing and distributing "fat" plugins, each plugin will
 contain its own copy of kui-core, including all of Electron (and its
 attendant copy of Chromium).
 
-An alternate krew integrration story, which we refer to as the "thin
+An alternate krew integration story, which we refer to as the "thin
 plugin" strategy, would require development of a chain loader. When
 installing a thin plugin, the plugin would install, if needed, the
-kui-loader plugin. This would: 1) allow for very small plugin
-downloads; 2) maintain the ability for plugins to pin themselves to a
-particular version of electron and kui-core; 3) avoid having a
-separate copy of chromium in memory for every plugin window.. We have
-a prototype of such a chain loader here:
+kui-loader plugin. This would:
+
+1) allow for very small plugin downloads;
+2) maintain the ability for plugins to pin themselves to a particular version of electron and kui-core;
+3) avoid having a separate copy of chromium in memory for every plugin window.
+
+A prototype of such a chain loader is here:
 [https://github.com/kui-shell/kask](https://github.com/kui-shell/kask).