Fix typos (#274)

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

build/auth.md

@@ -3,7 +3,7 @@
 This document defines how authentication is provided during execution
 of a build.
 
-The build system supports two types of authentication, using Kuberernetes'
+The build system supports two types of authentication, using Kubernetes'
 first-class `Secret` types:
 
 * `kubernetes.io/basic-auth`

build/build-templates.md

@@ -8,7 +8,7 @@ A set of curated and supported build templates is available in the
 ## What is a Build Template?
 
 A `BuildTemplate` encapsulates a shareable [build](./builds.md)
-process with some limited paramaterization capabilities.
+process with some limited parameterization capabilities.
 
 ### Example template
 

build/builds.md

@@ -160,7 +160,7 @@ For example, use volumes to accomplish one of the following common tasks:
 
  * [Mount a Kubernetes secret](./auth.md).
 
- * Creat an `emptyDir` volume to act as a cache for use across multiple build
+ * Create an `emptyDir` volume to act as a cache for use across multiple build
    steps. Consider using a persistent volume for inter-build caching.
 
  * Mount a host's Docker socket to use a `Dockerfile` for container image

community/REVIEWING.md

@@ -12,7 +12,7 @@ This document provides guidelines for how the project's
 *   [Code reviewers](#code-reviewers)
 *   [Reviewing changes](#reviewing-changes)
     *   [Holds](#holds)
-*   [Project maintainers](#project-maintainers)
+*   [Approvers](#approvers)
 *   [Merging PRs](#merging-prs)
 
 ## Pull requests welcome

eventing/README.md

@@ -103,9 +103,9 @@ more interesting and specific Sources over time.
 - **Feed** is a primitive object defining a connection between an EventType and
   the action (as an
   [CloudEvents compatible HTTP endpoint](https://github.com/cloudevents/spec/blob/master/http-transport-binding.md)).
-- **EventType** and **ClusterEventType** descibe a specific set of events with a
+- **EventType** and **ClusterEventType** describe a specific set of events with a
   common schema which are emitted by an EventSource. EventType is
-  namespace-scoped, while ClusterEventTypes are installed by an adminastrator
+  namespace-scoped, while ClusterEventTypes are installed by an administrator
   and available in all namespaces in your cluster.
 - **EventSource** and **ClusterEventSource** describe an external system which
   may produce one or more EventTypes.

install/Knative-with-Gardener.md

@@ -129,7 +129,7 @@ cluster.
 
 ## Alternative way to enable Knative with Gardener
 
-Ask your Gardener administrator to configure the Gardener Bouqet addon manager
+Ask your Gardener administrator to configure the Gardener Bouquet addon manager
 with the following CRDs:
 
 ```
@@ -156,7 +156,7 @@ spec:
     istio: "0.8.0"
 ```
 
-And of course create the respectve `ConfigMaps`:
+And of course create the respective `ConfigMaps`:
 
 ```
 curl https://raw.githubusercontent.com/knative/serving/v0.1.1/third_party/istio-0.8.0/istio.yaml