Correct grammar in code base and examples

examples/aws/ack-controller/README.md

@@ -1,7 +1,7 @@
 # Steps to deploy ack-controllers to cluster
 
 ## Deploying Controllers
-Combined ResourseGroup for ACK Controllers
+Combined ResourceGroup for ACK Controllers
 - IAM
 - EC2
 - EKS

examples/aws/ack-controller/controllers/ec2-controller.yaml

@@ -20,7 +20,7 @@ spec:
         iamRole:
           maxSessionDuration: integer | default=3600
           oidcProvider: string | required=true
-          roleDescription: string | default=IRSA role for ACK EC2 controller deployement on EKS cluster using kro Resource group
+          roleDescription: string | default=IRSA role for ACK EC2 controller deployment on EKS cluster using kro Resource group
         image:
           deletePolicy: string | default=delete
           repository: string | default=public.ecr.aws/aws-controllers-k8s/ec2-controller

examples/aws/ack-controller/controllers/eks-controller.yaml

@@ -20,7 +20,7 @@ spec:
         iamRole:
           maxSessionDuration: integer | default=3600
           oidcProvider: string | required=true
-          roleDescription: string | default=IRSA role for ACK EKS controller deployement on EKS cluster using kro Resource group
+          roleDescription: string | default=IRSA role for ACK EKS controller deployment on EKS cluster using kro Resource group
         iamPolicy:
           # would prefer to add a policyDocument here, need to support multiline string here
           description: string | default="policy for eks controller"

examples/aws/ack-controller/crds/eks-crd-group.yaml

@@ -386,7 +386,7 @@ spec:
                       type: string
                     podIdentityAssociations:
                       description: |-
-                        An array of Pod Identity Assocations to be created. Each EKS Pod Identity
+                        An array of Pod Identity Associations to be created. Each EKS Pod Identity
                         association maps a Kubernetes service account to an IAM Role.
 
                         For more information, see Attach an IAM Role to an Amazon EKS add-on using

examples/aws/data-processor/eda-eks-data-processor.yaml

@@ -267,7 +267,7 @@ spec:
             ]
             }
   # SNS email subscription for status notifications
-    - id: dataProcessingNotificationEmailSubsription
+    - id: dataProcessingNotificationEmailSubscription
       template:
         apiVersion: sns.services.k8s.aws/v1alpha1
         kind: Subscription

examples/aws/eks-cluster-mgmt/README.md

@@ -306,11 +306,11 @@ Update $WORKSPACE_PATH/$WORKING_REPO
    external-secrets   external-secrets-cert-controller-586c6cbfd7-m5x94   1/1     Running   0             5m14s
    external-secrets   external-secrets-d699ddc68-hhgps                    1/1     Running   0             5m14s
    external-secrets   external-secrets-webhook-7f467cd6bf-ppzd5           1/1     Running   0             5m14s
-   kube-sytem         efs-csi-controller-f7b568848-72rzc                  3/3     Running   0             4m12s
-   kube-sytem         efs-csi-controller-f7b568848-vh85b                  3/3     Running   0             4m12s
-   kube-sytem         efs-csi-node-5znbp                                  3/3     Running   0             4m13s
-   kube-sytem         efs-csi-node-gzpsn                                  3/3     Running   0             4m13s
-   kube-sytem         efs-csi-node-zbzlv                                  3/3     Running   0             4m13s
+   kube-system        efs-csi-controller-f7b568848-72rzc                  3/3     Running   0             4m12s
+   kube-system        efs-csi-controller-f7b568848-vh85b                  3/3     Running   0             4m12s
+   kube-system        efs-csi-node-5znbp                                  3/3     Running   0             4m13s
+   kube-system        efs-csi-node-gzpsn                                  3/3     Running   0             4m13s
+   kube-system        efs-csi-node-zbzlv                                  3/3     Running   0             4m13s
    kyverno            kyverno-admission-controller-5b4c74758b-kf2k7       1/1     Running   0             5m5s
    kyverno            kyverno-background-controller-7cf48d5b9d-f67h6      1/1     Running   0             5m5s
    kyverno            kyverno-cleanup-controller-cd4ccdd8c-4b4gp          1/1     Running   0             5m5s

examples/aws/eks-cluster-mgmt/addons/bootstrap/default/addons.yaml

@@ -180,7 +180,7 @@ aws_efs_csi_driver:
   releaseName: aws-efs-csi-driver
   annotationsAppSet:
     argocd.argoproj.io/sync-wave: "4" # Needs to be after eck-efs 
-  namespace: "kube-sytem"
+  namespace: "kube-system"
   chartName: aws-efs-csi-driver
   chartRepository: https://kubernetes-sigs.github.io/aws-efs-csi-driver
   defaultVersion: "3.0.7"

examples/aws/eks-cluster-mgmt/addons/default/addons/efs-chart/pod-identity/values.yaml

@@ -1,6 +1,6 @@
 podIdentityPolicyCreate: true
 podIdentityRole:
-  description: "EFS Controler Default Role"
+  description: "EFS Controller Default Role"
 podIdentityAssociation:
   serviceAccounts:
       - ack-efs-controller

examples/aws/eks-cluster-mgmt/charts/pod-identity/values.yaml

@@ -5,7 +5,7 @@
 # podIdentityRole:
 #   description: "Test"
 #   # Only one of the two can be true Managed Policy or Policy Refs
-#   # If Policy is created it will automaticaly add it on managed Policies or PolicyRefs
+#   # If Policy is created it will automatically add it on managed Policies or PolicyRefs
 #   managedPolicies:
 #     - "arn:aws:iam::aws:policy/AmazonSSMReadOnlyAccess" 
 #     - "arn:aws:iam::aws:policy/Admin"

examples/aws/eks-cluster-mgmt/terraform/hub/variables.tf

@@ -175,7 +175,7 @@ variable "cluster_name" {
 }
 
 variable "use_ack" {
-  description = "Defining to use ack or terraform for pod identity if this is true then we will use this label to deploy resouces with ack"
+  description = "Defining to use ack or terraform for pod identity if this is true then we will use this label to deploy resources with ack"
   type        = bool
   default     = true
 }

examples/aws/ingress-triangle/README.md

@@ -62,7 +62,7 @@ annotations:
 
 ### 2. ServiceIngress RGD - Resources
 
-ServiceIngress demonstrates how to use multipel RGDs:
+ServiceIngress demonstrates how to use multiple RGDs:
 
 ```yaml
 resources:

examples/aws/serverless-microservice/microservice.yaml

@@ -23,7 +23,7 @@ spec:
         authorizerPasswordParameterARN: string | required=true
 
   resources:
-# Business logic data store (Amazon DynamoDB table) along with the permissiosn to access it (to be used by the AWS Lambda function that implements business logic)
+# Business logic data store (Amazon DynamoDB table) along with the permissions to access it (to be used by the AWS Lambda function that implements business logic)
   - id: itemsTable
     template:
       apiVersion: dynamodb.services.k8s.aws/v1alpha1

examples/aws/webstack/Readme.md

@@ -63,7 +63,7 @@ a new file called instance.yaml.
 ```shell
 envsubst < "webstack/instance-tmpl.yaml" > "webstack/instance.yaml"
 ```
-`clusterName` is a required field to achieve pod identity association. If your cluster name is not 'kro' then replace the value assigned to this field in the `webstack/instance.yaml` file with the name of your cluter. 
+`clusterName` is a required field to achieve pod identity association. If your cluster name is not 'kro' then replace the value assigned to this field in the `webstack/instance.yaml` file with the name of your cluster. 
 
 <pre>
 apiVersion: kro.run/v1alpha1

examples/aws/webstack/instance-tmpl.yaml

@@ -10,5 +10,5 @@ spec:
     enabled: true
     access: write
   ingress:
-    enabled: true # this will expose unathenticated alb
+    enabled: true # this will expose unauthenticated alb
   service: {}

pkg/apis/condition_set_test.go

@@ -510,7 +510,7 @@ func doTestSetTrueAccessor(t *testing.T, cases []ConditionSetTrueTest) {
 
 			if tc.set == cts.root {
 				// Skip validation the happy condition because we can't be sure
-				// seting it true was correct. Use tc.happyWant to test that case.
+				// setting it true was correct. Use tc.happyWant to test that case.
 				return
 			}
 

pkg/cel/types.go

@@ -251,7 +251,7 @@ var celReservedSymbols = sets.NewString(
 	"var", "void", "while",
 )
 
-// NativeToValue is an implementation of the ref.TypeAdapater interface which supports conversion
+// NativeToValue is an implementation of the ref.TypeAdapter interface which supports conversion
 // of rule values to CEL ref.Val instances.
 func (rt *DeclTypeProvider) NativeToValue(val interface{}) ref.Val {
 	return rt.typeAdapter.NativeToValue(val)

pkg/controller/instance/controller.go

@@ -34,7 +34,7 @@ import (
 // ReconcileConfig holds configuration parameters for the reconciliation process.
 // It allows the customization of various aspects of the controller's behavior.
 type ReconcileConfig struct {
-	// DefaultRequeueDuration is the default duration to wait before requeueing a
+	// DefaultRequeueDuration is the default duration to wait before requeuing a
 	// a reconciliation if no specific requeue time is set.
 	DefaultRequeueDuration time.Duration
 	// DeletionGraceTimeDuration is the duration to wait after initializing a resource

pkg/graph/parser/schemaless_test.go

@@ -283,7 +283,7 @@ func TestParseSchemalessResourceEdgeCases(t *testing.T) {
 			wantErr: false,
 		},
 		{
-			name: "Complex strcture with various expressions combinations",
+			name: "Complex structure with various expressions combinations",
 			resource: map[string]interface{}{
 				"string": "${string.value}",
 				"number": 42,

pkg/graph/resource.go

@@ -54,7 +54,7 @@ type Resource struct {
 	// readyWhenExpressions is a list of the expressions that need to be evaluated
 	// before the resource is considered ready.
 	readyWhenExpressions []string
-	// includeWhenExpressions is a list of the expresisons that need to be evaluated
+	// includeWhenExpressions is a list of the expressions that need to be evaluated
 	// to decide whether to create a resource graph definition or not
 	includeWhenExpressions []string
 	// namespaced indicates if the resource is namespaced or cluster-scoped.

pkg/metadata/finalizers_test.go

@@ -78,7 +78,7 @@ func TestInstanceFinalizerUnstructured(t *testing.T) {
 		expectError   bool
 	}{
 		{
-			name: "Set instance finalizer on unstructred obj w/o finalizers",
+			name: "Set instance finalizer on unstructured obj w/o finalizers",
 			initialObject: &unstructured.Unstructured{
 				Object: map[string]interface{}{
 					"metadata": map[string]interface{}{},

pkg/runtime/runtime_test.go

@@ -60,7 +60,7 @@ func Test_RuntimeWorkflow(t *testing.T) {
 		withIncludeWhenExpressions([]string{"schema.spec.secret.include == true"}),
 		withObject(map[string]interface{}{
 			"metadata": map[string]interface{}{
-				// this shound not be evaluated since the
+				// this should not be evaluated since the
 				// resource should not be included
 				"name": "${schema.spec.secret.name}",
 			},

pkg/simpleschema/markers_test.go

@@ -78,7 +78,7 @@ func TestParseMarkers(t *testing.T) {
 			wantErr: false,
 		},
 		{
-			name:  "complex markers with json defaul value",
+			name:  "complex markers with json default value",
 			input: "default={\"key\": \"value\"} description=\"A complex \\\"description\\\"\" required=true",
 			want: []*Marker{
 				{MarkerType: MarkerTypeDefault, Key: "default", Value: "{\"key\": \"value\"}"},

test/integration/suites/core/externalref_test.go

@@ -142,7 +142,7 @@ var _ = Describe("ExternalRef", func() {
 
 		Expect(env.Client.Create(ctx, instance)).To(Succeed())
 
-		// this is the expected dpeloyment
+		// this is the expected deployment
 		deployment1 := &appsv1.Deployment{
 			ObjectMeta: metav1.ObjectMeta{
 				Name:      "test-deployment",

website/docs/api/specifications/simple-schema.md

@@ -103,7 +103,7 @@ This disables the field-validation normally offered by kro, and forwards the val
 :::
 
 ```yaml
-kind: ResourceGraphDefintion
+kind: ResourceGraphDefinition
 metadata: {}
 spec:
   schema:

website/versioned_docs/version-0.1.0/docs/concepts/00-resource-groups.md

@@ -21,7 +21,7 @@ defining:
 - What status to expose (status)
 
 When you create a **ResourceGroup**, kro generates a new API (a.k.a Custom
-Resource Defintion) in your cluster that others can use to deploy resources in a
+Resource Definition) in your cluster that others can use to deploy resources in a
 consistent, controlled way.
 
 ## Anatomy of a ResourceGroup

website/versioned_docs/version-0.1.0/docs/getting-started/02-deploy-a-resource-group.md

@@ -136,7 +136,7 @@ spec:
    kubectl apply -f resourcegroup.yaml
    ```
 
-3. **Inpsect the `ResourceGroup`**: Check the status of the resources created by
+3. **Inspect the `ResourceGroup`**: Check the status of the resources created by
    the ResourceGroup using the `kubectl` command:
 
    ```bash

website/versioned_docs/version-0.1.0/docs/overview.md

@@ -35,7 +35,7 @@ standardized and streamlined manner.
 <div align="center">
 
 ![End user interface - Custom API](/img/architecture/KRO-Dev-Interface.png)
-_Fugure 1: End user interface - Custom API_
+_Figure 1: End user interface - Custom API_
 
 </div>
 
@@ -57,7 +57,7 @@ handles the deployment and configuration of the required resources.
 <div align="center">
 
 ![Platform Team Interface](/img/architecture/KRO-Platform-Team.png)
-_Fugure 2: ResourceGroup (RG) - Platform Team Interface_
+_Figure 2: ResourceGroup (RG) - Platform Team Interface_
 
 </div>
 
@@ -75,7 +75,7 @@ requirements.
 <div align="center">
 
 ![ResourceGroup Instance](/img/architecture/KRO-Instance.png)
-_Fugure 3: ResourceGroup Instance (RGI)_
+_Figure 3: ResourceGroup Instance (RGI)_
 
 </div>
 

website/versioned_docs/version-0.1.0/docs/overview.md.bak

@@ -35,7 +35,7 @@ standardized and streamlined manner.
 <div align="center">
 
 ![End user interface - Custom API](/img/architecture/KRO-Dev-Interface.png)
-_Fugure 1: End user interface - Custom API_
+_Figure 1: End user interface - Custom API_
 
 </div>
 
@@ -57,7 +57,7 @@ handles the deployment and configuration of the required resources.
 <div align="center">
 
 ![Platform Team Interface](/img/architecture/KRO-Platform-Team.png)
-_Fugure 2: ResourceGroup (RG) - Platform Team Interface_
+_Figure 2: ResourceGroup (RG) - Platform Team Interface_
 
 </div>
 
@@ -75,7 +75,7 @@ requirements.
 <div align="center">
 
 ![ResourceGroup Instance](/img/architecture/KRO-Instance.png)
-_Fugure 3: ResourceGroup Instance (RGI)_
+_Figure 3: ResourceGroup Instance (RGI)_
 
 </div>
 

website/versioned_docs/version-0.1.0/examples/deploying-controller.md

@@ -26,7 +26,7 @@ spec:
         iamRole:
           maxSessionDuration: integer | default=3600
           oidcProvider: string | required=true
-          roleDescription: string | default=IRSA role for ACK EKS controller deployement on EKS cluster using kro Resource group
+          roleDescription: string | default=IRSA role for ACK EKS controller deployment on EKS cluster using kro Resource group
         iamPolicy:
           # would prefer to add a policyDocument here, need to support multiline string here
           description: string | default="policy for eks controller"

website/versioned_docs/version-0.2.0/docs/concepts/00-resource-group-definitions.md

@@ -21,7 +21,7 @@ defining:
 - What status to expose (status)
 
 When you create a **ResourceGraphDefinition**, kro generates a new API (a.k.a Custom
-Resource Defintion) in your cluster that others can use to deploy resources in a
+Resource Definition) in your cluster that others can use to deploy resources in a
 consistent, controlled way.
 
 ## Anatomy of a ResourceGraphDefinition

website/versioned_docs/version-0.2.0/docs/getting-started/02-deploy-a-resource-graph-definition.md

@@ -136,7 +136,7 @@ spec:
    kubectl apply -f resourcegraphdefinition.yaml
    ```
 
-3. **Inpsect the `ResourceGraphDefinition`**: Check the status of the resources created by
+3. **Inspect the `ResourceGraphDefinition`**: Check the status of the resources created by
    the ResourceGraphDefinition using the `kubectl` command:
 
    ```bash

website/versioned_docs/version-0.2.0/docs/overview.md

@@ -35,7 +35,7 @@ standardized and streamlined manner.
 <div align="center">
 
 ![End user interface - Custom API](/img/architecture/KRO-Dev-Interface.png)
-_Fugure 1: End user interface - Custom API_
+_Figure 1: End user interface - Custom API_
 
 </div>
 
@@ -57,7 +57,7 @@ handles the deployment and configuration of the required resources.
 <div align="center">
 
 ![Platform Team Interface](/img/architecture/KRO-Platform-Team.png)
-_Fugure 2: ResourceGraphDefinition (RG) - Platform Team Interface_
+_Figure 2: ResourceGraphDefinition (RG) - Platform Team Interface_
 
 </div>
 
@@ -75,7 +75,7 @@ requirements.
 <div align="center">
 
 ![ResourceGraphDefinition Instance](/img/architecture/KRO-Instance.png)
-_Fugure 3: ResourceGraphDefinition Instance (RGI)_
+_Figure 3: ResourceGraphDefinition Instance (RGI)_
 
 </div>
 

website/versioned_docs/version-0.2.0/docs/overview.md.bak

@@ -35,7 +35,7 @@ standardized and streamlined manner.
 <div align="center">
 
 ![End user interface - Custom API](/img/architecture/KRO-Dev-Interface.png)
-_Fugure 1: End user interface - Custom API_
+_Figure 1: End user interface - Custom API_
 
 </div>
 
@@ -57,7 +57,7 @@ handles the deployment and configuration of the required resources.
 <div align="center">
 
 ![Platform Team Interface](/img/architecture/KRO-Platform-Team.png)
-_Fugure 2: ResourceGraphDefinition (RG) - Platform Team Interface_
+_Figure 2: ResourceGraphDefinition (RG) - Platform Team Interface_
 
 </div>
 
@@ -75,7 +75,7 @@ requirements.
 <div align="center">
 
 ![ResourceGraphDefinition Instance](/img/architecture/KRO-Instance.png)
-_Fugure 3: ResourceGraphDefinition Instance (RGI)_
+_Figure 3: ResourceGraphDefinition Instance (RGI)_
 
 </div>
 

website/versioned_docs/version-0.2.0/examples/deploying-controller.md

@@ -26,7 +26,7 @@ spec:
         iamRole:
           maxSessionDuration: integer | default=3600
           oidcProvider: string | required=true
-          roleDescription: string | default=IRSA role for ACK EKS controller deployement on EKS cluster using kro Resource group
+          roleDescription: string | default=IRSA role for ACK EKS controller deployment on EKS cluster using kro Resource group
         iamPolicy:
           # would prefer to add a policyDocument here, need to support multiline string here
           description: string | default="policy for eks controller"

website/versioned_docs/version-0.2.1/docs/concepts/00-resource-group-definitions.md

@@ -21,7 +21,7 @@ defining:
 - What status to expose (status)
 
 When you create a **ResourceGraphDefinition**, kro generates a new API (a.k.a Custom
-Resource Defintion) in your cluster that others can use to deploy resources in a
+Resource Definition) in your cluster that others can use to deploy resources in a
 consistent, controlled way.
 
 ## Anatomy of a ResourceGraphDefinition