diff --git a/FTC-Self-Inspect.md b/FTC-Self-Inspect.md
index becd827..eeac969 100644
--- a/FTC-Self-Inspect.md
+++ b/FTC-Self-Inspect.md
@@ -15,6 +15,8 @@ The challenge is to maximize useful information in a small screen.  The Self Ins
 
 Pairing technology is a key aspect of Self Inspect reporting.  Remember that RC phones host via **Wi-Fi Direct**, while Control Hubs host via **Standard, or 'infrastructure', Wi-Fi**.
 
+In the DS app's Settings, the selected Pairing Method (Wi-Fi Direct or Control Hub) will influence acceptance/rejection in the DS Self Inspect report, as described in examples below.
+
 RC and DS phones must have Airplane Mode **ON**, and Wi-Fi **ON** but not connected to any Standard/infra Wi-Fi host such as an internet router or hotspot.  Devices should be set to **Forget** any local Wi-Fi networks.
 
 FTC control devices may use these combinations:
@@ -67,7 +69,7 @@ Here's a report from the same phone, with many items **rejected** by Self Inspec
 - Item 7 rejects `Bluetooth` for being **ON**; it must be off for FTC use.  This is also an Android system setting; swipe down twice or see Settings menu.
 - Item 8 rejects `Location services` for being **OFF**.  For devices running **Android 8** or higher, the FTC apps require Location enabled.  This is also an Android system setting; swipe down twice or see Settings menu.
 - Item 9 shows the DS phone's Wi-Fi radio is **ON**, as required for Wi-Fi Direct **or** Standard Wi-Fi pairing to an RC device.
-- Item 10 rejects the DS phone's connection via Standard/infrastructure Wi-Fi, to a device that's **not** an FTC Control Hub.  In this case, the phone is connected to a home Wi-Fi network.  This and other such networks must be set to **Forget**, in the device's Android Wi-Fi menu.  If temporary internet access is needed, 'Forget' that network afterwards.  <i>Also **Remove Account** for any Google or other accounts that may have been used during the internet session.  Such accounts can cause background activity, notifications and updates -- at the worst possible times.</i>
+- Item 10 rejects the DS phone's connection via Standard/infrastructure Wi-Fi, because the DS Pairing Method is set to Wi-Fi Direct -- thus intending to connect with an RC phone.  In this case, the phone is connected to a home Wi-Fi network.  This and other such networks must be set to **Forget**, in the device's Android Wi-Fi menu.  If temporary internet access is needed, 'Forget' that network afterwards.  <i>Also **Remove Account** for any Google or other accounts that may have been used during the internet session.  Such accounts can cause background activity, notifications and updates -- at the worst possible times.</i>
 - Item 11 rejects the device's **Wi-Fi Direct name** for not meeting FTC format requirements.  <i>The bad name shown here was created in the DS phone's Android Wi-Fi Direct settings; not possible using the app's DS Settings (Driver Station Name).</i>
 - Item 12 rejects the presence of an RC app installed on this DS device.  The rejection is not for the older version (6.2), but simply for being an RC app.
 
@@ -80,6 +82,7 @@ Here's a report from the same phone, with many items **rejected** by Self Inspec
 
 The same points apply as for DS Self Inspect 1 (immediately above), except:
 - Items 9 and 10 must now be Yes and Yes.  The DS phone's Wi-Fi radio is **ON**, and connected via Standard/infra Wi-Fi.  It does not indicate **what** the DS phone is connected to; that's covered by Item 11.
+- Item 10's Yes would be **rejected** if the DS Pairing Method was set to Wi-Fi Direct -- thus intending to connect with an RC phone.
 - Item 11 shows the Standard Wi-Fi **network name**, or Access Point (AP), that the DS phone is connected to.  The check-mark indicates the AP is an FTC legal device (Control Hub) and has a correctly formatted name.  This does **not** check that the DS and RC names match (team number).  In fact, this phone is 2468-A-DS and this Control Hub is 9999-A-RC, an **illegal combination** to be flagged by the FTC team or the Field Inspector.
 
 [<p align="right"><i>Return to Top</i>](#introduction)<p>
@@ -93,6 +96,7 @@ The same points apply as for DS Self Inspect 1 (immediately above), except:
 - Note that `Airplane Mode` has been omitted from the DS inspection, only for Driver Hub.  FTC rules exclude the Driver Hub and Control Hub from the Airplane Mode requirement.
 - Item 8 `Location services` appears only on devices running **Android 8** or higher.  This is an SDK/Android technology requirement, not an FTC rule.
 - Items 9 and 10 must be Yes and No.  `Wi-Fi Enabled` means the Driver Hub's Wi-Fi radio is **ON**, to use Wi-Fi Direct for the RC phone.  The Driver Hub is technically **able to also be connected** to a Standard/infrastructure Wi-Fi source, including an internet router or a Control Hub.  Item 10 confirms this is not happening; see next example.
+- Item 10's No would be **rejected** if the DS Pairing Method was set to Control Hub.
 - Item 11 indicates whether the **device name** meets FTC format requirements.  It does not check whether the paired device has a matching RC name (team number).
 - Item 12 verifies that the Driver Hub does **not** have an RC app installed.
 - Item 13 ensures the DS app meets the minimum version **for the current FTC season**, based on the device's system date.  This particular version 7.0.1 does not exactly match the RC phone's 7.0; Self Inspect will soon allow this 'point mismatch'.
@@ -112,6 +116,7 @@ This Self Inspect screen appeared while the Driver Hub was paired to an RC phone
 <br><i><b>DS Self Inspect 4, on Driver Hub paired to Control Hub</b></i><p>
 
 - Item 1 still offers one choice, "Disconnect from Wi-Fi Direct".  But now, touching that selection gives this message "There was an error disconnecting from Wi-Fi Direct".  That's because the Driver Hub is paired to a Control Hub, thus **not** via Wi-Fi Direct.
+- Item 10's Yes would be **rejected** if the DS Pairing Method was set to Wi-Fi Direct -- thus intending to connect with an RC phone.
 - Item 11 shows the Standard Wi-Fi **network name**, or Access Point (AP), that the Driver Hub is connected to.  The check-mark indicates the AP is an FTC legal device (Control Hub) and has a correctly formatted name.  This does **not** check that the DS and RC names match (team number).  In fact, this Driver Hub is 1234-A-DS and this Control Hub is 9999-A-RC, an **illegal combination** to be flagged by the FTC team or the Field Inspector.
 
 <p align="center">[[/images/FTC-Self-Inspect/tDS-4a.png]]