diff --git a/BUILD.md b/BUILD.md
index 7ed2de27272..fc80fe51ec1 100644
--- a/BUILD.md
+++ b/BUILD.md
@@ -268,7 +268,7 @@ Follow these instructions if you want to debug the KEDA webhook using VS Code.
    Refer to [this](https://code.visualstudio.com/docs/editor/debugging) for more information about debugging with VS Code.
 2. Expose your local instance to internet. If you can't expose it directly, you can use something like [localtunnel](https://theboroer.github.io/localtunnel-www/) using the command `lt --port 9443 --local-https --allow-invalid-cert` after installing the tool.
 
-3. Update the `admissing_webhooks.yaml` in `config/webhooks`, replacing the section (but not commiting this change)
+3. Update the `admissing_webhooks.yaml` in `config/webhooks`, replacing the section (but not committing this change)
    ```yaml
    webhooks:
    - admissionReviewVersions:
diff --git a/hack/update-codegen.sh b/hack/update-codegen.sh
index d784c4e24f7..76fe42b5c63 100755
--- a/hack/update-codegen.sh
+++ b/hack/update-codegen.sh
@@ -30,7 +30,7 @@ bash "${CODEGEN_PKG}"/generate-groups.sh "client,informer,lister" \
   --go-header-file "${SCRIPT_ROOT}"/hack/boilerplate.go.txt --output-base "${CODEGEN_OUTPUT_BASE}"
 
 # (Zbynek): If v2 is specified in go.mod, codegen unfortunately outputs to 'v2/pkg/generated' instead of 'pkg/generated',
-# and since we are using a specific ouput for codegen,  we need to move the generated code around the repo a bit
+# and since we are using a specific output for codegen,  we need to move the generated code around the repo a bit
 if [ -d "${CODEGEN_OUTPUT_GENERATED}" ]; then
   rm -rf "${SCRIPT_ROOT}"/pkg/generated
   mv "${CODEGEN_OUTPUT_GENERATED}" "${SCRIPT_ROOT}"/pkg/
diff --git a/tests/README.md b/tests/README.md
index 76510581db5..7b198a7eb4b 100644
--- a/tests/README.md
+++ b/tests/README.md
@@ -20,7 +20,7 @@ go test -v -tags e2e ./utils/cleanup_test.go      # Skip if you want to keep tes
 > As default, `go test -v -tags e2e ./utils/setup_test.go` deploys KEDA from upstream's main branch,
 > if you are adding an e2e test to your own code, this is not useful as you need your own version.
 > Like for [building and deploying your own image](../BUILD.md#custom-keda-as-an-image), you can use
-> the Makefile envrionment variables to customize KEDA deployment.
+> the Makefile environment variables to customize KEDA deployment.
 > eg. `IMAGE_REGISTRY=docker.io IMAGE_REPO=johndoe go test -v -tags e2e ./utils/setup_test.go`
 
 ### Specific test