diff --git a/e2e/redraw_example/src/components.gleam b/e2e/redraw_example/src/components.gleam
index b57ef8d..da89138 100644
--- a/e2e/redraw_example/src/components.gleam
+++ b/e2e/redraw_example/src/components.gleam
@@ -1,7 +1,7 @@
 //// Defines the base components used in the shared view. Think copmonents as in
 //// functions that simply returns the HTML correctly formatted.
 //// Every component accepts two arrays, attributes and children, to follow the
-//// same convention as Lustre standard HTML. That way, you could leverage on
+//// same convention as Lustre standard HTML. That way, you could leverage
 //// your knowledge of Lustre, and behaves exactly as expected.
 
 import redraw
diff --git a/e2e/shared_view/README.md b/e2e/shared_view/README.md
index 5b5e7c7..dc2b4fe 100644
--- a/e2e/shared_view/README.md
+++ b/e2e/shared_view/README.md
@@ -9,7 +9,7 @@ the siblings folder to get your head around that idea.
 
 ```toml
 # In gleam.toml.
-# Leverage on compiler path resolution.
+# Leverage compiler path resolution.
 [dependencies]
 shared_view = { path = "../shared_view" }
 ```
diff --git a/e2e/shared_view/src/components.gleam b/e2e/shared_view/src/components.gleam
index 089f637..c6a7251 100644
--- a/e2e/shared_view/src/components.gleam
+++ b/e2e/shared_view/src/components.gleam
@@ -1,7 +1,7 @@
 //// Defines the base components used in the shared view. Think copmonents as in
 //// functions that simply returns the HTML correctly formatted.
 //// Every component accepts two arrays, attributes and children, to follow the
-//// same convention as Lustre standard HTML. That way, you could leverage on
+//// same convention as Lustre standard HTML. That way, you could leverage
 //// your knowledge of Lustre, and behaves exactly as expected.
 
 import shared_styles as styles
diff --git a/landing_page/src/landing_page.gleam b/landing_page/src/landing_page.gleam
index 4187857..c8ba32e 100644
--- a/landing_page/src/landing_page.gleam
+++ b/landing_page/src/landing_page.gleam
@@ -46,7 +46,7 @@ fn app() {
 fn description_section() {
   redraw.fragment([
     title_container([
-      main_title("Leverage on your CSS knowledge."),
+      main_title("Leverage your CSS knowledge."),
       main_title("Create your own styles."),
       main_title("Make your application Gleaming."),
     ]),
diff --git a/sketch/README.md b/sketch/README.md
index f5003eb..c4bbf90 100644
--- a/sketch/README.md
+++ b/sketch/README.md
@@ -13,11 +13,11 @@ to maximise performance in the browser and on BEAM.
 ## Distributions
 
 Sketch is thought as bare package, built as a foundation for every CSS packages
-that want to leverage on it. In the Sketch package, you'll find all CSS
-properties accessible, as well as low level generation functions, to go from
-Sketch to CSS. Sketch package is also made for framework developers, to provide
-a common basement, reusable across the entire Gleam ecosystem, letting users
-reuse their knowledge no matter what they are coding.
+that want to leverage it. In the Sketch package, you'll find all CSS properties
+accessible, as well as low level generation functions, to go from Sketch to CSS.
+Sketch package is also made for framework developers, to provide a common
+basement, reusable across the entire Gleam ecosystem, letting users reuse their
+knowledge no matter what they are coding.
 
 Sketch already supports two compilation target:
 [Lustre](https://hexdocs.pm/lustre/), with
@@ -207,9 +207,9 @@ Because pure CSS generation is straightforward, `sketch_css` does not need a
 cache to generate correct CSS files. Instead, `sketch_css` ships with a CLI
 tool, able to read your Gleam styles files, and output corresponding your CSS
 automagically, while providing an abstraction layer written in Gleam, to make
-sure you're using the right classes! It's an other way to leverage on Sketch
-core and enjoy the styling in Gleam, while taking advantage of all the static
-CSS power!
+sure you're using the right classes! It's an other way to leverage Sketch core
+and enjoy the styling in Gleam, while taking advantage of all the static CSS
+power!
 
 To run the generator, you have to use the command
 `gleam run -m sketch/css generate` at the root of your project. By default,
@@ -291,9 +291,9 @@ module. Build your classes, and use them across your codebase!
 
 ## Using media queries and pseudo-selectors
 
-Because we're building CSS, we can leverage on its full power, contrarily to
-inline styling. This mean we can use media queries and pseudo-selectors! You
-only need to call the proper functions, and Sketch will take care of the rest.
+Because we're building CSS, we can leverage its full power, contrarily to inline
+styling. This mean we can use media queries and pseudo-selectors! You only need
+to call the proper functions, and Sketch will take care of the rest.
 
 ```gleam
 import sketch
diff --git a/sketch_css/README.md b/sketch_css/README.md
index 860dc90..f1073a1 100644
--- a/sketch_css/README.md
+++ b/sketch_css/README.md
@@ -10,7 +10,7 @@ CSS generation is straightforward, `sketch_css` does not need a cache to
 generate correct CSS files. Instead, `sketch_css` ships with a CLI tool, able to
 read your Gleam styles files, and output corresponding your CSS automagically,
 while providing an abstraction layer written in Gleam, to make sure you're using
-the right classes! It's an other way to leverage on Sketch core and enjoy the
+the right classes! It's an other way to leverage Sketch core and enjoy the
 styling in Gleam, while taking advantage of all the static CSS power!
 
 To run the generator, you have to use the command