diff --git a/README.md b/README.md
index 8b6fc8cd56b..92930338a8f 100644
--- a/README.md
+++ b/README.md
@@ -66,7 +66,7 @@ GitHub Actions will deploy the `main` branch automatically.
 
 ## Known Issues
 
-### nodeenv provided with Ubuntu 24.04 is old
+### `nodeenv` provided with Ubuntu 24.04 is old
 
 If you get the following errors:
 
@@ -81,12 +81,12 @@ An unexpected error has occurred: CalledProcessError: command: ('/usr/bin/python
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 ```
 
-Then this could be caused by the version of nodeenv delivered with Ubuntu 24.04.
+Then this could be caused by the version of `nodeenv` delivered with Ubuntu 24.04.
 You have two options.
 
 #### Option 1: Run pre-commit from a virtual environment
 
-1. Remove Ubuntu's pre-commit and nodeenv: `sudo apt purge nodeenv --autoremove`.
+1. Remove Ubuntu's pre-commit and `nodeenv`: `sudo apt purge nodeenv --autoremove`.
 1. Activate the virtual environment you created above: `. .venv/bin/activate`.
 1. Install pre-commit in the virtual environment: `pip install pre-commit`.
 1. Run pre-commit from the virtual environment: `pre-commit run --all`.
diff --git a/ci/vale/styles/config/vocabularies/Elastisys/accept.txt b/ci/vale/styles/config/vocabularies/Elastisys/accept.txt
index 72eed77fdcb..cdaed4199af 100644
--- a/ci/vale/styles/config/vocabularies/Elastisys/accept.txt
+++ b/ci/vale/styles/config/vocabularies/Elastisys/accept.txt
@@ -130,6 +130,7 @@ VM
 
 # Kubernetes terms
 Autoscaler
+autoscaled
 CRD
 CronJob
 finalizer
diff --git a/docs/adr/0056-allow-snippets-annotations-after-risk-acceptance.md b/docs/adr/0056-allow-snippets-annotations-after-risk-acceptance.md
index 0b66ce4b816..cf7805918f2 100644
--- a/docs/adr/0056-allow-snippets-annotations-after-risk-acceptance.md
+++ b/docs/adr/0056-allow-snippets-annotations-after-risk-acceptance.md
@@ -8,7 +8,7 @@
 
 We previously decided to allow [configuration snippet annotations](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#configuration-snippet) for Ingress NGINX, but only after formal risk acceptance from the Application Developer. However, we had not yet decided on handling specific use cases, such as whether [server snippets](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#server-snippet) should have stricter controls due to their higher risk profile.
 
-The difference is that config snippets allows to configure for whole location blocks and are validated by the Ingress Controller, while server snippets allows to configure for whole server block and are not validated by the Ingress Controller, they are passed directly to NGINX, which increases the vulnerability exposure area.
+The difference is that configuration snippets allows to configure for whole location blocks and are validated by the Ingress Controller, while server snippets allows to configure for whole server block and are not validated by the Ingress Controller, they are passed directly to NGINX, which increases the vulnerability exposure area.
 
 [Snippet Annotations](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/) are a powerful tool to allow injecting custom configurations, including both configuration and server snippets, into the Ingress NGINX Controller. For example, it allows things such as header renaming, custom authentication, or other advanced use cases etc.