docs: minor fixes

1 files changed, 7 insertions, 4 deletions

diff --git a/docs/features/passthrough.rst b/docs/features/passthrough.rst
index 83374955..80521393 100644
--- a/docs/features/passthrough.rst
+++ b/docs/features/passthrough.rst
@@ -3,14 +3,17 @@
 Ignore Domains
 ==============
 
-There are two main reasons why you may want to exempt some traffic from mitmproxy's interception mechanism:
+There are two main reasons why you may want to exempt some traffic from mitmproxy's interception
+mechanism:
 
 - **Certificate pinning:** Some traffic is is protected using `Certificate Pinning`_ and
   mitmproxy's interception leads to errors. For example, the Twitter app, Windows Update or
   the Apple App Store fail to work if mitmproxy is active.
-- **Convenience:** You really don't care about some parts of the traffic and just want them to go away.
+- **Convenience:** You really don't care about some parts of the traffic and just want them to go
+  away.
 
-If you want to peek into (SSL-protected) non-HTTP connections, check out the :ref:`tcpproxy` feature.
+If you want to peek into (SSL-protected) non-HTTP connections, check out the :ref:`tcpproxy`
+feature.
 If you want to ignore traffic from mitmproxy's processing because of large response bodies,
 take a look at the :ref:`responsestreaming` feature.
 
@@ -91,4 +94,4 @@ Here are some other examples for ignore patterns:
     ``GET http://example.com/`` request may be followed by a ``GET http://evil.com/`` request on the
     same connection. If we start to ignore the connection after the first request,
     we would miss the relevant second one.
-.. _Certificate Pinning: https://security.stackexchange.com/questions/29988/what-is-certificate-pinning
\ No newline at end of file
+.. _Certificate Pinning: https://security.stackexchange.com/questions/29988/what-is-certificate-pinning