Update warehouses.md - add section about the users table

Added a section about the user table - moved information from FAQ and added a note about sync behavior.

Author: Olesia

src/engage/warehouses.md

@@ -129,6 +129,12 @@ Similar to track calls in Connections, Engage track calls appear in your warehou
 | ------- | ---------------------- | ---------------------- |
 | u123    | 450.00                 | total_revenue_180_days |
 
+## Users table
+
+There are a couple of nuances to keep in mind when it comes to the users table. This table is an aggregate view based on the `user_id` field. This means that anonymous profiles with just an `anonymous_id` identifier aren't included in this view. You can still view identify calls for anonymous audiences and computed traits in the `identifies` table. 
+
+Users table will be synced as soon as the warehouse is connected as a destination in Engage, if you have previously created Engage computations. As a result, the table might contain the data from computations not directly connected to the warehouse.
+
 ## Sync frequency
 
 Although Engage can compute audiences and traits in real-time, these calculations are subject to the sync schedule allowed by your warehouses plan, which is usually hourly. You can check the warehouse sync history to see details about past and upcoming syncs. When you look at the sync schedule, sources with the `engage_` prefix sync data from Engage.
@@ -140,10 +146,6 @@ Although Engage can compute audiences and traits in real-time, these calculation
 
 Yes. You can use [Warehouses Selective Sync](/docs/connections/storage/warehouses/faq/#can-i-control-what-data-is-sent-to-my-warehouse) to manage which traits, audiences, and tables get synced from Engage.
 
-### Why are some users missing from the `users` table?
-
-The users table is an aggregate view based on the `user_id` field. This means that anonymous profiles with just an `anonymous_id` identifier aren't included in this view. You can still view identify calls for anonymous audiences and computed traits in the `identifies` table.
-
 ### Why are there multiple schemas prefixed with `engage_` in my warehouse when I only have one space?
 
 Segment currently can only connect a source to one instance of each destination, for example, one source cannot send to two different Amplitude instances. To get around this restriction, Engage creates multiple sources to send events to the destinations connected to your space.