From 00d2f339166db1667844f9d40be86093750233c2 Mon Sep 17 00:00:00 2001 From: Vse Mozhe Buty Date: Mon, 30 Nov 2020 17:11:46 +0200 Subject: [PATCH] Fix typo and ambiguity in 5.12 (Server Sent Events) --- 5-network/12-server-sent-events/article.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/5-network/12-server-sent-events/article.md b/5-network/12-server-sent-events/article.md index f6fd8dbd..c59d671a 100644 --- a/5-network/12-server-sent-events/article.md +++ b/5-network/12-server-sent-events/article.md @@ -66,7 +66,7 @@ eventSource.onmessage = function(event) { ### Cross-origin requests -`EventSource` supports cross-origin requests, like `fetch` any other networking methods. We can use any URL: +`EventSource` supports cross-origin requests, like `fetch` and any other networking methods. We can use any URL: ```js let source = new EventSource("https://another-site.com/events"); @@ -215,7 +215,7 @@ It offers: - Message ids to resume events, the last received identifier is sent in `Last-Event-ID` header upon reconnection. - The current state is in the `readyState` property. -That makes `EventSource` a viable alternative to `WebSocket`, as it's more low-level and lacks such built-in features (though they can be implemented). +That makes `EventSource` a viable alternative to `WebSocket`, as the latter is more low-level and lacks such built-in features (though they can be implemented). In many real-life applications, the power of `EventSource` is just enough.