From 8e6fabd69a124cc5b5ae763b58587ee6ee6ab3da Mon Sep 17 00:00:00 2001
From: Aldo Cortesi <aldo@nullcube.com>
Date: Wed, 2 Jan 2013 21:57:39 +1300
Subject: Docs - features.

---
 doc-src/clientreplay.html | 15 ++++++++++++---
 1 file changed, 12 insertions(+), 3 deletions(-)

(limited to 'doc-src/clientreplay.html')

diff --git a/doc-src/clientreplay.html b/doc-src/clientreplay.html
index c94f5034..6638d078 100644
--- a/doc-src/clientreplay.html
+++ b/doc-src/clientreplay.html
@@ -1,7 +1,4 @@
 
-- command-line: _-c path_ 
-- mitmproxy shortcut: _c_
-
 Client-side replay does what it says on the tin: you provide a previously saved
 HTTP conversation, and mitmproxy replays the client requests one by one. Note
 that mitmproxy serializes the requests, waiting for a response from the server
@@ -11,3 +8,15 @@ conversation, where requests may have been made concurrently.
 You may want to use client-side replay in conjunction with the
 [anticache](@!urlTo("anticache.html")!@) option, to make sure the server
 responds with complete data. 
+
+
+<table class="table">
+    <tbody>
+        <tr>
+            <th width="20%">command-line</th> <td>-c path</td>
+        </tr>
+        <tr>
+            <th>mitmproxy shortcut</th> <td><b>c</b></td>
+        </tr>
+    </tbody>
+</table>
-- 
cgit v1.2.3