[master] d2014e9 clarify that we will not see piped connections ever again

[Nils Goroll]

commit d2014e93f1472d666a1b0d84cb308d7ce38aa537
Author: Nils Goroll <nils.goroll at uplex.de>
Date:   Sun Sep 14 13:31:35 2014 +0200

    clarify that we will not see piped connections ever again

diff --git a/doc/sphinx/users-guide/vcl-built-in-subs.rst b/doc/sphinx/users-guide/vcl-built-in-subs.rst
index 5280eb4..9c9c690 100644
--- a/doc/sphinx/users-guide/vcl-built-in-subs.rst
+++ b/doc/sphinx/users-guide/vcl-built-in-subs.rst
@@ -43,11 +43,12 @@ of the following keywords:
 vcl_pipe
 ~~~~~~~~
 
-Called upon entering pipe mode. In this mode, the request is passed
-on to the backend, and any further data from either client or backend
+Called upon entering pipe mode. In this mode, the request is passed on
+to the backend, and any further data from both the client and backend
 is passed on unaltered until either end closes the
 connection. Basically, Varnish will degrade into a simple TCP proxy,
-shuffling bytes back and forth.
+shuffling bytes back and forth. For a connection in pipe mode, no
+other VCL subroutine will ever get called after `vcl_pipe`.
 
 The `vcl_pipe` subroutine may terminate with calling ``return()`` with one
 of the following keywords: