Docs: Remove inconsistent boldface around auxiliaries

Auxiliaries such as STRONGLY RECOMMENDED should be all caps,
but not boldface.

Bug: 149871806
Test: N/A
Change-Id: I4e9aa1a129c02ab5e70f64920b78dda3173a4f75

4 files changed, 10 insertions, 10 deletions

diff --git a/10_software-compatibility-testing/10_0_intro.md b/10_software-compatibility-testing/10_0_intro.md
index 26ddf19..db91f3f 100644
--- a/10_software-compatibility-testing/10_0_intro.md
+++ b/10_software-compatibility-testing/10_0_intro.md
@@ -3,7 +3,7 @@
 Device implementations MUST pass all tests described in this
 section.
 However, note that no software test package is fully comprehensive.
-For this reason, device implementers are **STRONGLY RECOMMENDED** to make the
+For this reason, device implementers are STRONGLY RECOMMENDED to make the
 minimum number of changes as possible to the reference and preferred
 implementation of Android available from the Android Open Source Project.
 This will minimize the risk of introducing bugs that create incompatibilities
diff --git a/5_multimedia/5_4_audio-recording.md b/5_multimedia/5_4_audio-recording.md
index 7fb4e19..f9dbda4 100644
--- a/5_multimedia/5_4_audio-recording.md
+++ b/5_multimedia/5_4_audio-recording.md
@@ -2,8 +2,8 @@
 
 While some of the requirements outlined in this section are listed as SHOULD
 since Android 4.3, the Compatibility Definition for future versions are planned
-to change these to MUST. Existing and new Android devices are **STRONGLY
-RECOMMENDED** to meet these requirements that are listed as SHOULD, or they
+to change these to MUST. Existing and new Android devices are STRONGLY
+RECOMMENDED to meet these requirements that are listed as SHOULD, or they
 will not be able to attain Android compatibility when upgraded to the future
 version.
 
diff --git a/7_hardware-compatibility/7_3_sensors.md b/7_hardware-compatibility/7_3_sensors.md
index 6f728c7..fad4504 100644
--- a/7_hardware-compatibility/7_3_sensors.md
+++ b/7_hardware-compatibility/7_3_sensors.md
@@ -38,7 +38,7 @@ http://developer.android.com/reference/android/hardware/SensorEvent.html#timesta
 in nanoseconds as defined in the Android SDK documentation, representing the
 time the event happened and synchronized with the
 SystemClock.elapsedRealtimeNano() clock. Existing and new Android devices are
-**STRONGLY RECOMMENDED** to meet these requirements so they will be able to
+STRONGLY RECOMMENDED to meet these requirements so they will be able to
 upgrade to the future platform releases where this might become a REQUIRED
 component. The synchronization error SHOULD be below 100 milliseconds.
 
@@ -100,7 +100,7 @@ gravity(4g) or more on any axis.
 *   [C-1-6] MUST have a standard deviation no greater than 0.05 m/s^, where
 the standard deviation should be calculated on a per axis basis on samples
 collected over a period of at least 3 seconds at the fastest sampling rate.
-*   [SR] are **STRONGLY RECOMMENDED** to implement the `TYPE_SIGNIFICANT_MOTION`
+*   [SR] are STRONGLY RECOMMENDED to implement the `TYPE_SIGNIFICANT_MOTION`
     composite sensor.
 *   [SR] are STRONGLY RECOMMENDED to implement and report [`TYPE_ACCELEROMETER_UNCALIBRATED`]
 (https://developer.android.com/reference/android/hardware/Sensor.html#STRING_TYPE_ACCELEROMETER_UNCALIBRATED)
diff --git a/7_hardware-compatibility/7_7_usb.md b/7_hardware-compatibility/7_7_usb.md
index 59faf56..4ff3961 100644
--- a/7_hardware-compatibility/7_7_usb.md
+++ b/7_hardware-compatibility/7_7_usb.md
@@ -16,18 +16,18 @@ device descriptor through `android.os.Build.SERIAL`.
 standard and MUST detect changes in the advertisement if they support
 Type-C USB.
 *    [SR] The port SHOULD use micro-B, micro-AB or Type-C USB form factor.
-Existing and new Android devices are **STRONGLY RECOMMENDED to meet these
-requirements** so they will be able to upgrade to the future platform releases.
+Existing and new Android devices are STRONGLY RECOMMENDED to meet these
+requirements so they will be able to upgrade to the future platform releases.
 *    [SR] The port SHOULD be located on the bottom of the device
 (according to natural orientation) or enable software screen rotation for
 all apps (including home screen), so that the display draws correctly when
 the device is oriented with the port at bottom. Existing and new Android
-devices are **STRONGLY RECOMMENDED to meet these requirements** so they will
+devices are STRONGLY RECOMMENDED to meet these requirements so they will
 be able to upgrade to future platform releases.
 *    [SR] SHOULD implement support to draw 1.5 A current during HS chirp
 and traffic as specified in the [USB Battery Charging specification, revision 1.2](http://www.usb.org/developers/docs/devclass_docs/BCv1.2_070312.zip).
-Existing and new Android devices are **STRONGLY RECOMMENDED to meet these
-requirements** so they will be able to upgrade to the future platform releases.
+Existing and new Android devices are STRONGLY RECOMMENDED to meet these
+requirements so they will be able to upgrade to the future platform releases.
 *    [SR] STRONGLY RECOMMENDED to not support proprietary
 charging methods that modify Vbus voltage beyond default levels, or alter
 sink/source roles as such may result in interoperability issues with the