Update src/connections/sources/catalog/libraries/website/shopify/index.md

Co-authored-by: forstisabella <[email protected]>

Author: joe-ayoub-segment

src/connections/sources/catalog/libraries/website/shopify/index.md

@@ -276,8 +276,8 @@ To save on API call volume Segment will only trigger an `identify()` event when
 ** Why are some events duplicated and triggered multiple times? **
 Shopify sometimes erroneously triggers duplicate `Address Info Entered`, `Shipping Info Entered`, `Contact Info Entered`, `Payment Info Entered` events in short succession. This is a known bug with Shopify. Segment deduplicates the majority of these duplicate events but is unable to filter all of them out. 
 
-** Why do some Address/Shipping/Contact/Payment Info Entered events contain product arrays? **
-Shopify sometimes includes product array details in the [Standard Events](https://shopify.dev/docs/api/web-pixels-api/standard-events){:target="\_blank"} which Segment uses to populate the `Address Info Entered`, `Shipping Info Entered`, `Contact Info Entered`, `Payment Info Entered` events. A decision was made to include these product details in the Segment events for completeness.  
+### Why do some Address/Shipping/Contact/Payment Info Entered events contain product arrays?
+Shopify sometimes includes product array details in [Standard Events](https://shopify.dev/docs/api/web-pixels-api/standard-events){:target="_blank"} which Segment uses to populate the `Address Info Entered`, `Shipping Info Entered`, `Contact Info Entered`, `Payment Info Entered` events. Segment includes these product details in Segment events.
 
 ### Why are some event properties missing even though the documentation indicates that they should be present?
 Mapping code is in place to map the majority of valuable fields from Shopify's [Standard Events](https://shopify.dev/docs/api/web-pixels-api/standard-events){:target="_blank"} to Segment events. If properties are missing, it is due to the values not being provided by the Shopify event.