aboutsummaryrefslogtreecommitdiffstats
path: root/doc-src/ssl.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc-src/ssl.html')
-rw-r--r--doc-src/ssl.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc-src/ssl.html b/doc-src/ssl.html
index a8004082..7ee9438e 100644
--- a/doc-src/ssl.html
+++ b/doc-src/ssl.html
@@ -27,7 +27,7 @@ a browser, just accepting the bogus SSL cert manually is not too much trouble,
but there are a number of cases where you will want to configure your testing
system or browser to trust the __mitmproxy__ CA as a signing root authority:
-- If you are testing non-browser software that checks SSL cert validiy using
+- If you are testing non-browser software that checks SSL cert validity using
the system certificate store.
- You are testing an app that makes non-interactive (JSONP, script src, etc.)
requests to SSL resources. Another workaround in this case is to manually visit