Fixing typos

docs/documentation/guides/kubernetes-operator.mdx

@@ -8,7 +8,7 @@ Infisical's Kubernetes Operator provides a seamless, secure, and automated way t
 
 In this guide, we'll walk through how to:
 
-1. **Install the Infisical Operator on your Kubernetes clustser**.
+1. **Install the Infisical Operator on your Kubernetes cluster**.
 2. **Configure Authentication using Kubernetes Service Accounts**.
 3. **Use Each of the three CRDs**.
         - **InfisicalSecret** [Sync secrets from Infisical to Kubernetes]
@@ -48,7 +48,7 @@ kubectl get pods -n default
   </Step>
   <Step title="Create a Machine Identity and Set Up a Project">
 
-The operator uses a [Machine Identity](https://infisical.com/docs/documentation/platform/identities/machine-identities) to authenticate with Infisical thorugh the Kubernetes Auth Method
+The operator uses a [Machine Identity](https://infisical.com/docs/documentation/platform/identities/machine-identities) to authenticate with Infisical through the Kubernetes Auth Method
 1. Login to [Infisical](https://app.infisical.com/)
 2. Select **Organization Access** from the left navigational pane
 3. Create an Identity and give it a name and a role
@@ -131,7 +131,7 @@ kubectl get secrets -n default | grep infisical
   </Step>
   <Step title="Create the InfisicalSecret CRD">
 
-The [InfisicalSecret](https://infisical.com/docs/integrations/platforms/kubernetes/infisical-secret-crd) CRD tells the oeprator the sync secrets from Infisical to Kubernetes. By referencing your ```identityID```, ```projectSlug```, and ```envSlug```, this CRD tells the Infisical Operator whic Infisical secrets to fetch and how to format them into a Kubernetes Secret. Make sure to edit the provided CRD to match your specific Machine Identity ID, Project ID, and which environment your secrets are being pulled from (default is prod).
+The [InfisicalSecret](https://infisical.com/docs/integrations/platforms/kubernetes/infisical-secret-crd) CRD tells the operator the sync secrets from Infisical to Kubernetes. By referencing your ```identityID```, ```projectSlug```, and ```envSlug```, this CRD tells the Infisical Operator which Infisical secrets to fetch and how to format them into a Kubernetes Secret. Make sure to edit the provided CRD to match your specific Machine Identity ID, Project ID, and which environment your secrets are being pulled from (default is prod).
     - **Project Slug**: Can be found when you select your project and navigate to settings
     - **Identity ID**: Can be found when you select your machine identity from your organization's access control
 
@@ -213,7 +213,7 @@ kubectl apply -f example-push-secret-crd.yaml
 
 The [InfisicalDynamicSecret](https://infisical.com/docs/integrations/platforms/kubernetes/infisical-dynamic-secret-crd) CRD allows you to sync dynamic secrets and create leases automatically in Kubernetes as native **Kubernetes Secret** resources Any Pod, Deployment, or other Kubernetes resource can make use of dynamic secrets from Infisical just like any other Kubernetes secret. 
 
-    1. Navigate to your Infisical **Project** and click on the dropdown next to **Add Secret**. From here you will seelct **Add Dynamic Secret**
+    1. Navigate to your Infisical **Project** and click on the dropdown next to **Add Secret**. From here you will select **Add Dynamic Secret**
         - Select **SQL Database** as the service you would like to connect to.
         - Make sure to select **PostegreSQL** as the service. Enter in the connection details for your database, specifically the **Host**, **Port**, **User**, **Password**, and **Database Name**.
         - For the **Secret Name**, if you want to use the same name as the one in the cloned **InfisicalDynamicSecret** CRD, use the name **dynamic-secret-lease**. Otherwise you will need to change the **dynamicSecret.secretName** config in the InfisicalDynamicSecret CRD to whatever you name the secret here.
@@ -231,7 +231,7 @@ The [InfisicalDynamicSecret](https://infisical.com/docs/integrations/platforms/k
     kubectl apply -f dynamic-secret-crd.yaml
     ```
 
-    4. After applying the CRD, you sohuld notive that the dynamic secret lease has been created and synced with your cluster. Verify by running:
+    4. After applying the CRD, you should notice that the dynamic secret lease has been created and synced with your cluster. Verify by running:
 
 ```console
 kubectl get secret dynamic-secret-test -n default -o yaml
@@ -242,4 +242,4 @@ kubectl get secret dynamic-secret-test -n default -o yaml
 ![dynamic secrets output](../../images/dynamic-secret-crd.png)
   </Step>
 </Steps>
-### Congratulations! You sucessfully synced secrets with Kubernetes.
+### Congratulations! You successfully synced secrets with Kubernetes.