Merge pull request #2 from team-plain/docs-fixes

add my fixes to docs

assignment.mdx

@@ -4,16 +4,16 @@ title: 'Assignment'
 
 <Frame>![Assignment within Plain](/public/images/assignment-introduction.png)</Frame>
 
-Threads can be assigned to any user or machine users in your workspace.
+Threads can be assigned to any user in your workspace.
 
-When you start typing a message, Plain will automatically assign you, so you typically don't really have to think about assigning yourself manually.
+When you start typing a message, Plain will automatically assign you, so you typically don't have to think about assigning yourself manually.
 
 If you want to assign a thread manually, you can use the shortcut **A** or use **⌘ + K**.
 
 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.
 
-We recommend turning sticky assignment off if your team has a shared support rotas. That way, whoever is on-call can pick up any threads you didn't finish.
+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.
 
 If you are interested in building fully automated bots using Plain, you can also programmatically assign threads to machine users as a starting point. If this sounds like an interesting use-case to you, please reach out to us via [email protected].

labels.mdx

@@ -4,7 +4,7 @@ title: 'Labels'
 
 <Frame>![Example labels](/public/images/labels-introduction.png)</Frame>
 
-Labels are a light weight and powerful way to categorize threads in Plain.
+Labels are a lightweight and powerful way to categorize threads in Plain.
 
 We recommend categorizing threads into topics so you immediately know, at a glance, what people are getting in touch about.
 

priorities.mdx

@@ -13,10 +13,10 @@ The available priorities are:
 - **Medium**
 - **Low**
 
-When you viewing a thread you can use the shortcut **P** to set the priority or use **⌘ + K**.
+When you are viewing a thread you can use the shortcut **P** to set the priority or use **⌘ + K**.
 
-When looking at your thread queue you can also filter and sort your thread by priority.
+When looking at your thread queue you can also filter and sort your threads by priority.
 
 Priorities can be useful in combination with contact forms. By asking questions such as "is this preventing you from using X?" you can determine whether bug reports or questions are high priority.
 
-Equally you can automatically set higher priorities for certain topics like security reports, if your contact form exposes a topic picker.
+Equally, you can automatically set higher priorities for certain topics like security reports, if your contact form exposes a topic picker.

reporting.mdx

@@ -10,7 +10,7 @@ You can see:
 
 - 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 next 24 hours
+- A preview of how many threads will be unsnoozed in the next 24 hours
 - Counts of assigned vs. unassigned threads
 - Breakdown of threads by customer group
 - Count of threads by label