Fix typos of files under the site directory

Signed-off-by: Tsuyoshi Hombashi <[email protected]>

Author: thombashi

site/book/02-concepts/03-functions.md

@@ -7,7 +7,7 @@ KRM resources. Some example use cases:
 - Add a label to resources based on some filtering criteria
 - Use a `Team` custom resource to generate a `Namespace` and associated
   organization-mandated defaults (e.g. `RBAC`, `ResourceQuota`, etc.) when
-  bootstraping a new team
+  bootstrapping a new team
 - Bulk transformation of all `PodSecurityPolicy` resources to improve the
   security posture.
 - Inject a sidecar container (service mesh, mysql proxy, logging) in a workload

site/book/04-using-functions/01-declarative-function-execution.md

@@ -124,7 +124,7 @@ For example, `set-labels:v0.1` is automatically expanded to `gcr.io/kpt-fn/set-l
 The `exec` field specifies the executable command for the function. You can specify
 an executable with arguments.
 
-Example below uses `sed` executable to replace all occurances of `foo` with `bar`
+Example below uses `sed` executable to replace all occurrences of `foo` with `bar`
 in the package resources.
 
 ```yaml

site/book/05-developing-functions/02-developing-in-Go.md

@@ -120,9 +120,9 @@ Learn more about the `KubeObject` from the [go doc](https://pkg.go.dev/github.co
 The "get-started" package contains a `./testdata` directory. You can use this to test out your functions. 
 
 ```shell
-# Edit the `testdata/resources.yaml` with your KRM resources. 
+# Edit the `testdata/test1/resources.yaml` with your KRM resources. 
 # resources.yaml already has a `Deployment` and `Service` as test data. 
-vim data/resources.yaml
+vim testdata/test1/resources.yaml
 
 # Convert the KRM resources and FunctionConfig resource to `ResourceList`, and 
 # then pipe the ResourceList as StdIn to your function

site/book/07-effective-customizations/01-single-value-replacement.md

@@ -120,7 +120,7 @@ find all the appropriate resources that need the namespace.
 We have put in the starter name `bucket` and have an [ensure-name-substring] 
 that shows the package consumer that the project ID prefix is what we suggest.
 However if they have a different naming convention they can alter the name 
-prefix or suffix on all the resources in the pacakge.
+prefix or suffix on all the resources in the package.
 
 Since we are trying to set the annotation to the project ID we can use the 
 [set-annotations] function one time and the annotation are going to be set on 

site/book/08-package-orchestration/01-system-requirements.md

@@ -1,4 +1,4 @@
-In order to follow the packge orchestration examples, you will need:
+In order to follow the package orchestration examples, you will need:
 
 * the Package Orchestration service (Porch)
   [installed](https://kpt.dev/guides/porch-installation) in your Kubernetes

site/guides/namespace-provisioning-ui.md

@@ -113,7 +113,7 @@ namespace team blueprint using the UI.
     - Click the **SAVE** button to close the add resource dialog.
   - Click the **ADD BUTTON** button and add a new Resource Quota resource.
     - In the Resource Metadata section, name the resource "base".
-    - In the Compute Resources setion, set Max CPU Requests to "40" and Max
+    - In the Compute Resources section, set Max CPU Requests to "40" and Max
       Memory Requests to "40G".
     - Click the **SAVE** button to close the add resource dialog.
   - Click the **SAVE** button on the upper right corner of the screen.

site/guides/porch-user-guide.md

@@ -426,7 +426,7 @@ deployments-e06c2f6ec1afdd8c7d977fcf204e4d543778ddac   cloned-bucket   v1
 deployments-11ca1db650fa4bfa33deeb7f488fbdc50cdb3b82   istions-clone   v1                         false    Draft       deployments
 deployments-c32b851b591b860efda29ba0e006725c8c1f7764   new-package     v1                         false    Draft       deployments
 
-# Propose two packge revisions to be be published
+# Propose two package revisions to be be published
 $ kpt alpha rpkg propose \
   deployments-11ca1db650fa4bfa33deeb7f488fbdc50cdb3b82 \
   deployments-c32b851b591b860efda29ba0e006725c8c1f7764 \

site/installation/migration.md

@@ -346,7 +346,7 @@ kpt `v0.39`) to `v1` version(compatible with kpt `v1.0`).
    [kpt-functions-catalog]. You can start migrating your existing kpt packages
    using the function.
 3. `July 1, 2021:` Package format `v1` will be released which guarantees
-   backwards compatability for new packages going forward. The existing kpt
+   backwards compatibility for new packages going forward. The existing kpt
    packages are not compatible with the kpt `v1.0` binary and users will be
    prompted to migrate/fix their packages.
 4. `TBD:` Feature releases and bug fixes for pre-v1 versions of kpt will be

site/reference/annotations/apply-time-mutation/README.md

@@ -95,7 +95,7 @@ will not follow the rules specified by these annotations.
 ### JSONPath syntax
 
 Since there is no formal specification for JSONPath, the supported syntax
-depends on the chosen implimentation. In this case, kpt uses the
+depends on the chosen implementation. In this case, kpt uses the
 [ajson](https://github.com/spyzhov/ajson) library. For details about what
 language features are supported, see the
 [json-path-comparison table](https://cburgmer.github.io/json-path-comparison/).

site/reference/schema/plan/README.md

@@ -8,7 +8,7 @@ applied. Each entry in the list contains the `apiVersion`, `kind`, `name`, and `
 also contains an `action` field, which defines which action will be taken on the resource during apply. It can have one of
 the values:
 * **Create**: The resource does not currently exist in the cluster and will be created.
-* **Unchanged**: The resource exists in the cluster and there are no chnages to it.
+* **Unchanged**: The resource exists in the cluster and there are no changes to it.
 * **Delete**: The resource exists in the cluster, but is not among the applied resources. Therefore it will be pruned.
 * **Update**: The resource exists in the cluster and will be updated.
 * **Skip**: No changes will be made to this resource due to the presence of one or more lifecycle directives.