Update documentation for SSLVersionMin

The default unset state is now an in-between state where TLS 1.0 and 1.1
fail, but the error is bypassable. (In the future, the minimum version
will truly be set to TLS 1.2.)

Bug: 1128976
Change-Id: I664b6279789cdc79a358cfe3e241e921d236da58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441656
Commit-Queue: David Benjamin <davidben@chromium.org>
Auto-Submit: David Benjamin <davidben@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812768}

components/policy/resources/policy_templates.json

@@ -13656,7 +13656,7 @@
       'tags': [],
       'desc': '''Setting the policy to a valid value means <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> won't use SSL/TLS versions less than the specified version. Unrecognized values are ignored.
 
-      If this policy is not set, then <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> uses a default minimum version of TLS 1.0.''',
+      If this policy is not set, then <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> will show an error for TLS 1.0 and TLS 1.1, but the user will be able to bypass it.''',
     },
     {
       'name': 'SSLVersionFallbackMin',