diff --git a/src/_posts/2019-08-30-civicrm-mailing-validation.md b/src/_posts/2019-08-30-civicrm-mailing-validation.md
index 3f930eb..5db7dea 100644
--- a/src/_posts/2019-08-30-civicrm-mailing-validation.md
+++ b/src/_posts/2019-08-30-civicrm-mailing-validation.md
@@ -7,8 +7,7 @@ category: howto
 date: 2019-08-30
 ---
 
-Some of our clients use [CiviCRM](https://civicrm.org/) which is a popular open source "constituent relationship management" platform; 
-one of those clients uses the "Mailing" features to send out emails to their supporters.  We found out they're experiancing a bug where a user sends out a mailing with the same name (not subject line, just the internal identifier 🙄) as an existing mailing, it'll cause the CRM to 
+Some of our clients use [CiviCRM](https://civicrm.org/) which is a popular open source "constituent relationship management" platform. One of those clients regularly uses the "Mailing" features to send out emails to their supporters and  we found out they're experiancing a bug where a user sends out a mailing with the same name (not subject line, just the internal identifier 🙄) as an existing mailing, it'll cause the CRM to 
 freeze up at a later time.
 
 As an added challenge, the mailings feature of CiviCRM [now use AngularJS](https://docs.civicrm.org/dev/en/latest/framework/angular/) following a recent rebuild by the developers, and there aren't many tutorials or examples out there of workarounds to this issue. Luckily, the CiviCRM developer community was super-helpful, and we managed to sort out some in-form validation to prevent duplicate mailing names for our client and now for you, too!