diff --git a/ADD_ADDON.md b/ADD_ADDON.md
index b9930ebdae..f66bb11836 100644
--- a/ADD_ADDON.md
+++ b/ADD_ADDON.md
@@ -4,7 +4,7 @@ To add a new addon to minikube the following steps are required:
 * For the new addon's .yaml file(s):
   * Put the required .yaml files for the addon in the minikube/deploy/addons directory.
   * Add the `kubernetes.io/minikube-addons: <NEW_ADDON_NAME>` label to each piece of the addon (ReplicationController, Service, etc.)
-  * In order to have `minkube open addons <NEW_ADDON_NAME>` work properly, the `kubernetes.io/minikube-addons-endpoint: <NEW_ADDON_NAME>` label must be added to the appropriate endpoint service (what the user would want to open/interact with).  This service must be of type NodePort.
+  * In order to have `minikube open addons <NEW_ADDON_NAME>` work properly, the `kubernetes.io/minikube-addons-endpoint: <NEW_ADDON_NAME>` label must be added to the appropriate endpoint service (what the user would want to open/interact with).  This service must be of type NodePort.
 
 * To add the addon into minikube commands/VM:
   * Add the addon with appropriate fields filled into the `Addon` dictionary, see this [Commit](https://github.com/kubernetes/minikube/commit/41998bdad0a5543d6b15b86b0862233e3204fab6#diff-e2da306d559e3f019987acc38431a3e8R133):