Warehouse doc improvements

Author: forstisabella

src/_includes/content/how-a-sync-works.md

@@ -1,5 +1,5 @@
 When Segment loads data into your warehouse, each sync goes through the following steps:
-1. **Ping:** Segment servers connect to your warehouse. For Redshift warehouses, Segment also runs a query to determine how many slices a cluster has. <br/>Common reasons a sync would fail at this step include a blocked VPN/IP, a warehouse that isn't publicly available, and user permission/credential errors. 
+1. **Ping:** Segment servers connect to your warehouse. For Redshift warehouses, Segment also runs a query to determine how many slices a cluster has. 
 2. **Scan:** Segment finds new events in AWS S3 and updated objects in Dynamo. 
 3. **Download:** Segment pulls the events and objects into a staging area.
 4. **Process:** The raw Segment event and object archive files are transformed into database-specific formats. The [warehouse schema](/docs/connections/storage/warehouses/schema/) is also defined in this step. 

src/connections/storage/warehouses/faq.md

@@ -95,10 +95,31 @@ After a source is created, you can enable or disable a warehouse sync within the
 
 ## Can I be notified on warehouse sync failures?
 
+You will recieve notifications in the Segment app for warehouse sync failiures. 
+
+To view the notifications:
+1. 
+
 ## How is my data formatted in my warehouse?
 
+Data in your warehouse is formatted into **schemas**, which involve a detailed description of database elements (tables, views, indexes, synonyms, etc.) and the relationships that exist between elements. Segment's schemas use the following template: <br/>`<source>.<collection>.<property>`, for example, `segment-engineering.tracks.userId`, where Source refers to the source or project name (segment-engineering), collection refers to the event (tracks), and the property refers to the data being collected (userId). For more information about Warehouse Schemas, see the [Warehouse Schemas](/docs/connections/storage/warehouses/schema) page.
+
 ## If my syncs fail and get fixed, will I need to ask for a backfill?
 
-Yes! If your syncs fail, you will need to ask for a backfill, as this is a manual process. 
+If your syncs fail, you will need to reach out to [Segment Support](https://segment.com/help/) to ask for a backfill. Be sure to include the following information in your request: 
+- The warehouse that requires the backfill
+- What sources you need information from
+- The timeframe of data that requires a backfill
 
 ## Can I change my schema names once they've been created?
+
+If you'd like to change the name of your schema:
+
+1. Open the Segment app. 
+2. Select your warehouse from the Sources tab. 
+3. On the source's overview page, select "Settings."
+4. Under the "Enable Source" section, disable your warehouse and click "Save Changes."   
+5. Select the "SQL Settings" tab. 
+6. Update the "Schema Name" field with your intended schema name and click "Save Changes."
+7. On the source's overview page, select "Basic."
+8. Under the "Enable Source" section, disable your warehouse and click "Save Changes."

src/connections/storage/warehouses/schema.md

@@ -8,7 +8,7 @@ Schemas of warehouse data are organized into the following template: <br/>
 `<source>.<collection>.<property>` eg. `segment-engineering.tracks.userId`, where Source refers to the source or project name (segment-engineering), collection refers to the event (tracks), and the property refers to the data being collected (userId).
 
 > note "Data warehouse column creation"
-> **Note:** Segment creates tables for each of your custom events, and columns for each event's custom properties. Segment does not allow unbounded `event` or `property` spaces in your data. Instead of recording events like "Ordered Product 15", use a single property of "Product Number" or similar.
+> **Note:** Segment creates tables for each of your custom events in your warehouse, with columns for each event's custom properties. Segment does not allow unbounded `event` or `property` spaces in your data. Instead of recording events like "Ordered Product 15", use a single property of "Product Number" or similar.
 
 ## Warehouse tables
 

src/connections/storage/warehouses/warehouse-syncs.md

@@ -15,6 +15,8 @@ Warehouses sync with all data coming from your source.
 
 ## Sync Frequency
 
+Your plan determines how frequently data is synced to your warehouse. 
+
 | Plan     | Frequency   |
 | -------- | ----------- |
 | Free     | Once a day  |