Re: [w3c/ServiceWorker] Editorial: remove unnecessary CacheStorage global object definition (PR #1792)

@domenic approved this pull request.



> @@ -2258,9 +2258,9 @@ spec: storage; urlPrefix: https://storage.spec.whatwg.org/
 
     Note: {{CacheStorage}} interface is designed to largely conform to <a lt="map objects">ECMAScript 6 Map objects</a> but entirely async, and with additional convenience methods. The methods, <code>clear</code>, <code>forEach</code>, <code>entries</code> and <code>values</code>, are intentionally excluded from the scope of the first version resorting to the ongoing discussion about the async iteration by TC39.
 
-    The user agent *must* create a {{CacheStorage}} object when a {{Window}} object or a {{WorkerGlobalScope}} object is created and associate it with that <dfn for="CacheStorage">global object</dfn>.
+    The user agent *must* create a {{CacheStorage}} object when a {{Window}} object or a {{WorkerGlobalScope}} object is created and associate it with that [=global object=].

```suggestion
    The user agent *must* create a {{CacheStorage}} object when a {{Window}} object or a {{WorkerGlobalScope}} object is created.
```

Removing this makes it clearer that there's nothing special; we just use the usual object association that all objects have.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/pull/1792#pullrequestreview-3204353553
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/pull/1792/review/3204353553@github.com>