Skip to content

Commit 1df00b1

Browse files
committed
Editorial: initialize a response does not have an optional argument
1 parent 49bff76 commit 1df00b1

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

fetch.bs

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8192,8 +8192,7 @@ enum ResponseType { "basic", "cors", "default", "error", "opaque", "opaqueredire
81928192

81938193
<div algorithm>
81948194
<p>To <dfn>initialize a response</dfn>, given a {{Response}} object <var>response</var>,
8195-
{{ResponseInit}} <var>init</var>, and an optional <a for=/>body with type</a> <var>body</var>, run
8196-
these steps:
8195+
{{ResponseInit}} <var>init</var>, and null or a <a for=/>body with type</a> <var>body</var>:
81978196

81988197
<ol>
81998198
<li><p>If <var>init</var>["{{ResponseInit/status}}"] is not in the range 200 to 599, inclusive,
@@ -8213,7 +8212,7 @@ these steps:
82138212
<var>init</var>["{{ResponseInit/headers}}"].
82148213

82158214
<li>
8216-
<p>If <var>body</var> was given, then:
8215+
<p>If <var>body</var> is non-null, then:
82178216

82188217
<ol>
82198218
<li>

0 commit comments

Comments
 (0)