From 4dff2039b0a3b6acaf964f3e61f63017822ade80 Mon Sep 17 00:00:00 2001 From: Gregory Gauthier Date: Tue, 31 Mar 2026 15:18:20 +0100 Subject: [PATCH] docs(workon): clarify references to workon command in documentation Update the description in todo/queued/workon.md to specifically mention the `workon` command instead of the generic "feature" for better clarity. --- todo/queued/workon.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/todo/queued/workon.md b/todo/queued/workon.md index 4900503..90e10b6 100644 --- a/todo/queued/workon.md +++ b/todo/queued/workon.md @@ -13,7 +13,7 @@ Grokkit is being customized to suit my own development workflow. So, there are a number of features that may not be translatable to other developers' habits. As such, this feature assumes that the repository has a "todo" folder with a "queued", "doing" and "completed" subfolder, that function as the in-situ ticketing system. If the "todo" folder is not present, grokkit will create it. -Also, if no IDE is specified in the config, the feature will default to not opening the editor. If `cnadd` is not available, the feature will default to not logging the beginning of the work. +Also, if no IDE is specified in the config, the `workon` command will default to not opening the editor. If `cnadd` is not available, the `workon` command will default to not logging the beginning of the work. **Benefits**: