Replace some relative urls

website/docs/reference/environment-import-export.mdx

@@ -14,7 +14,7 @@ import SearchPriority from '@site/src/components/SearchPriority';
 
 :::caution Removal notice
 
-Api admin state is deprecated from version 5 and removed from version 6. We recommend using the new [Environment Import & Export](/reference/deploy/environment-import-export).
+Api admin state is deprecated from version 5 and removed from version 6. We recommend using the new [Environment Import & Export](/how-to/how-to-environment).
 
 :::
 

website/docs/reference/public-signup.mdx

@@ -16,4 +16,4 @@ You can have only one active invite token at any given time. If an active token
 
 As an Admin, you can create, update, and delete invite tokens through the Unleash Admin UI in **Admin settings > User config > Users > Create invite link**.
 
-Alternatively, you can use the [Admin API](../reference/api/unleash/public-signup-tokens.tag.mdx) to manage the public invite token.
+Alternatively, you can use the [Admin API](../reference/api/unleash/public-signup-tokens.tag.mdx) to manage the public invite token.

website/docs/troubleshooting.mdx

@@ -110,7 +110,7 @@ Cross-Origin Resource Sharing (CORS) issues can prevent your client-side applica
 -   Define the allowed origins (e.g., `https://your-app.com`).
     -   **For troubleshooting:** You can temporarily set the allowed origin to `*` (a single asterisk) to allow all origins. This helps confirm if CORS is the root cause.
     -   **Important Security Note:** Using `*` in production is generally discouraged. Always restrict origins to only those that require access.
--   These settings can also be managed via the [Unleash API](/reference/api/unleash).
+-   These settings can also be managed via the [Unleash API](/api-overview).
 
 ### Configuring CORS for Unleash Edge