about summary refs log tree commit homepage
path: root/DEPLOY
diff options
context:
space:
mode:
Diffstat (limited to 'DEPLOY')
-rw-r--r--DEPLOY10
1 files changed, 5 insertions, 5 deletions
diff --git a/DEPLOY b/DEPLOY
index 253a068..1566d43 100644
--- a/DEPLOY
+++ b/DEPLOY
@@ -13,26 +13,26 @@ processing of the request body as it is being uploaded.
 In this case, haproxy or any similar (non-request-body-buffering) load
 balancer should be used to balance requests between different machines.
 
-== nginx proxying to \Rainbows! or Unicorn
+== nginx proxying to \Rainbows! or unicorn
 
 For high-traffic applications, routing slow actions to \Rainbows! with
 nginx is recommended as nginx can serve static files faster and nginx
-can forward fast actions to Unicorn.
+can forward fast actions to unicorn.
 
           static files
             |
       nginx |--> slow actions --> Rainbows!
             |
-            `--> fast actions --> Unicorn
+            `--> fast actions --> unicorn
 
 Be sure to set <tt>proxy_buffering off</tt> in nginx for "slow actions"
-if you have Comet applications (but not for Unicorn).
+if you have Comet applications (but not for unicorn).
 
 == Denial-of-Service Concerns
 
 Since \Rainbows! is designed to talk to slow clients with long-held
 connections, it may be subject to brute force denial-of-service attacks.
-In Unicorn and Mongrel, we've already enabled the "httpready" accept
+In unicorn and Mongrel, we've already enabled the "httpready" accept
 filter for FreeBSD and the TCP_DEFER_ACCEPT option in Linux; but it is
 still possible to build clients that work around and fool these
 mechanisms.