(DOCS): Direct Email Reply (RocketChat#1455)

Author: paulofariadias

administrator-guides/email/direct-reply/README.md

@@ -1,74 +1,73 @@
-# Direct Reply [Email]
+# Direct Email reply
 
 ## Introduction
 
-Enabling this feature will allow your users to reply to chat messages by directly replying to email notifications they receive. We are using [subaddressing](https://en.wikipedia.org/wiki/Email_address#Subaddressing) for this feature.
+Enable this feature to allow users to reply to chat messages by directly replying to email notifications they receive. We currently use [subaddressing](https://en.wikipedia.org/wiki/Email_address#Subaddressing) for this feature.
 
-## Setup credentials
+## Set up credentials
 
-Go to Administration settings -> Email -> Direct Reply.
+Go to `Administration settings > Email > Direct reply`.
 
-Enter:
+After that:
 
-- select email server's protocol (`IMAP` or `POP`)
-- your email server's host name (e.g. `imap.example.com` or `pop.example.com`)
+- select the email server protocol (`IMAP` or `POP`)
+- your email server host name (e.g. `imap.example.com` or `pop.example.com`)
 - the port (143 or 993 for IMAP and 110 or 995 for POP)
 - ignore TLS `true` if port 143 or 110
 - email check frequency (in minutes) if POP server (>=2)
-- delete intercepted emails: select/keep `true` if you don't want to keep copy of email messages (in case IMAP server), recommended.
-- Separator (default & recommended) is the character separating base & tag part of email. e.g. `base+tag@domain` (separator: +). [More info here](https://en.wikipedia.org/wiki/Email_address#Subaddressing)
+- delete intercepted emails. We recommend to select/keep `true` if you don't want to keep copy of email messages, in case IMAP server.
+- a separator (default and recommended) is the character separating base and tag part of the email. E.g.: `base+tag@domain` (separator: +). [More info here](https://en.wikipedia.org/wiki/Email_address#Subaddressing)
 - your credentials (Username & password)
 
- Once filled, click "Save changes".
+ Once filled, click **Save changes**.
 
-## Example Settings
+## Example settings
 
-### IMAP Settings
+### IMAP settings
 
 ![IMAP server configuration.](imap-1.png)
 
-### POP3 Settings
+### POP3 settings
 
-Make sure your **POP3** server **doesn't** keep **copy** of the emails, otherwise it would be treated as new message every time.
+Make sure your **POP3** server keeps keep **no** copy of emails, otherwise it is treated as a new message every time.
 
 ![POP server configuration.](pop-1.png)
 
-Now you can reply chat messages via email. It supports full formatting like inline, multiline, bold, italics etc.
+Now, you can reply chat messages via email. It supports full formatting like inline, multiline, bold, italics etc.
 
-### Switching from IMAP to POP
+### Switch from IMAP to POP
 
-- Before switching from IMAP to POP over **same** __email address__, you __must__ **empty all the folders**. Failing to delete all emails would result into **duplicate** messages, as all those messages in POP would be treated as new messages.
+- Before you switch from IMAP to POP over the same email address, you must empty all the folders. Keeping all emails results in duplicate messages, because all those messages in POP are treated as new messages.
 
 ## Note
 
-- As par now, emails only in **English** language are supported or at least quote `On <date>, <author> wrote:` is in English.
+- Currently, only emails in English are supported, or at least the quote `On <date>, <author> wrote:` is in English.
 
-Email body in languages **other than English** may also work until and unless `On <date>, <author> wrote:` is in English or copy of **older email** is **removed** manually.
+An Email body in languages other than English may also work until and unless `On <date>, <author> wrote:` is in English or a copy of older email is removed manually.
 
-- Only **text** messages will be supported, attachments are not supported yet.
+- Only text messages are supported; attachments are not supported yet.
 
-## Known Issues
+## Known issues
 
-### Quoted Headers
+### Quoted headers
 
-Quoted headers aren't picked up if the email client breaks it up into multiple
-lines.  GMail breaks up any lines over 80 characters for you.
+Quoted headers aren't picked up if the email client breaks it up into multiple lines.
+
+GMail breaks up any lines over 80 characters for you.
 
 ```
 On <date>, <author>
 wrote:
 > blah
 ```
 
-Not to mention that we're searching for "on" and "wrote".  It won't work
-with other languages.
+Not to mention that we are searching for `on` and `wrote`.  It doesn't work with other languages.
 
-Possible solution: While replying, remove everything else than your actual message.
+**Possible solution**: while replying, remove everything else than your actual message.
 
-### Weird Signatures
+### Weird signatures
 
-Lines starting with `-` or `_` sometimes mark the beginning of
-signatures:
+Lines starting with `-` or `_` sometimes mark the beginning of signatures:
 
 ```
 Hello
@@ -77,7 +76,7 @@ Hello
 Rick
 ```
 
-Not everyone follows this convention:
+But some users change this convention:
 
 ```
 Hello
@@ -93,6 +92,6 @@ GitHub
 
 ## Problem?
 
-Your message wasn't posted? Or got `Invalid Email.` in Admin console?
-This most likely means that email format was not as we expected it to be.
-There is a possibility that you were blocked or message/room was deleted.
+Your message wasn't posted? Did you get an `Invalid Email` in the `Admin` console?
+This most likely means that the email format was not as expected.
+Maybe you were blocked or the message/room was deleted.