Merge pull request #460 from segmentio/repo-sync

repo sync

Author: bot-docsteam

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

@@ -5,7 +5,7 @@ cmode-override: true
 hide-personas-partial: true
 id: 54521fd825e721e32a72eec8
 ---
-[Klaviyo](https://www.klaviyo.com/features/overview){:target="_blank"} is a powerful email platform focused on ecommerce that helps companies make more money. It supports segmentation based on category and event triggers like product bought, page viewed, email engagement, or amount spent.
+[Klaviyo](https://www.klaviyo.com){:target="_blank"} is a powerful email platform focused on ecommerce that helps companies make more money. It supports segmentation based on category and event triggers like product bought, page viewed, email engagement, or amount spent.
 
 It measures opens, clicks, revenue generated, breakdown of generated revenue based on custom attributes (like campaign type or amount gained per recipient), and provides trend reports, cohort analysis, and subscriber growth
 
@@ -213,7 +213,7 @@ analytics.track({
 
 ##### Send placed order events as order completed
 
-Enable this setting if you'd like to send `Order Completed` events as is rather than changing the event name to `Placed Order` on the server side (client side always sends `Order Completed`). Segment recommendeds that you keep this setting enabled so that both client- and server-side Klaviyo integrations send the same event for `Order Completed`. Klaviyo does not treat the event names differently in their backend feature wise. This option was introduced to bridge the existing disparity between Segment client- and server-side integrations regarding how this event name is sent without forcibly breaking the current behavior.
+Enable this setting if you'd like to send `Order Completed` events as is rather than changing the event name to `Placed Order` on the server side (client side always sends `Order Completed`). Segment recommends that you keep this setting enabled so that both client- and server-side Klaviyo integrations send the same event for `Order Completed`. Klaviyo does not treat the event names differently in their backend feature wise. This option was introduced to bridge the existing disparity between Segment client- and server-side integrations regarding how this event name is sent without forcibly breaking the current behavior.
 
 ## Personas
 

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

@@ -65,17 +65,15 @@ Windsor **requires** a **`userId`** and **`email`** for most integrations to wor
 
 Segment sends Identify calls to Windsor to create new users and their properties. You can find all your users on the [Users Page](https://app.windsor.io/people)
 
-### Best Practices
+### Best practices
 
-We recommend that you make an Identify call frequently from your app. As a general guide, call `identify`:
+Segment recommends that you make an Identify call frequently from your app. As a general guide, call `identify`:
 
 - On sign up
 - On every login (preferably on the device and server)
 - Every time a core user property changes (name, email, avatar or phone number)
 - On loading any pages that are only accessible by a logged in user
 
-You can find [additional best practices on using Identify with Windsor here](https://docs.windsor.io/docs/analytics#identify).
-
 
 ## Track
 
@@ -87,7 +85,7 @@ analytics.track('Login Button Clicked')
 
 Segment sends Track calls to Windsor as tracked events for each [user](https://app.windsor.io/people), and as events that appear on the Windsor [feed](https://app.windsor.io/feed).
 
-To get the best experience with Windsor, we recommend that you follow the Segment's specs for your industry or application .
+To get the best experience with Windsor, Segment recommends that you follow the Segment's specs for your industry or application .
 
 - [Mobile App](/docs/connections/spec/mobile/)
 - [E-Commerce](/docs/connections/spec/ecommerce/v2/)