diff options
| author | Matthias Endler <[email protected]> | 2013-06-27 01:01:01 +0200 |
|---|---|---|
| committer | Matthias Endler <[email protected]> | 2013-06-27 22:34:56 +0200 |
| commit | f664329b0b11bdaa74f694260b3e3b3678f83d81 (patch) | |
| tree | 6a8aebba642666a4c3f4b3b00d88f10234445b12 /guide/erlang_web.md | |
| parent | 61ca86b05493f82bcbddd76911fee64dc636c885 (diff) | |
| download | cowboy-f664329b0b11bdaa74f694260b3e3b3678f83d81.tar.gz cowboy-f664329b0b11bdaa74f694260b3e3b3678f83d81.tar.bz2 cowboy-f664329b0b11bdaa74f694260b3e3b3678f83d81.zip | |
Minor corrections of the guide
Diffstat (limited to 'guide/erlang_web.md')
| -rw-r--r-- | guide/erlang_web.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/guide/erlang_web.md b/guide/erlang_web.md index d665ffe..fa3d922 100644 --- a/guide/erlang_web.md +++ b/guide/erlang_web.md @@ -43,7 +43,7 @@ designed to work in a distributed setting, so it is a perfect match. Or is it? Surely you can find solutions to handle that many -concurrent connections with my favorite language... But all +concurrent connections with your favorite language... But all these solutions will break down in the next few years. Why? Firstly because servers don't get any more powerful, they instead get a lot more cores and memory. This is only useful @@ -90,7 +90,7 @@ The Web is asynchronous Long ago, the Web was synchronous because HTTP was synchronous. You fired a request, and then waited for a response. Not anymore. -It all started when XmlHttpRequest started being used. It allowed +It all began when XmlHttpRequest started being used. It allowed the client to perform asynchronous calls to the server. Then Websocket appeared and allowed both the server and the client |