diff --git a/api-reference/graphql/customers/customer-groups.mdx b/api-reference/graphql/customers/customer-groups.mdx
index 2f97ac0..c6cb74e 100644
--- a/api-reference/graphql/customers/customer-groups.mdx
+++ b/api-reference/graphql/customers/customer-groups.mdx
@@ -4,7 +4,7 @@ title: 'Customer groups'
 
 Customer groups can be used to group and segment your customers. For example you could organise your customers by their tier "Free", "Growth, "Enterprise" or make use of groups to keep track of customers trialing beta features.
 
-Customers can belong to one or many groups. You can filter your customers by group, allowing you to quickly focus on a subset of your customers.
+Customers can belong to one or many groups. You can filter customer threads by group, allowing you to quickly focus on a subset of them.
 
 This guide will show you how to add customers to groups using the API. You can also do this with the UI in Plain if you prefer.
 
diff --git a/api-reference/graphql/threads.mdx b/api-reference/graphql/threads.mdx
index fa9df20..1bbd05d 100644
--- a/api-reference/graphql/threads.mdx
+++ b/api-reference/graphql/threads.mdx
@@ -3,11 +3,11 @@ title: 'Threads'
 sidebarTitle: Overview
 ---
 
-Threads are the core of Plain's data model and equivalent to tickets or conversations in other support platforms. When you use Plain to help a customer you assign yourself to a thread and then mark the thread as done once you're done helping.
+Threads are the core of Plain's data model and equivalent to tickets or conversations in other support platforms. When you use Plain to help a customer you assign yourself to a thread and then mark the thread as `Done` once you're done helping.
 
 Threads are automatically created when a new email is received but can also be created via the API (when a customer submits a contact form for example).
 
-Threads have a status which can be in either **Todo**, **Snoozed** or **Done** and can only be assigned to one person.
+Threads have a status which can be in either `Todo`, `Snoozed` or `Done` and can only be assigned to one person.
 
 Threads belong to one customer but can contain multiple email threads and customers.
 
diff --git a/api-reference/graphql/threads/status-changes.mdx b/api-reference/graphql/threads/status-changes.mdx
index 7f6436d..e89e876 100644
--- a/api-reference/graphql/threads/status-changes.mdx
+++ b/api-reference/graphql/threads/status-changes.mdx
@@ -17,7 +17,7 @@ To change a threads status you need an API key with the following permissions:
 - `thread:edit`
 - `thread:read`
 
-### Mark thread as done
+### Mark thread as `Done`
 
 When any activity happens in a thread, it will move back to `Todo`.
 
@@ -36,7 +36,7 @@ Unlike traditional ticketing software, we expect a ticket to move between `Todo`
 
 You can snooze threads for a duration of time defined in seconds.
 
-When any activity happens in a thread, it will be automatically unsnoozed and move to **Todo**. Otherwise threads will be unsnoozed when the timer runs out.
+When any activity happens in a thread, it will be automatically unsnoozed and move to `Todo`. Otherwise threads will be unsnoozed when the timer runs out.
 
 <Tabs>
   <Tab title="Typescript SDK">
@@ -47,9 +47,9 @@ When any activity happens in a thread, it will be automatically unsnoozed and mo
   </Tab>
 </Tabs>
 
-### Mark thread as Todo
+### Mark thread as `Todo`
 
-This is useful if you mistakenly marked a thread as done or snoozed a thread and want to unsnooze it. Otherwise just write a message or do what you want to do and the thread will be automatically moved back to do **Todo**.
+This is useful if you mistakenly marked a thread as `Done` or snoozed a thread and want to unsnooze it. Otherwise just write a message or do what you want to do and the thread will be automatically moved back to do **Todo**.
 
 <Tabs items={['Typescript SDK', 'GraphQL']}>
   <Tab>
diff --git a/api-reference/migrate-to-threads.mdx b/api-reference/migrate-to-threads.mdx
index cf2b140..b191cde 100644
--- a/api-reference/migrate-to-threads.mdx
+++ b/api-reference/migrate-to-threads.mdx
@@ -49,7 +49,7 @@ In the ✨ **new** ✨ version of Plain:
 
 - A customer has multiple threads
 - A thread can be assigned
-- A thread has a status which is either Todo, Snoozed or Done
+- A thread has a status which is either `Todo`, `Snoozed` or `Done`
 - A thread has labels (e.g. "Bug report")
 - A thread has a priority
 - All emails and comms belong to a specific thread
diff --git a/assignment.mdx b/assignment.mdx
index 5b7da46..e5acbb5 100644
--- a/assignment.mdx
+++ b/assignment.mdx
@@ -12,7 +12,7 @@ If you want to assign a thread manually, you can use the shortcut **A** or use *
 
 By default in Plain, once you are assigned to a thread, you will never be automatically unassigned. This ensures that if you pick up a support request, you can see it through. We call this behavior "sticky assignment".
 
-If you'd like to change this behavior, you can do so in **Settings** → **Workflow**. Here you can choose to be automatically unassigned when a thread is marked as done or snoozed.
+If you'd like to change this behavior, you can do so in **Settings** → **Workflow**. Here you can choose to be automatically unassigned when a thread is marked as `Done` or `Snoozed`.
 
 We recommend turning sticky assignment off if your team has a shared support rota. That way, whoever is on-call can pick up any threads you didn't finish.
 
diff --git a/linear.mdx b/linear.mdx
index 531b722..08df88d 100644
--- a/linear.mdx
+++ b/linear.mdx
@@ -12,6 +12,6 @@ To do this, head to **Settings** → **Linear integration** and connect your wor
 
 Once this set-up is done, you can add a Linear issue from the right hand side of a thread or by pressing the shortcut `i`.
 
-Once a Linear issue is linked, the thread will move back to Todo when the Linear issue is completed or cancelled.
+Once a Linear issue is linked, the thread will move back to `Todo` when the Linear issue is completed or cancelled.
 
 This means that you can update customers when a bug or feature request that they reported has been fixed.
diff --git a/mint.json b/mint.json
index 65ef7a4..afcaf9e 100644
--- a/mint.json
+++ b/mint.json
@@ -76,7 +76,7 @@
       ]
     },
     {
-      "group": "Add context",
+      "group": "Adding context",
       "pages": ["customer-cards", "customer-groups", "events"]
     },
     {
diff --git a/quickstart.mdx b/quickstart.mdx
index 3655b57..26b342f 100644
--- a/quickstart.mdx
+++ b/quickstart.mdx
@@ -35,7 +35,7 @@ You can connect to Linear from **Settings** → **Linear**.
 
 </AccordionGroup>
 
-### Add context
+### Adding context
 
 To provide support more quickly, get more context into Plain from your own systems.
 
diff --git a/reporting.mdx b/reporting.mdx
index 375fa7f..7c1567f 100644
--- a/reporting.mdx
+++ b/reporting.mdx
@@ -8,7 +8,7 @@ When viewing your threads queue you can at a glance see key metrics on your curr
 
 You can see:
 
-- The breakdown of why a thread is in Todo (whether it's new threads, replies, Linear issues, etc.)
+- The breakdown of why a thread is in `Todo` (whether it's new threads, replies, Linear issues, etc.)
 - Distribution of threads by priority
 - A preview of how many threads will be unsnoozed in the next 24 hours
 - Counts of assigned vs. unassigned threads
diff --git a/shortcuts.mdx b/shortcuts.mdx
index a87d1bc..42e48f6 100644
--- a/shortcuts.mdx
+++ b/shortcuts.mdx
@@ -21,7 +21,7 @@ This is the list of available keyboard shortcuts in Plain:
 - **A** - Assign the thread
 - **P** - Change thread priority
 - **N** - Add a note to a thread
-- **E** - Mark a thread as done
+- **E** - Mark a thread as `Done`
 - **Z** - Snooze a thread
 - **!** - Mark customer as spam
 - **⌘ + .** - Show/hide queue