From de6fc3fad33065e9da4a5391356e31ae340a8755 Mon Sep 17 00:00:00 2001
From: Tim Otten <totten@civicrm.org>
Date: Wed, 3 Jun 2020 00:05:24 -0700
Subject: [PATCH] Update 5.26.0.md

---
 release-notes/5.26.0.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/release-notes/5.26.0.md b/release-notes/5.26.0.md
index 2ae54fee94d..91bd6fdc7d0 100644
--- a/release-notes/5.26.0.md
+++ b/release-notes/5.26.0.md
@@ -23,9 +23,9 @@ Released June 3, 2020
 
 ## NOTICE: WordPress Service URLs
 
-The upcoming release of WordPress 5.5 (ETA July 2016) requires changes to several CiviCRM URLs. CiviCRM 5.26+ adopts a new URL convention. For old URLs, there is transitional support that will work for most web-based visitors. However, this may not be sufficient for *external service integrations* (e.g. certain payment processors or email relays which send notifications to CiviCRM). Administrators should promptly assess and update any external services which submit notifications to their CiviCRM-WordPress sites.
+The upcoming release of WordPress 5.5 (ETA July 2016) requires changes to several CiviCRM URLs. CiviCRM 5.26+ adopts a new URL convention. For old URLs, there is transitional support that will work for most web-based visitors. However, this may not be sufficient for *external service integrations* (e.g. certain payment processors or email relays which send notifications to CiviCRM).
 
-For more information, see the blog post [CiviCRM 5.26 and WordPress: Important notice](https://civicrm.org/blog/kcristiano/civicrm-526-and-wordpress-important-notice).
+Administrators should promptly assess and update any external services which submit notifications to their CiviCRM-WordPress sites. For more information, see the blog post [CiviCRM 5.26 and WordPress: Important notice](https://civicrm.org/blog/kcristiano/civicrm-526-and-wordpress-important-notice).
 
 ## <a name="features"></a>Features
 
-- 
GitLab