From 8d18afa338274a3adc4b0037f0936a3e5628854c Mon Sep 17 00:00:00 2001
From: paul-gauthier <69695708+paul-gauthier@users.noreply.github.com>
Date: Sun, 21 May 2023 18:56:49 -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 806f4d073..323c21f3a 100644
--- a/docs/ctags.md
+++ b/docs/ctags.md
@@ -72,7 +72,7 @@ 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.
   - 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 their map might be too large
+Of course, for large repositories, even just their map might be too large
 for the context window.  However, this mapping approach opens up the
 ability to collaborate with GPT-4 on larger codebases than previous
 methods.  It also reduces the need to manually curate which files to