Update BigQuery Docs (#1599)

* Update BigQuery Docs

Update docs for BigQuery pipelines

* Fix Docs

Fix creat to create

* Fix Typos

---------

Co-authored-by: myronkaifung <97630035+myronkaifung@users.noreply.github.com>

pages/docs/cohort-sync/integrations/marketo.md

@@ -13,7 +13,7 @@ You must be a Mixpanel project admin to use the Marketo data integration.
 
 In order to setup your Mixpanel and Marketo Integration, you must be an Admin in both Marketo and your Mixpanel project. To set up the integration:
 
-1. Input your[ Marketo credentials](http://developers.marketo.com/rest-api/authentication/) (Client ID, Client Secret, Rest URL) in the Mixpanel integration setup flow. Remove "identity" from the url so its rest endpoint when setting up the integration looks like: https://051-pvi-353.mktorest.com/
+1. Input your[Marketo credentials](http://developers.marketo.com/rest-api/authentication/) (Client ID, Client Secret, Rest URL) in the Mixpanel integration setup flow. Remove "identity" from the url so its rest endpoint when setting up the integration looks like: https://051-pvi-353.mktorest.com/
 
 2. Create a Mixpanel Custom Field in Marketo. **This Custom Field should be set as a boolean type**. Read the [Marketo Documentation](https://docs.marketo.com/display/public/DOCS/Create+a+Custom+Field+in+Marketo) for additional information on how to set up a Custom Field.
 

pages/docs/data-pipelines/integrations/bigquery.md

@@ -34,7 +34,7 @@ Mixpanel requires two permissions to manage the dataset:
 
 - Navigate to **IAM & Admin** in your Google Cloud Console.
 - Click **+ ADD** to add principals
-- Add new principle `export-upload@mixpanel-prod-1.iam.gserviceaccount.com` and set the role as `BigQuery Job User`
+- Add new principal `export-upload@mixpanel-prod-1.iam.gserviceaccount.com` and set the role as `BigQuery Job User`
 - Click the **Save** button.
 
 ![image](/230698732-4dadbccf-1eeb-4e64-a6c7-8926eb49e5cc.png)
@@ -45,7 +45,7 @@ Mixpanel requires two permissions to manage the dataset:
 - Open the dataset intended for Mixpanel exports.
 - Click on **Sharing** and **Permissions** in the drop down.
 - In the Data Permissions window, click on **Add Principal**
-- Add new principle `export-upload@mixpanel-prod-1.iam.gserviceaccount.com` and set the role as `BigQuery Data Owner`, and save.
+- Add new principal `export-upload@mixpanel-prod-1.iam.gserviceaccount.com` and set the role as `BigQuery Data Owner`, and save.
 
 ![image](/230698735-972aedb5-1352-4ebc-82c4-ef075679779b.png)
 

pages/docs/data-pipelines/integrations/redshift-spectrum.md

@@ -102,7 +102,7 @@ To ensure secure operations, limit the trust relationship to the Mixpanel export
 
 This section outlines the necessary steps for configuring permissions to allow Mixpanel to create external schemas in Redshift Spectrum.
 
-### Step 1: Creat Policy
+### Step 1: Create Policy
 
 Create a policy in IAM with the necessary permissions to enable Mixpanel to interact with Redshift Spectrum, Glue Data Catalog, and S3. Replace `<BUCKET_NAME>` with your actual S3 bucket name:
 

pages/docs/data-pipelines/old-pipelines/integrations/schematized-bigquery-pipeline.md

@@ -3,7 +3,7 @@
 This guide describes how Mixpanel exports your data to a [Google BigQuery](https://cloud.google.com/bigquery/) dataset.  
 ## Design
 
-There are currently two ways to export mixpanel data into big.
+There are currently two ways to export mixpanel data into BigQuery.
 1. Exporting into Customer managed BigQuery (recommended)
 2. Exporting into Mixpanel managed BigQuery  
 
@@ -97,15 +97,15 @@ We recommend exporting Mixpanel data into customer-managed BigQuery, for this th
    **BigQuery Job User**
      * Go to **IAM &Admin** in your Google Cloud Console.
      * Click **+ ADD** to add principals
-     * Add new principle "export-upload@mixpanel-prod-1.iam.gserviceaccount.com" and set role as "BigQuery Job User", and save.
+     * Add new principal "export-upload@mixpanel-prod-1.iam.gserviceaccount.com" and set role as "BigQuery Job User", and save.
        ![image](/230698732-4dadbccf-1eeb-4e64-a6c7-8926eb49e5cc.png)
 
    **BigQuery Data Owner**
      * Go to **BigQuery** in your Google cloud Console.
      * Open the dataset you want mixpanel to export to.
      * Click on **sharing** and **permissions** in the drop down. 
      * In the Data Permissions window click on **Add Principal** 
-     * Add new principle "export-upload@mixpanel-prod-1.iam.gserviceaccount.com" and set role as "BigQuery Data Owner", and save.    
+     * Add new principal "export-upload@mixpanel-prod-1.iam.gserviceaccount.com" and set role as "BigQuery Data Owner", and save.    
        ![image](/230698735-972aedb5-1352-4ebc-82c4-ef075679779b.png)
 
 3. You need to pass this dataset and gcp project id as params when you [create your pipeline](https://developer.mixpanel.com/reference/create-warehouse-pipeline)

pages/docs/reports.md

@@ -103,7 +103,7 @@ You can select the following filtering options to show a subset of the propertie
 
 The events and properties in the menu are prefixed to provide additional context about the properties' type. They will be removed when additional context is not needed.
 
-- Event properties are not prefixed (except in [User report's menu](/docs/reports):
+- Event properties are not prefixed (except in [User report's menu](/docs/reports)):
 
     ![/Screen_Shot_2021-11-18_at_12.26.25_PM.png](/Screen_Shot_2021-11-18_at_12.26.25_PM.png)
 

pages/docs/tracking-best-practices/developer-environments.md

@@ -48,7 +48,7 @@ An organization is charged based on data across all projects. This means that if
 
 Generally speaking, Mixpanel users have more flexibility and get more valuable insights when combining the tracking of multiple platforms into a single project to study their overall user experience across platforms.
 
-While we generally recommend sending data from all platforms to a single project, it’s also best practice to create separate development and production projects to avoid cluttering production data with test data, regardless of platform. If you send events from all platforms to one project, you can still differentiate actions taken on your app vs. website via segmentation and filtering using the Operating System property (the Mixpanel JavaScript, iOS, and Android libraries store the Operating System property by default.
+While we generally recommend sending data from all platforms to a single project, it’s also best practice to create separate development and production projects to avoid cluttering production data with test data, regardless of platform. If you send events from all platforms to one project, you can still differentiate actions taken on your app vs. website via segmentation and filtering using the Operating System property (the Mixpanel JavaScript, iOS, and Android libraries store the Operating System property by default).
 
 If you decide to send events from multiple platforms to the same Mixpanel projects, follow these guidelines for the best results:
 

pages/docs/tracking-methods/integrations/launchdarkly.md

@@ -12,7 +12,7 @@ Doing this involves sending impression events from LaunchDarkly to Mixpanel and
 
 In order to perform its analyses, Mixpanel needs impression events. These events tell Mixpanel which user was exposed to which variant at which time. 
 
-These events must be called `$experiment_started` and must have the `Experiment name` and `Variant name` properties -- Mixpanel recognizes these events and uses them to autopopulate the Experiments report](/docs/reports/apps/experiments).
+These events must be called `$experiment_started` and must have the `Experiment name` and `Variant name` properties -- Mixpanel recognizes these events and uses them to autopopulate the Experiments report(/docs/reports/apps/experiments).
 ```json
 {
   "event": "$experiment_started",