style guide clean up

Author: sade-wusi

src/connections/destinations/catalog/matomo/index.md

@@ -7,34 +7,31 @@ id: 54521fda25e721e32a72eee7
 [Matomo](https://matomo.org/){:target="_blank"}, formerly Piwik, is the leading open source web analytics platform that gives you valuable insights into your website's visitors, your marketing campaigns and much more, so you can optimize your strategy and online experience of your visitors. 
 
 Segment’s Matomo destination code is open-source and can be viewed on GitHub:
-- [Javascript](https://github.com/segmentio/analytics.js-integrations/blob/master/integrations/piwik/lib/index.js){:target="_blank"}
-
-## Getting Started
-
+- [Javascript](https://github.com/segmentio/analytics.js-integrations/blob/master/integrations/piwik/lib/index.js){:target="_blank"}.
 
+## Getting started
 
 1. From the Segment web app, click **Catalog**.
-2. Search for "Matomo" in the Catalog, select it, and choose which of your sources to connect the destination to. Note the source must be sending events using our JavaScript library Analytics.js.
+2. Search for "Matomo" in the Catalog, select it, and choose which of your sources to connect the destination to. Note the source must be sending events using the Segment JavaScript library Analytics.js.
 3. In the destination settings, enter your Site ID. You can find your Site ID in your Matomo snippet.
-4. In the destination settings, enter your Server URL. You can find your Server URL in your snippet, we will append /matomo.php to the URL automatically.
-  5. When you enable Matomo in your Segment settings, Segment's CDN is updated within 45 minutes. Once that happens, Segment asynchronously loads `matomo.js` on your page whenever it is loaded. This means you should remove Matomo's snippet from your page.
+4. In the destination settings, enter your Server URL. You can find your Server URL in your snippet. Segment automatically appends /matomo.php to the URL.
+5. When you enable Matomo in your Segment settings, Segment's CDN is updated within 45 minutes. Once that happens, Segment asynchronously loads `matomo.js` on your page whenever it is loaded. This means you should remove Matomo's snippet from your page.
 
 ## Page
 If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
 
 ```js
 analytics.page();
 ```
-
-Our Page method triggers a call to Matomo's `trackPageView` method.
+The Page method triggers a call to Matomo's `trackPageView` method.
 
 ## Identify
 If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
 
 ```js
 analytics.identify('97980cfea0068');
 ```
-Our Identify method triggers a call to Matomo's `setUserId` method and will send the `userId` to Matomo.
+The Identify method triggers a call to Matomo's `setUserId` method and will send the `userId` to Matomo.
 
 ## Track
 If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
@@ -43,9 +40,9 @@ If you're not familiar with the Segment Specs, take a look to understand what th
 analytics.track('Logged In');
 ```
 
-We'll record a Matomo event whenever you make a `track` call.
+Segement records a Matomo event whenever you make a `track` call.
 
-For the example above, these event attributes are sent to Matomo:
+In the example, these event attributes are sent to Matomo:
 
 <table>
   <tr>
@@ -58,7 +55,7 @@ For the example above, these event attributes are sent to Matomo:
   </tr>
 </table>
 
-Find below another Track example, this time with all the available Matomo event parameters:
+See the following Track example, this time with all the available Matomo event parameters:
 
 ```js
 analytics.track('Created Account', {
@@ -68,7 +65,7 @@ analytics.track('Created Account', {
 })
 ```
 
-That call will create a Matomo Event with these attributes:
+That call creates a Matomo Event with these attributes:
 
 <table>
   <tr>
@@ -89,17 +86,18 @@ That call will create a Matomo Event with these attributes:
   </tr>
 </table>
 
-For **Event Value** you can name the event property `value` or `revenue`. We'll look for `value` first, then fall back to `revenue`.
+For **Event Value**, you can name the event property `value` or `revenue`. Segment looks for `value` first, then fall back to `revenue`.
 
-## Best Practices
+## Best practices
 
-Matomo allows you to set [custom variables](http://matomo.org/docs/custom-variables/){:target="_blank"} with your pageviews and events. With Segment, you can set page-scoped custom variables with any `track` call you make with analytics.js.
+Matomo lets you set [custom variables](http://matomo.org/docs/custom-variables/){:target="_blank"} with your pageviews and events. With Segment, you can set page-scoped custom variables with any Track call you make with analytics.js.
 
-Since these custom variables must be mapped to an index you define, which can change from call to call, the only way we can support these custom variables with full flexibility is to allow you to pass your map in the `context.Matomo.customVars` dictionary of each call.
+Since these custom variables must be mapped to an index you define, which can change from call to call, the only way that Segment can support these custom variables with full flexibility is to allow you to pass your map in the `context.Matomo.customVars` dictionary of each call.
 
-To take advantage of this feature, your `track` calls should look like this:
+To take advantage of this feature, your Track calls should look like this:
 
-> **Note** The destination's name is still "piwik" in the JSON for these calls.
+> info ""
+> The destination's name is still "piwik" in the JSON for these calls.
 
 ```js
 analytics.track('event', {
@@ -117,6 +115,6 @@ analytics.track('event', {
 ```
 
 ### Goals
-If you want to flag specific events as Matomo Goals you can do so by mapping those events in your Segment Source Destinations page under Matomo Settings.
+If you want to flag specific events as Matomo Goals, you can do so by mapping those events in your Segment Source Destinations page under Matomo Settings.
 
-Fill in the event on the left and the Goal ID from Matomo on the right. Then every time the event happens we'll fire Matomo's `trackGoal` method.
+Fill in the event on the left and the Goal ID from Matomo on the right. Then every time the event happens Segment fires Matomo's `trackGoal` method.