Fixups

Author: jgraham

index.bs

@@ -3837,7 +3837,7 @@ NetworkFetchTimingInfo = {
     connectStart: uint,
     connectEnd: uint,
     tlsStart: uint,
-    tlsEnd: uint,
+    <!-- tlsEnd: uint this should be the same as connectEnd -->
     requestStart: uint,
     responseStart: uint,
     <!-- TODO responseHeadersEnd: uint: Not sure quite what to use for this -->
@@ -3862,7 +3862,7 @@ To <dfn>get the fetch timings</div> given |request|:
    it's not null, or a new [=connection timing info=] otherwise.
 
 1. Let |request time| be [=convert fetch timestamp=] given [=convert fetch
-   timestamp=] given |timing|'s [=fetch/start time=] and |global|.
+   timestamp=] given |timing|'s <a spec=fetch>start time</a> and |global|.
 
 1. Let |redirect start| be [=convert fetch timestamp=] given |timing|'s
    [=redirect start time=] and |global|.
@@ -3882,9 +3882,6 @@ To <dfn>get the fetch timings</div> given |request|:
 1. Let |TLS start| be [=convert fetch timestamp=] given |connection timing|'s
    [=secure connection start time=] and |global|.
 
-1. Let |TLS end| be [=convert fetch timestamp=] given |connection timing|'s
-   [=secure connection end time=] and |global|.
-
 1. Let |connect start| be [=convert fetch timestamp=] given |connection
    timing|'s [=connection start time=] and |global|.
 
@@ -3898,7 +3895,7 @@ To <dfn>get the fetch timings</div> given |request|:
    network-response start time=] and |global|.
 
 1. Let |response end| be [=convert fetch timestamp=] given |timing|'s
-   [=fetch/end time=] and |global|.
+   <a spec=fetch>end time</a> and |global|.
 
 1. Return a [=map=] matching the <code>NetworkFetchTimingInfo</code> production
     with the <code>requestTime</code> field set to |request time|, the
@@ -3908,10 +3905,10 @@ To <dfn>get the fetch timings</div> given |request|:
     <code>dnsStart</code> field set to |DNS start|, the <code>dnsEnd</code>
     field set to |DNS end|, the <code>connectStart</code> field set to |connect
     start|, the <code>connectEnd</code> field set to |connect end|, the
-    <code>tlsStart</code> field set to |TLS start|, the <code>tlsEnd</code>
-    field set to |TLS end|, the <code>requestStart</code> field set to |request
-    start|, the <code>responseStart</code> field set to |response start|, and
-    the <code>responseEnd</code> field set to |response end|.
+    <code>tlsStart</code> field set to |TLS start|, the
+    <code>requestStart</code> field set to |request start|, the
+    <code>responseStart</code> field set to |response start|, and the
+    <code>responseEnd</code> field set to |response end|.
 
 </div>
 
@@ -3986,15 +3983,15 @@ To <dfn>get the initiator</dfn> given |request|:
 
 1. Let |type| be "<code>other</code>".
 
-1. If |request| is a [=CORS Preflight Request=], set |type| to
+1. If |request| is a [=CORS-Preflight Request=], set |type| to
    "<code>preflight</code>".
 
 1. TODO: Get the |type|. It's not quite clear how this ought to work; the CDP
    data depends on whether the navigation was kicked off by the parser or by
    script (so e.g. inserting an image from script causes the initiator to be
    "<code>script</code>"), but that doesn't correspond to anything in Fetch.
 
-1. If |request|'s [=request/initiator-type=] is "<code>fetch</code>" or
+1. If |request|'s [=request/initiator type=] is "<code>fetch</code>" or
    "<code>xmlhttprequest</code>":
 
   1. Let |stack trace| be the [=current stack trace=].
@@ -4225,7 +4222,7 @@ request sent</dfn> steps given |request|:
 1. Let (|related browsing contexts|, |params|) be the result of [=get the base
    network event data=] given |request|.
 
-1. Let |initiator| be the result of [=get an initiator=] with |request|.
+1. Let |initiator| be the result of [=get the initiator=] with |request|.
 
 1. Set the <code>initiatior</code> field of |params| to |initiator|.