Editorial: improve COOP/COEP cross-linking and metadata

Author: ArthurSonzogni

source

@@ -93687,10 +93687,10 @@ interface mixin <dfn>WindowOrWorkerGlobalScope</dfn> {
 
    <dt>self . <code subdfn data-x="dom-crossOriginIsolated">crossOriginIsolated</code></dt>
    <dd><p>Returns whether scripts running in this global are allowed to use APIs that require
-   cross-origin isolation. This depends on the `<code data-x="">Cross-Origin-Opener-Policy</code>`
-   and `<code data-x="">Cross-Origin-Embedder-Policy</code>` HTTP response headers and the
-   "<code data-x="cross-origin-isolated-feature">cross-origin-isolated</code>"
-   feature.</p></dd>
+   cross-origin isolation. This depends on the `<code
+   data-x="http-cross-origin-opener-policy">Cross-Origin-Opener-Policy</code>` and
+   `<code>Cross-Origin-Embedder-Policy</code>` HTTP response headers and the "<code
+   data-x="cross-origin-isolated-feature">cross-origin-isolated</code>" feature.</p></dd>
   </dl>
 
   <div class="example">
@@ -119180,7 +119180,8 @@ interface <dfn>External</dfn> {
   </dl>
 
 
-  <h3>`<dfn><code data-x="http-cross-origin-opener-policy">Cross-Origin-Opener-Policy</code></dfn>`</h3>
+  <h3>`<dfn http-header><code
+  data-x="http-cross-origin-opener-policy">Cross-Origin-Opener-Policy</code></dfn>`</h3>
 
   <p>This section describes a header for registration in the Permanent Message Header Field
   Registry. <ref spec=RFC3864></p>