[master] 193a8c7 Fix typos

[Bjørn Ruberg]

commit 193a8c716da3298df5ae6ba85af8a38241f53e1f
Author: Bjoern Ruberg <bjorn at doffen.hjemme.ruberg.no>
Date:   Tue Mar 1 22:18:30 2011 +0100

    Fix typos

diff --git a/doc/sphinx/tutorial/advanced_topics.rst b/doc/sphinx/tutorial/advanced_topics.rst
index 5bdb7b4..4491c28 100644
--- a/doc/sphinx/tutorial/advanced_topics.rst
+++ b/doc/sphinx/tutorial/advanced_topics.rst
@@ -43,7 +43,7 @@ Edge Side Includes
 Varnish can cache create web pages by putting different pages
 together. These *fragments* can have individual cache policies. If you
 have a web site with a list showing the 5 most popular articles on
-your site this list can probably be cached as a fragment and included
+your site, this list can probably be cached as a fragment and included
 in all the other pages. Used properly it can dramatically increase
 your hit rate and reduce the load on your servers. ESI looks like this::
 
diff --git a/doc/sphinx/tutorial/logging.rst b/doc/sphinx/tutorial/logging.rst
index 9dce29a..c79fbd3 100644
--- a/doc/sphinx/tutorial/logging.rst
+++ b/doc/sphinx/tutorial/logging.rst
@@ -45,11 +45,11 @@ with a tag indicating what sort of activity is beeing logged. Tags
 starting with Rx indicate Varnish is recieving data and Tx indicates
 sending data.
 
-The third column tell us whether this is is data comming or going to
+The third column tell us whether this is is data coming or going to
 the client (c) or to/from the backend (b). The forth column is the
 data being logged.
 
-Now, you can filter quite a bit with varnishlog. The basics option you
+Now, you can filter quite a bit with varnishlog. The basic option you
 want to know are:
 
 -b
@@ -73,5 +73,5 @@ want to know are:
  Group log entries by request ID.
 
 
-Now that Varnish seem to work OK its time to put Varnish on port 80
+Now that Varnish seem to work OK it's time to put Varnish on port 80
 while we tune it.
diff --git a/doc/sphinx/tutorial/putting_varnish_on_port_80.rst b/doc/sphinx/tutorial/putting_varnish_on_port_80.rst
index 5742806..73a80ff 100644
--- a/doc/sphinx/tutorial/putting_varnish_on_port_80.rst
+++ b/doc/sphinx/tutorial/putting_varnish_on_port_80.rst
@@ -7,7 +7,7 @@ purposes. You should test your application and if it works OK we can
 switch, so Varnish will be running on port 80 and your web server on a
 high port.
 
-First we kill off varnishd.::
+First we kill off varnishd::
 
      # pkill varnishd
 
@@ -15,11 +15,11 @@ and stop your web server. Edit the configuration for your web server
 and make it bind to port 8080 instead of 80. Now open the Varnish
 default.vcl and change the port of the *default* backend to 8080.
 
-Start up your web server and then start varnish.::
+Start up your web server and then start varnish::
 
       # varnishd -f /usr/local/etc/varnish/default.vcl -s malloc,1G -T 127.0.0.1:2000
 
 Note that we've removed the -a option. Now Varnish, as its default
-setting dictates, will bind to the http port (80). Now everyone thats
+setting dictates, will bind to the http port (80). Now everyone
 accessing your site will be accessing through Varnish.
 
diff --git a/doc/sphinx/tutorial/starting_varnish.rst b/doc/sphinx/tutorial/starting_varnish.rst
index cbf94f8..6c89f54 100644
--- a/doc/sphinx/tutorial/starting_varnish.rst
+++ b/doc/sphinx/tutorial/starting_varnish.rst
@@ -21,14 +21,14 @@ I added a few options, lets go through them:
  - one gigabyte. 
 
 ``-T 127.0.0.1:2000``
- Varnish has a buildt in text-based administration
+ Varnish has a built-in text-based administration
  interface. Activating the interface makes Varnish manageble without
  stopping it. You can specify what interface the management interface
  should listen to. Make sure you don't expose the management interface
  to the world as you can easily gain root access to a system via the
- Varnish management interace. I recommend tieing it to localhost. If
- you have users on your system that you don't fully trust use firewall
- rules to restrict access to the interace to root only.
+ Varnish management interface. I recommend tieing it to localhost. If
+ you have users on your system that you don't fully trust, use firewall
+ rules to restrict access to the interface to root only.
 
 ``-a 0.0.0.0:8080``
  I specify that I want Varnish to listen on port 8080 for incomming
@@ -36,8 +36,9 @@ I added a few options, lets go through them:
  Varnish listen on port 80, which is the default.
 
 Now you have Varnish running. Let us make sure that it works
-properly. Use your browser to go to http://192.168.2.2:8080/ - you
-should now see your web application running there.
+properly. Use your browser to go to http://192.168.2.2:8080/
+(obviously, you should replace the IP address with one on your own
+system) - you should now see your web application running there.
 
 Whether or not the application actually goes faster when run through
 Varnish depends on a few factors. If you application uses cookies for