Use absolute links (#129)

...to simplify documentation import.

Author: BotondGalxc

docs/manual_restore.md

@@ -5,8 +5,8 @@ The advantage of the backup-restore-sidecar is that it automatically restores th
 1. Take a copy of your existing stateful set by running `kubectl get sts -o yaml <your-database-sts>`
 2. Now, get into a clean state, i.e. delete the existing stateful set and the pvc of your database
 3. Deploy the exact stateful set you had but only with the backup-restore-sidecar container and tail some file such that container does not die. This is your "helper" stateful set, which you can use for manual administration. 
-   - For postgres check the example [here](../deploy/postgres_manual_restore.yaml)
-   - For rethinkdb check the example [here](../deploy/rethinkdb_manual_restore.yaml)
+   - For postgres check the example [here](https://github.com/metal-stack/backup-restore-sidecar/blob/master/deploy/postgres_manual_restore.yaml)
+   - For rethinkdb check the example [here](https://github.com/metal-stack/backup-restore-sidecar/blob/master/deploy/rethinkdb_manual_restore.yaml)
 4. Enter the container in your "helper" pod by running `kubectl exec -it <your-database-helper-pod>-0 -c backup-restore-sidecar -- bash`
 5. Inside the container, you can view the existing backup versions using `backup-restore-sidecar restore ls`
 6. Choose the version to restore by running `backup-restore-sidecar restore <version>`