fix(docs): minor spelling and grammar fixes (#578)

Author: newtondev

website/docs/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
@@ -126,7 +126,7 @@ correctness and set up the necessary components:
    - Validates your schema definition follows the simple schema format
    - Ensures all resource templates are valid Kubernetes manifests
    - Checks that referenced values exist and are of the correct type
-   - Confirms resource dependencies form a valid Directed Acycled Graph(DAG)
+   - Confirms resource dependencies form a valid Directed Acyclic Graph(DAG)
      without cycles
    - Validates all CEL expressions in status fields and conditions
 
@@ -158,7 +158,7 @@ its behavior accordingly.
 ## ResourceGraphDefinition Instance Example
 
 After the **ResourceGraphDefinition** is validated and registered in the cluster, users
-can can create instances of it. Here's an example of how an instance for the
+can create instances of it. Here's an example of how an instance for the
 `WebApplication` might look:
 
 ```yaml title="my-web-app-instance.yaml"
@@ -198,4 +198,4 @@ resources:
        namespace: # optional, if empty uses instance namespace
 ```
 
-As part of the processing the Resource Graph, the instance reconciler waits for the `externalRef` object to be present and reads the object from the cluster as a node in the graph. Subsequent resources can use data from this node.
+As part of processing the Resource Graph, the instance reconciler waits for the `externalRef` object to be present and reads the object from the cluster as a node in the graph. Subsequent resources can use data from this node.

website/docs/docs/concepts/10-simple-schema.md

@@ -118,7 +118,7 @@ metrics: "map[string]float"
 ### Custom Types
 
 Custom types are specified in the separate `types` section.
-They provide a map of names to type specifications, that follow the simple schema.
+They provide a map of names to type specifications that follow the simple schema.
 
 Example:
 

website/docs/docs/concepts/20-access-control.md

@@ -25,7 +25,7 @@ effectively also has admin access to the cluster.
 
 ## `aggregation` Access
 
-In the `aggreagation` access mode, the chart includes an [_aggregated_ `ClusterRole`](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#aggregated-clusterroles)
+In the `aggregation` access mode, the chart includes an [_aggregated_ `ClusterRole`](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#aggregated-clusterroles)
 which dynamically includes all rules from all `ClusterRoles` that have the label
 `rbac.kro.run/aggregate-to-controller: "true"`.
 

website/docs/docs/getting-started/01-Installation.md

@@ -99,7 +99,7 @@ helm upgrade kro oci://ghcr.io/kro-run/kro/kro \
 :::info[**CRD Updates**]
 
 Helm does not support updating CRDs, so you may need to manually update or
-remove and re-apply kro related CRDs. For more information, refer to the Helm
+remove and reapply kro related CRDs. For more information, refer to the Helm
 documentation.
 
 :::

website/docs/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
@@ -154,7 +154,7 @@ spec:
 ### Create your Application Instance
 
 Now that your `ResourceGraphDefinition` is created, kro has generated a new API
-(Application) that orchestrates creation of the a `Deployment`, a `Service`, and
+(Application) that orchestrates the creation of a `Deployment`, a `Service`, and
 an `Ingress`. Let's use it!
 
 1. **Create an Application instance**: Create a new file named `instance.yaml`

website/docs/docs/overview.md

@@ -35,7 +35,7 @@ standardized and streamlined manner.
 <div align="center">
 
 ![End user interface - Custom API](../../../images/architecture-diagrams/KRO-Dev-Interface.png)
-_Fugure 1: End user interface - Custom API_
+_Figure 1: End user interface - Custom API_
 
 </div>
 
@@ -50,14 +50,14 @@ In the depicted example, the **Platform Team** has created a **RG** with
 arbitrary name "Application Stack" that encapsulates the necessary resources,
 along with any additional logic, abstractions, and security best practices. When
 the RGD is applied to the cluster, a new API of kind ApplicationStack is created
-and available for Developer to interact with. The Developers no longer need to
+and available for the Developer to interact with. The Developers no longer need to
 directly manage the underlying infrastructure complexities, as the custom API
 handles the deployment and configuration of the required resources.
 
 <div align="center">
 
 ![Platform Team Interface](../../../images/architecture-diagrams/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](../../../images/architecture-diagrams/KRO-Instance.png)
-_Fugure 3: ResourceGraphDefinition Instance (RGI)_
+_Figure 3: ResourceGraphDefinition Instance (RGI)_
 
 </div>