From 421b241ff010ae979cff8df504b6744e4c291aeb Mon Sep 17 00:00:00 2001
From: Maximilian Hils <git@maximilianhils.com>
Date: Sun, 30 Aug 2015 13:40:23 +0200
Subject: remove http2http references

---
 doc-src/features/reverseproxy.html | 17 ++++++-----------
 doc-src/modes.html                 |  8 ++++----
 2 files changed, 10 insertions(+), 15 deletions(-)

(limited to 'doc-src')

diff --git a/doc-src/features/reverseproxy.html b/doc-src/features/reverseproxy.html
index 5ef4efc5..af5a5c53 100644
--- a/doc-src/features/reverseproxy.html
+++ b/doc-src/features/reverseproxy.html
@@ -7,22 +7,17 @@ mitmproxy forwards HTTP proxy requests to an upstream proxy server.
 <table class="table">
     <tbody>
         <tr>
-            <th width="20%">command-line</th> <td>-R <i>schema</i>://hostname[:port]</td>
+            <th width="20%">command-line</th> <td>-R <i>scheme</i>://hostname[:port]</td>
         </tr>
     </tbody>
 </table>
 
-Here, **schema** is one of http, https, http2https or https2http. The latter
-two extended schema specifications control the use of HTTP and HTTPS on
-mitmproxy and the upstream server. You can indicate that mitmproxy should use
-HTTP, and the upstream server uses HTTPS like this:
+Here, **scheme** signifies if the proxy should use TLS to connect to the server.
+mitmproxy accepts both encrypted and unencrypted requests and transforms them to what the server
+expects.
 
-	http2https://hostname:port
-
-And you can indicate that mitmproxy should use HTTPS while the upstream
-service uses HTTP like this:
-
-	https2http://hostname:port
+    mitmdump -R https://httpbin.org -p 80
+    mitmdump -R https://httpbin.org -p 443
 
 
 ### Host Header
diff --git a/doc-src/modes.html b/doc-src/modes.html
index b5a38696..a878fd82 100644
--- a/doc-src/modes.html
+++ b/doc-src/modes.html
@@ -149,7 +149,7 @@ this:
     <h1>Reverse Proxy</h1>
 </div>
 
-Mitmproxy is usually used with a client that uses the proxy to access the
+mitmproxy is usually used with a client that uses the proxy to access the
 Internet. Using reverse proxy mode, you can use mitmproxy to act like a normal
 HTTP server:
 
@@ -174,14 +174,14 @@ requests recorded in mitmproxy.
 
 - Say you have some toy project that should get SSL support. Simply set up
 mitmproxy with SSL termination and you're done (<code>mitmdump -p 443 -R
-https2http://localhost:80/</code>). There are better tools for this specific
+http://localhost:80/</code>). There are better tools for this specific
 task, but mitmproxy is very quick and simple way to set up an SSL-speaking
 server.
 
 - Want to add a non-SSL-capable compression proxy in front of your server? You
-could even spawn a mitmproxy instance that terminates SSL (https2http://...),
+could even spawn a mitmproxy instance that terminates SSL (-R http://...),
 point it to the compression proxy and let the compression proxy point to a
-SSL-initiating mitmproxy (http2https://...), which then points to the real
+SSL-initiating mitmproxy (-R https://...), which then points to the real
 server. As you see, it's a fairly flexible thing.
 
 Note that mitmproxy supports either an HTTP or an HTTPS upstream server, not
-- 
cgit v1.2.3