Formatting, typo

doc/sphinx/tutorial/starting_varnish.rst

@@ -5,12 +5,13 @@ Starting Varnish
 ----------------
 
 This tutorial will assume that you are running Varnish on Ubuntu, Debian,
-Red Hat Enterprise Linux or Centos. Those of you running on other
+Red Hat Enterprise Linux or CentOS. Those of you running on other
 platforms might have to do some mental translation exercises in order
 to follow this. Since you're on a "weird" platform you're probably used
 to it. :-)
 
-Make sure you have Varnish succesfully installed (following one of the procedures described in "Installing Varnish" above.
+Make sure you have Varnish successfully installed (following one of the
+procedures described in "Installing Varnish" above.
 
 When properly installed you start Varnish with ``service varnish start``.  This will start
 Varnish if it isn't already running.
@@ -18,15 +19,16 @@ Varnish if it isn't already running.
 .. XXX:What does it do if it is already running? benc
 
 Now you have Varnish running. Let us make sure that it works
-properly. Use your browser to go to http://127.0.0.1:6081/
-(obviously, you should replace the IP address with the IP for the machine that currently runs Varnish. 
-The default configuration will try to forward requests to a web
-application running on the same machine as Varnish was installed on. Varnish expects the web application to be exposed over http on port 8080.
+properly. Use your browser to go to http://127.0.0.1:6081/ (Replace the IP
+address with the IP for the machine that runs Varnish) The default
+configuration will try to forward requests to a web application running on the
+same machine as Varnish was installed on. Varnish expects the web application
+to be exposed over http on port 8080.
 
 If there is no web application being served up on that location Varnish will
 issue an error. Varnish Cache is very conservative about telling the
 world what is wrong so whenever something is amiss it will issue the
-same generic "Error 503 Service Unavilable".
+same generic "Error 503 Service Unavailable".
 
 You might have a web application running on some other port or some
 other machine. Let's edit the configuration and make it point to
@@ -44,7 +46,7 @@ probably look like this::
   }
 
 We'll change it and make it point to something that works. Hopefully
-www.varnish-cache.org is up. Let's use that. Replace the text with::
+http://www.varnish-cache.org/ is up. Let's use that. Replace the text with::
 
   vcl 4.0;
   
@@ -58,6 +60,6 @@ Now issue ``service varnish reload`` to make Varnish reload it's
 configuration. If that succeeded visit http://127.0.0.1:6081/ in your
 browser and you should see some directory listing. It works! The
 reason you're not seeing the Varnish official website is because your
-client isn't sending the appropriate Host: header in the request and
+client isn't sending the appropriate `Host` header in the request and
 it ends up showing a listing of the default webfolder on the machine
-usually serving up varnish-cache.org.
+usually serving up http://www.varnish-cache.org/ .