Add batch fixes from #8080

src/_includes/content/connection-modes-intro.md

@@ -2,22 +2,12 @@ Segment's web source (Analytics.js), and native client-side libraries (iOS, Andr
 
 - **Cloud-mode**: The sources send data directly to the Segment servers, which then translate it for each connected downstream destination, and send it on. Translation is done on the Segment servers, keeping your page size, method count, and load time small.
 
-  <div class="premonition info">
-    <div class="fa fa-info-circle"></div>
-    <div class="content">
-      <p class="header">Healthcare and Life Sciences (HLS) customers can encrypt data flowing into their destinations</p>
-      <p> HLS customers with a HIPAA eligible workspace can encrypt data in fields marked as Yellow in the Privacy Portal before they flow into an event stream, cloud-mode destination.
-      <br>To learn more about data encryption, see the <a href="/docs/privacy/hipaa-eligible-segment/#data-encryption">HIPAA Eligible Segment documentation</a>.</p>
-    </div>
-  </div>
+  > info "Healthcare and Life Sciences (HLS) customers can encrypt data flowing into their destination"
+  > HLS customers with a HIPAA eligible workspace can encrypt data in fields marked as Yellow in the Privacy Portal before they flow into an event stream, cloud-mode destination.
+  > To learn more about data encryption, see the [HIPAA Eligible Segment documentation](/docs/segment/privacy/hipaa-eligible-segment/#data-encryption).
 
 - **Device-mode**: You include additional code on your website or mobile app which allows Segment to use the data you collect on the device to make calls directly to the destination tool's API, without sending it to the Segment servers _first_. (You still send your data to the Segment servers, but this occurs asynchronously.) This is also called *wrapping* or *bundling*, and it might be required when the source has to be loaded on the page to work, or loaded directly on the device to function correctly. When you use Analytics.js, you can change the device-mode destinations that a specific source sends from within the Segment web app, without touching any code.
 
-
-<div class="premonition info">
-  <div class="fa fa-info-circle"></div>
-  <div class="content">
-    <p class="header"></p>
-    <p>If you use Server source libraries, they only send data directly to Segment in Cloud-mode. Server library implementations operate in the server backend, and can't load additional destination SDKs.</p>
-  </div>
-</div>
+  > info ""
+  >
+  > If you use Server source libraries, they only send data directly to Segment in Cloud-mode. Server library implementations operate in the server backend, and can't load additional destination SDKs.

src/_includes/content/dev-center-note.md

@@ -1 +1,3 @@
-<div class="premonition info"><div class="fa fa-info-circle"></div><div class="content"><p class="header">Developer Center no longer accepts new components.</p><p markdown=1>Segment is redeveloping the Developer Center and will launch a new version when complete. To stay up to date, add your contact information [in this Airtable form](https://airtable.com/shrT3b4C7agUEBKVS){:target="_blank"}.</p></div></div>
+> info "Developer Center no longer accepts new components"
+>
+> Segment is redeveloping the Developer Center and will launch a new version when complete. To stay up to date, add your contact information [in this Airtable form](https://airtable.com/shrT3b4C7agUEBKVS)

src/connections/sources/catalog/libraries/server/http-api/index.md

@@ -7,7 +7,7 @@ The Segment HTTP Tracking API lets you record analytics data from any website or
 
 Segment has native [sources](/docs/connections/sources/) for most use cases (like JavaScript and iOS) that are open-source and built for high-performance. But for unsupported use cases, [blocked event forwarding](/docs/protocols/enforce/forward-blocked-events/) or when you're using [Segment-Managed Custom Domain](/docs/connections/sources/custom-domain/), you may want to send data to Segment's HTTP API directly.
 
-> info "HTTP API sources in EU workspaces should use the `events.eu1.segmentapis.com` endpoint"
+> info "HTTP API sources in EU workspaces should use the events.eu1.segmentapis.com endpoint"
 > If you are located in the EU and use the `https://api.segment.io/v1/` endpoint, you might not see any errors, but your events will not appear in the Segment app. For more information about regional support, see the [Source Regional support](/docs/guides/regional-segment/#source-regional-support) documentation. 
 
 ## Headers
@@ -23,7 +23,7 @@ Choose between [writeKey authentication](#writeKey-authentication), [basic authe
 Authenticate to the Tracking API by sending your project's **Write Key** along with a request.
 The authentication writeKey should be sent as part of the body of the request. This will be encrypted over https.
 
-```
+```shell
   curl --location 'https://api.segment.io/v1/track' \
   --header 'Content-Type: application/json' \
   --data-raw '{
@@ -58,7 +58,7 @@ Include the access token in the Authorization header as a Bearer token along wit
 
 For example, to use the access token in the HTTP API Source, use `access_token` in the header and `write_key` in the payload. An example cURL request looks like: 
 
-```
+```shell
   curl --location 'https://api.segment.io/v1/track' \
   --header 'Content-Type: application/json' \
   --header 'Authorization: Bearer <access token>' \

src/getting-started/02-simple-install.md

@@ -82,7 +82,7 @@ That snippet loads Analytics.js onto the page _asynchronously_, so it won't affe
 <br>
 The [Identify](/docs/connections/spec/identify/) method tells Segment who the current user is. It includes a unique user ID and any optional traits you know about them. You can read more about it in the [Identify method reference](/docs/connections/sources/catalog/libraries/website/javascript#identify).
 <br><br>
-> info "You don't need to call `identify` for anonymous visitors to your site"
+> info "You don't need to call identify for anonymous visitors to your site"
 > Segment automatically assigns them an `anonymousId` so just calling `page` and `track` works without `identify`.
 <br>
 Here's an example of what a basic call to `identify` might look like:

src/protocols/starter.md

@@ -12,7 +12,7 @@ With Segment tracking plans you can choose from the most common Events, and crea
 
 This is a great way to get a head start on your tracking, and also to monitor events coming into your workspace as you implement your Segment tracking.
 
-### Starter tracking plan access
+## Starter tracking plan access
 
 Only Workspace Owners can set up or edit the starter tracking plan.
 

src/segment-app/iam/sso.md

@@ -102,7 +102,7 @@ Enter your domain and click "Add Domain." When you click verify, you're given tw
 To configure SSO for multiple workspaces, your admin must configure access to each workspace as a separate app in your identity provider. You are unable to use verified domain(s) across multiple workspaces and will encounter the following error if you add a domain that is already verified in another workspace:
 
 > warning ""
-> **Warning**: This domain has already been claimed.
+> This domain has already been claimed.
 
 After your administrator configures separate apps for each workspace in your IdP, the end-users can log in to the IdP and click on the relevant app for the workspace you are trying to access. This is also referred to as IdP-initiated SSO. 
 

src/unify/Traits/sql-traits.md

@@ -28,7 +28,7 @@ This unlocks some interesting possibilities to help you meet your business goals
 > info ""
 > Note that after you bring in data with SQL Traits, changing data types for fields may not be compatible with all destinations.
 
-### Example: cloud sources sync
+## Example: cloud sources sync
 
 SQL Traits allow you to import data from [object cloud sources](/docs/connections/sources/#object-cloud-sources) like Salesforce, Stripe, Zendesk, Hubspot, Marketo, Intercom, and more. For example, bring in Salesforce Leads or Accounts, Zendesk ticket behavior, or Stripe LTV calculations.