Apply suggestions from code review

Co-authored-by: stayseesong <[email protected]>

Author: forstisabella

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

@@ -7,8 +7,7 @@ redirect_from:
 
 Segment's [BigQuery](https://cloud.google.com/bigquery/){:target="_blank"} connector makes it easy
 to load web, mobile, and third-party source data like Salesforce, Zendesk, and
-Google AdWords into a BigQuery data warehouse.  When you integrate BigQuery with Segment you get a fully managed data pipeline
-loaded into a powerful and cost-effective data warehouse.
+Google AdWords into a BigQuery data warehouse.  When you integrate BigQuery with Segment you get a fully managed data pipeline loaded into a powerful and cost-effective data warehouse.
 
 The Segment warehouse connector runs a periodic ETL (Extract - Transform - Load) process to pull raw events and objects from your sources and load them into your BigQuery cluster. 
 For more information about the ETL process, including how it works and common ETL use cases, refer to [Google Cloud's ETL documentation](https://cloud.google.com/learn/what-is-etl){:target="_blank"}.
@@ -22,20 +21,22 @@ To store your Segment data in BigQuery, complete the following steps:
 
 ### Create a Project and Enable BigQuery
 
+To create a project and enable BigQuery:
 1. Navigate to the [Google Developers Console](https://console.developers.google.com/){:target="_blank"}.
 2. Configure the [Google Cloud Platform](https://console.cloud.google.com/){:target="_blank"}:
   - If you don't have a project already, [create one](https://support.google.com/cloud/answer/6251787?hl=en&ref_topic=6158848){:target="_blank"}.
   - If you have an existing project, [enable the BigQuery API](https://cloud.google.com/bigquery/quickstart-web-ui){:target="_blank"}. Once you've done so, you should see BigQuery in the "Resources" section of Cloud Platform.
-3. Copy the project ID. You will need it when you create a warehouse source in the Segment app.
+3. Copy the project ID. You'll need it when you create a warehouse source in the Segment app.
 
 > note "Enable billing"
-> When creating your project, you must [enable billing](https://support.google.com/cloud/answer/6293499#enable-billing){:target="_blank"} so Segment can write into the cluster.
+> When you create your project, you must [enable billing](https://support.google.com/cloud/answer/6293499#enable-billing){:target="_blank"} so Segment can write into the cluster.
 
 ### Create a service account for Segment
 
+To create a service account for Segment: 
 1. From the Navigation panel on the left, select **IAM & admin** > **Service accounts**.
 2. Click **Create Service Account**.
-3. Enter a name for the service account (for example `segment-warehouses`) and click **Create**.
+3. Enter a name for the service account (for example, `segment-warehouses`) and click **Create**.
 4. Assign the service account the following roles:
     - `BigQuery Data Owner`
     - `BigQuery Job User`
@@ -46,15 +47,17 @@ If you have trouble creating a new service account, refer to [Google Cloud's doc
 
 ### Create the Warehouse in Segment
 
-1. From the homepage of the Segment app, select **Connections**, click **Add Destination** and search for "BigQuery".
+To create the warehouse in Segment: 
+1. From the homepage of the Segment app, select **Connections > Add Destination** and search for **BigQuery**.
 2. Click **BigQuery**.
 3. Select the source(s) you'd like to sync with the BigQuery destination, and click **Next**.
 3. Enter a name for your destination in the **Name your destination** field.
 4. Enter your Project ID in the **Project ID** field.
-  <br/>**Optional:** Enter a [region code](https://cloud.google.com/compute/docs/regions-zones/){:target="_blank"} in the **Location** field (the default is "US".)
+  <br/>*Optional:* Enter a [region code](https://cloud.google.com/compute/docs/regions-zones/){:target="_blank"} in the **Location** field (the default is *US*.)
 5. Copy the contents of the JSON key that you created for the Segment service account into the **Credentials** field.
 6. Click **Connect**.
-7. If Segment is able to connect to your project, a warehouse will be created and your first sync will begin shortly.
+
+If Segment is able to connect to your project, a warehouse will be created and your first sync will begin shortly.
 
 ## Schema
 
@@ -65,8 +68,8 @@ contain duplicate data, **views** do _not_ contain duplicate data.
 
 The Segment connector uses [partitioned
 tables](https://cloud.google.com/bigquery/docs/partitioned-tables){:target="_blank"}. Partitioned
-tables allow you to query a subset of data, thus increasing query performance
-and decreasing costs.
+tables allow you to query a subset of data, which increases query performance
+and decreases costs.
 
 To query a full table, use the following command:
 
@@ -121,6 +124,7 @@ to your warehouse, [remove access to the shared Service Account](#remove-access-
 You can remove access to the shared Service Account 
 (`[email protected]`) using the following instructions:
 
+To remove access to the shared Service Account: 
 1. Create a [new Service Account for Segment](#create-a-service-account-for-segment) using the linked instructions.
 2. Verify that the data is loading into your warehouse. 
 3. Sign in to the [Google Developers Console](https://console.developers.google.com){:target="_blank"}.
@@ -140,7 +144,7 @@ BigQuery charges based on the amount of data scanned by your queries. Views are
 a derived view over your tables that Segment uses for de-duplication of events.
 Therefore, Segment recommends you query a specific view whenever possible to avoid
 duplicate events and historical objects. It's important to note that BigQuery
-views are not cached.
+views aren't cached.
 
 > note "Understanding BigQuery views"
 > BigQuery's views are logical views, not materialized views, which means that the query that defines the view is re-executed every time the view is queried. Queries are billed according to the total amount of data in all table fields referenced directly or indirectly by the top-level query.
@@ -151,7 +155,7 @@ destination table.
 
 ### Query structure
 
-If you typically start exploratory data analysis with `SELECT *`, consider
+If you start exploratory data analysis with `SELECT *`, consider
 specifying the fields to reduce costs.
 
 Refer to the section on [partitioned tables](#partitioned-tables) for details on
@@ -189,7 +193,7 @@ pricing [on Google Cloud's BigQuery pricing page](https://cloud.google.com/bigqu
 BigQuery allows you to set up [Cost Controls and
 Alerts](https://cloud.google.com/bigquery/cost-controls){:target="_blank"} to help control and
 monitor costs. If you want to learn more about the costs associated with BigQuery,
-Google Cloud has provided [a
+Google Cloud provides [a
 calculator](https://cloud.google.com/products/calculator/){:target="_blank"} to estimate your
 costs.
 
@@ -198,13 +202,13 @@ costs.
 You can connect a BI tool like Mode or Looker to BigQuery, or query
 directly from the BigQuery console.
 
-BigQuery now supports standard SQL, which you can enable [using Google Cloud's query UI](https://cloud.google.com/bigquery/docs/reference/standard-sql/introduction#changing_from_the_default_dialect){:target="_blank"}. 
-This does not work with views, or with a query that uses table range 
+BigQuery supports standard SQL, which you can enable [using Google Cloud's query UI](https://cloud.google.com/bigquery/docs/reference/standard-sql/introduction#changing_from_the_default_dialect){:target="_blank"}. 
+This doesn't work with views, or with a query that uses table range 
 functions.
 
 ### Does Segment support streaming inserts?
 
-Segment's connector does not support streaming inserts at this time. If you have
+Segment's connector doesn't support streaming inserts at this time. If you have
 a need for streaming data into BigQuery, [contact Segment support](https://segment.com/requests/integrations/){:target="_blank"}.
 
 ### Can I customize my sync schedule?