Making requested content changes [netlify-build]

Author: forstisabella

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

@@ -1,6 +1,3 @@
-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. 
-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. 
-5. **Load:** Segment de-duplicates the transformed data and loads it into your warehouse. If you have queries set up in your warehouse, they run after the data is loaded into your warehouse. ***This is the only step that connects to your warehouse: all other steps are internal to Segment.*** 
+When Segment loads data into your warehouse, each sync goes through two 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. Common reasons a sync might fail at this step include a blocked VPN or IP, a warehouse that isn't set to be publicly accessible, or an issue with user permissions or credentials. 
+2. **Load:** Segment de-duplicates the transformed data and loads it into your warehouse. If you have queries set up in your warehouse, they run after the data is loaded into your warehouse. 

src/connections/storage/warehouses/faq.md

@@ -93,34 +93,43 @@ After a source is created, you can enable or disable a warehouse sync within the
 
 ## Can I be notified when warehouse syncs fail?
 
-If you enabled activity notifications for your storage destination, you'll receive notifications in the Segment app when warehouse syncs fail.
+If you enabled activity notifications for your storage destination, you'll receive notifications in the Segment app for the fifth and 20th consecutive warehouse failures.
 
 To sign up for warehouse sync notifications:
 1. Open the Segment app. 
 2. Go to **Settings** > **User Preferences**. 
 3. In the Activity Notifications section, select **Storage Destinations**.
 4. Enable **Storage Destination Sync Failed**. 
 
-## How is my data formatted in my warehouse?
+## How is the 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.
+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.user_id`, 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 (user_id). 
+
+> note " "
+> All schema data is always represented in snake case.
+
+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 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 date range of data that requires a backfill
+If your syncs fail, you do not need to reach out to Segment Support to request a backfill. Once a successful sync takes place, 
+Segment will automatically load all of the data created since the last successful sync. 
+
 
 ## Can I change my schema names once they've been created?
 
-If you'd like to change the name of your schema:
+Segment stores the name of your hanging the name of your schema in the **SQL Settings** page without updating the name in your data warehouse causes the schema 
+to be split into two after the name is changed. 
 
-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."
+To change the name of your schema without disruptions: 
+
+1. Open the Segment app, select your warehouse from the Sources tab, and select **Settings.**
+2. Under the "Enable Source" section, disable your warehouse and click **Save Changes.**   
+3. Select the "SQL Settings" tab. 
+4. Update the "Schema Name" field with the new name for your schema and click **Save Changes.**
+5. Rename the schema in your Data Warehouse to match the new name in the Segment app. 
+6. Open the Segment app, select your warehouse from the Sources tab, and select **Settings.** On the source's settings page, select "Basic."
+7. Under the "Enable Source" section, enable your warehouse and click **Save Changes.**

src/connections/storage/warehouses/images/how-a-sync-works.png

@@ -3,7 +3,7 @@ title: Warehouse Schemas
 ---
 
 A **schema** describes the way that the data in a warehouse is organized. Schemas of warehouse data are organized into the following template:
-`<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).
+`<source>.<collection>.<property>`, for example `segment_engineering.tracks.user_id`, 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 (user_id). All schemas convert collection and property names from `CamelCase` to `snake_case`.
 
 > note "Warehouse column creation"
 > **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.
@@ -412,15 +412,18 @@ Data types are set up in your warehouse based on the first value that comes in f
 
 The data types that Segment currently supports include:
 
-### `timestamp`
+#### `timestamp`
 
-### `integer`
+#### `integer`
 
-### `float`
+#### `float`
 
-### `boolean`
+#### `boolean`
 
-### `varchar`
+#### `varchar`
+
+> note " "
+> To change data types after they've been determined, please reach out to [Segment Support](https://segment.com/help/contact) for assistance. 
 
 ## Column Sizing
 

src/connections/storage/warehouses/schema.md

@@ -3,10 +3,6 @@ title: Warehouse Syncs
 redirect_from: '/connections/warehouses/selective-sync/'
 ---
 
-<!--- The Warehouse Sync process prepares the raw data coming from a source and loads it into a warehouse destination. There are two phases to the sync process:
-1. **Preparation phase**: This is where Segment prepares the data coming from a source so that it's in the right format for the loading phase. 
-2. **Loading phase**: This is where Segment deduplicates data and the data loads into the warehouse destination. Any sync issues that occur in this phase can be traced back to your warehouse. -->
-
 Instead of constantly streaming data to the warehouse destination, Segment loads data to the warehouse in bulk at regular intervals. Before the data loads, Segment inserts and updates events and objects, and automatically adjusts the schema to make sure the data in the warehouse is inline with the data in Segment.
 
 {% include content/how-a-sync-works.md %}
@@ -17,13 +13,16 @@ Warehouses sync with all data coming from your source. However, Business plan me
 
 Your plan determines how frequently data is synced to your warehouse. 
 
-| Plan     | Frequency   |
-| -------- | ----------- |
-| Free     | Once a day  |
-| Team     | Twice a day |
-| Business | Up to 24 times a day. Generally, these syncs are fixed to the top of the hour (:00), but these times can vary. |
+| Plan      | Frequency                                                                                                      |
+| --------- | -------------------------------------------------------------------------------------------------------------- |
+| Free      | Once a day (every 86,400 seconds)                                                                              |
+| Team      | Twice a day (every 43,200 seconds)                                                                             |
+| Business* | Up to 24 times a day. Generally, these syncs are fixed to the top of the hour (:00), but these times can vary. |
+
+*If you're a Business plan member and would like to adjust your sync frequency, you can do so using the Selective Sync feature. To enable Selective Sync, please go to **Warehouse** > **Settings** > **Sync Schedule**. 
 
-If you're a Business plan member and would like to adjust your sync frequency, you can do so using the Sync Schedule feature. To enable Sync Schedule, please go to **Warehouse** > **Settings** > **Sync Schedule**. 
+> note "Why can't I sync more than 24 times per day?"
+> We do not set syncs to happen more than once per hour (ie, 24 times per day). The warehouse product is not designed for real-time data, so more frequent syncs would not necessarily be helpful.
 
 ## Sync History
 You can use the Sync History page to see the status and history of data updates in your warehouse. The Sync History page is available for every source connected to each warehouse. This page helps you answer questions like, “Has the data from a specific source been updated recently?” “Did a sync completely fail, or only partially fail?” and “Why wasn’t this sync successful?”