Remove 'whitelist' term from OverrideSecurityRestrictionsOnInsecureOrigin policy description

Bug: 1097644
Change-Id: I913ad49ca0c9916a835cf2ee7df35330c78c6ced
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2386097Reviewed-by: Pavol Marko <pmarko@chromium.org>
Commit-Queue: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#803769}

components/policy/resources/policy_templates.json

@@ -18440,7 +18440,7 @@
       'caption': '''Origins or hostname patterns for which restrictions on
       insecure origins should not apply''',
       'tags': ['system-security'],
-      'desc': '''Setting the policy specifies a list of origins (URLs) or hostname patterns (such as *.example.com) for which security restrictions on insecure origins won't apply. Organizations can set whitelist origins for legacy applications that can't deploy TLS or set up a staging server for internal web development, so developers can test out features requiring secure contexts without having to deploy TLS on the staging server. This policy also prevents the origin from being labeled "Not Secure" in the address bar.
+      'desc': '''Setting the policy specifies a list of origins (URLs) or hostname patterns (such as *.example.com) for which security restrictions on insecure origins won't apply. Organizations can specify origins for legacy applications that can't deploy TLS or set up a staging server for internal web development, so developers can test out features requiring secure contexts without having to deploy TLS on the staging server. This policy also prevents the origin from being labeled "Not Secure" in the address bar.
 
       Setting a list of URLs in this policy amounts to setting the command-line flag --unsafely-treat-insecure-origin-as-secure to a comma-separated list of the same URLs. The policy overrides the command-line flag and UnsafelyTreatInsecureOriginAsSecure, if present.