diff --git a/README.md b/README.md
index 08039c2..bcce9ba 100644
--- a/README.md
+++ b/README.md
@@ -24,11 +24,11 @@
 
 - **pretty**: `pls` output is cleaner, friendlier and more colorful.
 - **powerful**: `pls` provides more features than the competition.
-- **performant**: `pls` is speedy and performant (written in Rust).
+- **performing**: `pls` is speedy and performing (written in Rust).
 - **practical**: `pls` has sensible defaults and an effortless interface.
 - **petite**: `pls` is a small, single-file, binary executable.
 - **pliable**: `pls` can be extensively tweaked by power users and pros.
-- **personable**: `pls` prioritises consumption by humans over scripts.
+- **personable**: `pls` prioritizes consumption by humans over scripts.
 
 Pick whichever adjective helps you remember the command name.
 
diff --git a/docs/src/content/docs/about/comparison.mdx b/docs/src/content/docs/about/comparison.mdx
index 3e63a05..7702b0e 100644
--- a/docs/src/content/docs/about/comparison.mdx
+++ b/docs/src/content/docs/about/comparison.mdx
@@ -6,7 +6,7 @@ description:
 ---
 
 <Pls /> has the distinction of being an `ls(1)` replacement specifically
-targeted a a pro audience. This leads to different motivations, different
+targeted a pro audience. This leads to different motivations, different
 decisions, different choices and different defaults. This also gives us the
 advantage of being able to provide features that are powerful but complex.
 
diff --git a/docs/src/content/docs/about/faq.mdx b/docs/src/content/docs/about/faq.mdx
index 398016f..45f1b7d 100644
--- a/docs/src/content/docs/about/faq.mdx
+++ b/docs/src/content/docs/about/faq.mdx
@@ -60,9 +60,9 @@ deep customisation.
 **Why Rust and not _&lt;language&gt;_?**
 
 Rust is a good choice for CLI utilities because it enables them to be very
-performant. The pros don't want to see lag in a core part of your workflow.
+performing. The pros don't want to see lag in a core part of your workflow.
 
-Before I learned Rust, <Pls /> was written in Python (which was another reason
+Before, I learned Rust, <Pls /> was written in Python (which was another reason
 it's called <Pls />). It seemed like a good fit at the time because it was
 decently fast and easy to develop and distribute, but at a certain point Python
 started becoming a speed bottleneck. The point being, give me a good reason, and
diff --git a/docs/src/content/docs/about/intro.mdx b/docs/src/content/docs/about/intro.mdx
index facf333..13823ee 100644
--- a/docs/src/content/docs/about/intro.mdx
+++ b/docs/src/content/docs/about/intro.mdx
@@ -29,8 +29,8 @@ your directories, and searching for specific files, effortless.
     <Pls /> providers more features than the competition. It uses a cascading
     config system with specs.
   </Card>
-  <Card title="Performant" icon="rocket">
-    <Pls /> is speedy and performant (written in Rust). It continues to be fast
+  <Card title="Performing" icon="rocket">
+    <Pls /> is speedy and performing (written in Rust). It continues to be fast
     even with all features enabled.
   </Card>
   <Card title="Practical" icon="approve-check">
diff --git a/docs/src/content/docs/features/detail_view.mdx b/docs/src/content/docs/features/detail_view.mdx
index 7576a92..9de8878 100644
--- a/docs/src/content/docs/features/detail_view.mdx
+++ b/docs/src/content/docs/features/detail_view.mdx
@@ -113,7 +113,7 @@ pls --det=all # or -d=all
 
 ## Configuration
 
-Each of the detail fields is deeply customisable. Read on to know more the
+Each of the detail fields is deeply customizable. Read on to know more the
 customisation options supported by each field.
 
 ### Fields
diff --git a/src/config.rs b/src/config.rs
index 0651f29..0babd89 100644
--- a/src/config.rs
+++ b/src/config.rs
@@ -3,9 +3,9 @@
 //! `pls` supports customisation in two ways, through CLI arguments that change
 //! the output per session and through `.pls.yml` YAML files that can go deeper
 //! to tweak each individual string, change icons and add new node specs.
-//! Together they make `pls` the most customisable file lister.
+//! Together they make `pls` the most customizable file lister.
 //!
-//! For example, the the CLI arg `--det` controls what metadata columns must be
+//! For example, the CLI arg `--det` controls what metadata columns must be
 //! shown in a given run, whereas the `.pls.yml` file can be used to change the
 //! individual name for these columns.
 //!