Make the origin more clear in the docs.

[policy-templates.git] / README.md

diff --git a/README.md b/README.md
index bd3f58af638105527993c82ccddd857dd79d726b..0fc184870a63c65daa2822fdb82ce2164a2d5182 100644 (file)
--- a/README.md
+++ b/README.md
@@ -373,7 +373,7 @@ Value (string):
 }
 ```
 ### AutoLaunchProtocolsFromOrigins
-Define a list of external protocols that can be used from listed origins without prompting the user.
+Define a list of external protocols that can be used from listed origins without prompting the user. The origin is the scheme plus the hostname.
 
 The syntax of this policy is exactly the same as the [Chrome AutoLaunchProtocolsFromOrigins policy](https://cloud.google.com/docs/chrome-enterprise/policies/?policy=AutoLaunchProtocolsFromOrigins) except that you can only use valid origins (not just hostnames). This also means that you cannot specify an asterisk for all origins.
 
@@ -4196,10 +4196,12 @@ as well as the following security preferences:
 |     If true, client certificates are loaded from the operating system certificate store.
 | security.ssl.errorReporting.enabled | boolean | true
 |     If false, SSL errors cannot be sent to Mozilla.
+| security.tls.enable_0rtt_data | boolean | true
+|     If false, TLS early data is turned off (Firefox 93, Firefox 91.2, Firefox 78.15).
 | security.tls.hello_downgrade_check | boolean | true
 |     If false, the TLS 1.3 downgrade check is disabled.
 | security.tls.version.enable-deprecated | boolean | false
-|     If true, browser will accept TLS 1.0. and TLS 1.1 (Firefox 86, Firefox 78.8)
+|     If true, browser will accept TLS 1.0. and TLS 1.1 (Firefox 86, Firefox 78.8).
 | security.warn_submit_secure_to_insecure | boolean | true
 |     If false, no warning is shown when submitting s form from https to http.