First pass of bigquery edits

Author: forstisabella

src/_includes/content/warehouse-sync-sched.md

@@ -1,4 +1,4 @@
-Your data will be available in Warehouses between 24 and 48 hours from your first sync. Your warehouse then syncs once, or twice a day depending on your [Segment Plan](https://segment.com/pricing).
+Your data will be available in Warehouses between 24 and 48 hours from your first sync. Your warehouse then syncs once or twice a day depending on your [Segment Plan](https://segment.com/pricing).
 
 Segment allows Business Tier (BT) customers to schedule the time and frequency of warehouse data syncs.
 

src/connections/storage/catalog/bigquery/index.md

@@ -16,10 +16,6 @@ process to pull raw events and objects and load them into your BigQuery cluster.
 Using BigQuery through Segment means you'll get a fully managed data pipeline
 loaded into one of the most powerful and cost-effective data warehouses today.
 
-If you notice any gaps,
-out-dated information or want to leave some feedback to help us improve
-our documentation, [let us know](https://segment.com/help/contact)!
-
 ## Getting Started
 
 First, you'll want to enable BigQuery for your Google Cloud project. Then, you
@@ -32,7 +28,7 @@ warehouse in Segment.
 2. Configure [Cloud Platform](https://console.cloud.google.com/):
   - If you don't have a project already, [create one](https://support.google.com/cloud/answer/6251787?hl=en&ref_topic=6158848).
   - If you have an existing project, you will need to [enable the BigQuery API](https://cloud.google.com/bigquery/quickstart-web-ui).
-    Once you've done so, you should see BigQuery in the ["Resources" section](https://cl.ly/0W2i2I2B2R0M) of Cloud Platform.
+    Once you've done so, you should see BigQuery in the "Resources" section of Cloud Platform.
   - **Note:** make sure [billing is enabled](https://support.google.com/cloud/answer/6293499#enable-billing) on your project,
     otherwise Segment will not be able to write into the cluster.
 3. Copy your project ID, as you will need it later.
@@ -56,11 +52,11 @@ The downloaded file will be used to create your warehouse in the next section.
 1. In Segment, go to **Workspace** > **Add destination** > Search for "BigQuery"
 2. Select **BigQuery**
 3. Enter your project ID in the **Project** field
-4. Copy the contents of the credentials (the JSON key) into the **Credentials** field
-5. (Optional) Enter a [region code](https://cloud.google.com/compute/docs/regions-zones/) in the **Location** field (the default will be "US")
+4. Copy the contents of the credentials (the JSON key) into the **Credentials** field <br/>
+**Optional:** Enter a [region code](https://cloud.google.com/compute/docs/regions-zones/) in the **Location** field (the default will be "US")
 6. Click **Connect**
-7. if Segment is able to successfully connect with the **Project ID** and **Credentials**,
-the warehouse will be created and your first sync should begin shortly
+7. if Segment is able to successfully connect with the provided **Project ID** and **Credentials**,
+a warehouse will be created and your first sync should begin shortly
 
 ### Schema
 
@@ -108,17 +104,17 @@ from <project-id>.<source-name>.<collection-name>_view
 
 For early customers using BigQuery with Segment, rather than providing Segment
 with credentials, access was granted to a shared Service Account
-(`connector@segment-1119.iam.gserviceaccount.com`). While convenient early
-adopters, this presents potential security risks that we would prefer to address
+(`connector@segment-1119.iam.gserviceaccount.com`). While convenient for early
+adopters, this presents potential security risks that Segment would prefer to address
 proactively.
 
-Starting in **March 2019**, we're going to start requiring BigQuery customers to
-create their own Service Accounts and provide us with those credentials instead.
+As of **March 2019**, Segment requires BigQuery customers to
+create their own Service Accounts and provide the app with those credentials instead.
 In addition, any attempts to update warehouse connection settings will also
 require these credentials. This effectively deprecates the shared Service
-Account, and in the future it will be deactivated completely.
+Account.
 
-In order to stay ahead of this, make sure to migrate your warehouse by following
+In order to stay ahead of this change, make sure to migrate your warehouse by following
 the instructions in the "Create a Service Account for Segment" section above.
 Then, head to your warehouse's connection settings and update with the
 **Credentials** you created along the way.
@@ -159,7 +155,7 @@ querying sub-sets of tables.
 Absolutely! You will just need to modify one of the references to 60 in the view
 definition to the number of days of your choosing.
 
-We chose 60 days as it suits the needs for most of our customers. However,
+We chose 60 days as it suits the needs of most of our customers. However,
 you're welcome to update the definition of the view as long as the name stays
 the same.
 
@@ -196,8 +192,8 @@ costs.
 You can connect to BigQuery using a BI tool like Mode or Looker, or query
 directly from the BigQuery console.
 
-BigQuery now supports standard SQL, which you can enable using their query UI.
-This does not work with views, or with a query that utilizes table range
+BigQuery now supports standard SQL, which you can enable using their query UI. 
+This does not work with views, or with a query that uses table range 
 functions.
 
 ### Does Segment support streaming inserts?