summary refs log tree commit homepage
diff options
context:
space:
mode:
-rw-r--r--PHILOSOPHY4
-rw-r--r--TUNING2
-rw-r--r--lib/unicorn/worker.rb4
3 files changed, 5 insertions, 5 deletions
diff --git a/PHILOSOPHY b/PHILOSOPHY
index c74db52..5def914 100644
--- a/PHILOSOPHY
+++ b/PHILOSOPHY
@@ -64,7 +64,7 @@ from the effects of slow I/O.
 By acting as a buffer to shield unicorn from slow I/O, a reverse proxy
 will inevitably incur overhead in the form of extra data copies.
 However, as I/O within a local network is fast (and faster still
-with local sockets), this overhead is neglible for the vast majority
+with local sockets), this overhead is negligible for the vast majority
 of HTTP requests and responses.
 
 The ideal reverse proxy complements the weaknesses of unicorn.
@@ -86,7 +86,7 @@ A reverse proxy for unicorn should meet the following requirements:
    In many (most?) cases, network devices and their interrupts are
    only be handled by one CPU at a time.  It should avoid contention
    within the system by serializing all network I/O into one (or few)
-   userspace procceses.  Network I/O is not a CPU-intensive task and
+   userspace processes.  Network I/O is not a CPU-intensive task and
    it is not helpful to use multiple CPU cores (at least not for GigE).
 
 4. It should efficiently manage persistent connections (and
diff --git a/TUNING b/TUNING
index ca291ad..542ebdc 100644
--- a/TUNING
+++ b/TUNING
@@ -52,7 +52,7 @@ See Unicorn::Configurator for details on the config file format.
   and may also thrash CPU caches, cancelling out performance gains
   one would normally expect.
 
-* UNIX domain sockets are slighly faster than TCP sockets, but only
+* UNIX domain sockets are slightly faster than TCP sockets, but only
   work if nginx is on the same machine.
 
 == Other \Unicorn settings
diff --git a/lib/unicorn/worker.rb b/lib/unicorn/worker.rb
index cd41e22..1fb6a4a 100644
--- a/lib/unicorn/worker.rb
+++ b/lib/unicorn/worker.rb
@@ -63,13 +63,13 @@ class Unicorn::Worker
   # Changes the worker process to the specified +user+ and +group+
   # This is only intended to be called from within the worker
   # process from the +after_fork+ hook.  This should be called in
-  # the +after_fork+ hook after any priviledged functions need to be
+  # the +after_fork+ hook after any privileged functions need to be
   # run (e.g. to set per-worker CPU affinity, niceness, etc)
   #
   # Any and all errors raised within this method will be propagated
   # directly back to the caller (usually the +after_fork+ hook.
   # These errors commonly include ArgumentError for specifying an
-  # invalid user/group and Errno::EPERM for insufficient priviledges
+  # invalid user/group and Errno::EPERM for insufficient privileges
   def user(user, group = nil)
     # we do not protect the caller, checking Process.euid == 0 is
     # insufficient because modern systems have fine-grained