From c34d1e3de6483b1ab8a1a3add53fb84364c68249 Mon Sep 17 00:00:00 2001
From: Aldo Cortesi <aldo@nullcube.com>
Date: Mon, 11 Mar 2013 11:49:36 +1300
Subject: Docs, examples.

---
 doc-src/scripting/inlinescripts.html | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

(limited to 'doc-src/scripting')

diff --git a/doc-src/scripting/inlinescripts.html b/doc-src/scripting/inlinescripts.html
index 7abf743c..39752b7f 100644
--- a/doc-src/scripting/inlinescripts.html
+++ b/doc-src/scripting/inlinescripts.html
@@ -13,6 +13,15 @@ lets the script interact with the global mitmproxy state. The __response__
 event also gets an instance of Flow, which we can use to manipulate the
 response itself.
 
+We can now run this script as follows:
+
+<pre class="terminal">
+> mitmdump -s add_header.py
+</pre>
+
+The new header will be added to all responses passing through the proxy.
+
+
 
 ## Events
 
@@ -60,7 +69,7 @@ Called once on script shutdown, after any other events.
 
 The main classes you will deal with in writing mitmproxy scripts are:
 
-<table class="kvtable">
+<table class="table">
     <tr>
         <th>libmproxy.flow.ClientConnection</th>
         <td>Describes a client connection.</td>
-- 
cgit v1.2.3