More cache-neutral language

spec/amp-cache-debugging.md

@@ -1,14 +1,13 @@
 # AMP Cache Debugging
 
-**Why is my doc broken on the AMP cache?**
+**Why is my doc broken on an AMP cache?**
 
 Valid AMP documents typically appear and behave the same on AMP Caches as they
 do on the origin. However, there are some components and server configurations
 that can be problematic.
 
 If a particular document appears and behaves as expected on your origin, but not
-when viewed via the cache ([how to map origin URLs to cache
-URLs](https://developers.google.com/amp/cache/overview#amp-cache-url-format)),
+when viewed via the cache (how to map origin URLs to [Google's AMP Cache](https://developers.google.com/amp/cache/overview#amp-cache-url-format)),
 first open the developer console in your browser, and ensure no errors or
 warnings appear. If this doesn't resolve the problem, run the document through
 [AMPBench](https://ampbench.appspot.com/) and resolve any unexpected errors or
@@ -20,5 +19,5 @@ table below.
 |Web fonts do not appear (fallback fonts are used)|Fonts served with incorrect MIME type|Specify an [acceptable MIME type](https://github.com/ampproject/amphtml/blob/master/spec/amp-cache-guidelines.md#mime-types-for-fonts) for fonts|
 |Web fonts do not appear (fallback fonts are used)|Cache not whitelisted by font provider|Contact font provider and ask them to whitelist [all caches](https://github.com/ampproject/amphtml/blob/master/spec/amp-cors-requests.md#cors-security-in-amp)|
 |Assets (e.g. fonts and images) do not appear (**HTTP origins only**)|Document uses protocol-relative URLs|Switch to absolute URLs (that is, `http://www.site.com/doc/amp`, not `//www.site.com/doc/amp`)|
-|Assets (e.g. fonts and images) do not appear|Cache is unable to access assets|Ensure the Google crawler is able to access your assets and is not blocked by `robots.txt`, IP address, or user agent, etc. ([List of user agents used by Google's crawler](https://support.google.com/webmasters/answer/1061943?hl=en).)|
+|Assets (e.g. fonts and images) do not appear|Cache is unable to access assets|Ensure the cache is able to access your assets and is not blocked by `robots.txt`, IP address, or user agent, etc. (List of user agents used by [Google's crawler](https://support.google.com/webmasters/answer/1061943?hl=en).)|
 |Dynamic elements such as `<amp-form>`, `<amp-list>` do not behave as expected|Broken or non-existent CORS headers|These components cause browsers to make cross-origin requests from the cache to your origin. These requests are blocked by default. To allow these requests, emit [CORS headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS) that whitelist [all caches](https://github.com/ampproject/amphtml/blob/master/spec/amp-cors-requests.md#cors-security-in-amp).|