[netlify-build]

Author: stayseesong

src/connections/reverse-etl/index.md

@@ -63,9 +63,9 @@ To add your warehouse as a source:
 >>>>>>> 1eb6924a9 ([netlify-build]):src/connections/reverse-etl/index.md
 3. Select the source you want to add. You can choose between BigQuery, Redshift, and Snowflake.
 4. Follow the corresponding setup guide for your Reverse ETL source. 
-    * [BigQuery Reverse ETL setup guide](/docs/connections/reverse-etl/bigquery-setup/)
-    * [Redshift Reverse ETL setup guide](/docs/connections/reverse-etl/redshift-setup/)
-    * [Snowflake Reverse ETL setup guide](/docs/connections/reverse-etl/snowflake-setup/)
+    * [BigQuery Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup/)
+    * [Redshift Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/redshift-setup/)
+    * [Snowflake Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/snowflake-setup/)
 5. Add the account information for your source.  
 >>>>>>> 401fa6bc5 (edits)
     * For Snowflake users: Learn more about the Snowflake Account ID [here](https://docs.snowflake.com/en/user-guide/admin-account-identifier.html){:target="_blank"}.

src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md

@@ -28,7 +28,7 @@ To set up the Segment BigQuery connector:
 20. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again.
 6. Click **Create Source** if the test connection is successful.
 
-Once you've added BigQuery as a source, you can [add a model](/docs/connections/sources/reverse-etl#step-2-add-a-model).
+Once you've added BigQuery as a source, you can [add a model](/docs/connections/reverse-etl#step-2-add-a-model).
 
 ## Constructing your own role or policy
 When you construct your own role or policy, Segment needs the following permissions:

src/connections/reverse-etl/reverse-etl-source-setup-guides/snowflake-setup.md

@@ -59,4 +59,4 @@ Follow the instructions below to set up the Segment Snowflake connector. Segment
    -- role access
    GRANT ROLE segment_reverse_etl TO USER segment_reverse_etl_user;
    ```
-7. Follow the steps listed in the [Add a Source](/docs/connections/sources/reverse-etl#step-1-add-a-source) section to finish adding Snowflake as a source.
+7. Follow the steps listed in the [Add a Source](/docs/connections/reverse-etl#step-1-add-a-source) section to finish adding Snowflake as a source.

src/connections/sources/index.md

@@ -174,7 +174,7 @@ Segment's [Pixel Tracking API](/docs/connections/sources/catalog/libraries/serve
 | Unsubscribe          | The recipient clicked on message's subscription management link.                                                      |
 
 ## Reverse ETL sources
-Reverse ETL sources are data warehouses that enable you to use [Reverse ETL](/docs/connections/sources/reverse-etl) to send data from your warehouse source to your destinations. 
+Reverse ETL sources are data warehouses that enable you to use [Reverse ETL](/docs/connections/reverse-etl) to send data from your warehouse source to your destinations. 
 
 Reverse ETL supports [these sources] and Segment is actively working on adding more. If you'd like to request Segment to add a particular source, please note it on the [feedback form](https://airtable.com/shriQgvkRpBCDN955){:target="_blank"}.
 

src/guides/usage-and-billing/mtus-and-throughput.md

@@ -122,7 +122,7 @@ All Engage data are omitted from billing MTU and API throughput calculations, in
 Replays only affect your MTU count if you are using a [Repeater](/docs/connections/destinations/catalog/repeater/) destination, which might send data that hasn't yet been seen this month back through a source.
 
 ## MTUs and Reverse ETL 
-See the [Reverse ETL usage limts](/docs/connections/reverse-etl/#usage-limits) to see how MTUs affect your Reverse ETL usage limits. 
+See the [Reverse ETL usage limits](/docs/connections/reverse-etl/#usage-limits) to see how MTUs affect your Reverse ETL usage limits. 
 
 ## Why is my MTU count different from what I see in my destinations and other tools?