Update API secret deprecation link in documentation

pages/docs/orgs-and-projects/managing-projects.mdx

@@ -59,7 +59,7 @@ This table provides the values for the **project token** and the **API secret**.
 <Callout type="warning">
 <strong>API Secret Deprecation</strong>
 
-The project API secret is deprecated and will be retired on **March 3 2027**. For new projects or integrations, use [Service Accounts](/docs/reference/Service%20Accounts%20API/service-accounts-api.md) instead. Existing API‑secret workflows will continue to work until retirement but should be migrated when convenient.
+The project API secret is deprecated and will be retired on **March 3 2027**. For new projects or integrations, use [Service Accounts](https://developer.mixpanel.com/reference/service-accounts) instead. Existing API‑secret workflows will continue to work until retirement but should be migrated when convenient.
 </Callout>
 
 ![manageprojects 4 Image](/manageprojects4.png)

reference/Ingestion API/ingestion-api-authentication.md

@@ -7,4 +7,4 @@ content:
 privacy:
   view: public
 ---
-Most of our Ingestion API calls such as [Import Events](ref:import-events), [Track Events](ref:track-event), [User Profiles](ref:user-profiles), and [Group Profiles](ref:group-profiles) only require a [Project Token](ref:project-token). Because these APIs are often called from our client-side SDKs, we do not want to expose credentials, but we do need to know which project to send data to so we use the Project Token for that purpose. However, a few of the more powerful APIs such as [Lookup Tables](ref:lookup-tables) **do require authentication**. For these, it's recommended to use a [Service Account](ref:service-account). We also have legacy support for [Project Secret](ref:project-secret) but suggest any new integrations use a Service Account.
+Most of our Ingestion API calls such as [Import Events](ref:import-events), [Track Events](ref:track-event), [User Profiles](ref:user-profiles), and [Group Profiles](ref:group-profiles) only require a [Project Token](ref:project-token). Because these APIs are often called from our client-side SDKs, we do not want to expose credentials, but we do need to know which project to send data to so we use the Project Token for that purpose. However, a few of the more powerful APIs such as [Lookup Tables](ref:lookup-tables) **do require authentication**. For these, it's recommended to use a [Service Account](ref:service-accounts). We also have legacy support for [Project Secret](ref:project-secret) but suggest any new integrations use a Service Account.

reference/Mixpanel APIs/authentication/service-accounts.md

@@ -39,7 +39,7 @@ requests.get(
 
 > 🚧 Owner or Admin Permissions Required
 >
-> You must have Owner or Admin permissions to manage a project's Service Accounts. Learn more in our [permissions help doc](https://mixpanelsupport.zendesk.com/hc/en-us/articles/360024613412).
+> You must have Owner or Admin permissions to manage a project's Service Accounts. Learn more in our [permissions help doc](https://docs.mixpanel.com/docs/orgs-and-projects/roles-and-permissions#permissions).
 
 <HTMLBlock>{`
 <div class="mixpanel-custom-two-column">
@@ -87,7 +87,7 @@ requests.get(
 </style>
 `}</HTMLBlock>
 
-Any service account you create from the project settings page will be automatically be assigned an admin role. Deleting a service account will revoke access only from that project.
+Any service account you create from the project settings page will be automatically be assigned an organization member role. Deleting a service account will revoke access only from that project.
 
 <HTMLBlock>{`
 <div class="create-service-account">