Skip to content
This repository

Cosmetic fixes for the readme #70

Merged
merged 1 commit into from almost 2 years ago

2 participants

Oleg Pudeyev Marek
Oleg Pudeyev
p commented May 16, 2012

Some spelling/grammar fixes.

Marek majek merged commit bd5e798 into from May 16, 2012
Marek majek closed this May 16, 2012
Marek
Owner
majek commented May 16, 2012

Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Showing 1 unique commit by 1 author.

May 16, 2012
Oleg Pudeyev Cosmetic fixes for the readme 79b408d
This page is out of date. Refresh to see the latest.

Showing 1 changed file with 6 additions and 6 deletions. Show diff stats Hide diff stats

  1. 12  README.md
12  README.md
Source Rendered
@@ -308,10 +308,10 @@ and sticky sessions (aka session affinity).
308 308
 
309 309
 ### WebSocket compatible load balancer
310 310
 
311  
-Often WebSockets don't play nicely with proxies and loadbalancers.
  311
+Often WebSockets don't play nicely with proxies and load balancers.
312 312
 Deploying a SockJS server behind Nginx or Apache could be painful.
313 313
 
314  
-Fortunetely recent versions of an excellent loadbalancer
  314
+Fortunetely recent versions of an excellent load balancer
315 315
 [HAProxy](http://haproxy.1wt.eu/) are able to proxy WebSocket
316 316
 connections. We propose to put HAProxy as a front line load balancer
317 317
 and use it to split SockJS traffic from normal HTTP data. Take a look
@@ -345,7 +345,7 @@ Development and testing
345 345
 -----------------------
346 346
 
347 347
 If you want to work on SockJS-node source code, you need to clone the
348  
-git repo and follow this steps. First you need to install
  348
+git repo and follow these steps. First you need to install
349 349
 dependencies:
350 350
 
351 351
     cd sockjs-node
@@ -357,7 +357,7 @@ You're ready to compile CoffeeScript:
357 357
     make build
358 358
 
359 359
 If compilation succeeds you may want to test if your changes pass all
360  
-the tests. Currently, there are two separate test suits. For both of
  360
+the tests. Currently, there are two separate test suites. For both of
361 361
 them you need to start a SockJS-node test server (by default listening
362 362
 on port 8081):
363 363
 
@@ -401,10 +401,10 @@ Various issues and design considerations
401 401
 ### Authorization
402 402
 
403 403
 SockJS-node does not expose cookies to the application. This is done
404  
-deliberatly as using cookie-based authorization with SockJS simply
  404
+deliberately as using cookie-based authorization with SockJS simply
405 405
 doesn't make sense and will lead to security issues.
406 406
 
407  
-Cookies are a contract between a browser and a http server, and are
  407
+Cookies are a contract between a browser and an http server, and are
408 408
 identified by a domain name. If a browser has a cookie set for
409 409
 particular domain, it will pass it as a part of all http requests to
410 410
 the host. But to get various transports working, SockJS uses a middleman
Commit_comment_tip

Tip: You can add notes to lines in a file. Hover to the left of a line to make a note

Something went wrong with that request. Please try again.