Skip to content

Commit f951037

Browse files
Merge pull request #7340 from segmentio/Lfdelossantos-patch-1
Fix the wrong version of its/it's
2 parents 0792f20 + 3701b73 commit f951037

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/connections/storage/warehouses/schema.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ The table below describes the schema in Segment Warehouses:
132132
| `<source>.pages` | A table with your `page` method calls. This table includes the `properties` you record for pages as top-level columns, for example `<source>.pages.title`. |
133133
| `<source>.screens` | A table with your `screen` method calls. This table includes `properties` you record for screens as top-level columns, for example `<source>.screens.title`. |
134134
| `<source>.tracks` | A table with your `track` method calls. This table includes standardized properties that are all common to all events: `anonymous_id`, `context_*`, `event`, `event_text`, `received_at`, `sent_at`, and `user_id`. This is because every event that you send to Segment has different properties. For querying by the custom properties, use the `<source>.<event>` tables instead. |
135-
| `<source>.<event>` | For `track` calls, each event like `Signed Up` or `Order Completed` also has it's own table (for example. `initech.clocked_in`) with columns for each of the event's distinct `properties` (for example. `initech.clocked_in.time`). |
135+
| `<source>.<event>` | For `track` calls, each event like `Signed Up` or `Order Completed` also has its own table (for example. `initech.clocked_in`) with columns for each of the event's distinct `properties` (for example. `initech.clocked_in.time`). |
136136

137137

138138
## Identifies table

0 commit comments

Comments
 (0)