From 85cd9e833a69f2a345b310afd7ef241667e31ec7 Mon Sep 17 00:00:00 2001
From: paul-gauthier <69695708+paul-gauthier@users.noreply.github.com>
Date: Sun, 21 May 2023 22:16:43 -0700
Subject: [PATCH] Update ctags.md

---
 docs/ctags.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/ctags.md b/docs/ctags.md
index c3aa580f6..a653950ad 100644
--- a/docs/ctags.md
+++ b/docs/ctags.md
@@ -71,7 +71,7 @@ aider/
 
 Mapping out the repo like this provides some benefits:
 
-  - GPT can see variables, classes, methods and function signatures from everywhere in the repo. This alone may give it enough context to solve many tasks. For example, it can probably figure out how to use the API exported from a module based on the details shown in the map.
+  - GPT can see variables, classes, methods and function signatures from everywhere in the repo. This alone may give it enough context to solve many tasks. For example, it can probably figure out how to use the API exported from a module just based on the details shown in the map.
   - If it needs to see more code, GPT can use the map to figure out by itself which files it needs to look at. GPT will then ask to see these specific files, and `aider` will automatically add them to the chat context (with user approval).
 
 Of course, for large repositories, even just their map might be too large