From 975e496143e10a5fcc2a0cc393834d29bfb2592a Mon Sep 17 00:00:00 2001 From: Anton Zhluktarev Date: Fri, 21 Jun 2019 19:09:32 +0300 Subject: [PATCH] Small typo in article Missed 'i' in receive --- 5-network/09-server-sent-events/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/5-network/09-server-sent-events/article.md b/5-network/09-server-sent-events/article.md index 49b191fd..aeb2ca78 100644 --- a/5-network/09-server-sent-events/article.md +++ b/5-network/09-server-sent-events/article.md @@ -18,7 +18,7 @@ Why should one ever use it? The main reason: it's simpler. In many applications, the power of `WebSocket` is a little bit too much. -We need to receve a stream of data from server: maybe chat messages or market prices, or whatever. That's what `EventSource` is good at. Also it supports auto-reconnect, something we need to implement manually with `WebSocket`. Besides, it's a plain old HTTP, not a new protocol. +We need to receive a stream of data from server: maybe chat messages or market prices, or whatever. That's what `EventSource` is good at. Also it supports auto-reconnect, something we need to implement manually with `WebSocket`. Besides, it's a plain old HTTP, not a new protocol. ## Getting messages