changes

Author: Paul Yoo

src/connections/destinations/catalog/launchdarkly-subscription/index.md

@@ -1,5 +1,5 @@
 ---
-title: LaunchDarkly-subscription Destination
+title: LaunchDarkly Events Destination
 rewrite: true
 ---
 LaunchDarkly is a feature management platform that empowers development teams to safely deliver and control software through feature flags.
@@ -21,13 +21,16 @@ This destination is maintained by LaunchDarkly. For any issues with the destinat
 ## Track
 If you aren't familiar with the Segment Spec,  take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like:
 
-```javascript
-analytics.track('Order Completed',
-    {
-    value: 99.84,
-    type: "expedited"
-    }
-)
+```json
+{
+  "anonymousId": "23adfd82-aa0f-45a7-a756-24f2a7a4c8955",
+  "type": "track",
+  "properties": {
+    "value": 99.84,
+  },
+  "userId": "test-user-s6dndc",
+  "event": "Order Completed"
+}
 ```
 
 LaunchDarkly ingests that call as:
@@ -41,16 +44,15 @@ LaunchDarkly ingests that call as:
   "metricValue": 99.84,
   "data": {
     "value": 99.84,
-    "type": "expedited"
   }
 }
 ```
 
+> note ""
+> **Note**: The LaunchDarkly Metric must be actively recording and have a Feature Flag attached for Segment events to appear in your LaunchDarkly Project.
+
 Segment sends Track calls to LaunchDarkly as a `track` event. It appears on your [Debugger page](https://app.launchdarkly.com/default/production/debugger/goals).
 
 `track` events map to a Metric if the Segment event name exactly matches the Name of an active LaunchDarkly experiment metric.
 
 The `userKey` field maps to the `userId` field; if there is no `userId` field, LaunchDarkly uses `anonymousId` field for the `userKey` field.
-
-> note ""
-> **Note**: The LaunchDarkly Metric must be actively recording and have a Feature Flag attached.