Skip to content

Commit a0116c8

Browse files
Merge pull request #7938 from segmentio/DOC-1186
Warehouse Schema and Protocols Overview review
2 parents 94eaa48 + ccc6012 commit a0116c8

File tree

3 files changed

+72
-79
lines changed

3 files changed

+72
-79
lines changed

src/_data/protocols.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ sections:
66
description: "Good data quality starts with a well thought out Tracking Plan. With Protocols, you can define your events and corresponding properties in a Tracking Plan. This tracking plan becomes a central source of truth for product, engineering, analytics, and business teams."
77
path: /protocols/tracking-plan/best-practices/
88
- name: 2. Validate data quality with violations
9-
description: "With your tracking plan living in Segment, you can apply it to 1 or more data sources. Any event or property that does not match the tracking plan will generate a violation. Violations are displayed in aggregated form to spot trends, and detailed form to help you quickly find and resolve discrepancies."
9+
description: "With your tracking plan living in Segment, you can apply it to one or more data sources. Any event or property that does not match the tracking plan will generate a violation. Violations are displayed in aggregated form to spot trends, and detailed form to help you quickly find and resolve discrepancies."
1010
path: /protocols/validate/connect-sources/
1111
- name: 3. Enforce data standards with controls
1212
description: "To maintain a high degree of quality over time, we offer strict controls to block non-conforming events. Blocked events can be forwarded to a separate quarantined Segment source for analysis and review."
1313
path: /protocols/enforce/schema-configuration/
1414
- name: 4. Resolve data issues with transformations
15-
description: "Even the most exacting data collection processes are subject to human error and organizational complexity. Transformations can be applied from within Protocols to change event and property names without touching code."
15+
description: "Even the most exacting data collection processes are subject to human error and organizational complexity. Apply Transformations within Protocols to change event and property names without touching code."
1616
path: /protocols/transform/
1717

1818
- section_title: Learn more
@@ -25,5 +25,5 @@ sections:
2525
description: "Create a Tracking Plan to standardize your collected data."
2626
path: /protocols/tracking-plan/create/
2727
- name: FAQ
28-
description: "Get answers to Protocols questions that come up the most."
28+
description: "Get answers to frequent Protocols questions."
2929
path: /protocols/faq/

0 commit comments

Comments
 (0)