Fix broken urls (#57)

* Fix broken urls * another fix * Update gettingstarted/sandbox/usethesandbox.md Co-authored-by: Diego Rivera <diego.rivera@telefonica.com> * suggestion --------- Co-authored-by: Diego Rivera <diego.rivera@telefonica.com>
Telefonica · Dec 4, 2024 · dbfda8d · dbfda8d
1 parent 533688e
commit dbfda8d
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/gettingstarted/sandbox/usethesandbox.md b/gettingstarted/sandbox/usethesandbox.md
@@ -8,7 +8,7 @@ category: 66d5624a492663000f4ed527
 
 Open Gateway APIs access is granted to applications, not developers, so every application can have limited access to the scope and for the purpose it needs.
 
-[More information on Privacy](../../about/privacy.md)
+[More information on Privacy](/docs/privacy)
 
 Therefore the way to get credentials to test the APIs is to register an application in the Sandbox console. You will use your application credentials to authenticate your requests to the APIs from any test you code no matter if it is actually a comprehensive application or just a tiny script to run from the a command line interface.
 
@@ -83,11 +83,11 @@ Note that if you selected the Production mode, you will have to wait for the app
 
 So far you have used the Sandbox console to register your application as the client to the APIs, which means your application is the entity granted access with its credentials.
 
-> You can use this credentials directly in the [API reference](../apireference.md)
+> You can use this credentials directly in the [API reference](/reference)
 
 Now you will use such credentials to effectively consume de APIs from your code. You can use any programming language and any platform that supports HTTP requests, or you can use the Sandbox SDK for convenience. Our Open Gateway Sandbox provides you with a Python SDK and will publish SDKs in other common languages soon.
 
-[Check the pros and cons of using HTTP integration or SDKs to consume the APIs](./sdkreference.md)
+[Check the pros and cons of using HTTP integration or SDKs to consume the APIs](./sdkreference)
 
 When it comes to our Sandbox's SDK, the following particular considerations apply:
 - Once you shift to a Channel Partner in a commercial stage, your production code will need to use their SDKs instead of the Sandbox's one you used for testing and prototyping or, in the worst case, you will have to use the HTTP integration method instead if no SDK is available for your app's language.
@@ -102,10 +102,10 @@ The path URL to add to the base URL for each API is defined in the API reference
 
 #### API reference
 
-You can check the OpenAPI v3 specification of each API in the list of [Available APIs](../../catalog/available.md) or in the [API Roadmap](../../catalog/roadmap.md).
+You can check the OpenAPI v3 specification of each API in the [API Reference](/reference) section.
 
 You will be able to test the APIs from their specification pages on the Sandbox by setting the `host` variable to its default value, which is the Sandbox API gateway base URL.
 
 ### Sandbox SDK reference
 
-You can check the reference of the current Sandbox SDK reference in the [Python Sandbox SDK](./sdkreference.md) guide. The scope of the APIs covered and the programming languages supported will be extended progressively according to the Sandbox roadmap.
+You can check the reference of the current Sandbox SDK reference in the [Python Sandbox SDK](./sdkreference) guide. The scope of the APIs covered and the programming languages supported will be extended progressively according to the Sandbox roadmap.