Merge pull request #3105 from segmentio/PR3100-fix

metronome fixes

Author: stayseesong

src/connections/destinations/catalog/actions-metronome/index.md

@@ -14,37 +14,34 @@ redirect_from:
 
 Metronome also enables product-led growth with a consistent source of truth for use and billing. Freely experiment with pricing and packaging and put iteration directly in the hands of your Product team.
 
-## Benefits of Metronome (Actions)
-Metronome (Actions) provides the following benefits:
-
-- **Streamlined Configuration**. Configure connection details on a per-event basis, rather than for the destination as a whole. 
-
-- **Easy access to data**. The event variables picker shows you all the available data from the event you use to test the Trigger. Variables are clearly labeled to ensure they stand out from other text and markup.
-
-- **Clear mapping of data** Actions-based destinations enable you to define the mapping between the data Segment receives from your source, and the data Segment sends to Metronome.
-
 ## Getting Started
 
-1. From the Segment web app, click **Catalog**, then click **Destinations** 
-2. Search for **Metronome** within the Destinations Catalog and select **Metronome (Actions)**
-3. Click **Configure Actions Metronome**.
+1. From the Segment web app, click **Catalog**, then click **Destinations**
+2. Search for **Metronome (Actions)** within the Destinations Catalog and select **Metronome (Actions)**
+3. Click **Configure Metronome (Actions)**.
 4. Select the source you’d like to connect to and give the destination a name
 5. Enter your Metronome API Token into the Segment Connection Settings UI (save changes).
 
 {% include components/actions-fields.html %}
 
+
 ## Mapping events to Metronome
 
-Map Segment events the [Metronome event format](https://docs.metronome.com/getting-usage-data-into-metronome/overview/){:target="_blank"}. Metronome requires the five fields listed below: 
+Map Segment events to the [Metronome event format](https://docs.metronome.com/getting-usage-data-into-metronome/overview/){:target="_blank"}. Metronome requires the five fields listed below: 
 
+Field | Type | Description
+----- | ---- | ------------
+`transaction_id` | (string) | The unique identifier for each event.
+`customer_id` | (string) | Represents which customer in Metronome the event applies to.
+`timestamp` | (string) | This is when the event happened in [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt){:target="_blank"}.
+`event_type` | (string) | This is the kind of event. For example, `page_view` or `cpu_used`.
+`properties` | (object) | The key/value pairs with details of the event.
 
-| Metronome field  | Type   | Description                                                                                                            |
-| ---------------- | ------ | ---------------------------------------------------------------------------------------------------------------------- |
-| `transaction_id` | String | A unique identifier for each event.                                                                                    |
-| `customer_id`    | String | The customer in Metronome to which the event applies                                                                   |
-| `timestamp`      | String | The time at which the event occurred, in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt){:target="_blank"} format. |
-| `event_type`     | String | The type of event passed. For example, `page_view` or `cpu_used`.                                                      |
-| `properties`     | Object | Key/value pairs with details of the event                                                                              |
+## Benefits of Metronome (Actions)
+Metronome (Actions) provides the following benefits:
 
+- **Streamlined Configuration**. Configure connection details on a per-event basis, rather than for the destination as a whole. 
 
+- **Easy access to data**. The event variables picker shows you all the available data from the event you use to test the Trigger. Variables are clearly labeled to ensure they stand out from other text and markup.
 
+- **Clear mapping of data** Actions-based destinations enable you to define the mapping between the data Segment receives from your source, and the data Segment sends to Metronome.