diff --git a/reference/Data Pipelines API/retrieve-pipelines/get-warehouse-pipeline-status.md b/reference/Data Pipelines API/retrieve-pipelines/get-warehouse-pipeline-status.md
index 11fd3093fc..4400d4377f 100644
--- a/reference/Data Pipelines API/retrieve-pipelines/get-warehouse-pipeline-status.md	
+++ b/reference/Data Pipelines API/retrieve-pipelines/get-warehouse-pipeline-status.md	
@@ -11,7 +11,7 @@ Given the name of the pipeline this API returns the status of the pipeline. It r
 
 **Example Response:** Status with no Summary and a Filter
 
-```curl
+```sh
 curl https://data.mixpanel.com/api/2.0/nessie/pipeline/status \
   -u API_SECRET: \
   -d name="YOUR_PIPELINE_NAME" \
diff --git a/reference/Mixpanel APIs/authentication/project-token.md b/reference/Mixpanel APIs/authentication/project-token.md
index 626fdd945e..1d6dabb989 100644
--- a/reference/Mixpanel APIs/authentication/project-token.md	
+++ b/reference/Mixpanel APIs/authentication/project-token.md	
@@ -9,8 +9,6 @@ Every Mixpanel project has a unique alphanumerical token for collecting data. A
 
 With that in mind, it is important to note that a project's token is not a form of authorization. It is an identification sent along with each piece of data you send to your project.
 
-Project token is solely used in our Ingestion APIs. For any events with a timestamp of more than five days, we require you to provide authentication via Project Secret along with the token.
-
 ## Sending data with a Project Token
 
 For [Track Events](ref:track-event), tokens are provided as values inside of the data sent to Mixpanel. Where this value is stored is dependent on the API endpoint used. Information on the specific location can be found in the Ingestion API's specification.
diff --git a/reference/Mixpanel APIs/overview.md b/reference/Mixpanel APIs/overview.md
index 1da1a36333..04b6b44dd7 100644
--- a/reference/Mixpanel APIs/overview.md	
+++ b/reference/Mixpanel APIs/overview.md	
@@ -25,7 +25,7 @@ Use the Query AP to get the same calculated data the powers Mixpanel's web appli
 **EU Residency Server:** `data-eu.mixpanel.com/api/2.0/export`
 Use the Raw Data Export API endpoint to obtain your event data. This API supports direct download or uploading to a cloud bucket.
 
-### [**Data Pipelines API**](ref:data-warehouse-api) 
+### [**Data Pipelines API**](ref:overview-2)
 **Standard Server:** `data.mixpanel.com/api/2.0/nessie`
 **EU Residency Server:** `data-eu.mixpanel.com/api/2.0/nessie`
 Use the Data Pipelines API to export Mixpanel data to your own Data Warehouse. Mixpanel’s Data Pipelines product removes the need to build complex connectors, maintain exporting code, and apply ad-hoc data transformations.