diff --git a/docs/architecture.md b/docs/architecture.md
index 272431eb7..1d5134f12 100644
--- a/docs/architecture.md
+++ b/docs/architecture.md
@@ -43,7 +43,7 @@ is responsible for the following domains:
 Helm client, and interfaces with the Kubernetes API server. The server
 is responsible for the following:
 
-- Listing for incomming requests from the Helm client
+- Listening for incoming requests from the Helm client
 - Combining a chart and configuration to build a release
 - Installing charts into Kubernetes, and then tracking the subsequent
   release
diff --git a/docs/developers.md b/docs/developers.md
index 5ebdc58fe..5f41ce045 100644
--- a/docs/developers.md
+++ b/docs/developers.md
@@ -30,7 +30,7 @@ To run Helm and Tiller locally, you can run `bin/helm` or `bin/tiller`.
 - Helm and Tiller are known to run on Mac OSX and most Linuxes, including
   Alpine.
 - Tiller must have access to a Kubernets cluster. It learns about the
-  cluster by examining the Kube config files that `kubectl` uese.
+  cluster by examining the Kube config files that `kubectl` uses.
 
 ## gRPC and Protobuf
 
@@ -68,7 +68,7 @@ GCR registry.
 
 For development, we highly recommend using the
 [Kubernetes Minikube](https://github.com/kubernetes/minikube)
-developer-oriented distribution. Once this is installed, you can use 
+developer-oriented distribution. Once this is installed, you can use
 `helm init` to install into the cluster.
 
 For developing on Tiller, it is sometimes more expedient to run Tiller locally
@@ -186,4 +186,3 @@ Conventions:
   messages.
 - Deprecated RPCs, messages, and fields are marked deprecated in the comments (`// UpdateFoo
   DEPRECATED updates a foo.`).
-