Merge pull request #2257 from ticketmaster/misspell

fix misspellings

README.md

@@ -107,7 +107,7 @@ Take the work from step (1) above, move it into a
 `someApp` subdirectory called `base`, then
 place overlays in a sibling directory.
 
-An overlay is just another kustomization, refering to
+An overlay is just another kustomization, referring to
 the base, and referring to patches to apply to that
 base.
 

api/builtins/NamespaceTransformer.go

@@ -52,7 +52,7 @@ func (p *NamespaceTransformerPlugin) Transform(m resmap.ResMap) error {
 
 		matches := m.GetMatchingResourcesByCurrentId(r.CurId().Equals)
 		if len(matches) != 1 {
-			return fmt.Errorf("namespace tranformation produces ID conflict: %+v", matches)
+			return fmt.Errorf("namespace transformation produces ID conflict: %+v", matches)
 		}
 	}
 	return nil

api/internal/crawl/README.md

@@ -209,7 +209,7 @@ but they are functional.
 
 ## Technical details
 
-### Overall design and imlpementation
+### Overall design and implementations
 
 There are a few components that are all running together in order to get
 the overall application to work smoothly. This section will provide a brief

api/internal/crawl/config/elastic/esbackup.yaml

@@ -11,7 +11,7 @@ metadata:
 spec:
   storage:
     gcs:
-      # the bucket must exist for the snapshot respository to be created successfully.
+      # the bucket must exist for the snapshot repository to be created successfully.
       bucket: kustomize-backup
       # the path does not need to exist.
       # If the path does not exist, the controller will create the folder in the GCS bucket.

api/internal/crawl/search_cmds/transformer.md

@@ -1,4 +1,4 @@
-Find all the trasnformer files whose `kinds` field includes `HelmValues`, and
+Find all the transformer files whose `kinds` field includes `HelmValues`, and
 only output certain fields of each document:
 ```
 curl -s -X GET "${ElasticSearchURL}:9200/${INDEXNAME}/_search?pretty" -H 'Content-Type: application/json' -d'

docs/FAQ.md

@@ -18,7 +18,7 @@ cluster
 Resources (including configmap and secret generators)
 can _still be shared_ via the recommended best practice
 of placing them in a directory with their own
-kustomization file, and refering to this directory as a
+kustomization file, and referring to this directory as a
 [`base`](glossary.md#base) from any kustomization that
 wants to use it.  This encourages modularity and
 relocatability.

docs/eschewedFeatures.md

@@ -48,7 +48,7 @@ like adding labels or annotatations, get dedicated
 transformer plugins - `LabelTransformer`,
 `AnnotationsTransformer`, etc.
 These accept relatively simple YAML configuration
-allowing easy targetting of any number of resources.
+allowing easy targeting of any number of resources.
 
 Another class of edits take data from one specific
 object's field and use it in another (e.g. a service

docs/fields.md

@@ -206,7 +206,7 @@ See [field-name-replicas].
 ### resources
 
 Each entry in this list must be a path to a
-_file_, or a path (or URL) refering to another
+_file_, or a path (or URL) referring to another
 kustomization _directory_, e.g.
 
 ```

docs/glossary.md

@@ -273,9 +273,9 @@ more than one version).
 
 _kustomize_ is a command line tool supporting
 template-free, structured customization of declarative
-configuration targetted to k8s-style objects.
+configuration targeted to k8s-style objects.
 
-_Targetted to k8s means_ that kustomize has some
+_Targeted to k8s means_ that kustomize has some
 understanding of API resources, k8s concepts like
 names, labels, namespaces, etc. and the semantics of
 resource patching.

docs/plugins/README.md

@@ -209,7 +209,7 @@ a YAML file containing its configuration (the file name
 provided in the kustomization file).
 
 > TODO: restrictions on plugin to allow the _same exec
-> plugin_ to be targetted by  both the
+> plugin_ to be targeted by both the
 > `generators` and `transformers` fields.
 >
 > - first arg could be the fixed string

docs/v2.1.0_changelog.md

@@ -78,7 +78,7 @@ a7a2589e Fix yaml in generator examples.
 529db049 Introduce envs field.
 6d309b52 Introduce stacked transformers.
 abf538d8 Keep backward compatibility for image transformer
-7e12918f Keep var refernce in resources
+7e12918f Keep var references in resources
 7130e3ff Leave defautconfig empty for images
 3e85c458 Load default config for image transformer
 4162dbc2 Maintain resources in order loaded.

docs/versioningPolicy.md

@@ -37,7 +37,7 @@ the _kustomize Go API_.
 
 [import path]: https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher
 
-In `kustomize/v3` (and preceeding major versions), the
+In `kustomize/v3` (and preceding major versions), the
 kustomize program and the API live the same Go
 module at `sigs.k8s.io/kustomize`, at [import path]
 `sigs.k8s.io/kustomize/v3`.

examples/inlinePatch.md

@@ -4,7 +4,7 @@
 # Demo: Inline Patch
 
 A kustomization file supports patching in three ways:
-- patchesStrategicMerge: A list of patch files where each file is parsed as a [Stragetic Merge Patch].
+- patchesStrategicMerge: A list of patch files where each file is parsed as a [Strategic Merge Patch].
 - patchesJSON6902: A list of patches and associated targetes, where each file is parsed as a [JSON Patch] and can only be applied to one target resource.
 - patches: A list of patches and their associated targets. The patch can be applied to multiple objects. It auto detects whether the patch is a [Strategic Merge Patch] or [JSON Patch].
 

plugin/builtin/namespacetransformer/NamespaceTransformer.go

@@ -56,7 +56,7 @@ func (p *plugin) Transform(m resmap.ResMap) error {
 
 		matches := m.GetMatchingResourcesByCurrentId(r.CurId().Equals)
 		if len(matches) != 1 {
-			return fmt.Errorf("namespace tranformation produces ID conflict: %+v", matches)
+			return fmt.Errorf("namespace transformation produces ID conflict: %+v", matches)
 		}
 	}
 	return nil