update paths

src/pages/guides/authentication/JWT/faq.md

@@ -2,4 +2,4 @@
 
 <InlineAlert slots="text"/>
 
-As of June 30, 2025, Service Account (JWT) credentials have reached their end of life and are no longer supported. All server-to-server integrations must use the [OAuth Server-to-Server credentials](../authentication/ServerToServerAuthentication/implementation.md). View the [migration guide](../authentication/ServerToServerAuthentication/migration.md) to know more.
+As of June 30, 2025, Service Account (JWT) credentials have reached their end of life and are no longer supported. All server-to-server integrations must use the [OAuth Server-to-Server credentials](../../authentication/ServerToServerAuthentication/implementation.md). View the [migration guide](../../authentication/ServerToServerAuthentication/migration.md) to know more.

src/pages/guides/authentication/JWT/index.md

@@ -2,4 +2,4 @@
 
 <InlineAlert slots="text"/>
 
-As of June 30, 2025, Service Account (JWT) credentials have reached their end of life and are no longer supported. All server-to-server integrations must use the [OAuth Server-to-Server credentials](../ServerToServerAuthentication/implementation.md). View the [migration guide](../ServerToServerAuthentication/migration.md) to know more.
+As of June 30, 2025, Service Account (JWT) credentials have reached their end of life and are no longer supported. All server-to-server integrations must use the [OAuth Server-to-Server credentials](../../authentication/ServerToServerAuthentication/implementation.md). View the [migration guide](../../authentication/ServerToServerAuthentication/migration.md) to know more.

src/pages/guides/authentication/JWT/jwt-certificate.md

@@ -2,4 +2,4 @@
 
 <InlineAlert slots="text"/>
 
-As of June 30, 2025, Service Account (JWT) credentials have reached their end of life and are no longer supported. All server-to-server integrations must use the [OAuth Server-to-Server credentials](../authentication/ServerToServerAuthentication/implementation.md). View the [migration guide](../authentication/ServerToServerAuthentication/migration.md) to know more.
+As of June 30, 2025, Service Account (JWT) credentials have reached their end of life and are no longer supported. All server-to-server integrations must use the [OAuth Server-to-Server credentials](../../authentication/ServerToServerAuthentication/implementation.md). View the [migration guide](../../authentication/ServerToServerAuthentication/migration.md) to know more.

src/pages/guides/authentication/JWT/samples.md

@@ -3,4 +3,4 @@
 
 <InlineAlert slots="text"/>
 
-As of June 30, 2025, Service Account (JWT) credentials have reached their end of life and are no longer supported. All server-to-server integrations must use the [OAuth Server-to-Server credentials](../authentication/ServerToServerAuthentication/implementation.md). View the [migration guide](../authentication/ServerToServerAuthentication/migration.md) to know more.
+As of June 30, 2025, Service Account (JWT) credentials have reached their end of life and are no longer supported. All server-to-server integrations must use the [OAuth Server-to-Server credentials](../../authentication/ServerToServerAuthentication/implementation.md). View the [migration guide](../../authentication/ServerToServerAuthentication/migration.md) to know more.

src/pages/guides/authentication/JWT/scopes.md

@@ -3,4 +3,4 @@
 
 <InlineAlert slots="text"/>
 
-As of June 30, 2025, Service Account (JWT) credentials have reached their end of life and are no longer supported. All server-to-server integrations must use the [OAuth Server-to-Server credentials](../authentication/ServerToServerAuthentication/implementation.md). View the [migration guide](../authentication/ServerToServerAuthentication/migration.md) to know more.
+As of June 30, 2025, Service Account (JWT) credentials have reached their end of life and are no longer supported. All server-to-server integrations must use the [OAuth Server-to-Server credentials](../../authentication/ServerToServerAuthentication/implementation.md). View the [migration guide](../../authentication/ServerToServerAuthentication/migration.md) to know more.

src/pages/guides/authentication/ServerToServerAuthentication/faqs.md

@@ -17,9 +17,8 @@
 
 
 ### What's happening?  
-As of June 30, 2025, Service Account (JWT) credentials have reached their end of life and are no longer supported. All server-to-server integrations must use the [OAuth Server-to-Server credentials](implementation.md). View the [migration guide](migration.md) to know more.
-
 
+As of June 30, 2025, Service Account (JWT) credentials have reached their end of life and are no longer supported. All server-to-server integrations must use the [OAuth Server-to-Server credentials](../../authentication/ServerToServerAuthentication/implementation.md). View the [migration guide](../../authentication/ServerToServerAuthentication/migration.md) to know more.
 
 ### What is a credential? 
 While building an integration, developers need to call Adobe APIs from their application. To call Adobe APIs, their integration must uniquely identify itself to Adobe. This ensures that only your application can retrieve your data from us.  
@@ -32,12 +31,12 @@ A credential is used to uniquely identify your integration to Adobe. To use an A
 
 ### Will my Adobe integrations or applications stop working immediately?
 
-No. Any integration or application using the Service Account (JWT) credential will stop working after current certificates expire, or March 1, 2026 (whichever is earlier). See [deprecation timelines](./migration.md#deperecation-timelines). See section on [migration next steps](#migration-next-steps).
+No. Any integration or application using the Service Account (JWT) credential will stop working after current certificates expire, or March 1, 2026 (whichever is earlier). See [deprecation timelines](migration.md#deprecation-timelines). See section on [migration next steps](#migration-next-steps).
 
 
 
 ### What is the deadline to migrate to the new credential? 
-The deadline to migrate has passed. If you integration is already broken or about to break after certificates expire, you must migrate it to use the new OAuth Server-to-Server credential as soon as possible. See [deprecation timelines](./migration.md#deperecation-timelines). See [migration guide](./migration.md).
+The deadline to migrate has passed. If you integration is already broken or about to break after certificates expire, you must migrate it to use the new OAuth Server-to-Server credential as soon as possible. See [deprecation timelines](migration.md#deprecation-timelines). See [migration guide](migration.md).
 
 
 
@@ -54,15 +53,15 @@ Furthermore, Adobe will automatically convert Service Account (JWT) to OAuth Ser
 
 
 ### What are the benefits of using the OAuth Server-to-Server credential? 
-You can read more about OAuth Server-to-Server credentials in our [implementation guide](./implementation.md). You can view the comparison between the OAuth Server-to-Server credential and the Service Account (JWT) credential [here](./migration.md#why-oauth-server-to-server-credentials).
+You can read more about OAuth Server-to-Server credentials in our [implementation guide](implementation.md). You can view the comparison between the OAuth Server-to-Server credential and the Service Account (JWT) credential [here](migration.md#why-oauth-server-to-server-credentials).
 
 ### Can I programmatically rotate client secrets for OAuth Server-to-Server credentials? 
-Absolutely. View our guide on rotating client secrets programmatically [here](./implementation.md#rotating-client-secrets-programmatically).
+Absolutely. View our guide on rotating client secrets programmatically [here](implementation.md#rotating-client-secrets-programmatically).
 
 
 
 ### What should I do if my client secrets get leaked? 
-We recommend immediately [rotating your application's client secret](./implementation.md#rotating-client-secrets) and contacting Adobe customer support if you wish to invalidate any existing tokens.
+We recommend immediately [rotating your application's client secret](implementation.md#rotating-client-secrets) and contacting Adobe customer support if you wish to invalidate any existing tokens.
 
 
 

src/pages/guides/authentication/ServerToServerAuthentication/implementation.md

@@ -13,7 +13,7 @@ The following guide goes over finer implementation details for OAuth Server-to-S
 
 ## Setting up the OAuth Server-to-Server credential
 
-Depending on the API or an Event to your project on the Adobe Developer Console, you can select the OAuth Server-to-Server credential. The OAuth Server-to-Server credential is available for all APIs and Events supporting the [Service Account (JWT) credential *(deprecated)*](./index.md#service-account-jwt-credential-deprecated).
+Depending on the API or an Event to your project on the Adobe Developer Console, you can select the OAuth Server-to-Server credential. The OAuth Server-to-Server credential is available for all APIs and Events supporting the [Service Account (JWT) credential *(deprecated)*](index.md#service-account-jwt-credential-deprecated).
 
 ### Credential Name
 

src/pages/guides/index.md

@@ -65,4 +65,4 @@ Use Project Filters to narrow your search when looking for a specific project. Y
 
 ### Project Activity Logs
 
-View who created or last modified a project by visiting the Project overview page. You can also view the exact set of changes made to the project in the last year (who, what, and when) by visiting the [Activity Logs](projects/index.md#view-a-projects-activity-log) tab within the Project.
+View who created or last modified a project by visiting the Project overview page. You can also view the exact set of changes made to the project in the last year (who, what, and when) by visiting the [Activity Logs](projects/index.md#view-a-projects-activity-log) tab within the Project.