Refine description and symptoms for mail loop NDR

Updated the description for clarity and improved the wording in the symptoms section.

Author: Cloud-Writer

Exchange/ExchangeServer/mailflow/hop-count-exceeded-possible-mail-loop.md

@@ -1,6 +1,6 @@
 ---
 title: 554 5.4.14 Hop count exceeded - possible mail loop NDR for outgoing email
-description: Provides a fix for the 554 5.4.14 Hop count exceeded - possible mail loop issue in Exchange Server.
+description: Provides a fix for the 554 5.4.14 Hop count exceeded NDR.
 author: cloud-writer
 ms.author: meerak
 audience: ITPro
@@ -19,20 +19,21 @@ ms.date: 01/24/2024
 ms.reviewer: v-six
 ---
 
-# "554 5.4.14 Hop count exceeded - possible mail loop" NDR for outgoing email that's sent to an on-premises application in Exchange Server
+# "554 5.4.14 Hop count exceeded" NDR for outgoing email sent to an on-premises application in Exchange Server
 
 ## Symptoms
 
 Consider the following scenario:
 
-- You added a parent domain, **contoso.com**, as an accepted domain to an on-premises Microsoft Exchange Server 2016 or 2013 environment.
+- You configure **contoso.com** as a parent domain. 
+- You add the **contoso.com** parent domain as an accepted domain in an on-premises Microsoft Exchange Server 2016 or 2013 environment.
 - You have an on-premises application server domain, such as **app.contoso.com**, that is a subdomain of the parent domain.
-- You configured the parent domain to accept email messages from domains such as ***.contoso.com**.
+- You configure the parent domain to accept email messages from domains such as ***.contoso.com**.
 - You try to send an email message to the on-premises application through Exchange Server.
 
-In this scenario, the message cannot be sent. Instead, it loops between the Exchange Edge Transport server and Microsoft 365. Additionally, you receive a non-delivery report (NDR) that resembles the following:
+In this scenario, the message can't be sent. Instead, it loops between the Exchange Edge Transport server and Microsoft 365. Additionally, you receive a non-delivery report (NDR) that resembles the following:
 
-> **554 5.4.14 Hop count exceeded - possible mail loop**
+> `554 5.4.14 Hop count exceeded - possible mail loop`
 
 ## Cause
 
@@ -44,7 +45,7 @@ In this scenario, the subdomain is part of the address space in the **EdgeSync -
 
 To fix this issue, use the following steps:
 
-1. Add the subdomain as an accepted domain. To do this, run the following command:
+1. Add the subdomain as an accepted domain. Run the following command:
 
     ```powershell
     New-AcceptedDomain -DomainName app.Contoso.com -DomainType InternalRelay -Name app.contoso.com