From 37253ffa17c63ea3fd0c201fa4e62ee36e5ce2ff Mon Sep 17 00:00:00 2001
From: smdyv <88971341+smdyv@users.noreply.github.com>
Date: Thu, 25 Aug 2022 15:05:41 +0200
Subject: Add highlighting style for placeholders

This is in accordance with Google's developer documentation style guide.
---
 static/faq.html | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to 'static/faq.html')

diff --git a/static/faq.html b/static/faq.html
index 65e72191..e58ce351 100644
--- a/static/faq.html
+++ b/static/faq.html
@@ -643,7 +643,7 @@
                     enabled, and it has the option to automatically restore app data when an app is
                     reinstalled, so it wouldn't lose track of it being the same profile.</p>
 
-                    <p>The <code>ANDROID_ID</code> string is a 64-bit random number, unique to each
+                    <p>The <var>ANDROID_ID</var> string is a 64-bit random number, unique to each
                     combination of profile and app signing key. The 64-bit limitation means it isn't
                     particularly useful due to the possibility of collisions. It's tied to the lifetime of
                     profiles and does not persist through profile deletion or a factory reset. This is
@@ -655,13 +655,13 @@
 
                     <p>The advertising ID is a Google Play services feature not included in the baseline
                     Android API, so it isn't an API included in GrapheneOS. The advertising ID is unique
-                    to each profile. It isn't unique to each app signing key like <code>ANDROID_ID</code>,
+                    to each profile. It isn't unique to each app signing key like <var>ANDROID_ID</var>,
                     but that makes little difference since apps within the same profile can communicate
-                    with each other with mutual consent. It's comparable to <code>ANDROID_ID</code> but
+                    with each other with mutual consent. It's comparable to <var>ANDROID_ID</var> but
                     provides an 128-bit value so it provides a strong cryptographic guarantee against
                     collisions, although a device messing with apps could set it to the same value used in
                     another profile. The advertising ID is exposed via the Settings app and can be reset
-                    to a new random value, unlike <code>ANDROID_ID</code> which remains the same for the
+                    to a new random value, unlike <var>ANDROID_ID</var> which remains the same for the
                     lifetime of the profile, but apps can tie it to the previous ID since they can detect
                     that it changed via their own ID in their app data. The advertising ID can
                     also now be disabled (zeroed).</p>
@@ -673,7 +673,7 @@
                     track of the profile. Apps previously had little reason to do things like this because
                     they were able to persist data through an uninstall and reinstallation by default. The
                     modern storage model means they need to request access to user data to do this. The
-                    existence of <code>ANDROID_ID</code> means they don't yet need to bother with that but
+                    existence of <var>ANDROID_ID</var> means they don't yet need to bother with that but
                     that will change on GrapheneOS and will likely change for baseline Android too.
                     However, profiles are the only way to provide a strong assurance of separate
                     identities since the application model of the OS is designed to support communication
-- 
cgit v1.3.1