Fix Sandbox whitelist guide path

callflows/authorization/authorization_openapi.yaml

@@ -27,7 +27,7 @@ paths:
       description: |
         Authorizes an application to access a resource from the user device
 
-        **NOTE**: In case you are using our Sandbox as a host, please take into account that the `login_hint` parameter, although optional according to the OpenID Connect specification, is mandatory in order to inform about the end-user identifier so the Sandbox checks its whitelist for privacy reasons. Check the [Whitelist](/docs/sandbox/whitelist) guide for more information.
+        **NOTE**: In case you are using our Sandbox as a host, please take into account that the `login_hint` parameter, although optional according to the OpenID Connect specification, is mandatory in order to inform about the end-user identifier so the Sandbox checks its whitelist for privacy reasons. Check the [Whitelist](/docs/whitelist) guide for more information.
       operationId: authorize
       parameters: 
         - name: response_type

gettingstarted/sandbox/whitelist.md

@@ -1,15 +1,14 @@
 ---
 title: Sandbox line whitelist
 excerpt: Get familiar with our Sandbox's whitelist and how it's meant to guard our operators' customers' privacy.
-path: docs/sandbox/whitelist
 category: 66d5624a492663000f4ed527
 ---
 
 ## On privacy
 
 Having actual operator's mobile lines in you whitelist is mandatory for testing the APIs in the production mode. This way, you as a tester can make real calls to the operators' APIs and get real responses without compromising anyone else's privacy by accessing just your own line's data.
 
-Check the [Privacy](../../about/privacy.md) section for more information on why Open Gateway is Privacy by Design.
+Check the [Privacy](/docs/privacy.md) section for more information on why Open Gateway is Privacy by Design.
 
 ## Adding your mobile lines to the whitelist