FontAccess: Permission string explains specific use-case

This changes the permission string for the Font Access API so that it
succinctly explains the use-case for the API to the end-user.

The string is not ideal, because at best, it does not guarantee that the
API will be used for that purpose, and at worst, it is lying (e.g. one
may use the API for other legitimate purposes).

That said, that's the compromise we've landed on to test this API with
users.

Bug: 1043306
Change-Id: I30b31bcae8a39f942021ef87f88a53ed3453d3a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2437090
Commit-Queue: Balazs Engedy <engedy@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811744}

components/permissions_strings.grdp

@@ -123,7 +123,7 @@ This will otherwise be blocked by your privacy settings. This will allow the con
     Open and place windows on your screens
   </message>
   <message name="IDS_FONT_ACCESS_PERMISSION_FRAGMENT" desc="Permission request shown if the user is visiting a site that wants to access locally installed font data. Follows a prompt: 'This site would like to:'">
-    Use the fonts installed on your computer so you can create advanced typography
+    Use the fonts on your computer so you can create high-fidelity content
   </message>
   <message name="IDS_IDLE_DETECTION_PERMISSION_FRAGMENT" desc="Permission request shown if the user is visiting a site that wants to monitor when the user is interacting with their device. Follows a prompt: 'This site would like to:'">
     Know when you're present

components/permissions_strings_grdp/IDS_FONT_ACCESS_PERMISSION_FRAGMENT.png.sha1

-1acf180e72599e85eaf3dfd47606fc3509bb226e
+9a50fdc1c97d6a9f810706c2ae5293e6e35280e7
\ No newline at end of file