From 3eb484213e00914dd4e6fd21041538b867c3e43e Mon Sep 17 00:00:00 2001
From: Chris Needham <chris.needham@bbc.co.uk>
Date: Thu, 30 Jul 2020 17:19:31 +0100
Subject: [PATCH] Fix typos

---
 fetch.bs | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/fetch.bs b/fetch.bs
index 7afac06c9..8c7491ce3 100644
--- a/fetch.bs
+++ b/fetch.bs
@@ -5363,7 +5363,7 @@ fetch("/", {method:"HEAD"})
 </code></pre>
 
  <p>If you want to check a particular response header and then process the response of a
- cross-origin resources:
+ cross-origin resource:
 
  <pre><code class=lang-javascript>
 fetch("https://pk.example/berlin-calling.json", {mode:"cors"})
@@ -5434,7 +5434,7 @@ interface Headers {
 `<code>Set-Cookie</code>` <a for=/>header</a>. In a way this is problematic as unlike all other
 headers `<code>Set-Cookie</code>` headers cannot be combined, but since `<code>Set-Cookie</code>`
 headers are not exposed to client-side JavaScript this is deemed an acceptable compromise.
-Implementations could chose the more efficient {{Headers}} object representation even for a
+Implementations could choose the more efficient {{Headers}} object representation even for a
 <a for=/>header list</a>, as long as they also support an associated data structure for
 `<code>Set-Cookie</code>` headers.
 
@@ -7295,6 +7295,7 @@ Brad Porter,
 Bryan Smith,
 Caitlin Potter,
 Cameron McCormack,
+Chris Needham,
 Chris Rebert,
 Clement Pellerin,
 Collin Jackson,