copy

docs/ctags.md

@@ -68,7 +68,14 @@ Mapping out the repo like this provides some benefits:
   - GPT can see the 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 for the context window. However, this mapping approach significantly improves collaboration with GPT-4 on larger codebases compared to previous methods. It also minimizes the need for manual curation of files to add to the chat, empowering GPT to autonomously identify relevant files for the task at hand.
+Of course, for large repositories, even 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 minimizes the need for manual curation of
+files to add to the chat, empowering GPT to autonomously identify
+relevant files for the task at hand.
 
 ## Using ctags to make the map