diff --git a/lib/mutant/reporter/cli/printer/isolation_result.rb b/lib/mutant/reporter/cli/printer/isolation_result.rb
index 61fb63a73..6bcb5a671 100644
--- a/lib/mutant/reporter/cli/printer/isolation_result.rb
+++ b/lib/mutant/reporter/cli/printer/isolation_result.rb
@@ -34,8 +34,8 @@ class IsolationResult < self
 
           FORK_ERROR_MESSAGE = <<~'MESSAGE'
             Forking the child process to isolate the mutation in failed.
-            This meant that the either the RubyVM or your OS was under
-            too much pressure to add another child process.
+            This meant that either the RubyVM or your OS was under too much
+            pressure to add another child process.
 
             Possible solutions are:
             * Reduce concurrency
diff --git a/spec/unit/mutant/reporter/cli/printer/isolation_result_spec.rb b/spec/unit/mutant/reporter/cli/printer/isolation_result_spec.rb
index 61ca1b42f..c9ab2d9ba 100644
--- a/spec/unit/mutant/reporter/cli/printer/isolation_result_spec.rb
+++ b/spec/unit/mutant/reporter/cli/printer/isolation_result_spec.rb
@@ -62,8 +62,8 @@ def backtrace
 
       it_reports <<~'STR'
         Forking the child process to isolate the mutation in failed.
-        This meant that the either the RubyVM or your OS was under
-        too much pressure to add another child process.
+        This meant that either the RubyVM or your OS was under too much
+        pressure to add another child process.
 
         Possible solutions are:
         * Reduce concurrency
@@ -110,8 +110,8 @@ def backtrace
 
       it_reports <<~'STR'
         Forking the child process to isolate the mutation in failed.
-        This meant that the either the RubyVM or your OS was under
-        too much pressure to add another child process.
+        This meant that either the RubyVM or your OS was under too much
+        pressure to add another child process.
 
         Possible solutions are:
         * Reduce concurrency