fix typo in getting started section and add more context

src/connections/destinations/catalog/ab-smartly/index.md

@@ -7,13 +7,11 @@ title: AB Smartly Destination
 
 This destination is maintained by A/B Smartly. For any issues with the destination, [contact A/B Smartly's Support](mailto:support@absmartly.com).
 
-> note "Note:"
-> The A/B Smartly Destination is in beta as the team is actively developing the destination. To join the beta program or to provide feedback to help improve A/B Smartly's Destination and documentation, [contact A/B Smartly's support team](mailto:support@absmartly.com).
 
 
 ## Implementation Prerequisite
 
-A/B Smartly works differently than other Segment destinations. Because A/B Smartly SDKs are used to modify and deliver experiences to users, you must be implement them at a point in your website or app that allows them to make visual modifications for users.
+A/B Smartly works differently than other Segment destinations. Because A/B Smartly SDKs are used to modify and deliver experiences to users, you must implement them at a point in your website or app that allows them to make visual modifications for users.
 
 A/B Smartly requires you to integrate the A/B Smartly SDKs natively, before the Segment snippet or implementation.
 
@@ -33,7 +31,7 @@ Segment provides specific implementation details for A/B Smartly in the sections
 6. If the integration requests for an Application name go to your A/B Smartly dashboard (`https://your-org-name.absmartly.com/application/create`) and create an Application named "Segment", or whatever you would like to call it. Use that name in the Application field of the integration settings.
 7. Add also your A/B Smartly Collector endpoint. It's the same endpoint that you are using in all your A/B Smartly SDKs.
 8. Enter the environment from your Environment list (`https://your-org-name.absmartly.com/environment/list`) that should receive your Segment data. Most likely it will be the production one.
-9. And finally a mapping of Segment Identities to A/B Smartly Units(`https://your-org-name.absmartly.com/unit/list`). You should map all your Segment identities that you would like to use in your A/B tests to the units that you already have in A/B Smartly. Check your unit list on A/B Smartly(`https://your-org-name.absmartly.com/unit/list`).
+9. And finally a mapping of Segment Identities to A/B Smartly Units(`https://your-org-name.absmartly.com/unit/list`). You should map all of your Segment identities that you would like to use in your A/B tests to the units that you already have in A/B Smartly. Users must map all the identity types, but not for the individual users. Map all of your ids in your Unit List(`https://your-org-name.absmartly.com/unit/list`).
 10. Optionally go to "Goal Mapping" and start adding the track calls that you would like to see showing up on A/B Smartly as goals. You only need to create a name mapping if the name of the goal on A/B Smartly's platform is different from the name of the track call in Segment.
 
 
@@ -46,7 +44,7 @@ Take a look at the [Page method documentation](/docs/connections/spec/page/) to
 analytics.page()
 ```
 
-Segment sends Page calls to A/B Smartly as a `pageview` goal. The goal name is`<page_name>_pageview`. The page name is lower-cased and any spaces or special characters are replaced with underscores. For example, a view of the "Home" page triggers the `home_pageview` goal. If the goal doesn't exist in the A/B Smartly web console, it is ignored. 
+Segment sends Page calls to A/B Smartly as a `pageview` goal. The goal name is`<page_name>_pageview`. The page name is lower-cased and any spaces or special characters are replaced with underscores. For example, a view of the "Home" page triggers the `home_pageview` goal. If the goal doesn't exist in the A/B Smartly web console, it is ignored.
 
 
 ## Screen