updated docs links

Author: tobihagemann

content/blog/2022-01-11-ios-vulnerability.de.md

@@ -45,7 +45,7 @@ Yes, the vaults themselves are still fully protected, regardless of which cloud
 
 ## Why is there decrypted data in the first place?
 
-At some point, you need to have cleartext data, otherwise you can’t work with them. Cryptomator is fully integrated into the Files app, which means that it is bound to and limited by the File Provider Extension API. It requires to have readable (cleartext) data readily available. Keep in mind that Cryptomator’s [target is to ensure privacy in the cloud](https://docs.cryptomator.org/en/latest/security/security-target/) and not on the device itself.
+At some point, you need to have cleartext data, otherwise you can’t work with them. Cryptomator is fully integrated into the Files app, which means that it is bound to and limited by the File Provider Extension API. It requires to have readable (cleartext) data readily available. Keep in mind that Cryptomator’s [target is to ensure privacy in the cloud](https://docs.cryptomator.org/security/security-target/) and not on the device itself.
 
 ## Are there any other plans regarding the local cache?
 

content/blog/2022-01-11-ios-vulnerability.en.md

@@ -44,7 +44,7 @@ Yes, the vaults themselves are still fully protected, regardless of which cloud
 
 ## Why is there decrypted data in the first place?
 
-At some point, you need to have cleartext data, otherwise you can’t work with them. Cryptomator is fully integrated into the Files app, which means that it is bound to and limited by the File Provider Extension API. It requires to have readable (cleartext) data readily available. Keep in mind that Cryptomator’s [target is to ensure privacy in the cloud](https://docs.cryptomator.org/en/latest/security/security-target/) and not on the device itself.
+At some point, you need to have cleartext data, otherwise you can’t work with them. Cryptomator is fully integrated into the Files app, which means that it is bound to and limited by the File Provider Extension API. It requires to have readable (cleartext) data readily available. Keep in mind that Cryptomator’s [target is to ensure privacy in the cloud](https://docs.cryptomator.org/security/security-target/) and not on the device itself.
 
 ## Are there any other plans regarding the local cache?
 

content/blog/2022-12-08-boxcryptor-shuts-down-find-your-cloud-encryption-alternative.en.md

@@ -52,4 +52,4 @@ Switching from Boxcryptor to Cryptomator is simple. Boxcryptor provides an [off-
 
 And you have successfully created your first vault.
 
-If you want, you can unlock it immediately and reveal the virtual drive. From now on, you can store your sensitive files here, e.g., the data that you previously encrypted with Boxcryptor, in order to encrypt them in the cloud with Cryptomator from now on. [Detailed instructions are available here.](https://docs.cryptomator.org/en/latest/desktop/adding-vaults/)
+If you want, you can unlock it immediately and reveal the virtual drive. From now on, you can store your sensitive files here, e.g., the data that you previously encrypted with Boxcryptor, in order to encrypt them in the cloud with Cryptomator from now on. [Detailed instructions are available here.](https://docs.cryptomator.org/desktop/adding-vaults/)

content/blog/2023-02-01-1.7.0-what-you-need-to-know.de.md

@@ -16,7 +16,7 @@ Wir sind sehr stolz auf diese Version, da sie technische Altlasten beseitigt, la
 </figure>
 
 ## Verschlüsselte Datei finden
-Wie bereits erwähnt, enthält Cryptomator 1.7.0 eine Funktion, die schon lange gewünscht wurde: Die Suche nach dem verschlüsselten Gegenstück einer Datei. Das klingt kompliziert, ist aber leicht zu verstehen, wenn man sich vor Augen hält, dass Cryptomator Dateinamen verschlüsselt und die Verzeichnisstruktur verschleiert ([siehe unsere Dokumentation](https://docs.cryptomator.org/en/latest/security/architecture/#filename-encryption)).
+Wie bereits erwähnt, enthält Cryptomator 1.7.0 eine Funktion, die schon lange gewünscht wurde: Die Suche nach dem verschlüsselten Gegenstück einer Datei. Das klingt kompliziert, ist aber leicht zu verstehen, wenn man sich vor Augen hält, dass Cryptomator Dateinamen verschlüsselt und die Verzeichnisstruktur verschleiert ([siehe unsere Dokumentation](https://docs.cryptomator.org/security/vault/#filename-encryption)).
 
 Vor Version 1.7.0 musste man anhand der genauen Zeitstempel erraten, welche verschlüsselte Datei zu welcher Klartextdatei gehört. Jetzt kannst du, sobald der Tresor entsperrt ist, das verschlüsselte Gegenstück zu jeder Datei im Tresor herausfinden, indem du auf „Verschlüsselte Datei finden“ klickst und eine Datei im Tresor auswählst. Du kannst auch einfach Dateien aus deinem Tresor auf diese Schaltfläche ziehen. Überzeuge dich selbst in diesem kurzen Video:
 

content/blog/2023-02-01-1.7.0-what-you-need-to-know.en.md

@@ -16,7 +16,7 @@ We are very proud of this release, as it eliminates technical debt, delivers lon
 </figure>
 
 ## Locate Encrypted File
-As already mentioned, Cryptomator 1.7.0 includes a feature that has been requested for a very long time: Locating the encrypted counterpart of a file. Sounds complex, but once you remember that Cryptomator encrypts filenames and obfuscates the directory structure ([see our docs](https://docs.cryptomator.org/en/latest/security/architecture/#filename-encryption)), it is easy to understand.
+As already mentioned, Cryptomator 1.7.0 includes a feature that has been requested for a very long time: Locating the encrypted counterpart of a file. Sounds complex, but once you remember that Cryptomator encrypts filenames and obfuscates the directory structure ([see our docs](https://docs.cryptomator.org/security/vault/#filename-encryption)), it is easy to understand.
 
 Prior to 1.7.0, you had to guess which encrypted file corresponds to which cleartext file based on the exact timestamps. Now, once the vault is unlocked, the encrypted counterpart of any file in the vault can be revealed by clicking on the "Locate Encrypted File" button and selecting a file in the vault. Or you can simply drag and drop the files from your vault onto this button. See for yourself in this short video:
 

content/blog/2023-08-11-hub-1.2.0.de.md

@@ -24,7 +24,7 @@ Unsere neue „Benutzerprofil“-Seite zentralisiert das Gerätemanagement und d
 
 ## :arrow_up: Upgrade-Informationen
 
-Ein Upgrade auf 1.2.0 ist einfach. Wenn du die stabile Version `stable` verwendest, musst du nur das Image pullen und den Service neu starten. Andernfalls aktualisiere die Versionsnummer in deiner Docker Compose- oder Kubernetes-Spec-Datei, bevor du den Service neu startest. Denke daran, immer ein [Backup deiner Daten](https://docs.cryptomator.org/en/latest/hub/setup/#backup) zu erstellen, insbesondere vor dem Upgrade. Bei Managed-Instanzen kannst du sicher sein, dass du bereits die neueste Version verwendest.
+Ein Upgrade auf 1.2.0 ist einfach. Wenn du die stabile Version `stable` verwendest, musst du nur das Image pullen und den Service neu starten. Andernfalls aktualisiere die Versionsnummer in deiner Docker Compose- oder Kubernetes-Spec-Datei, bevor du den Service neu startest. Denke daran, immer ein [Backup deiner Daten](https://docs.cryptomator.org/hub/deployment/#backup) zu erstellen, insbesondere vor dem Upgrade. Bei Managed-Instanzen kannst du sicher sein, dass du bereits die neueste Version verwendest.
 
 ## :next_track_button: Was kommt als Nächstes?
 

content/blog/2023-08-11-hub-1.2.0.en.md

@@ -24,7 +24,7 @@ Our new "User Profile" page centralizes device management and user settings in o
 
 ## :arrow_up: Upgrade Info
 
-Upgrading to 1.2.0 is simple. If you are on the `stable` lane, you just have to pull the image and restart the service. Otherwise, update the version number in your Docker Compose or Kubernetes spec file before you restart the service. Remember to always [back up your data](https://docs.cryptomator.org/en/latest/hub/setup/#backup), especially before upgrading. For managed instances, rest assured, you're already on the latest version.
+Upgrading to 1.2.0 is simple. If you are on the `stable` lane, you just have to pull the image and restart the service. Otherwise, update the version number in your Docker Compose or Kubernetes spec file before you restart the service. Remember to always [back up your data](https://docs.cryptomator.org/hub/deployment/#backup), especially before upgrading. For managed instances, rest assured, you're already on the latest version.
 
 ## :next_track_button: What's Next
 

content/blog/2023-12-01-hub-1.3.0.de.md

@@ -18,7 +18,7 @@ Dieser Abschnitt ist nur für Administratoren relevant, die ihre eigene Cryptoma
 
 Wenn du Administrator einer selbst gehosteten Cryptomator Hub-Instanz bist, führe bitte die folgenden Schritte aus, um Cryptomator Hub zu aktualisieren:
 
-1. [Sichere die Datenbank](https://docs.cryptomator.org/en/latest/hub/setup/#backup). **:warning: Die Bedeutung eines funktionierenden Backups kann nicht hoch genug eingeschätzt werden.**
+1. [Sichere die Datenbank](https://docs.cryptomator.org/hub/deployment/#backup). **:warning: Die Bedeutung eines funktionierenden Backups kann nicht hoch genug eingeschätzt werden.**
 2. Aktualisiere das Container-Image auf die neueste Version: `ghcr.io/cryptomator/hub:1.3.0`
     - Überspringe diesen Schritt, wenn du das `stable` Tag verwendest. Wir werden den `stable`-Tag in ein paar Wochen aktualisieren, um auf die neue Version zu verweisen.
 3. Wende die Änderungen in deinem Container-Orchestrator an. Überwache den Status des Pods, bevor du fortfährst.

content/blog/2023-12-01-hub-1.3.0.en.md

@@ -18,7 +18,7 @@ This section is only relevant for administrators who host their own Cryptomator
 
 As mentioned above, if you're an administrator of a self-hosted Cryptomator Hub instance, follow these steps to update Cryptomator Hub:
 
-1. [Back up the database](https://docs.cryptomator.org/en/latest/hub/setup/#backup). **:warning: The importance of a working backup cannot be overstated.**
+1. [Back up the database](https://docs.cryptomator.org/hub/deployment/#backup). **:warning: The importance of a working backup cannot be overstated.**
 2. Refresh your container image to the latest version: `ghcr.io/cryptomator/hub:1.3.0`
     - Skip this step if you're using the `stable` tag. We will update the `stable` tag to point to the new version in a couple of weeks.
 3. Implement the changes within your container orchestrator. Monitor for healthy pod statuses before proceeding.

content/blog/2025-01-24-android-accrescent.de.md

@@ -11,7 +11,7 @@ summary: "Cryptomator für Android ist jetzt auf Accrescent verfügbar und biete
 
 Wir freuen uns, ankündigen zu können, dass Cryptomator für Android jetzt auf [Accrescent](https://accrescent.app/app/org.cryptomator) verfügbar ist – einem datenschutzorientierten App-Store mit robusten Sicherheitsfunktionen.
 
-Dies erweitert unsere bestehenden Vertriebskanäle, darunter [Google Play](https://docs.cryptomator.org/en/latest/android/setup/#google-play-store), [APK Store](https://docs.cryptomator.org/en/latest/android/setup/#apk-store) und F-Droid (sowohl [unser Repository](https://docs.cryptomator.org/en/latest/android/setup/#cryptomator-f-droid-repository) als auch das [Haupt-Repository](https://docs.cryptomator.org/en/latest/android/setup/#main-f-droid-repository)). Warum haben wir einen weiteren Vertriebskanal hinzugefügt?
+Dies erweitert unsere bestehenden Vertriebskanäle, darunter [Google Play](https://docs.cryptomator.org/android/setup/#google-play-store), [APK Store](https://docs.cryptomator.org/android/setup/#apk-store) und F-Droid (sowohl [unser Repository](https://docs.cryptomator.org/android/setup/#cryptomator-f-droid-repository) als auch das [Haupt-Repository](https://docs.cryptomator.org/android/setup/#main-f-droid-repository)). Warum haben wir einen weiteren Vertriebskanal hinzugefügt?
 
 ## Warum Accrescent?
 

content/blog/2025-01-24-android-accrescent.en.md

@@ -10,7 +10,7 @@ summary: "Cryptomator for Android is now available on Accrescent, offering enhan
 
 We are excited to announce that Cryptomator for Android is now available on [Accrescent](https://accrescent.app/app/org.cryptomator), a privacy-focused app store with robust security features.
 
-This addition complements our existing distribution channels, including [Google Play](https://docs.cryptomator.org/en/latest/android/setup/#google-play-store), [APK Store](https://docs.cryptomator.org/en/latest/android/setup/#apk-store), and F-Droid (both [our repository](https://docs.cryptomator.org/en/latest/android/setup/#cryptomator-f-droid-repository) and the [main repository](https://docs.cryptomator.org/en/latest/android/setup/#main-f-droid-repository)). So why did we choose to add another distribution channel?
+This addition complements our existing distribution channels, including [Google Play](https://docs.cryptomator.org/android/setup/#google-play-store), [APK Store](https://docs.cryptomator.org/android/setup/#apk-store), and F-Droid (both [our repository](https://docs.cryptomator.org/android/setup/#cryptomator-f-droid-repository) and the [main repository](https://docs.cryptomator.org/android/setup/#main-f-droid-repository)). So why did we choose to add another distribution channel?
 
 ## Why Accrescent?