diff --git a/src/connections/storage/warehouses/schema.md b/src/connections/storage/warehouses/schema.md index e8eaeaafc7..4c35f49b72 100644 --- a/src/connections/storage/warehouses/schema.md +++ b/src/connections/storage/warehouses/schema.md @@ -132,7 +132,7 @@ The table below describes the schema in Segment Warehouses: | `.pages` | A table with your `page` method calls. This table includes the `properties` you record for pages as top-level columns, for example `.pages.title`. | | `.screens` | A table with your `screen` method calls. This table includes `properties` you record for screens as top-level columns, for example `.screens.title`. | | `.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 `.` tables instead. | -| `.` | 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`). | +| `.` | 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`). | ## Identifies table