diff --git a/cabal-testsuite/README.md b/cabal-testsuite/README.md
index cc87122816d847b975ae67ae5d26a40e40454fa6..9ed234d5600cf7f6286425c92f894f92ccbe6da1 100644
--- a/cabal-testsuite/README.md
+++ b/cabal-testsuite/README.md
@@ -137,7 +137,7 @@ these with include `hasSharedLibraries`, `hasProfiledLibraries`,
 `hasCabalShared`, `isGhcVersion`, `isWindows`, `isLinux`, `isOSX`
 and `hasCabalForGhc`.
 
-**I programatically modified a file in my test suite, but Cabal/GHC
+**I programmatically modified a file in my test suite, but Cabal/GHC
 doesn't seem to be picking it up.**  You need to sleep sufficiently
 long before editing a file, in order for file system timestamp
 resolution to pick it up.  Use `withDelay` and `delay` prior to
@@ -152,7 +152,7 @@ Hermetic tests
 --------------
 
 By default, we run tests directly on the source code that is checked into the
-source code repository.  However, some tests require programatically
+source code repository.  However, some tests require programmatically
 modifying source files, or interact with Cabal commands which are
 not hermetic (e.g., `cabal freeze`).  In this case, cabal-testsuite
 supports opting into a hermetic test, where we first make copy of all