[master] ba20513 Fix up syntax for matching in docs

[Tollef Fog Heen]

commit ba2051320e581c84026821ed3e86fa3681e294dc
Author: Tollef Fog Heen <tfheen at varnish-software.com>
Date:   Fri Jul 15 08:39:37 2011 +0200

    Fix up syntax for matching in docs

diff --git a/doc/sphinx/faq/general.rst b/doc/sphinx/faq/general.rst
index 12617f5..5a1fbac 100644
--- a/doc/sphinx/faq/general.rst
+++ b/doc/sphinx/faq/general.rst
@@ -86,13 +86,13 @@ The "varnishlog" utility may produce a horrendous amount of output.  To be able
 
 The ReqStart token will include the client IP address.  To see log entries matching this, type::
 
-        $ varnishlog -c -o ReqStart 192.0.2.123
+        $ varnishlog -c -m ReqStart:192.0.2.123
 
 To see the backend requests generated by a client IP address, we can match on the TxHeader token, since the IP address of the client is included in the X-Forwarded-For header in the request sent to the backend.
 
 At the shell command line, type::
 
-        $ varnishlog -b -o TxHeader 192.0.2.123
+        $ varnishlog -b -m TxHeader:192.0.2.123
 
 **How can I rewrite URLS before they are sent to the backend?**
 
diff --git a/doc/sphinx/tutorial/troubleshooting.rst b/doc/sphinx/tutorial/troubleshooting.rst
index aeb2786..7ab9435 100644
--- a/doc/sphinx/tutorial/troubleshooting.rst
+++ b/doc/sphinx/tutorial/troubleshooting.rst
@@ -80,13 +80,13 @@ give you a clue. Since varnishlog logs so much data it might be hard
 to track the entries down. You can set varnishlog to log all your 503
 errors by issuing the following command:::
 
-   $ varnishlog -c -o TxStatus 503
+   $ varnishlog -c -m TxStatus:503
 
 If the error happened just a short time ago the transaction might still
 be in the shared memory log segment. To get varnishlog to process the
 whole shared memory log just add the -d option:::
 
-   $ varnishlog -d -c -o TxStatus 503
+   $ varnishlog -d -c -m TxStatus:503
 
 Please see the varnishlog man page for elaborations on further
 filtering capabilities and explanation of the various options.