[IMP] email faqs: email limit

closes odoo/documentation#9672

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>

content/applications/general/email_communication/faq.rst

@@ -12,8 +12,9 @@ Outgoing emails
 Email is not sent
 -----------------
 
-The first indicator showing that an email has not been sent is the presence of a red :guilabel:`✉️
+The first indicator showing that an email has not been sent is the presence of a red
-(envelope)` icon, next to the date and time of the message, located in the chatter.
+:icon:`fa-envelope` :guilabel:`(envelope)` icon, next to the date and time of the message, located
+in the chatter.
 
 .. image:: faq/red-envelop.png
    :align: center
@@ -42,13 +43,18 @@ Odoo's email servers from being blacklisted.
 Here are the default limits for new databases:
 
 - **200 emails per day** for Odoo Online and Odoo.sh databases with an active subscription.
-- **20 emails per day** for one-app free databases.
+- **50 emails per day** for one-app free and trial databases.
-- **50 emails per day** for trial databases.
+
-- In the case of migration, the daily limit might be reset to 50 emails per day.
+.. important::
+   In a one-app free database, if the *Email Marketing* app is installed, the email limit is **20
+   emails per day**.
+
+.. note::
+   In the case of migration, the daily limit might be reset to 50 emails per day.
 
 If the daily limit is reached:
 
-- Contact the Odoo support team, who may increase the daily limit depending on the following
+- Contact the Odoo support team, who may increase the daily limit, depending on the following
   factors:
 
   #. How many users are in the database?
@@ -72,7 +78,7 @@ If the daily limit is reached:
 SMTP error
 **********
 
-Simple Mail Transport Protocol (SMTP) error messages explain why an email wasn't transmitted
+*Simple Mail Transport Protocol (SMTP)* error messages explain why an email was not transmitted
 successfully. :abbr:`SMTP (Simple Mail Transport Protocol)` is a protocol to describe the email
 structure, and transmits data from messages over the Internet. The error messages generated by email
 services are helpful tools to diagnose and troubleshoot email problems.
@@ -83,9 +89,9 @@ services are helpful tools to diagnose and troubleshoot email problems.
    mta4471.mail.bf1.yahoo.com --- Below this line is a copy of the message.`
 
 The debug menu can be used to investigate SMTP sending issues from a database. To access the menu,
-:ref:`developer mode <developer-mode>` must be activated. Once activated, navigate to the
+:ref:`developer mode <developer-mode>` **must** be activated. Once activated, navigate to the
-:menuselection:`Debug Menu` in the top right of the menu bar (the :guilabel:`🐞 (bug)` icon),
+:menuselection:`Debug Menu` in the top-right of the menu bar (the :icon:`fa-bug` :guilabel:`(bug)`
-:menuselection:`Debug Menu --> Manage Messages`
+icon), and select :menuselection:`Debug Menu --> Manage Messages` from the resulting drop-down menu.
 
 The :guilabel:`Manage Messages` menu opens a list of all the messages sent in a particular record.
 Within each message there is information on sending, including the type, and subtype, of the
@@ -128,11 +134,10 @@ Email is sent late
 Email campaigns send at a scheduled time, using a delay pre-programed in the database. Odoo uses a
 delayed task to send emails that are considered "not urgent" (newsletter formats, such as: mass
 mailing, marketing automation, and events). The system utility **cron** can be used to schedule
-programs to run automatically at predetermined intervals. Odoo uses that policy in order to avoid
+programs to run automatically at predetermined intervals. Odoo uses that policy to avoid cluttering
-cluttering the mail servers and, instead, prioritizes individual communication. This **cron** is
+the mail servers and, instead, prioritizes individual communication. This **cron** is called
-called :guilabel:`Mail: Email Queue Manager`, and can be accessed in :ref:`developer mode
+:guilabel:`Mail: Email Queue Manager`, and can be accessed in :ref:`developer mode <developer-mode>`
-<developer-mode>` by going to :menuselection:`Settings app --> Technical menu --> Automation -->
+by going to :menuselection:`Settings app --> Technical menu --> Automation: Scheduled Actions`.
-Scheduled Actions`.
 
 .. image:: faq/email-scheduled-later.png
    :align: center
@@ -154,9 +159,9 @@ invoices, purchase orders, etc.) are sent immediately.
 Incoming emails
 ===============
 
-When there is an issue with incoming emails, there might not be an indication, per se, in Odoo. It
+When there is an issue with incoming emails, there might not be an indication in Odoo. It is the
-is the sending email client, who tries to contact a database, that will get a bounce-back message
+sending email client, who tries to contact a database, that gets a bounce-back message (most of the
-(most of the time a :guilabel:`550: mailbox unavailable` error message).
+time it is a :guilabel:`550: mailbox unavailable` error message).
 
 Email is not received
 ---------------------
@@ -229,5 +234,5 @@ of what can be helpful when reaching out to the Odoo Support team about an issue
 .. note::
    The bounce system parameter needs to be set in the technical settings in order for the database
    to correctly receive bounce messages. To access this setting, go to :menuselection:`Settings app
-   --> Technical menu --> Parameters --> System Parameters`. Then select the parameter name
+   --> Technical menu --> Parameters: System Parameters`. Then, select the parameter name
-   :guilabel:`mail.bounce.alias` and set the value to `bounce` if it isn't already set.
+   :guilabel:`mail.bounce.alias` and set the value to `bounce` if it is not already set.