Fix Cloudflare capitalization. Clarify Cache Lookups and Clearing.

source/_docs/global-cdn.md

@@ -49,14 +49,14 @@ Upgrading to the Global CDN is available for most Professional and Business leve
       <td>Global Distribution</td>
     </tr>
     <tr>
-      <th>Cache Shards</th>
-      <td>3-4 per site</td>
-      <td>None</td>
+      <th>Cache Lookups</th>
+      <td>Randomly Routed to One of Three Pools</td>
+      <td>Routed to the Pool Most Likely to Hit</td>
     </tr>
     <tr>
       <th>Cache Clearing</th>
-      <td>Flush All</td>
-      <td>Granular</td>
+      <td>Blocks, takes up to 2000ms</td>
+      <td>Non-blocking, takes up to 150ms to take effect</td>
     </tr>
     <tr>
       <th>HTTPS Service</th>
@@ -136,10 +136,10 @@ Pantheon's Global CDN has some advantages over solutions some customers may alre
 
 Even if you want to retain your existing CDN because of specific features they provide, the upgrade will improve your end-user experience, as your custom CDN will be able to pull pages and assets from a nearby Pantheon Global CDN location, rather than the origin datacenter.
 
-### What about CloudFlare?
-Many customers currently take advantage of CloudFlare's awesome Universal SSL offering to get free HTTPS service for their website. If you are _just_ using CloudFlare for the HTTPS service, you can switch to the Global CDN and get an upgrade in performance and SSLLabs score.
+### What about Cloudflare?
+Many customers currently take advantage of Cloudflare's awesome Universal SSL offering to get free HTTPS service for their website. If you are _just_ using Cloudflare for the HTTPS service, you can switch to the Global CDN and get an upgrade in performance and SSLLabs score.
 
-However, customers using CloudFlare's WAF tools or other features may want to keep CloudFlare in their stack. We still recommend upgrading your Pantheon site to the Global CDN as this will improve cache hitrates and performance. There are no known issues with layering CloudFlare and the Global CDN together. Ignore the DNS recommendations and action required notices from the Site Dashboard, and use the [configuration described in our related guide](/docs/guides/cloudflare-enable-https/) instead.
+However, customers using Cloudflare's WAF tools or other features may want to keep Cloudflare in their stack. We still recommend upgrading your Pantheon site to the Global CDN as this will improve cache hitrates and performance. There are no known issues with layering Cloudflare and the Global CDN together. Ignore the DNS recommendations and action required notices from the Site Dashboard, and use the [configuration described in our related guide](/docs/guides/cloudflare-enable-https/) instead.
 
 To use Cloudflare as a DNS hosting provider and Pantheon's Global CDN and Managed HTTPS service, configure DNS as recommended in the Site Dashboard and disable Cloudflare's CDN by toggling the cloud icon to grey so it's disabled.