Merge pull request #8018 from lopenchi/develop

Small fixes - Batch 2.4 - Part 2

Author: stayseesong

src/connections/sources/catalog/cloud-apps/surveysparrow/index.md

@@ -42,7 +42,7 @@ The table below lists the properties included in the events listed above.
 | Property Name   | Description               |
 | --------------- | ------------------------- |
 | `event`         | Type of the event          |
-| `survey`        | Will hold all the properties data  including surveys, answers,channel,expressions,variables        |
+| `survey`        | Will hold all the properties data including surveys, answers,channel,expressions,variables        |
 | `survey`        | Meta details about the survey          |
 | `contact`       | Contact which has created the response         |
 | `expressions`   | Computed expressions data of the survey         |

src/connections/sources/catalog/cloud-apps/voucherify/index.md

@@ -41,7 +41,7 @@ Below are the events that Voucherify sends to Segment. These events appear as ta
 | Event                                  | Description                                                                                                                                    | Fields                                                                                                                        |
 |----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
 | Customer Redemption Succeeded          | Triggered when a redemption is successfully completed by a customer (successful use of a voucher to receive a discount or other reward).       | order (object), promotion_tier (object), redemption (object), voucher (object), holder (object)                               |
-| Customer Redemption Failed             | Triggered  when a redemption attempt fails due to an issue with the voucher or customer.                                                       | order (object), promotion_tier (object), redemption (object), voucher (object), holder (object)                               |
+| Customer Redemption Failed             | Triggered when a redemption attempt fails due to an issue with the voucher or customer.                                                        | order (object), promotion_tier (object), redemption (object), voucher (object), holder (object)                               |
 | Customer Redemption Rollback Succeeded | Triggered when a redemption is successfully rolled back, which means removal of the voucher and reversal of any associated discount or reward. | order (object), promotion_tier (object), redemption (object), redemption_rollback (object), voucher (object), holder (object) |
 | Customer Redemption Rollback Failed    | Triggered when an attempt to roll back the redemption fails.                                                                                   | order (object), promotion_tier (object), redemption (object), redemption_rollback (object), voucher (object), holder (object) |
 
@@ -51,8 +51,8 @@ Below are the events that Voucherify sends to Segment. These events appear as ta
 |---------------------------------------|---------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|
 | Customer Reward Redemptions Created   | Triggered when a customer redeems a reward in Voucherify account.                           | reward (object), reward_assignment (object), reward_redemption (object), voucher (object), source (object), holder (object), balance |
 | Customer Reward Redemptions Completed | Triggered when a customer's redemption request is completed (customer received the reward). | reward (object), reward_assignment (object), reward_redemption (object), voucher (object), source (object), holder (object), balance |
-| Customer Rewarded                     | Triggered when a customer is rewarded with a main reward.                                   | redemption (object),  referral_tier (object), reward (object), voucher (object), holder (object), balance                            |
-| Customer Rewarded Loyalty Points      | Triggered when a customer is rewarded with loyalty points.                                  | earning_rule (object),  loyalty_tier (object), order (object), voucher (object), holder (object), balance                            |
+| Customer Rewarded                     | Triggered when a customer is rewarded with a main reward.                                   | redemption (object), referral_tier (object), reward (object), voucher (object), holder (object), balance                             |
+| Customer Rewarded Loyalty Points      | Triggered when a customer is rewarded with loyalty points.                                  | earning_rule (object), loyalty_tier (object), order (object), voucher (object), holder (object), balance                             |
 
 ### Validation events
 

src/privacy/consent-management/consent-in-retl.md

@@ -138,7 +138,7 @@ You can validate that you successfully created your consent mapping in Segment C
 
 Segment automatically adds the [consent object](/docs/privacy/consent-management/consent-in-segment-connections/#consent-object) to every event that's routed downstream to your Segment Connections destination. [Consent enforcement in Connections](/docs/privacy/consent-management/consent-in-segment-connections/) validates that only consenting data flows downstream to any classic Segment destinations connected to your Segment Connections instance.
 
-Open the Source Debugger for your Reverse ETL source and confirm that the [consent object](/docs/privacy/consent-management/consent-in-segment-connections/#consent-object) appears on every event and that the consent object has the categories you mapped in [Step 2: Identify consent columns](#step-2-identify-consent-columns).
+Open the Source Debugger for your Reverse ETL source and confirm that the [consent object](/docs/privacy/consent-management/consent-in-segment-connections/#consent-object) appears on every event and that the consent object has the categories you mapped in [Step 3: Identify consent columns](#step-3-identify-consent-columns).
 
 ### Segment Profiles
 Open the [Profile Explorer](/docs/unify/#profile-explorer) and verify that your profiles contain the [Segment Consent Preference Updated](/docs/privacy/consent-management/consent-in-unify/#segment-consent-preference-updated-event) event.

src/privacy/consent-management/consent-in-unify.md

@@ -96,7 +96,7 @@ If you're using Consent Management and Profiles, you shouldn't give your custome
 
 ## Consent preference conflicts
 
-When collecting end user consent, you can occasionally capture multiple consent preferences linked to the same user, for example, from a user's cell phone browser and the web browser on their laptop (called a [device-level conflict](#device-level-conflict)) or when two distinct Unify profiles are merged together (called a [profile-level conflict](#profile-level-conflict)). 
+When collecting end user consent, you can occasionally capture multiple consent preferences linked to the same user, for example, from a user's cell phone browser and the web browser on their laptop (called a [device-level conflict](#device-level-conflicts)) or when two distinct Unify profiles are merged together (called a [profile-level conflict](#profile-level-conflict)). 
 
 
 ### Backfill consent preferences on your Profiles
@@ -107,7 +107,7 @@ If you want to use end-user consent coming directly from your single source of t
 
 ## Consent preference conflicts
 
-When collecting end user consent, you can occasionally capture multiple consent preferences linked to the same user. For example, you might collect consent from a user's cell phone browser and the web browser on their laptop (called a [device-level conflict](#device-level-conflict)) or merge two distinct Unify profiles together (called a [profile-level conflict](#profile-level-conflict)). 
+When collecting end user consent, you can occasionally capture multiple consent preferences linked to the same user. For example, you might collect consent from a user's cell phone browser and the web browser on their laptop (called a [device-level conflict](#device-level-conflicts)) or merge two distinct Unify profiles together (called a [profile-level conflict](#profile-level-conflict)). 
 
 
 ### Device-level conflicts
@@ -159,4 +159,4 @@ You can validate consent is present on the Profile by looking for the consent tr
 ## Troubleshooting consent preferences stored on the Profile
 
 ### If I have 2 sources connected to a Unify space and only 1 is set up to collect consent, which consent preferences does Segment record?
-Consent preferences collected in the [consent object](/docs/privacy/consent-management/consent-in-segment-connections/#consent-object) from the source are used to store consent on the Profile. Sources with no consent object do not impact what is stored on the Profile. If the source generates an empty consent object, Segment interprets this as an end-user failing to consent to any category. As a result, the consent preference will be updated to `false` for all consent categories.
+Consent preferences collected in the [consent object](/docs/privacy/consent-management/consent-in-segment-connections/#consent-object) from the source are used to store consent on the Profile. Sources with no consent object do not impact what is stored on the Profile. If the source generates an empty consent object, Segment interprets this as an end-user failing to consent to any category. As a result, the consent preference will be updated to `false` for all consent categories.