Skip to content

Commit 00d2f33

Browse files
authored
Fix typo and ambiguity in 5.12 (Server Sent Events)
1 parent e1a3f63 commit 00d2f33

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Diff for: 5-network/12-server-sent-events/article.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ eventSource.onmessage = function(event) {
6666

6767
### Cross-origin requests
6868

69-
`EventSource` supports cross-origin requests, like `fetch` any other networking methods. We can use any URL:
69+
`EventSource` supports cross-origin requests, like `fetch` and any other networking methods. We can use any URL:
7070

7171
```js
7272
let source = new EventSource("https://another-site.com/events");
@@ -215,7 +215,7 @@ It offers:
215215
- Message ids to resume events, the last received identifier is sent in `Last-Event-ID` header upon reconnection.
216216
- The current state is in the `readyState` property.
217217

218-
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).
218+
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).
219219

220220
In many real-life applications, the power of `EventSource` is just enough.
221221

0 commit comments

Comments
 (0)