[4.0] c8663d5 Sync with reality

Federico G. Schwindt fgsch at lodoss.net
Tue Jun 24 11:31:40 CEST 2014


commit c8663d50d0b420dfa28d1a1b8b6fc0560b6fffd0
Author: Federico G. Schwindt <fgsch at lodoss.net>
Date:   Mon Apr 28 16:33:34 2014 +0100

    Sync with reality
    
    Update board members, URLs, spelling and fmt(1).

diff --git a/doc/sphinx/tutorial/introduction.rst b/doc/sphinx/tutorial/introduction.rst
index 2fbc43a..330764f 100644
--- a/doc/sphinx/tutorial/introduction.rst
+++ b/doc/sphinx/tutorial/introduction.rst
@@ -3,32 +3,32 @@
 The fundamentals of web proxy caching with Varnish
 --------------------------------------------------
 
-Varnish is a caching HTTP reverse proxy. It recieves requests from
-clients and tries to answer them from the cache. If Varnish cannot answer
-the request from the cache it will forward the request to the backend,
+Varnish is a caching HTTP reverse proxy. It receives requests from clients
+and tries to answer them from the cache. If Varnish cannot answer the
+request from the cache it will forward the request to the backend,
 fetch the response, store it in the cache and deliver it to the client.
 
-When Varnish has a cached response ready it is typically delivered in
-a matter of microseconds, two orders of magnitude faster than your
-typical backend server, so you want to make sure to have Varnish answer
-as many of the requests as possible directly from the cache.
+When Varnish has a cached response ready it is typically delivered in a
+matter of microseconds, two orders of magnitude faster than your typical
+backend server, so you want to make sure to have Varnish answer as many
+of the requests as possible directly from the cache.
 
-Varnish decides whether it can store the content or not based on the response
-it gets back from the backend. The backend can instruct Varnish to cache the
-content with the HTTP response header `Cache-Control`. There are a few
-conditions where Varnish will not cache, the most common one being the use of
-cookies. Since cookies indicates a client-specific web object, Varnish will by
-default not cache it.
+Varnish decides whether it can store the content or not based on the
+response it gets back from the backend. The backend can instruct Varnish
+to cache the content with the HTTP response header `Cache-Control`. There
+are a few conditions where Varnish will not cache, the most common one
+being the use of cookies. Since cookies indicates a client-specific web
+object, Varnish will by default not cache it.
 
-This behaviour as most of Varnish functionality can be changed using policies
-written in the Varnish Configuration Language (VCL). See
+This behaviour as most of Varnish functionality can be changed using
+policies written in the Varnish Configuration Language (VCL). See
 :ref:`users-guide-index` for more information on how to do that.
 
 Performance
 ~~~~~~~~~~~
 
-Varnish has a modern architecture and is written with performance in
-mind.  It is usually bound by the speed of the network, effectively
+Varnish has a modern architecture and is written with performance
+in mind.  It is usually bound by the speed of the network, effectively
 turning performance into a non-issue. You get to focus on how your web
 application work and you can allow yourself, to some degree, to care
 less about performance and scalability.
@@ -38,45 +38,44 @@ less about performance and scalability.
 Flexibility
 ~~~~~~~~~~~
 
-One of the key features of Varnish Cache, in addition to its
-performance, is the flexibility of its configuration language,
-VCL. VCL enables you to write policies on how incoming requests should
-be handled. 
+One of the key features of Varnish Cache, in addition to its performance,
+is the flexibility of its configuration language, VCL. VCL enables you
+to write policies on how incoming requests should be handled.
 
 In such a policy you can decide what content you want to serve, from
-where you want to get the content and how the request or response
-should be altered. 
+where you want to get the content and how the request or response should
+be altered.
 
 Supported platforms
 --------------------
 
-Varnish is written to run on modern versions of Linux and FreeBSD and
-the best experience is had on those platforms. Thanks to our
-contributors it also runs on NetBSD, OpenBSD, OS X and various
-Solaris-descendants like Oracle Solaris, OmniOS and SmartOS.
+Varnish is written to run on modern versions of Linux and FreeBSD and the
+best experience is had on those platforms. Thanks to our contributors
+it also runs on NetBSD, OpenBSD, OS X and various Solaris-descendants
+like Oracle Solaris, OmniOS and SmartOS.
 
 About the Varnish development process
 -------------------------------------
 
 Varnish is a community driven project. The development is overseen by
-the Varnish Governing Board which currently consist of Poul-Henning
-Kamp (Architect), Rogier Mulhuijzen (Fastly) and Kristian Lyngstøl
-(Varnish Software).
+the Varnish Governing Board which currently consist of Poul-Henning Kamp
+(Architect), Rogier Mulhuijzen (Fastly) and Lasse Karstensen (Varnish
+Software).
 
-Please see https://www.varnish-cache.org/trac/wiki/Contributing as
-a starting point if you would like to contribute to Varnish.
+Please see https://www.varnish-cache.org/trac/wiki/Contributing as a
+starting point if you would like to contribute to Varnish.
 
 Getting in touch
 ----------------
 
-You can get in touch with us trough many channels. For real time chat
-you can reach us on IRC trough the server irc.linpro.net on the
-#varnish and #varnish-hacking channels.
-The are two mailing lists available. One for user questions and one
-for development discussions. See https://www.varnish-cache.org/mailinglist for
-information and signup.  There is also a web forum on the same site.
+You can get in touch with us through many channels. For real time chat
+you can reach us on IRC trough the server irc.linpro.net on the #varnish
+and #varnish-hacking channels.
+There are two mailing lists available. One for user questions and one
+for development discussions. See https://www.varnish-cache.org/lists
+for information and signup.  There is also a web forum on the same site.
 
 Now that you have a vague idea on what Varnish Cache is, let see if we
 can get it up and running.
 
-.. XXX:The above three paragraphs are repetetive this is already handled in previos chapters. The only new information is Governing Board which could be moved to the introduction and the paragraphs scrapped. benc
+.. XXX:The above three paragraphs are repetitive this is already handled in previous chapters. The only new information is Governing Board which could be moved to the introduction and the paragraphs scrapped. benc



More information about the varnish-commit mailing list