Skip to content

Commit 92dad44

Browse files
committed
removed "you can"
1 parent 5b05f60 commit 92dad44

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/protocols/tracking-plan/create.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ The Tracking Plan editor is organized as a spreadsheet to help you add new even
4141
| Permitted Values | Enter simple regular expressions to validate property values. This works when a property data type is set to `string`. For example, you can add pipe delimited strings to the regex column to generate violations when a property value does not match fall, winter or spring. |
4242

4343
> info ""
44-
> The Status, Data Type, and Permitted Values columns appear as you add a track call property.
44+
> The Status, Data Type, and Permitted Values columns appear as you add a track call property.
4545
4646
### Add a new track call
4747
To add a new track call:
@@ -78,7 +78,7 @@ Protocols Tracking Plans use [JSON Schemas](https://json-schema.org/) to validat
7878
You can edit the JSON schema for each track event listed in the tracking plan, and a common JSON schema definition that applies across all events.
7979

8080
#### Track event JSON schema
81-
Each track event in the tracking plan has a separate JSON schema definition to validate the properties in that event. To edit, you can click on the overflow menu next to each event row in the Tracking Plan.
81+
Each track event in the tracking plan has a separate JSON schema definition to validate the properties in that event. To edit, click on the overflow menu next to each event row in the Tracking Plan.
8282

8383
> info ""
8484
> Advanced edits to the JSON schema are not visible in the Tracking Plan and make it harder for other users to understand the validation logic. Be sure to communicate to any other Protocols users that you are making changes in the validation logic.

0 commit comments

Comments
 (0)