Merge pull request #8080 from lopenchi/develop

pwseg · web-flow · commit ba6c9e4a8689 · 2025-10-24T09:28:35.000-07:00
Small fixes - Batch 3.1
diff --git a/src/_includes/content/connection-modes-intro.md b/src/_includes/content/connection-modes-intro.md
@@ -6,7 +6,7 @@ Segment's web source (Analytics.js), and native client-side libraries (iOS, Andr
     <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.
+      <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>
diff --git a/src/_includes/content/dev-center-note.md b/src/_includes/content/dev-center-note.md
@@ -1 +1,7 @@
-<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>
+<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>
diff --git a/src/_includes/content/reset-mobile.md b/src/_includes/content/reset-mobile.md
@@ -1,2 +1,6 @@
-> info ""
-> The reset method doesn't clear the `userId` from connected client-side integrations. If you want to clear the `userId` from connected client-side destination plugins, you'll need to call the equivalent reset method for that library.
+<div class="premonition info">
+  <div class="fa fa-info-circle"></div>
+  <div class="content">
+    <p>The reset method doesn't clear the `userId` from connected client-side integrations. If you want to clear the `userId` from connected client-side destination plugins, you'll need to call the equivalent reset method for that library.</p>
+  </div>
+</div>
diff --git a/src/_includes/content/syntax-note.md b/src/_includes/content/syntax-note.md
@@ -1,2 +1,6 @@
-> info ""
-> Based on the library you use, the syntax in the examples might be different. You can find library-specific documentation on the [Sources Overview](/docs/connections/sources/) page.
+<div class="premonition info">
+  <div class="fa fa-info-circle"></div>
+  <div class="content">
+    <p markdown=1>Based on the library you use, the syntax in the examples might be different. You can find library-specific documentation on the [Sources Overview](/docs/connections/sources/) page.</p>
+  </div>
+</div>
diff --git a/src/_includes/content/tracking-api-limit.md b/src/_includes/content/tracking-api-limit.md
@@ -1,3 +1,7 @@
-> warning "HTTP Tracking API limits"
->
-> Segment's HTTP Tracking API accepts batch requests up to **500 KB**. To avoid errors in event creation, ensure that individual event payload sizes remain below **32 KB**.
+<div class="premonition warning">
+  <div class="fa fa-exclamation-circle"></div>
+  <div class="content">
+    <p class="header">HTTP Tracking API limits</p>
+    <p>Segment's HTTP Tracking API accepts batch requests up to <strong>500 KB</strong>. To avoid errors in event creation, ensure that individual event payload sizes remain below <strong>32 KB</strong>.</p>
+  </div>
+</div>
diff --git a/src/connections/sources/catalog/libraries/server/http-api/index.md b/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>' \
diff --git a/src/engage/content/sms/template.md b/src/engage/content/sms/template.md
@@ -46,9 +46,9 @@ Send a test SMS message before you include it as a step in your Journey.
 
 1. After you build your SMS template, click **Test SMS**.
 2. If your template has profile traits, enter a trait value for the test SMS. This ensures that your merge tags work as expected.
-- Empty fields show the default value that you've assigned. For example, `loyal customer` would be the default for the following merge tag: {% raw %}```{{profile.traits.first_name | default: "loyal customer"}}```{% endraw %}. If there's no default value, the field will be blank.
+   - Empty fields show the default value that you've assigned. For example, `loyal customer` would be the default for the following merge tag: {% raw %}```{{profile.traits.first_name | default: "loyal customer"}}```{% endraw %}. If there's no default value, the field will be blank.
 3. Enter recipient phone numbers for the test message.
-- Profiles that you send test messages to must have a userId in Segment.
+   - Profiles that you send test messages to must have a userId in Segment.
 4. Click **Send test SMS**.
 
 
diff --git a/src/engage/index.md b/src/engage/index.md
@@ -27,4 +27,4 @@ Create lists of users or accounts that match specific criteria. For example, aft
 #### Sync audiences to downstream tools
 Once you create your Computed Traits and Audiences, Engage sends them to your Segment Destinations in just a few clicks. You can use these Traits and Audiences to personalize messages across channels, optimize ad spend, and improve targeting. You can also use the [Profile API](/docs/unify/profile-api) to build in-app and onsite personalization. Learn more about [using Engage data](/docs/engage/using-engage-data/) and the [Profile API](/docs/unify/profile-api).
 
-{% include components/reference-button.html href="https://segment.com/customers/drift/" icon="personas.svg" title="Personalizing marketing campaigns" description="Marketing teams use Engage to run real-time multi-channel marketing campaigns based off specific user attributes they've computed in Engage. Read about how Drift used Engage to increase prospect engagement by 150% in two months." %}
+{% include components/reference-button.html href="https://segment.com/customers/drift/" icon="personas.svg" title="Personalizing marketing campaigns" description="Marketing teams use Engage to run real-time multi-channel marketing campaigns based off specific user attributes they've computed in Engage. Read about how Drift used Engage to increase prospect engagement by 150% in two months." %}
diff --git a/src/getting-started/02-simple-install.md b/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:
diff --git a/src/getting-started/index.md b/src/getting-started/index.md
@@ -8,7 +8,4 @@ With Segment, you can track [first-party customer data](https://segment.com/lear
 
 Segment simplifies the process of collecting data and connecting new tools, allowing you to spend more time using your data and less time trying to collect, process, and share it with business tools. In most cases, you won't even need to touch your tracking code to connect to new tools. 
 
-<div class="double">
-  <div></div>
-  {% include components/reference-button.html newtab="false" href="/getting-started/01-what-is-segment/" icon="symbols/arrow-right.svg" title="Ready to get started?" description="Let's walk through the steps to get up and running on Segment. Let's go!" variant="related" subtitle="next"  %}
-</div>
+{% include components/reference-button.html newtab="false" href="/getting-started/01-what-is-segment/" icon="symbols/arrow-right.svg" title="Ready to get started?" description="Let's walk through the steps to get up and running on Segment. Let's go!" variant="related" subtitle="next"  %}
diff --git a/src/protocols/apis-and-extensions/anomaly_detection.md b/src/protocols/apis-and-extensions/anomaly_detection.md
@@ -52,7 +52,8 @@ After you've enabled [Violation Forwarding](/docs/protocols/validate/forward-vio
 You can copy and paste the example snippet below into the Event Template field to format the Slack message with the event name, violation description and source name. You can customize this message however you want, including adding @ mentions, and any of the [properties included in the Violation Generated event](/docs/protocols/validate/forward-violations/).
 
 ```
-Source: {% raw %}`{{properties.sourceName}}` \nEvent: `{{properties.eventName}}` \nViolation: `{{properties.violationDescription}}`{% endraw %}
+Source: {% raw %}`{{properties.sourceName}}` \nEvent: `{{properties.eventName}}` \nViolation: `{{properties.violationDescription}}`
+{% endraw %}
 ```
 When you're done, it'll look like the screenshot below.
 
diff --git a/src/protocols/starter.md b/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.
 
diff --git a/src/segment-app/iam/sso.md b/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. 
 
diff --git a/src/unify/Traits/sql-traits.md b/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.
 
