fix minor issues

infeo · infeo · commit a1014b7fafab · 2026-05-05T18:08:58.000+02:00
diff --git a/docs/desktop/password-and-recovery-key.mdx b/docs/desktop/password-and-recovery-key.mdx
@@ -14,7 +14,7 @@ So, [choosing a strong password](/docs/security/best-practices.mdx#good-password
 Additionally, a unique *recovery key* can be derived for each vault while creating its password or later.
 A *recovery key* allows you to create a new password if you forget the original one.
 Do note that the *recovery key* feature does not break encryption in any way.
-It is a human readable form of your decrypted [masterkey](/docs/security/architecture.mdx#masterkey) and therefore independent of the current vault password and highly confidential.
+It is a human-readable form of your decrypted [masterkey](/docs/security/architecture.mdx#masterkey) and therefore independent of the current vault password and highly confidential.
 Keep it as safe as your password.
 
 All actions can be carried out using the `Password` tab under vault options.
diff --git a/docs/desktop/setup.mdx b/docs/desktop/setup.mdx
@@ -6,7 +6,7 @@ sidebar_position: 1
 
 # Setup
 
-The Desktop version of Cryptomator is currently available for Windows, macOS, and Linux. 
+The Desktop version of Cryptomator is currently available for Windows, macOS, and Linux.
 Download and installation process varies depending on your operating system. Follow the instructions for your operating system.
 Ensure that your computer's specifications meet the system requirements required to run Cryptomator smoothly.
 
@@ -38,7 +38,7 @@ Change your [Gatekeeper settings](https://support.apple.com/HT202491) if macOS b
 
 Cryptomator is available on Linux via `Flatpak`, `PPA` and `AUR` package managers, and as an AppImage (an `.appimage` file).
 
-The easiest and recommended way of installing Cryptomator on Linux is by downloading Cryptomator's AppImage (an `.appimage` file) - as it works on almost all distributions. 
+The easiest and recommended way of installing Cryptomator on Linux is by downloading Cryptomator's AppImage (an `.appimage` file) - as it works on almost all distributions.
 Just remember to [make it executable](https://docs.appimage.org/user-guide/run-appimages.html#running-appimages) before you try to run it.
 
 Visit our [downloads page](https://cryptomator.org/downloads/#linux) to choose your preferred installation method.
diff --git a/docs/hub/access-vault.mdx b/docs/hub/access-vault.mdx
@@ -31,7 +31,7 @@ Cryptomator should open your default browser for authentication. If you're not a
 
 ### 3. Register Device {/* #register-device */}
 
-If you just did setup your account, a vault owner needs to grant you access for the requested vault as described [here](vault-management.mdx#update-permissions). Retry unlocking the vault after the vault owner granted you access.
+If you just setup your account, a vault owner needs to grant you access for the requested vault as described [here](vault-management.mdx#update-permissions). Retry unlocking the vault after the vault owner granted you access.
 
 <Image src="/img/hub/unlock-access-denied.png" alt="Access is denied since it has not been granted by a vault owner yet" width="715" height="541" />
 
diff --git a/docs/hub/deployment.mdx b/docs/hub/deployment.mdx
@@ -20,7 +20,7 @@ Cryptomator Hub is also offered as a hosted solution, including 99.5%-uptime gua
 1. Customize the template if needed (e.g., adjust the Ingress settings) and deploy the software stack to your cluster
 
 Afterwards you're done.
-You can now login to Cryptomator Hub and start [creating vaults](vault-management.mdx) or [add users](user-group-management.mdx).
+You can now log in to Cryptomator Hub and start [creating vaults](vault-management.mdx) or [add users](user-group-management.mdx).
 
 ## Hardware Requirements {/* #hardware-requirements */}
 
diff --git a/docs/hub/vault-management.mdx b/docs/hub/vault-management.mdx
@@ -72,7 +72,7 @@ Store it at a safe location, tick the checkbox and complete the setup by clickin
 
 :::warning
 The recovery key is **highly confidential**.
-It is a human readable form of the vault [masterkey](/docs/security/architecture.mdx#masterkey), which is used to encrypt your data and independent of the key management in Cryptomator Hub.
+It is a human-readable form of the vault [masterkey](/docs/security/architecture.mdx#masterkey), which is used to encrypt your data and independent of the key management in Cryptomator Hub.
 :::
 
 When the setup is finished, you have the opportunity to download the initial vault template and place it in your desired cloud storage location.
diff --git a/docs/misc/supported-cloud-services.mdx b/docs/misc/supported-cloud-services.mdx
@@ -49,7 +49,7 @@ The following Cloud Services are natively supported by Cryptomator for Android a
 
 [^no-accrescent]: Not supported by the [Accrescent variant](/docs/android/setup.mdx#accrescent) because this Cloud Service requires proprietary dependencies.
 
-[^file-providers]: Some Android and iOS apps integrate into the operating system's file manager with their own storage spaces to allow seamless access to their files via so called "File Providers." Cryptomator generally supports saving vaults in those spaces, but is dependent on those apps explicitly supporting access by other apps like Cryptomator. For more technical information about this see [here](https://github.com/cryptomator/android/issues/553) for Android and [here](https://github.com/cryptomator/ios/issues/51) for iOS.
+[^file-providers]: Some Android and iOS apps integrate into the operating system's file manager with their own storage spaces to allow seamless access to their files via "File Providers." Cryptomator generally supports saving vaults in those spaces, but is dependent on those apps explicitly supporting access by other apps like Cryptomator. For more technical information about this see [here](https://github.com/cryptomator/android/issues/553) for Android and [here](https://github.com/cryptomator/ios/issues/51) for iOS.
 
 [^webdav-list]: Please see [Cloud Services with WebDAV support](#cloud-services-with-webdav-support) for a non-exhaustive list of Cloud Services and information about accessing them with WebDAV.
 
diff --git a/docs/security/architecture.mdx b/docs/security/architecture.mdx
@@ -74,7 +74,7 @@ These keys are themselves protected and can be retrieved using, either of the fo
 
 ### Using Cryptomator Hub {/* #using-cryptomator-hub */}
 
-When using [Cryptomator Hub](/docs/hub/access-vault.mdx), the encrypted raw masterkey can be retrieved from a the server component.
+When using [Cryptomator Hub](/docs/hub/access-vault.mdx), the encrypted raw masterkey can be retrieved from the server component.
 
 :::note
 If a vault is managed by Cryptomator Hub, the `vault.cryptomator`'s `kid` field will point to the resource URI of said vault on the corresponding Hub instance, prefixed by `hub+`.
