resolve conflicts

Author: Ayush Bherwani

developer-tools/dashboard/get-started/create-api.md

@@ -38,7 +38,6 @@ requiring an API key secret or JWTs with each API request.
 We recommend the following best practices when creating your API keys:
 
 - Group API key endpoints by environment. For example, create separate API keys for production or development environments.
-- Group API key endpoints by groups or individuals [sharing the API key](../how-to/project-sharing.md).
 - Limit the number of networks or services per API key only to the necessary endpoints.
 - Group the API key endpoints based on shared security considerations such as
   [allowlists](../how-to/secure-an-api/use-an-allowlist.md) or

developer-tools/dashboard/how-to/project-sharing.md

@@ -24,17 +24,17 @@ Select one of the cards below to learn more about using the dashboard.
 <CardList
   items={[
     {
-      href: "get-started/create-api",
+      href: "./get-started/create-api",
       title: "Create an API key",
       description: "Learn how to create an API key that allows you to make API calls."
     },
     {
-      href: "how-to/secure-an-api/api-key",
+      href: "./how-to/secure-an-api/api-key",
       title: "Secure your API key",
       description: "Learn how to secure your API key to avoid unwanted costs and unauthorized access."
     },
     {
-      href: "how-to/dashboard-stats",
+      href: "./how-to/dashboard-stats",
       title: "Monitor API call stats",
       description: "Learn how to use the dashboard to view API call stats."
     }