From 3697b9fd1112ccb850f67dbc0c1f7664dcdf1651 Mon Sep 17 00:00:00 2001
From: tanjunchen <2799194073@qq.com>
Date: Wed, 2 Oct 2019 10:31:26 +0800
Subject: [PATCH] fix some spelling mistakes

---
 .../implemented/20190925-minikube-enhancement-process.md      | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/enhancements/implemented/20190925-minikube-enhancement-process.md b/enhancements/implemented/20190925-minikube-enhancement-process.md
index 9eba4ccc13..1ecbefbb27 100644
--- a/enhancements/implemented/20190925-minikube-enhancement-process.md
+++ b/enhancements/implemented/20190925-minikube-enhancement-process.md
@@ -57,7 +57,7 @@ KEP's are a well-understood, but lengthier process geared toward making changes
 #### Con's
 
 * Invisible to casual contributors to a project, as these proposals do not show up within the GitHub project page
-* Lengthy template (1870+ words) that prompts for information that is not relevent to minikube
+* Lengthy template (1870+ words) that prompts for information that is not relevant to minikube
 * Time commitment deters casual contribution
 
 ### Google Docs Proposal Template
@@ -70,7 +70,7 @@ Rather than maintaining Markdown documents in the minikube repository, we could
 
 ### Con's
 
-* Authors may waste unneccessary time styling output
+* Authors may waste unnecessary time styling output
 * Styling may be inconsistent between proposals
 * Invisible to casual contributors to a project, as these proposals do not show up within the GitHub project page