aboutsummaryrefslogtreecommitdiffstats
path: root/docs/src/content/concepts-certificates.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/src/content/concepts-certificates.md')
-rw-r--r--docs/src/content/concepts-certificates.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/src/content/concepts-certificates.md b/docs/src/content/concepts-certificates.md
index 20b03dc6..9b5f1a83 100644
--- a/docs/src/content/concepts-certificates.md
+++ b/docs/src/content/concepts-certificates.md
@@ -65,7 +65,7 @@ SSL sites that your client visits. Since your browser won't trust the mitmproxy
CA out of the box, you will see an SSL certificate warning every time you visit
a new SSL domain through mitmproxy. When you are testing a single site through a
browser, just accepting the bogus SSL cert manually is not too much trouble, but
-there are a many circumstances where you will want to configure your testing
+there are many circumstances where you will want to configure your testing
system or browser to trust the mitmproxy CA as a signing root authority. For
security reasons, the mitmproxy CA is generated uniquely on the first start and
is not shared between mitmproxy installations on different devices.