docs: mention m subcommand

Amolith created

Change summary

README.md | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)

Detailed changes

README.md 🔗 

@@ -113,11 +113,12 @@ events.
 
 ### Event rendering
 
-The interactive, human-focused sub-commands are for watching these events and
-the resulting list as they change in real-time-ish. The goal and description and
-tasks and their descriptions are rendered at the top of the UI and updated based
-on database events using some Charm libraries. Change events are underneath the
-rendered state, sorted most recent (top) to least recent (bottom).
+The interactive, human-focused sub-commands (for now, just `m` for `m`onitor),
+are for watching the events and the resulting list as they change in
+real-time-ish. The goal and description and tasks and their descriptions are
+rendered at the top of the UI and updated based on database events using some
+Charm libraries. Change events are underneath the rendered state, sorted most
+recent (top) to least recent (bottom).
 
 This will probably be implemented later, once the LLM-oriented planning commands
 are solid and I see regular success with them.