diff --git a/docs/chart_repository.md b/docs/chart_repository.md index 1c65348b3..fe1463c72 100644 --- a/docs/chart_repository.md +++ b/docs/chart_repository.md @@ -1,6 +1,6 @@ # The Chart Repository Guide -## Prerequistes +## Prerequisites * Go through the [Quickstart](quickstart.md) Guide * Read through the [Charts](charts.md) document @@ -80,7 +80,7 @@ Congratulations, now you have an empty GCS bucket ready to serve charts! In a similar way you can create charts repository using Github Pages. The first step will be to **create your gh-pages branch**. -You can do that localy as. +You can do that locally as. ``` $ git checkout -b [name_of_your_new_branch] diff --git a/docs/charts.md b/docs/charts.md index 7eac4a130..6955f0ab7 100644 --- a/docs/charts.md +++ b/docs/charts.md @@ -199,7 +199,7 @@ charts/ mysql-3.2.1.tgz ``` -Manging charts with `requirements.yaml` is a good way to easily keep +Managing charts with `requirements.yaml` is a good way to easily keep charts updated, and also share requirements information throughout a team. diff --git a/docs/charts_hooks.md b/docs/charts_hooks.md index a0effd1e3..dc8e98aea 100644 --- a/docs/charts_hooks.md +++ b/docs/charts_hooks.md @@ -29,7 +29,7 @@ The following hooks are defined: resources have been deleted. - pre-upgrade: Executes on an upgrade request after templates are rendered, but before any resources are loaded into Kubernetes (e.g. - before a kuberntes apply operation). + before a Kubernetes apply operation). - post-upgrade: Executes on an upgrade after all resources have been upgraded. - pre-rollback: Executes on a rollback request after templates are @@ -91,7 +91,7 @@ or `post-delete` hook. ## Writing a Hook -Hooks are just Kubernetes manfiest files with special annotations in the +Hooks are just Kubernetes manifest files with special annotations in the `metadata` section. Because they are template files, you can use all of the normal template features, including reading `.Values`, `.Release`, and `.Template`. @@ -145,7 +145,7 @@ One resource can implement multiple hooks: Similarly, there is no limit to the number of different resources that may implement a given hook. For example, one could declare both a secret -as a config map as a pre-install hook. It is important to keep in mind, +and a config map as a pre-install hook. It is important to keep in mind, though, that there are no ordering guarantees about hooks. When subcharts declare hooks, those are also evaluated. There is no way diff --git a/docs/charts_tips_and_tricks.md b/docs/charts_tips_and_tricks.md index 5919d77c2..4872e0091 100644 --- a/docs/charts_tips_and_tricks.md +++ b/docs/charts_tips_and_tricks.md @@ -46,7 +46,7 @@ they're blocks or template partials. And often, it's cleaner to keep these in their own files. In the `templates/` directory, any file that begins with an -underscore(`_`) is not expected to ouput a Kubernetes manifest file. So +underscore(`_`) is not expected to output a Kubernetes manifest file. So by convention, helper templates and partials are placed in a `_helpers.tpl` file. diff --git a/docs/developers.md b/docs/developers.md index f5f9cf8d2..4ae16a10d 100644 --- a/docs/developers.md +++ b/docs/developers.md @@ -29,7 +29,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 +- Tiller must have access to a Kubernetes cluster. It learns about the cluster by examining the Kube config files that `kubectl` uses. ## gRPC and Protobuf diff --git a/docs/glossary.md b/docs/glossary.md index 641dfdd59..875807268 100644 --- a/docs/glossary.md +++ b/docs/glossary.md @@ -118,7 +118,7 @@ A release can be upgraded to a newer chart or configuration. But since release history is stored, a release can also be _rolled back_ to a previous release number. This is done with the `helm rollback` command. -Importantly, a rolled back release will recieve a new release number. +Importantly, a rolled back release will receive a new release number. Operation | Release Number ----------|--------------- @@ -148,7 +148,7 @@ information on where each chart can be downloaded from. (Many chart repositories serve the charts as well as the `index.yaml` file.) A Helm client can point to zero or more chart repositories. By default, -Helm clients point the the `stable` official Kubernetes chart +Helm clients point to the `stable` official Kubernetes chart repository. ## Values (Values Files, values.yaml) diff --git a/docs/provenance.md b/docs/provenance.md index 538c41405..9693b907b 100644 --- a/docs/provenance.md +++ b/docs/provenance.md @@ -1,7 +1,7 @@ # Helm Provenance and Integrity Helm has provenance tools which help chart users verify the integrity and origin -of a package. Using industry-standard tools based on PKI, GnuPG, and well-resepected +of a package. Using industry-standard tools based on PKI, GnuPG, and well-respected package managers, Helm can generate and verify signature files. **Note:** diff --git a/docs/using_helm.md b/docs/using_helm.md index d688e0700..eb0805bc2 100644 --- a/docs/using_helm.md +++ b/docs/using_helm.md @@ -38,7 +38,7 @@ _repositories_. When you first install Helm, it is preconfigured to talk to the official Kubernetes charts repository. This repository contains a number of -carefully currated and maintained charts. This chart repository is named +carefully curated and maintained charts. This chart repository is named `stable` by default. You can see which charts are available by running `helm search`: