diff --git a/docs/deployment/schedulers/k3s.md b/docs/deployment/schedulers/k3s.md
index 500f98f4c..a27cbbffd 100644
--- a/docs/deployment/schedulers/k3s.md
+++ b/docs/deployment/schedulers/k3s.md
@@ -1090,7 +1090,7 @@ See the [Kustomize](https://kustomize.io/) website for more details on how to us
 ### Using kubectl remotely
 
 > [!WARNING]
-> Certain ports must be open for interacting with the remote kubernets api. Refer to the [K3s networking documentation](https://docs.k3s.io/installation/requirements?os=debian#networking) for the required open ports between servers prior to running the command.
+> Certain ports must be open for interacting with the remote kubernetes api. Refer to the [K3s networking documentation](https://docs.k3s.io/installation/requirements?os=debian#networking) for the required open ports between servers prior to running the command.
 
 By default, Dokku assumes that all it controls all actions on the cluster, and thus does not expose the `kubectl` binary for administrators. To interact with kubectl, you will need to retrieve the `kubeconfig` for the cluster and configure your client to use that configuration.
 
diff --git a/docs/deployment/schedulers/scheduler-management.md b/docs/deployment/schedulers/scheduler-management.md
index ca20b4539..95036d825 100644
--- a/docs/deployment/schedulers/scheduler-management.md
+++ b/docs/deployment/schedulers/scheduler-management.md
@@ -123,7 +123,7 @@ At this time, the following dokku commands are used to implement a complete sche
     - triggers: post-app-clone-setup
 - `cron`: generates cron tasks for the app
     - triggers: scheduler-uses-host-cron, scheduler-cron-write
-- `deploy`: deploys app proceses and checks the status of a deploy
+- `deploy`: deploys app processes and checks the status of a deploy
     - triggers: scheduler-app-status, scheduler-deploy, scheduler-is-deployed, scheduler-logs-failed
 - `enter`: enters a running container
     - triggers: scheduler-enter