5 files changed, 15 insertions, 7 deletions
diff --git a/doc/site/src/docs/index.page b/doc/site/src/docs/index.page
index b01be0b..314dac0 100644
--- a/doc/site/src/docs/index.page
+++ b/doc/site/src/docs/index.page
@@ -14,7 +14,7 @@ docs that you can refer to based on these.
  h2. Getting Started
  
  Start here to get a good grounding in getting Mongrel up and running.
-These documents are targetted at developers who will be starting off
+These documents are targeted at developers who will be starting off
  using Mongrel and might want to throw in a few little tricks. 
  Serious deployments should check out *Deployment Best Practices*.
  
@@ -74,7 +74,7 @@ People writing plugins will want these.
  * "GemPlugin RDoc":/gem_plugin_rdoc/index.html
  
  
-If there's documentation you'd like then feel free to e-mail the list or post
+If there's documentation you'd like then feel free to E-mail the list or post
  to the tracker.
  
  h1. Other People's Documentation
diff --git a/doc/site/src/docs/lighttpd.page b/doc/site/src/docs/lighttpd.page
index 592a512..ffd12d2 100644
--- a/doc/site/src/docs/lighttpd.page
+++ b/doc/site/src/docs/lighttpd.page
@@ -1,9 +1,16 @@
----
+--
  title: Lighttpd
  inMenu: true
  directoryName: Documentation
  ---
  
+*I'm sad to say that I have to recommend people not use lighttpd anymore.*
+The author hasn't updated the mod_proxy plugin and isn't providing too much
+support for the bugs it has.  If you're running lighttpd and you constantly
+see 500 errors that are never recovered, then you should switch to Apache
+or another web server that can handle properly balancing backends.
+
+
  h1.  Using Lighttpd With Mongrel
  
  It is possible host an application with just Mongrel since it is
diff --git a/doc/site/src/docs/pound.page b/doc/site/src/docs/pound.page
index c625562..616e30c 100644
--- a/doc/site/src/docs/pound.page
+++ b/doc/site/src/docs/pound.page
@@ -16,7 +16,7 @@ h2. Requirements
  
  We assume that the following:
  
-* Pound and the monogrel cluster are running on the same machine [1].
+* Pound and the Mongrel cluster are running on the same machine [1].
  * *Pound 2.0.4* is built and installed, including SSL support if desired.
  * The *mongrel* gem is installed.
  * The *mongrel_cluster* gem is installed.
@@ -134,6 +134,7 @@ SSL: <%= @sslyn %>
  
  Visiting @http://127.0.0.1/Test/@ should show @SSL: false@ while visiting @https://127.0.0.1/Test/@
  should return @SSL: true@.
+
  fn1. It is not required that pound run on the same machine as the mongrel servers.  It was just chosen
  for this example.
  
diff --git a/doc/site/src/news.page b/doc/site/src/news.page
index cb2243a..a4082ec 100644
--- a/doc/site/src/news.page
+++ b/doc/site/src/news.page
@@ -226,7 +226,7 @@ h2. Mar-15:   Mongrel 0.3.11 -- Edge Rails Compliant
  
  The main thing with this release is that it works with edge Rails
  and has all the right dependencies.  There was a nasty bug with
-how RubyGems loads autorequired gems when any dependency is loaded.
+how RubyGems loads auto required gems when any dependency is loaded.
  In order to avoid this GemPlugins will now require the init.rb for
  the plugin directly rather than through RubyGems.  There are also
  other little tweaks to clean up how Rails runs.
@@ -310,7 +310,7 @@ Just do:
   $ gem install mongrel_status
  
  If you run mongrel_rails now you'll see a new command "status".
-Change to a Rails appliction directory where you have a daemon
+Change to a Rails application directory where you have a daemon
  running and it'll print out the PID.
  
  There will be tons of documentation coming out, and the ability
diff --git a/doc/site/src/security.page b/doc/site/src/security.page
index cb61c85..bc6c2ca 100644
--- a/doc/site/src/security.page
+++ b/doc/site/src/security.page
@@ -25,7 +25,7 @@ the future.
  
  h2. Mongrels HTTP Restrictions
  
-Many of the exploits out there currently for web servers tend to expoit
+Many of the exploits out there currently for web servers tend to exploit
  either ambiguous areas of the HTTP grammar, or the lack of size specifications
  in the protocol.  To protect against this Mongrel uses a fairly strict parser,
  but since many browser authors don't read specifications (and hell, who'd want