make requested updates

forstisabella · forstisabella · commit 1291478bb87a · 2024-06-11T17:01:50.000-04:00
diff --git a/src/privacy/consent-management/consent-in-segment-connections.md b/src/privacy/consent-management/consent-in-segment-connections.md
@@ -27,7 +27,7 @@ If your sources also contain the integrations object, Segment will look at the c
 Segment requires every event from all of your sources to include the end user consent preferences, captured by your CMP or your application logic, in the form of the **consent object**. The consent object is a JSON object nestled inside of the [context object](/docs/connections/spec/common/#context) with the following format:
 
 > success ""
-> The JSON keys in the consent object should represent the `categoryId` for each consent column. 
+> The JSON keys in the consent object should represent the `categoryId` for each consent category. 
 
 ```json
 {

Original file line number	Diff line number	Diff line change
`@@ -27,7 +27,7 @@ If your sources also contain the integrations object, Segment will look at the c`
`27`	`27`	`Segment requires every event from all of your sources to include the end user consent preferences, captured by your CMP or your application logic, in the form of the consent object. The consent object is a JSON object nestled inside of the [context object](/docs/connections/spec/common/#context) with the following format:`
`28`	`28`
`29`	`29`	`> success ""`
`30`		-> The JSON keys in the consent object should represent the `categoryId` for each consent column.
	`30`	+> The JSON keys in the consent object should represent the `categoryId` for each consent category.
`31`	`31`
`32`	`32`	```json
`33`	`33`	`{`