diff --git a/docs/customer-groups.mdx b/docs/customer-groups.mdx
index 716bd55..d40f9ee 100644
--- a/docs/customer-groups.mdx
+++ b/docs/customer-groups.mdx
@@ -1,6 +1,6 @@
---
title: 'Customer groups'
-description: 'Organise and segment your customers'
+description: 'Organise and segment your customers.'
---
Customer groups can be used to organize and segment your customers. For example you could organise your customers by their tier "Free", "Growth, "Enterprise" or use temporary groups to keep track of customers trialing beta features.
diff --git a/docs/data-model.mdx b/docs/data-model.mdx
index b12f18e..3fc47cd 100644
--- a/docs/data-model.mdx
+++ b/docs/data-model.mdx
@@ -5,15 +5,15 @@ description: 'A quick run-through of how things are structured within Plain.'
This page will give you a birds eye view of how Plain is structured. Whether you are using Plain's API or not, this is a quick way to get your bearings.
-Within Plain all data belongs to a **Workspace**. When you sign-up you create a workspace. Within a workspace you have **Users**, **Customers**, **Threads**, **Labels**, and **Events**.
+Within Plain all data belongs to a **Workspace**. Within a workspace you have **Users**, **Customers**, **Threads**, **Labels**, and **Events**.
## Workspace
-Everything within Plain happens in a workspace. Typically you will have one workspace using your company's name like you would in Slack or Discord.
+Everything within Plain happens in a workspace. Typically you will have one workspace like you would in Slack or Discord.
If you want to just try Plain you can make a demo workspace. Demo workspaces have the full functionality of a real workspace but come with a pre-generated support email adress which you can not change. They are also free!
-If you have multiple sub-products or want to have a staging environment with which to build API integrations out you can also create multiple workspaces to do that. (e.g. "Acme Staging" and "Acme Production").
+You can also create multiple workspaces if you want a testing environment: e.g. "Acme Staging" and "Acme Production".
## Users
@@ -31,9 +31,7 @@ Customers can also belong to one or more customer groups. This let's you organis
Threads are the core of Plain's data model and equivalent to tickets or conversations in other support platforms.
-Each thread belongs to one customer and has a status which is one of `Todo`, `Done` or `Snoozed`.
-
-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.
+Each thread belongs to one customer and has a status which is one of `Todo`, `Done` or `Snoozed`. 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 created automatically by inbound communications or programatically via the API, for example when a contact form is submitted.
diff --git a/docs/email/alternate-emails.mdx b/docs/email/alternate-emails.mdx
index 0d090b8..4564236 100644
--- a/docs/email/alternate-emails.mdx
+++ b/docs/email/alternate-emails.mdx
@@ -2,4 +2,13 @@
title: 'Alternate addresses'
---
-TODO
+Within Plain you can configure up to 5 alternate email addresses. Alternate email addresses allow you to receive and send emails from Plain just like your main support email address.
+
+You can configure these at the bottom of **Settings** → **Email** page in Plain.
+
+Alternate email addresses must:
+
+- Have the same domain as the main. E.g. if you main support email is help@acme.com then you could have hello@acme.com as an alternate addresses but not sales@tnt.com.
+- Be forwarded in the same way as your main help email to the email address Plain provides you when setting up your email.
+
+Once alternate emails are set up you can choose to reply from them when writing an email in Plain. By default Plain will always try to reply with the same email used by the customer.
diff --git a/docs/email/receiving.mdx b/docs/email/receiving.mdx
index 0e0b509..15f6d4f 100644
--- a/docs/email/receiving.mdx
+++ b/docs/email/receiving.mdx
@@ -20,13 +20,17 @@ If your email provider is not Google, you can still set up email forwarding in d
Under "Default routing" click on "CONFIGURE" or "ADD ANOTHER RULE"
- 
+
+ 
+
In the dropdown, select "Single recipient" and write your **support email address** under "Email address"
- 
+
+ 
+
@@ -34,17 +38,20 @@ If your email provider is not Google, you can still set up email forwarding in d
Choose "Replace recipient" and paste the inbound email address (`@inbound.postmarkapp.com`)
- 
+
+ 
+
- Scroll further down, and choose "Perform this action on non-recognised and recognised addresses"
+ Scroll further down, and choose "Perform this action on non-recognised and recognised addresses"
-
+
+ 
+
+ ...and That's it! 💅
-
-And That's it! 💅
diff --git a/docs/email/sending.mdx b/docs/email/sending.mdx
index b28f561..9a0e556 100644
--- a/docs/email/sending.mdx
+++ b/docs/email/sending.mdx
@@ -1,12 +1,13 @@
---
title: 'Sending emails'
-description: 'To be able to send emails from Plain using your support email address, you will need to add a couple of DNS records to your domain.'
---
+To be able to send emails from Plain using your support email address, you will need to add a couple of DNS records to your domain.
+
While setting up your email, you will see DNS settings that need to be
configured for your domain:
-
+
The first record is the "DKIM". It is part of the available mechanisms that exist to authenticate
emails: verifying that you're the actual sender of the email.
diff --git a/public/images/email-setup/email-setup-4.png b/public/images/email-setup/email-setup-4.png
index dc7581a..dcd9702 100644
Binary files a/public/images/email-setup/email-setup-4.png and b/public/images/email-setup/email-setup-4.png differ
diff --git a/public/images/labels/labels-introduction.png b/public/images/labels/labels-introduction.png
index 76c59d9..d215910 100644
Binary files a/public/images/labels/labels-introduction.png and b/public/images/labels/labels-introduction.png differ