Fix grammar, broken link, and minor wording issues across docs

Author: tobihagemann

docs/desktop/admin-config.md

@@ -15,7 +15,7 @@ It is a system-level key-value file that persists across updates.
 Editing the *admin configuration* may require elevated privileges (i.e. admin or root permissions).
 :::
 
-The storage location of the Admin configuration file `config.properties` depends on the OS. The following table shows for each OS the storage path:
+The storage location of the admin configuration file `config.properties` depends on the OS. The following table shows the storage path for each OS:
 
 
 | OS      | Default Path                                                 |

docs/desktop/files-in-use.md

@@ -26,7 +26,7 @@ If another user is currently editing a file, Cryptomator can block opening that
 :::note
 The usage information is passed with the files being edited.
 Therefore, it requires either the vault residing on shared storage (for example, a network share) or file synchronization.
-In the latter case, it takes around 10s until the status is synchronized to other devices (depending on the sync app).
+In the latter case, it takes around 10 seconds until the status is synchronized to other devices (depending on the sync app).
 :::
 
 ## What You Will See {#what-you-will-see}
@@ -46,7 +46,7 @@ Use this only if you are sure it is safe, because forcing access can overwrite s
 We recommend the following sequence when receiving a "File is in use" notification:
 1. Ask the person shown in the notification whether they are still editing the file.
 1. If they already closed the file but it is still shown as "in use", use "Ignore Use Status".
-1. Open a file marked as in use without checking with teammates only in exceptional situations.
+1. Only open a file marked as in use without checking with teammates in exceptional situations.
 1. In that case, create a backup copy first to avoid losing edits.
 
 ## Stale Use Status {#stale-use-status}

docs/desktop/password-and-recovery-key.md

@@ -136,7 +136,7 @@ Available keychains are:
   Uses the KDE Wallet or the GNOME keyring to store your password.
   The password is only stored locally in the default KDE Wallet or the default GNOME keyring. Secret Service is the successor of KDE Wallet and GNOME keyring, as it works for both.
 
-  Requires KDE Wallet or GNOME keyring to be installed and running on your Linux system, with the default wallet, respectively keyring present.
+  Requires KDE Wallet or GNOME keyring to be installed and running on your Linux system, with the default wallet or keyring present.
 </details>
 
  There are also third-party plug-ins for Cryptomator that allow you to store vault passwords in external password managers:

docs/hub/admin.md

@@ -95,7 +95,7 @@ This feature is currently in **early access** and will be fully available in ver
 - **Emergency Access Recovery Aborted** – A council member aborted a running recovery process.
 
 :::note
-When a council member starts a recovery process both `Emergency Access Recovery Started` and `Emergency Access Recovery Approved` is logged.
+When a council member starts a recovery process, both `Emergency Access Recovery Started` and `Emergency Access Recovery Approved` are logged.
 :::
 
 #### Legacy {#event-type-legacy}
@@ -161,7 +161,7 @@ This configuration defines default [Emergency Access](emergency-access.md) value
 
 <Image src="/img/hub/admin-emergency-access.png" alt="Emergency Access" width="1440" height="658" />
 
-Enable `Enable Emergency Access` and configure:
+Activate `Enable Emergency Access` and configure:
 
 * `Required Keys`: Number of required key shares
 * `Keyholders`: Default council members (only activated users)

docs/hub/early-access.md

@@ -9,4 +9,4 @@ sidebar_position: 10
 These features are currently in **early access** and will be fully available in **Cryptomator Hub 1.5.0**.
 
 - [User & Group Management](/hub/user-group-management) — Manage users, groups, roles, and permissions directly in Hub
-- [Emergency Access](/hub/emergency-access) - Restore access to a vault in case of account loss or ownership issues
+- [Emergency Access](/hub/emergency-access) — Restore access to a vault in case of account loss or ownership issues

docs/hub/emergency-access.md

@@ -15,7 +15,7 @@ Its process requires a group of trusted users (the "council") to approve the rec
 When enough approvals are collected, the emergency change is completed and vault management access is restored.
 Technically, this is implemented using key splitting based on **[Shamir's Secret Sharing](https://en.wikipedia.org/wiki/Shamir%27s_secret_sharing)**.
 
-## Setup Emergency Access
+## Set Up Emergency Access
 
 The feature can be activated for new and existing vaults:
 
@@ -45,7 +45,7 @@ Use this quick guide to choose the right process:
 | Give vault access to different users (owners/members) | `Choose Vault Members` |
 | Remove access from specific users | `Choose Vault Members` |
 | Replace council members who approve emergency operations | `Change Emergency Access Council` |
-| Change how many council approvals are required (threshold) | Configurable in the [admin settings](../admin#emergency-access) |
+| Change how many council approvals are required (threshold) | Configurable in the [admin settings](admin.md#emergency-access) |
 
 :::note
 Starting a process automatically approves the process.
@@ -72,7 +72,7 @@ The minimum required number of members is configured in the [Admin settings](adm
 ## Approve a Recovery Process
 
 To view or approve running Emergency Access processes, open the `Emergency Access` list.
-If for a vault an Emergency Access process is running, the vault is displayed with a process button.
+If an Emergency Access process is running for a vault, the vault is displayed with a process button.
 If you haven't approved the process, the button includes `Approve now`.
 
 <Image src="/img/hub/emergency_access_vault_list_change_council_approve_now.png" alt="Emergency Access Vault List Approve Now" width="2560" height="1080" />