diff --git a/PROJECTPAGE.md b/PROJECTPAGE.md
index 46beefc..cc176f7 100644
--- a/PROJECTPAGE.md
+++ b/PROJECTPAGE.md
@@ -6,36 +6,24 @@ This module queues URLs or paths to your [Purge](https://www.drupal.org/project/
 Drupal 8 introduces tag-based cache invalidation which is much more efficient
 than legacy URL or path based invalidation and leads to less processing and
 smaller queues. However, when your CDN or external caching system **does not
-support tag-based invalidation**, this module is for you!
+support tag-based invalidation**, this module may be for you, with one caveat (read the section **Very important warning**, found below).
 
 ## How it works
-The module trains its _traffic registry_ by collecting URLs from requests that
-miss cache inside Drupal's own page cache. These URLs are stored along with
-their associated _cache tags_ inside this same _traffic registry_. Now when
-Drupal invalidates a set of tags because someone edited a page, these tags are
-used to fetch URLs from the registry and are added to the Purge queue.
+The **Purge URL Querers** module trains its _traffic registry_ by collecting URLs from requests that miss cache inside Drupal's own page cache. These URLs are stored with their associated _cache tags_ inside the _traffic registry_. When Drupal invalidates a set of tags because someone edited a page, these tags are
+used to fetch URLs from the registry and are added to the _Purge_ queue.
 
 ##### Accuracy
-Those that remember the [cache expiration](https://www.drupal.org/project/expire)
-module for Drupal 7 are familiar with the _side effects_ of some changes not
-being automatically detected. This module can guarantee very high accuracy since
-it simply leverages D8's highly innovative _tags based_ caching architecture,
-which is thoroughly covered by tests that cover edge cases most site builders
-wouldn't think off. Examples of things that _just work_ are
-pagers (``/news/?page=10``), RSS or Json views (``/rss.xml``) and any view or
-view block, like that one dynamic block placed on ``/contact`` that shows
-corporate press releases.
+Those that remember the [Cache Expiration](https://www.drupal.org/project/expire)
+module for Drupal 7 are familiar with the module's _side effects_ - namely, certain changes were not automatically detected _(such as:)_. Purge was engineered to guarantee accurate results, as it leverages D8's innovative _tags based_ caching architecture, which is thoroughly tested, covering more extreme edge cases. Examples are pagers (``/news/?page=10``), RSS or JSon feeds (``/rss.xml``), and any view or view block.  Have a single dynamic block placed on ``/contact`` that shows corporate press releases?  It's now covered!
 
 ## Very important warning!
-This module isn't suited for everyone and *can bring your site down* if you're not careful!
+This module isn't suited for everyone and *can bring your site down* if you're not careful.  **Purge URL Queuers** stores URLs for all of your traffic.  Sites with thousands of content items can contribute to a large registry and increased *database strain*. If queries from this module are slowing down your website, your alternatives are:
 
-Because it stores URLs for all of your traffic, sites with thousands of content items can end up creating a unsustainable large registry with *database strain* as ultimate consequence. If you're noticing that queries coming from this module are severely slowing down your website, the only alternatives you have are:
-
-1. Switch to a CDN that does support tag-based cache invalidation.
-2. Stay with the CDN, but:
+1. Switch to a CDN that supports tag-based cache invalidation.
+2. Stay with your current CDN, but:
   * Uninstall and stop using ``purge_queuer_url``.
   * Configure the CDN to override your caching policy at the edge.
-  * The override should set a reasonably short cache policy for all CDN-to-browser delivery.
+    * The override should set a reasonably short cache policy for all CDN-to-browser delivery.
 
 ## Getting started