docs: Remove single-entry numbered lists in Grouping and Sorting

Also, make the instruction lines explicit for each field,
by inserting 'sort by ' or 'group by '.

Author: claremacrae

docs/Queries/Grouping.md

@@ -23,28 +23,28 @@ For more information, including adding your own customised statuses, see [[Statu
 
 ### Status
 
-1. `status` (Done or Todo, which is capitalized for visibility in the headings)
-    - Note that the Done group is displayed before the Todo group,
+- `group by status` (Done or Todo, which is capitalized for visibility in the headings)
+  - Note that the Done group is displayed before the Todo group,
       which differs from the Sorting ordering of this property.
 
 ### Status Name
 
-1. `status.name`
-    - This groups by the names you give to your custom statuses, in alphabetical order.
+- `group by status.name`
+  - This groups by the names you give to your custom statuses, in alphabetical order.
 
 > [!released]
 `group by status.name` was introduced in Tasks 1.23.0.
 
 ### Status Type
 
-1. `status.type`
-    - This groups by the types you have given to your custom statuses.
-    - In order to impose a useful sort order, the types are prefixed with a number, so the groups will appear in this order, and with these group names:
-        - `1 IN_PROGRESS`
-        - `2 TODO`
-        - `3 DONE`
-        - `4 CANCELLED`
-        - `5 NON_TASK`
+- `group by status.type`
+  - This groups by the types you have given to your custom statuses.
+  - In order to impose a useful sort order, the types are prefixed with a number, so the groups will appear in this order, and with these group names:
+    - `1 IN_PROGRESS`
+    - `2 TODO`
+    - `3 DONE`
+    - `4 CANCELLED`
+    - `5 NON_TASK`
 
 > [!released]
 `group by status.type` was introduced in Tasks 1.23.0.
@@ -53,52 +53,52 @@ For more information, including adding your own customised statuses, see [[Statu
 
 ### Done Date
 
-1. `done`
-    - The done date of the task, including the week-day, or `No done date`.
+- `group by done`
+  - The done date of the task, including the week-day, or `No done date`.
 
 > [!released]
 >
 > - `done` grouping option was introduced in Tasks 1.7.0.
 
 ### Due Date
 
-1. `due`
-    - The due date of the task, including the week-day, or `No due date`.
+- `group by due`
+  - The due date of the task, including the week-day, or `No due date`.
 
 > [!released]
 >
 > - `due` grouping option was introduced in Tasks 1.7.0.
 
 ### Scheduled Date
 
-1. `scheduled`
-    - The scheduled date of the task, including the week-day, or `No scheduled date`.
+- `group by scheduled`
+  - The scheduled date of the task, including the week-day, or `No scheduled date`.
 
 > [!released]
 >
 > - `scheduled` grouping option was introduced in Tasks 1.7.0.
 
 ### Start Date
 
-1. `start`
-    - The start date of the task, including the week-day, or `No start date`.
+- `group by start`
+  - The start date of the task, including the week-day, or `No start date`.
 
 > [!released]
 >
 > - `start` grouping option was introduced in Tasks 1.7.0.
 
 ### Created Date
 
-1. `created`
-    - The created date of the task, including the week-day, or `No created date`.
+- `group by created`
+  - The created date of the task, including the week-day, or `No created date`.
 
 > [!released]
 `created` grouping option was introduced in Tasks 2.0.0.
 
 ### Happens
 
-1. `happens`
-    - The earliest of start date, scheduled date, and due date, including the week-day, or `No happens date` if none of those are set.
+- `group by happens`
+  - The earliest of start date, scheduled date, and due date, including the week-day, or `No happens date` if none of those are set.
 
 > [!released]
 `happens` grouping option was introduced in Tasks 1.11.0.
@@ -107,46 +107,46 @@ For more information, including adding your own customised statuses, see [[Statu
 
 ### Priority
 
-1. `priority`
-    - The priority of the task, namely one of:
-        - `Priority 0: Highest`
-        - `Priority 1: High`
-        - `Priority 2: Medium`
-        - `Priority 3: None`
-        - `Priority 4: Low`
-        - `Priority 5: Lowest`
+- `group by priority`
+  - The priority of the task, namely one of:
+    - `Priority 0: Highest`
+    - `Priority 1: High`
+    - `Priority 2: Medium`
+    - `Priority 3: None`
+    - `Priority 4: Low`
+    - `Priority 5: Lowest`
 
 > [!released]
 >
 > - `priority` grouping option was introduced in Tasks 1.11.0.
 
 ### Urgency
 
-1. `urgency` ([[Urgency|urgency]])
-    - Currently, the groups run from the lowest urgency to highest.
-    - You can reverse this with `group by urgency reverse`.
-    - In a future release, the default group order will become from the highest urgency to lowest.
+- `group by urgency` ([[Urgency|urgency]])
+  - Currently, the groups run from the lowest urgency to highest.
+  - You can reverse this with `group by urgency reverse`.
+  - In a future release, the default group order will become from the highest urgency to lowest.
 
 > [!released]
 >
 > - `urgency` grouping option was introduced in Tasks 3.6.0.
 
 ### Recurrence
 
-1. `recurring`
-    - Whether the task is recurring: either `Recurring` or `Not Recurring`.
-1. `recurrence`
-    - The recurrence rule of the task, for example `every week on Sunday`, or `None` for non-recurring tasks.
-    - Note that the text displayed is generated programmatically and standardised, and so may not exactly match the text in any manually typed tasks. For example, a task with `🔁 every Sunday` is grouped in `every week on Sunday`.
+- `group by recurring`
+  - Whether the task is recurring: either `Recurring` or `Not Recurring`.
+- `group by recurrence`
+  - The recurrence rule of the task, for example `every week on Sunday`, or `None` for non-recurring tasks.
+  - Note that the text displayed is generated programmatically and standardised, and so may not exactly match the text in any manually typed tasks. For example, a task with `🔁 every Sunday` is grouped in `every week on Sunday`.
 
 > [!released]
 >
 > - `recurring` and `recurrence` grouping options were introduced in Tasks 1.11.0.
 
 ### Tags
 
-1. `tags`
-    - The tags of the tasks or `(No tags)`. If the task has multiple tags, it will show up under every tag.
+- `group by tags`
+  - The tags of the tasks or `(No tags)`. If the task has multiple tags, it will show up under every tag.
 
 > [!released]
 >
@@ -156,31 +156,31 @@ For more information, including adding your own customised statuses, see [[Statu
 
 ### File Path
 
-1. `path` (the path to the file that contains the task, that is, the folder and the filename)
+- `group by path` (the path to the file that contains the task, that is, the folder and the filename)
 
 ### Root
 
-1. `root` (the top-level folder of the file that contains the task, that is, the first directory in the path, which will be `/` for files in root of the vault)
+- `group by root` (the top-level folder of the file that contains the task, that is, the first directory in the path, which will be `/` for files in root of the vault)
 
 > [!released]
 `root` grouping option was introduced in Tasks 1.11.0.
 
 ### Folder
 
-1. `folder` (the folder to the file that contains the task, which will be `/` for files in root of the vault)
+- `group by folder` (the folder to the file that contains the task, which will be `/` for files in root of the vault)
 
 ### File Name
 
-1. `filename` (the link to the file that contains the task, without the `.md` extension)
-    - Note that tasks from different notes with the same file name will be grouped together in the same group.
+- `group by filename` (the link to the file that contains the task, without the `.md` extension)
+  - Note that tasks from different notes with the same file name will be grouped together in the same group.
 
 ### Backlink
 
-1. `backlink` (the text that would be shown in the task's [[Backlinks|backlink]], combining the task's file name and heading, but with no link added)
+- `group by backlink` (the text that would be shown in the task's [[Backlinks|backlink]], combining the task's file name and heading, but with no link added)
 
 ### Heading
 
-1. `heading` (the heading preceding the task, or `(No heading)` if there are no headings in the file)
+- `group by heading` (the heading preceding the task, or `(No heading)` if there are no headings in the file)
 
 ## Multiple groups
 

docs/Queries/Sorting.md

@@ -20,18 +20,18 @@ For more information, including adding your own customised statuses, see [[Statu
 
 ### Status
 
-1. `status` (done or todo)
+- `sort by status` (done or todo)
 
 ### Status Name
 
-1. `status.name` (Done, Todo, Cancelled, In Progress, Unknown, My very important custom status, etc - sorted alphabetically)
+- `sort by status.name` (Done, Todo, Cancelled, In Progress, Unknown, My very important custom status, etc - sorted alphabetically)
 
 > [!released]
 `sort by status.name` was introduced in Tasks 1.23.0.
 
 ### Status Type
 
-1. `status.type` (Sorted in the order `IN_PROGRESS`, `TODO`, `DONE`, `CANCELLED` then `NON_TASK`)
+- `sort by status.type` (Sorted in the order `IN_PROGRESS`, `TODO`, `DONE`, `CANCELLED` then `NON_TASK`)
 
 > [!released]
 `sort by status.type` was introduced in Tasks 1.23.0.
@@ -40,30 +40,30 @@ For more information, including adding your own customised statuses, see [[Statu
 
 ### Done Date
 
-1. `done` (the date when the task was done)
+- `sort by done` (the date when the task was done)
 
 ### Due Date
 
-1. `due` (the date when the task is due)
+- `sort by due` (the date when the task is due)
 
 ### Scheduled Date
 
-1. `scheduled` (the date when the task is scheduled)
+- `sort by scheduled` (the date when the task is scheduled)
 
 ### Start Date
 
-1. `start` (the date when the task starts)
+- `sort by start` (the date when the task starts)
 
 ### Created Date
 
-1. `created` (the date when the task was created)
+- `sort by created` (the date when the task was created)
 
 > [!released]
 `sort by created` was introduced in Tasks 2.0.0.
 
 ### Happens
 
-1. `happens` (the earliest of start date, scheduled date, and due date)
+- `sort by happens` (the earliest of start date, scheduled date, and due date)
 
 > [!released]
 `sort by happens` was introduced in Tasks 1.21.0.
@@ -72,29 +72,29 @@ For more information, including adding your own customised statuses, see [[Statu
 
 ### Description
 
-1. `description` (the description of the task)
+- `sort by description` (the description of the task)
 
 ### Priority
 
-1. `priority` (priority of the task; "low" is below "none": [[Priority|priorities]])
+- `sort by priority` (priority of the task; "low" is below "none": [[Priority|priorities]])
 
 ### Urgency
 
-1. `urgency` ([[Urgency|urgency]])
+- `sort by urgency` ([[Urgency|urgency]])
 
 ### Recurrence
 
-1. `recurring` (recurring tasks sort before non-recurring ones: [[Recurring Tasks]])
+- `sort by recurring` (recurring tasks sort before non-recurring ones: [[Recurring Tasks]])
 
 ### Tags
 
-1. `tag` (the description of the task)
+- `sort by tag` (the description of the task)
 
 ## Sort by File Properties
 
 ### File Path
 
-1. `path` (the path to the file that contains the task)
+- `sort by path` (the path to the file that contains the task)
 
 ### Root
 
@@ -106,15 +106,15 @@ It is not currently possible to sort by the folder that contains the task.
 
 ### File Name
 
-1. `filename` (the filename of the file that contains the task, with its extension)
-    - Note that tasks from different notes with the same file name will be sorter.
+- `sort by filename` (the filename of the file that contains the task, with its extension)
+  - Note that tasks from different notes with the same file name will be sorter.
 
 > [!released]
 `sort by filename` was introduced in Tasks 1.21.0.
 
 ### Heading
 
-1. `sort by heading` (the heading preceding the task; files with empty headings sort before other tasks)
+- `sort by sort by heading` (the heading preceding the task; files with empty headings sort before other tasks)
 
 > [!released]
 `sort by heading` was introduced in Tasks 1.21.0.