diff --git a/docs/Status-files.md b/docs/Status-files.md
index ba865b2eb37..6e29066e24f 100644
--- a/docs/Status-files.md
+++ b/docs/Status-files.md
@@ -70,7 +70,7 @@ dart2js, should produce a CompileError".
 
 [clue]: https://en.wikipedia.org/wiki/Cluedo
 
-With miles of tests and piles of configurtions, we need a compact notation for
+With miles of tests and piles of configurations, we need a compact notation for
 defining expectations. That's what status files aim to be.
 
 A status file is a line-oriented (newlines are significant) plain text file.
diff --git a/docs/Testing.md b/docs/Testing.md
index 02eb0566e08..be7acdd9e09 100644
--- a/docs/Testing.md
+++ b/docs/Testing.md
@@ -152,7 +152,7 @@ behavior was the last time we ran the test under some configuration. We call
 this the test's **status**.
 
 In the past, status was recorded in a separate set of
-[**status files**][Status-files.md]. These live in the repo under `tests/`.
+[**status files**](Status-files.md). These live in the repo under `tests/`.
 In order to change the expected
 behavior of a test, you had to manually change the status file and then commit
 that change. In practice, we found this doesn't scale to the number of tools and