diff --git a/.github/vale/dicts/aiven.dic b/.github/vale/dicts/aiven.dic
index bf5df58e5d..6dd8654ada 100644
--- a/.github/vale/dicts/aiven.dic
+++ b/.github/vale/dicts/aiven.dic
@@ -40,6 +40,7 @@ connect
 Couchbase
 CPU/MS
 CRD
+cURL
 cyber
 datacenter
 datacenters
diff --git a/docs/platform/howto/monitoring-services.rst b/docs/platform/howto/monitoring-services.rst
index 36ef06bd7b..be1be8adc8 100644
--- a/docs/platform/howto/monitoring-services.rst
+++ b/docs/platform/howto/monitoring-services.rst
@@ -10,7 +10,7 @@ When running Aiven services, you get access by default to both metrics and logs
 
 You can also use the dedicated functions :ref:`service logs <avn-service-logs>` and :ref:`service metrics <avn-service-metrics>` to export your service's monitoring data via the :doc:`Aiven CLI </docs/tools/cli>`.
 
-Additionaly, you have the option to :doc:`export logs and metrics to an Aiven service or external provider</docs/platform/concepts/logs-metrics-alerts>`, expanding your monitoring capabilities. For example:
+Additionally, you have the option to :doc:`export logs and metrics to an Aiven service or external provider</docs/platform/concepts/logs-metrics-alerts>`, expanding your monitoring capabilities. For example:
 
 - You can send logs to :doc:`Aiven for Opensearch</docs/products/opensearch>`.
 - You can send metrics to :doc:`Aiven for m3</docs/products/m3db>`, and visualise these metrics with :doc:`Aiven for Grafana</docs/products/grafana>`.