From 0ee05afdbb5f49c35ee8ec2447b1a91bba888650 Mon Sep 17 00:00:00 2001
From: sandbank52641 <153552626+sandbank52641@users.noreply.github.com>
Date: Tue, 23 Jan 2024 20:37:58 +0100
Subject: [PATCH] start introducing conforming procedure style
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The changes summarized:

* Use angle brackets (`>`) instead of arrow symbols (`➔`).
* Put a non-breaking space (`&#160;`) before each angle bracket.
* Wrap sequences and elements in bold element (`<b>`).
* Accessibility: Wrap angle bracket in a span tag with an aria-label.

References:

* https://developers.google.com/style/procedures#multi-action-procedures
* https://developers.google.com/style/ui-elements#angle-brackets

I use the entity number `&#160;` for the non-breaking space instead of
the named character entity `&nbsp;` because `xmllint` produces a linting
error (which is to be expected).

```
parser error : Entity 'nbsp' not defined
```

Ideally we want to use the named character entity (`&nbsp;`), but I
couldn't find a reasonable solution. In order not to block this change,
I've opted for the entity number (`&#160;`). If a reasonable solution is
found, the entity number can be easily replaced by the named character
entity.

The changes require more than just replacing the currently used arrow.
The surrounding context should be checked to determine whether a change
is appropriate at this point and whether it requires further changes in
the context itself.

The paragraphs are wrapped with the currently used 98 characters. If
using vim:

```
:set tw=98
```

Vim's wrapping is weird when applied several times. To work around this,
we can unwrap the paragraph first. To select a paragraph, unwrap and
rewrap: Point to the line of the paragraph, and type `vipJgqq` in normal
mode.
---
 static/install/cli.html | 16 +++++++++-------
 static/install/web.html | 16 +++++++++-------
 2 files changed, 18 insertions(+), 14 deletions(-)

diff --git a/static/install/cli.html b/static/install/cli.html
index 9bb9119a..dcc610df 100644
--- a/static/install/cli.html
+++ b/static/install/cli.html
@@ -170,14 +170,16 @@
 
                 <p>OEM unlocking needs to be enabled from within the operating system.</p>
 
-                <p>Enable the developer options menu by going to Settings ➔ About phone/tablet and
-                repeatedly pressing the build number menu entry until developer mode is
-                enabled.</p>
+                <p>Enable the developer options menu by going to <b>Settings&#160;<span
+                aria-label="and then">></span> About phone/tablet</b> and repeatedly
+                pressing the <b>Build number</b> menu entry until developer mode is enabled.</p>
 
-                <p>Next, go to Settings ➔ System ➔ Developer options and toggle on the 'OEM
-                unlocking' setting. On device model variants (SKUs) which support being sold as
-                locked devices by carriers, enabling 'OEM unlocking' requires internet access so
-                that the stock OS can check if the device was sold as locked by a carrier.</p>
+                <p>Next, go to <b>Settings&#160;<span aria-label="and then">></span>
+                System&#160;<span aria-label="and then">></span> Developer options</b> and
+                toggle on the <b>OEM unlocking</b> setting. On device model variants (SKUs) which
+                support being sold as locked devices by carriers, enabling <b>OEM unlocking</b>
+                requires internet access so that the stock OS can check if the device was sold as
+                locked by a carrier.</p>
 
                 <p>For the Pixel 6a, OEM unlocking won't work with the version of the stock OS
                 from the factory. You need to update it to the June 2022 release or later via an
diff --git a/static/install/web.html b/static/install/web.html
index 023b7ede..880c2fb8 100644
--- a/static/install/web.html
+++ b/static/install/web.html
@@ -168,14 +168,16 @@
 
                 <p>OEM unlocking needs to be enabled from within the operating system.</p>
 
-                <p>Enable the developer options menu by going to Settings ➔ About phone/tablet and
-                repeatedly pressing the build number menu entry until developer mode is
-                enabled.</p>
+                <p>Enable the developer options menu by going to <b>Settings&#160;<span
+                aria-label="and then">></span> About phone/tablet</b> and repeatedly
+                pressing the <b>Build number</b> menu entry until developer mode is enabled.</p>
 
-                <p>Next, go to Settings ➔ System ➔ Developer options and toggle on the 'OEM
-                unlocking' setting. On device model variants (SKUs) which support being sold as
-                locked devices by carriers, enabling 'OEM unlocking' requires internet access so
-                that the stock OS can check if the device was sold as locked by a carrier.</p>
+                <p>Next, go to <b>Settings&#160;<span aria-label="and then">></span>
+                System&#160;<span aria-label="and then">></span> Developer options</b> and
+                toggle on the <b>OEM unlocking</b> setting. On device model variants (SKUs) which
+                support being sold as locked devices by carriers, enabling <b>OEM unlocking</b>
+                requires internet access so that the stock OS can check if the device was sold as
+                locked by a carrier.</p>
 
                 <p>For the Pixel 6a, OEM unlocking won't work with the version of the stock OS
                 from the factory. You need to update it to the June 2022 release or later via an