diff --git a/src/test-table.md b/src/test-table.md
index cd1ee58..6847225 100644
--- a/src/test-table.md
+++ b/src/test-table.md
@@ -4,7 +4,7 @@ Table-driven tests with [subtests] can be a helpful pattern for writing tests
 to avoid duplicating code when the core test logic is repetitive.
 
 If a system under test needs to be tested against _multiple conditions_ where
-certain parts of the the inputs and outputs change, a table-driven test should
+certain parts of the inputs and outputs change, a table-driven test should
 be used to reduce redundancy and improve readability.
 
   [subtests]: https://go.dev/blog/subtests
diff --git a/style.md b/style.md
index b5c9610..9fef812 100644
--- a/style.md
+++ b/style.md
@@ -3663,7 +3663,7 @@ Table-driven tests with [subtests](https://go.dev/blog/subtests) can be a helpfu
 to avoid duplicating code when the core test logic is repetitive.
 
 If a system under test needs to be tested against *multiple conditions* where
-certain parts of the the inputs and outputs change, a table-driven test should
+certain parts of the inputs and outputs change, a table-driven test should
 be used to reduce redundancy and improve readability.
 
 <table>