Small content edits

Author: forstisabella

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

@@ -3,4 +3,4 @@ When Segment loads data into your warehouse, each sync goes through the followin
 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. <br/>***This is the only step that connects to your warehouse: all other steps are internal to Segment.*** 
+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.*** 

src/connections/storage/warehouses/faq.md

@@ -46,9 +46,7 @@ Your warehouse id appears in the URL when you look at the [warehouse destination
 
 Data is available in Warehouses within 24-48 hours, depending on your tier's sync frequency. For more information about sync frequency by tier, see [Sync Frequency](/docs/connections/storage/warehouses/warehouse-syncs/#sync-frequency).
 
-Real-time loading of the data into Segment Warehouses would cause significant performance degradation at query time because of the way Redshift uses large batches to optimize and compress columns. To optimize for your query speed, reliability, and robustness, Segment guarantees that your data will be available in Redshift within 24 hours. The underlying Redshift datastore has a subtle tradeoff between data freshness, robustness, and query speed. For the best experience, Segment needs to balance all three of these.
-
-As Segment improves and updates the ETL processes and optimizes for SQL query performance downstream, the actual load time will vary, but Segment ensures it's always within 24 hours.
+Real-time loading of the data into Segment Warehouses would cause significant performance degradation at query time. To optimize for your query speed, reliability, and robustness, Segment guarantees that your data will be available in your warehouse within 24 hours. The underlying datastore has a subtle tradeoff between data freshness, robustness, and query speed. For the best experience, Segment needs to balance all three of these.
 
 ## What if I want to add custom data to my warehouse?
 
@@ -109,7 +107,7 @@ Data in your warehouse is formatted into **schemas**, which involve a detailed d
 
 ## If my syncs fail and get fixed, will I need to ask for a backfill?
 
-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: 
+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

src/connections/storage/warehouses/index.md

@@ -34,7 +34,7 @@ Examples of data warehouses include Amazon Redshift, Google BigQuery, and Postgr
 
 [How do I give users permissions to my warehouse?](/docs/connections/storage/warehouses/add-warehouse-users/)
 
-Check out our [Frequently Asked Questions about Warehouses](/docs/connections/storage/warehouses/faq/) and [a list of helpful Redshift queries to get you started](/docs/connections/storage/warehouses/redshift-useful-sql).
+Check out our [Frequently Asked Questions about Warehouses](/docs/connections/storage/warehouses/faq/) and [a list of helpful SQL queries to get you started with Redshift ](/docs/connections/storage/warehouses/redshift-useful-sql).
 
 ## FAQs
 

src/connections/storage/warehouses/schema.md

@@ -2,10 +2,8 @@
 title: Warehouse Schemas
 ---
 
-A **schema** describes the way that the data in a warehouse is organized. Schemas include a detailed description of database elements (tables, views, indexes, synonyms, etc.) and the relationships that exist between elements. 
-
-Schemas of warehouse data are organized into 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).
+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).
 
 > 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.
@@ -137,7 +135,7 @@ The table below describes the schema in Segment Warehouses:
 
 ## Identifies table
 
-The `identifies` table stores the `.identify()` method calls =. Query it to find out user-level information. It has the following columns:
+The `identifies` table stores the `.identify()` method calls. Query it to find out user-level information. It has the following columns:
 
 | method          | property                                                                                                                                                                                   |
 | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
@@ -428,7 +426,7 @@ The data types that Segment currently supports include:
 
 After analyzing the data from dozens of customers, we set the string column length limit at 512 characters. Longer strings are truncated. We found this was the sweet spot for good performance and ignoring non-useful data.
 
-We special-case compression for some known columns, like event names and timestamps. The others default to LZO. We may add look-ahead sampling down the road, but from inspecting the datasets today this would be unnecessary complexity.
+We special-case compression for some known columns, like event names and timestamps. The others default to LZO. We may add look-ahead sampling down the road, but from inspecting the datasets today this would be unnecessary complex.
 
 ## Timestamps
 
@@ -476,4 +474,6 @@ All tables use `received_at` for the sort key. Amazon Redshift stores your data
 
 [How do I give users permissions to my warehouse?](/docs/connections/storage/warehouses/add-warehouse-users/)
 
+[How frequently does data sync to my warehouse?](/docs/connections/storage/warehouses/warehouse-syncs/#sync-frequency)
+
 Check out our [Frequently Asked Questions about Warehouses](/docs/connections/storage/warehouses/faq/) and [a list of helpful Redshift queries to get you started](/docs/connections/storage/warehouses/redshift-useful-sql).

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

@@ -11,7 +11,7 @@ Instead of constantly streaming data to the warehouse destination, Segment loads
 
 {% include content/how-a-sync-works.md %}
 
-Warehouses sync with all data coming from your source. 
+Warehouses sync with all data coming from your source. However, Business plan members can manage the data that is sent to your warehouses using [Selective Sync](#warehouse-selective-sync).
 
 ## Sync Frequency