Apply suggestions from code review

Co-authored-by: Patricia Santa Ana <[email protected]>

Author: Maddy-Cloudflare

src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment.mdx

@@ -11,9 +11,9 @@ With pre-delivery deployment, also known as Inline deployment, Email Security ev
 
 Before you change your MX records, you will have to set up the [Time to Live (TTL)](/dns/manage-dns-records/reference/ttl/) on your DNS records. If you do not set up the TTL, the DNS propagation will take longer to happen. 
 
-We suggest to decrease the TTL to five minutes (also known as [Auto](/dns/manage-dns-records/reference/ttl/#proxied-records)) 3 to 5 days prior to the planned MX record change. Reducing the TTL allows the DNS record to propagate ahead of time, so changes take effect rapidly. Once you have completed your onboarding process, you can choose to increase the TTL.
+Cloudflare recommends to decrease the TTL to five minutes (also known as [Auto](/dns/manage-dns-records/reference/ttl/#proxied-records)) 3 to 5 days prior to the planned MX record change. Reducing the TTL allows the DNS record to propagate ahead of time, so changes take effect rapidly. Once you have completed your onboarding process, you can choose to increase the TTL.
 
-Once you have configured your TTL, you can deploy Email Security via MX/Inline. An MX record is a [DNS record](/dns/manage-dns-records/). 
+When you have configured your TTL, you can deploy Email Security via MX/Inline. An MX record is a [DNS record](/dns/manage-dns-records/). 
 
 If your DNS records are hosted by Cloudflare (or any other provider, except for Google), you can [edit your DNS records](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records) via the dashboard or the API to point your MX records to Cloudflare.