upstream/helm
1
0
Fork 0
mirror of https://github.com/helm/helm.git synced 2026-05-28 04:35:48 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

docs(spelling): Fix some random misspellings

Browse source
This commit is contained in:
Kent Rancourt 2016-10-05 18:52:39 -04:00
parent ea66d66d2d
commit e6a9110ce0
2 changed files with 3 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/architecture.md
View file

@ -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

5
docs/developers.md
View file

@ -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.`).