aboutsummaryrefslogtreecommitdiffstats
path: root/docs/features
diff options
context:
space:
mode:
Diffstat (limited to 'docs/features')
-rw-r--r--docs/features/responsestreaming.rst2
-rw-r--r--docs/features/upstreamcerts.rst2
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/features/responsestreaming.rst b/docs/features/responsestreaming.rst
index af3d889a..8975c1f8 100644
--- a/docs/features/responsestreaming.rst
+++ b/docs/features/responsestreaming.rst
@@ -10,7 +10,7 @@ such as videos, where buffering the whole file slows down the client's browser.
By default, mitmproxy will read the entire response, perform any indicated
manipulations on it and then send the (possibly modified) response to
the client. In some cases this is undesirable and you may wish to "stream"
-the reponse back to the client. When streaming is enabled, the response is
+the response back to the client. When streaming is enabled, the response is
not buffered on the proxy but directly sent back to the client instead.
On the command-line
diff --git a/docs/features/upstreamcerts.rst b/docs/features/upstreamcerts.rst
index c687aec7..af2e2226 100644
--- a/docs/features/upstreamcerts.rst
+++ b/docs/features/upstreamcerts.rst
@@ -11,7 +11,7 @@ then used to generate the interception certificate, which is sent to the client
so the connection can continue.
This rather intricate little dance lets us seamlessly generate correct
-certificates even if the client has specifed only an IP address rather than the
+certificates even if the client has specified only an IP address rather than the
hostname. It also means that we don't need to sniff additional data to generate
certs in transparent mode.