Merge pull request #3113 from mcough2/patch-2

Added some clarity to the initial setup section

Author: markzegarelli

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

@@ -14,10 +14,10 @@ Metronome also enables product-led growth with a consistent source of truth for
 ## Getting Started
 
 1. From the Segment web app, click **Catalog**, then click **Destinations**
-2. Search for **Metronome (Actions)** within the Destinations Catalog and select **Metronome (Actions)**
+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).
+4. Select the source you’d like to connect to and give the destination a name (for example, `Metronome Instance #1`).
+5. Enter your Metronome API Token on the **Settings** pane in the **API Token** box, and save changes.
 
 {% include components/actions-fields.html %}
 
@@ -41,4 +41,4 @@ Metronome (Actions) provides the following benefits:
 
 - **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.
+- **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.