Update formating issue in COIL_for_partners.md

BUG=b:186065737

Change-Id: I5bc964a6a61ef19682274e11aad05ff22d5c3c10
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2845487
Auto-Submit: Nathan Persall <persall@google.com>
Reviewed-by: Charlie Reis <creis@chromium.org>
Commit-Queue: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#875863}

styleguide/COIL_for_Partners.md

@@ -16,7 +16,7 @@ In addition to helping to maintain these changes when contributing to or buildin
 
 
 
-*   **Review and update** documentation, code and technical materials with respect to identified disrespectful terms**.  Directly replace identified disrespectful terms **with precise terms where possible, such as in  code branches, **master** ⇒ **main**;  **white list** ⇒ **allow list**.   (For a publicly available list of terms, refer to the list posted on [chromium.googlesource.com](https://www.google.com/url?q=https://chromium.googlesource.com/chromiumos/repohooks/%2B/refs/heads/main/blocked_terms.txt&sa=D&source=editors&ust=1614112385305000&usg=AOvVaw2isDcAxXDdDANvl-XPO-y4).)
+*   **Review and update** documentation, code and technical materials with respect to identified disrespectful terms.  **Directly replace identified disrespectful terms** with precise terms where possible, such as in  code branches, **master** ⇒ **main**;  **white list** ⇒ **allow list**.   (For a publicly available list of terms, refer to the list posted on [chromium.googlesource.com](https://www.google.com/url?q=https://chromium.googlesource.com/chromiumos/repohooks/%2B/refs/heads/main/blocked_terms.txt&sa=D&source=editors&ust=1614112385305000&usg=AOvVaw2isDcAxXDdDANvl-XPO-y4).)
 *   **For schematics, use current [Reference Design Schematic Net Naming](https://chromeos.google.com/partner/dlm/docs/reference-designs/Google_Reference_Design_Schematic_Style_Guidelines.html#net-naming-convention)** to meet the inclusive standard, with particular focus on [SPI signal names](https://www.oshwa.org/a-resolution-to-redefine-spi-signal-names/).  
 *   **Adopt pre-submit checks for code check ins** to catch inadvertent re-introduction of disrespectful terms.   (See \_check\_keywords function on [chromium.googlesource.com](https://www.google.com/url?q=https://chromium.googlesource.com/chromiumos/repohooks/%2B/refs/heads/main/blocked_terms.txt&sa=D&source=editors&ust=1614112385305000&usg=AOvVaw2isDcAxXDdDANvl-XPO-y4).)
 *   **Use precise language** when direct replacement is awkward, undefined, or using a term that can be perceived as oppressive and disrespectful, such as with **sanity** ⇒ **health check**;  **white label**  ⇒ **custom label**; and **master/slave** relationship ⇒  direct reference of items, such as with components on a schematic.