Fix links

Author: mortenlj

docs/persistence/postgres/how-to/existing-instance-private-ip.md

@@ -20,7 +20,7 @@ Under `Events` you should see an error detailing the reason for the failure.
 If you see a message that says `Cannot assign a private IP address for an existing Cloud SQL instance in a Shared VPC`, 
 the problem is that the deletion of the application resulted in a bit of information being lost, which causes nais to attempt to assign a private IP to the instance.
 
-An [SQLInstance](../../persistence/postgres/explanations/cloud-sql-instance.md) created before 2024-04-18 will have a public IP address, and can not be updated to have a private IP address.
+An [SQLInstance](../explanations/cloud-sql-instance.md) created before 2024-04-18 will have a public IP address, and can not be updated to have a private IP address.
 This error occurs when the SQLInstance resource in the cluster has been deleted, without the corresponding instance actually being deleted in GCP.
 In this case, nais is unable to detect that the instance has a public IP, and will attempt to assign a private IP, which is not possible.
 

docs/workloads/how-to/troubleshooting.md

@@ -182,9 +182,9 @@ When the SQLInstance is not ready, either because it is still being created, or
 Possible causes and how to resolve them:
 
  - An existing certificate blocks creation of a new one.  
-   See [Certification sync issues](./postgres/how-to/certification-sync-issues.md) for more information.
+   See [Certification sync issues](../../persistence/postgres/how-to/certification-sync-issues.md) for more information.
  - Attempting to assign a private IP to an existing Cloud SQL instance. 
-   See [Failing to assign private IP to an existing Cloud SQL instance](./postgres/how-to/existing-instance-private-ip.md) for more information.
+   See [Failing to assign private IP to an existing Cloud SQL instance](../../persistence/postgres/how-to/existing-instance-private-ip.md) for more information.
 
 ### Step 4. Ask for help