Apply suggestions from code review

Co-authored-by: pwseg <[email protected]>

Author: forstisabella

src/connections/destinations/catalog/actions-hubspot-cloud/index.md

@@ -36,7 +36,7 @@ HubSpot Cloud Mode (Actions) provides the following benefits over the classic Hu
 - **Support for custom behavioral events**. Send [custom behavioral events](https://developers.hubspot.com/docs/api/analytics/events){:target="_blank"} and event properties to HubSpot.
 - **Create records in custom objects**. Use your Segment events to create records in any standard or custom object in your HubSpot account.
 
-  > warning ""
+  > info ""
   > A HubSpot Enterprise Marketing Hub account is required to send Custom Behavioral Events.
 
 ## Getting started

src/connections/destinations/catalog/amazon-lambda/index.md

@@ -145,7 +145,7 @@ To create an IAM role:
 7. Copy and paste the following code into your trust relationship. You should replace `<your-source-id>` with either the Source ID of the attached Segment source (the default) or the External ID set in your AWS Lambda destination settings.
   * `arn:aws:iam::595280932656:role/customer-lambda-prod-destination-access` refers to Segment's AWS Account, and is what allows Segment's Destination to access the role to invoke your Lambda.
 
-> success ""
+> info ""
 > You can find your Source ID by navigating to **Settings > API Keys** from your Segment source homepage.
 
     ```json

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

@@ -46,9 +46,9 @@ When you send an Alias call to CleverTap, CleverTap updates the user's profile w
 
 ## Track
 
-When you `track` an event, Segment sends that event to CleverTap as a custom event. CleverTap requires `identify` traits such as `userId` or `email` to record and associate the Track event. Without these traits, the Track event does not appear in CleverTap.
+When you `track` an event, Segment sends that event to CleverTap as a custom event. CleverTap requires Identify traits like `userId` or `email` to record and associate the Track event. Without these traits, the Track event does not appear in CleverTap.
 
-CleverTap does not support arrays or nested objects for custom track event properties.
+CleverTap does not support arrays or nested objects for custom Track event properties.
 
 The default logic for the cloud mode connection to CleverTap will lower case and snake_case any event properties passed from Segment's servers to CleverTap. The device mode connection will not lower case or snake_case any event properties passed directly to CleverTap from the client.
 

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

@@ -107,7 +107,7 @@ To configure a custom dimension:
 After you map your dimensions, Segment checks the user traits and properties in [Identify](/docs/connections/spec/identify), [Track](/docs/connections/spec/track) and [Page](/docs/connections/spec/page) calls to see if you defined them as a dimension. If you have defined them in your mapping, Segment sends that dimension to Google Analytics.
 
 > success ""
-> Segment sends traits in [Identify](/docs/connections/spec/identify) calls that map to Custom Dimensions in Google Analytics when the next [Track](/docs/connections/spec/track) or [Page call](/docs/connections/spec/page) call triggers from the browser.
+> Segment sends traits in [Identify](/docs/connections/spec/identify) calls that map to Custom Dimensions in Google Analytics when the next [Track](/docs/connections/spec/track) or [Page](/docs/connections/spec/page) call triggers from the browser.
 
 Continuing the example above, you can set the **Gender** trait with the value of **Male**, which maps to `dimension 1`. Segment passes this value to Google Analytics with **Viewed History** [Track](/docs/connections/spec/track) calls.
 

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

@@ -488,7 +488,7 @@ For HTTPS Web Push to work, you need to host two files in the `root` directory o
 * `serviceworker.js`
 
 > info "Serviceworker file naming convention"
-> The name of the serviceworker file must be `serviceworker.js`. Please contact MoEngage support at [email protected] if you want to give your serviceworker file a different filename.
+> The name of the serviceworker file must be `serviceworker.js`. Please contact MoEngage support at [email protected] if you want to give your serviceworker file a different name.
 
 #### 2.b Add link to manifest in HTML (HTTPS)
 Add the following line in the <head> tag of your page.

src/connections/destinations/catalog/recombee-ai/index.md

@@ -11,9 +11,7 @@ versions:
     link: /docs/connections/destinations/catalog/actions-recombee
 ---
 
-<<<<<<< Updated upstream
 [Recombee](https://recombee.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} is a Recommender as a Service that can use your data to provide the most accurate recommendations of content or products for your users.
-=======
 Use this Segment destination to send your interaction data views, purchases, plays, etc.) to Recombee.
 
 This destination is maintained by Recombee. For any issues with the destination, [contact the Recombee Support team](mailto:[email protected]).

src/connections/sources/about-cloud-sources.md

@@ -18,7 +18,7 @@ Event Cloud Sources can export their data both into Segment warehouses, and into
 Object Cloud App Sources can export data and import it directly into a Segment warehouse. You *must* have a Segment warehouse enabled before you enable these. From the warehouse, you can analyze your data with SQL, use [Reverse ETL](/docs/connections/reverse-etl) to extract data, or use Engage SQL Traits to build audiences. Some examples of Object Cloud sources are Salesforce (account information), Zendesk (support cases), and Stripe (payments information).
 
 > info ""
-> You can send data from website, mobile, and server sources to a warehouse **or** to destinations. You can only send object cloud app source data can **only** go to warehouses.
+> You can send data from website, mobile, and server sources to a warehouse **or** to destinations. You can only send object cloud app source data to warehouses.
 
 
 ## How do cloud sources work?