From b2e93c1feae8c07f08e49b337bbadff90ac17612 Mon Sep 17 00:00:00 2001
From: FreeScout <40499291+freescout-helpdesk@users.noreply.github.com>
Date: Sun, 3 Sep 2023 08:48:34 +0300
Subject: [PATCH] Updated Sending Issues (markdown)

---
 Sending-Issues.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Sending-Issues.md b/Sending-Issues.md
index 9d13bf1..36d9f49 100644
--- a/Sending-Issues.md
+++ b/Sending-Issues.md
@@ -2,7 +2,7 @@
 
 There are two steps:
 
-- **Step 1. FreeScout passes an email to the mail server for delivery.** If there is an error on this step FreeScout shows this error in Outgoing Email, in "Manage > Logs > Send Errors" and to the customer in the conversation (after 1 hour of attempts).
+- **Step 1. FreeScout passes an email to the mail server for delivery.** If there is an error on this step FreeScout shows this error in Outgoing Emails window, in "Manage > Logs > Send Errors" and to the customer in the conversation (after 1 hour of attempts).
 - **Step 2. Mail server delivers an email to the recipient.** If there is an error on this step the only way for FreeScout to know about it - is to receive a bounce email from the mail server responsible for delivering the email. If FreeScout receives a bounce email it tries to link it to the conversation it's related and show corresponding info in the related conversation and thread.
 
 So here can be issues of two kinds: