diff --git a/docs/core/logging.md b/docs/core/logging.md
index 30ae20a76..5a2eaf143 100644
--- a/docs/core/logging.md
+++ b/docs/core/logging.md
@@ -152,7 +152,7 @@ Powertools for AWS Lambda (Java) extends the functionality of Log4J. Below is an
 
 !!! info "LambdaJsonLayout is now deprecated"
 
-    Configuring utiltiy using `<LambdaJsonLayout/>` plugin is deprecated now. While utility still supports the old configuration, we strongly recommend upgrading the 
+    Configuring utility using `<LambdaJsonLayout/>` plugin is deprecated now. While utility still supports the old configuration, we strongly recommend upgrading the 
     `log4j2.xml` configuration to `JsonTemplateLayout` instead. [JsonTemplateLayout](https://logging.apache.org/log4j/2.x/manual/json-template-layout.html) is recommended way of doing structured logging.
     
     Please follow [this guide](#upgrade-to-jsontemplatelayout-from-deprecated-lambdajsonlayout-configuration-in-log4j2xml) for upgrade steps.
diff --git a/docs/utilities/parameters.md b/docs/utilities/parameters.md
index 85d30d77e..c221e3a88 100644
--- a/docs/utilities/parameters.md
+++ b/docs/utilities/parameters.md
@@ -580,7 +580,7 @@ You could specify a different provider as long as it extends `BaseProvider` and/
     }
     ```
 
-    In this case ```SecretsProvider``` will be used to retrieve a raw value that is then trasformed into the target Object by using ```JsonTransformer```.
+    In this case ```SecretsProvider``` will be used to retrieve a raw value that is then transformed into the target Object by using ```JsonTransformer```.
     To show the convenience of the annotation compare the following two code snippets.