From 966041feea4345dac282f532f722c9424baaf64f Mon Sep 17 00:00:00 2001
From: pixelzoom <cmalley@pixelzoom.com>
Date: Tue, 26 Oct 2021 15:53:04 -0600
Subject: [PATCH] formatting, https://github.com/phetsims/phet-info/issues/168

---
 doc/alternative-input-quick-start-guide.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/alternative-input-quick-start-guide.md b/doc/alternative-input-quick-start-guide.md
index 9d4334d0..783a8249 100644
--- a/doc/alternative-input-quick-start-guide.md
+++ b/doc/alternative-input-quick-start-guide.md
@@ -12,11 +12,11 @@ Follow these steps to add support for alternative input to a simulation.
 
 2. Run `grunt update` to generate `{{REPO}}_a11y_view.html` and modify `{{REPO}}_en.html`.
 
-3. For non-LayoutBox parent Nodes, explicitly set `this.pdomOrder` at the end of constructor. Do not rely on scenery’s
+3. For non-`LayoutBox` parent Nodes, explicitly set `this.pdomOrder` at the end of constructor. Do not rely on scenery’s
    default ordering, which corresponds to the order that children are added. It’s better to decouple rendering order and
-   traversal order by explicitly setting `this.pdomOrder`.
+   traversal order by explicitly setting `this.pdomOrder`. Note that most of the work here is in ScreenView subclasses.
 
-4. For LayoutBox parents do nothing. The layout order and traversal order are typically the same.
+4. For `LayoutBox` Nodes do nothing. The layout order and traversal order are typically the same.
 
 5. If you need to augment `this.pdomOrder` in a subclass, read about the numerous pitfalls
    in https://github.com/phetsims/scenery/issues/1308.