Update src/connections/destinations/catalog/actions-optimizely-data-platform/index.md

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

Author: Romani-Ramzi

src/connections/destinations/catalog/actions-optimizely-data-platform/index.md

@@ -33,20 +33,29 @@ After you set up your Optimizely Data Platform destination, Segment syncs your c
 
 After you enable the Optimizely Data Platform destination, you must map the events that you want Twilio Segment to send to ODP.
 
-In Twilio Segment, on the **Mappings** tab of the Optimizely Data Platform destination, there is a list of pre-built mappings that you can enable or disable. For example, if you enable the **Email Opened** mapping, each email opened event syncs from Twilio Segment to ODP going forward.
+In Twilio Segment, on the **Mappings** tab of the Optimizely Data Platform destination, Segment displays a list of pre-built mappings that you can enable or disable. For example, if you enabled the **Email Opened** mapping, each email opened event Segment ingested after you enabled the mapping would sync to ODP.
 
 If you want to map an event that is not listed:
 1. Click **New Mapping > Custom Event**.
-2. (Optional) Enter a descriptive name for the event.
-3. In section 1, select the event that you want to send to ODP.
-4. In section 2, click **Load Test Event from Source**. This generates the raw data for the selected event and populates the mappings in section 3.
-5. In section 3, the ID and timestamp field mappings auto-populate, but you can edit them as desired. Ensure you select the event type and, optionally, the event action. For example, if you are configuring a custom event to track button clicks, select _button_ for the event type, and _click_ for the event action.
-   > 📘 Note
-   > 
-   > In ODP, each event requires an ID, timestamp, and event type. The event action is optional. See [Events](https://docs.developers.optimizely.com/optimizely-data-platform/docs/thebasics-events) in the ODP documentation.
-6. (Optional) To ensure the custom event is configured correctly, in section 4, click **Send test event to destination**.
-7. Click Save.
-8. Toggle the **Status** to **Enabled** for the custom event you created.
+2. _(Optional)_: Enter a descriptive name for the event.
+3. Select the event that you want to send to ODP.
+4. Click **Load Test Event from Source**. This generates the raw data for the selected event and populates your mappings. The ID and timestamp field mappings auto-populate, but you can edit them as desired.
+5. Select the event type and, optionally, the event action. For example, if you are configuring a custom event to track button clicks, select _button_ for the event type and _click_ for the event action.
+
+> info "Required fields"
+> In ODP, each event requires an ID, timestamp, and event type. The event action is optional. See ODP's [Events](https://docs.developers.optimizely.com/optimizely-data-platform/docs/thebasics-events) documentation for more details.
+
+<ol style="counter-reset: none;">
+  <li value="6" markdown=1>
+  _(Optional)_: To ensure the custom event is configured correctly, click **Send test event to destination**.
+  </li>
+  <li value="7" markdown=1>
+  Click **Save**.
+  </li>
+  <li value="8" markdown=1>
+  Toggle your custom event's status to **Enabled**.
+  </li>
+</ol>	
 
 The event data sends from Twilio Segment to ODP starting after you enable the mapping in the destination. It does not retroactively send events that occurred prior to configuring the integration and enabling the mappings.