diff --git a/README.md b/README.md
index 98b68f0c2..4fa1ef10e 100644
--- a/README.md
+++ b/README.md
@@ -19,7 +19,8 @@ Here are some example transcripts that show how you can chat with `aider` to wri
 
 * [**Complex Multi-file Change with Debugging**](https://aider.chat/examples/complex-change.html): GPT makes a complex code change that is coordinated across multiple source files, and resolves bugs by reviewing error output and doc snippets.
 
-* [**Create a Black Box Test Case**](https://aider.chat/examples/add-test.html): GPT creates a "black box" test case without access to the source of the method being tested, using only a [high level map of the repository based on ctags](https://aider.chat/docs/ctags.html).
+* [**Create a Black Box Test Case**](https://aider.chat/examples/add-test.html): GPT creates a "black box" test case without access to the source of the method being tested, using only a
+[high level map of the repository based on ctags](https://aider.chat/docs/ctags.html).
 
 You can find more chat transcripts on the [examples page](https://aider.chat/examples/).
 
diff --git a/examples/add-test.md b/examples/add-test.md
index 4d25d5297..401183474 100644
--- a/examples/add-test.md
+++ b/examples/add-test.md
@@ -7,7 +7,7 @@ access to the source code of the function being tested or any of the
 other code in the repo.**
 
 Instead, GPT is operating entirely off a
-[ctags based repo map](https://aider.chat/docs/ctags.html)
+[high level map of the repository based on ctags](https://aider.chat/docs/ctags.html),
 which provides details on all the symbols and function signatures in the repo.
 Using only the meta-data in the map, GPT is able to figure out how to call the method to be tested, as well as how to instantiate multiple class objects that are required to prepare for the test.