diff --git a/docs/misc/dev/configure-sqlite-wasm.md b/docs/misc/dev/configure-sqlite-wasm.md
deleted file mode 100644
index 9084dd5e..00000000
--- a/docs/misc/dev/configure-sqlite-wasm.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-layout: default
-title: Configure SQLite for use with WebAssembly
-parent: Development
-grand_parent: Miscellaneous
-nav_order: 2
----
-
-# Configure SQLite for use with WebAssembly
-To configure SQLite for use with WebAssembly follow these steps:
-
-1. Add NuGet package
-```
-dotnet add package SQLitePCLRaw.bundle_e_sqlite3
-```
-
-2. Modify .csproj and add the following:
-```xml
-    <PropertyGroup>
-        <WasmBuildNative>true</WasmBuildNative>
-    </PropertyGroup>
-```
-
-3. Make sure the "wasm-tools" workload is installed on the local machine in order to build the project:
-```
-dotnet workload install wasm-tools
-```
diff --git a/docs/misc/dev/enable-webauthn-pfr-chrome.md b/docs/misc/dev/enable-webauthn-pfr-chrome.md
index a25d8693..157e7454 100644
--- a/docs/misc/dev/enable-webauthn-pfr-chrome.md
+++ b/docs/misc/dev/enable-webauthn-pfr-chrome.md
@@ -7,9 +7,7 @@ nav_order: 9
 ---
 
 # WebAuthn
-The webauthn implementation in order to quick unlock the vault requires the use of a FIDO2 authenticator.
-
-This can be either the built-in browser authenticator or an external authenticator like a Yubikey.
+Webauthn allows to quick unlock the vault. This can be either the built-in browser authenticator or an external authenticator like a Yubikey.
 
 At the time of writing (2024-10-04), only some browsers support the required PRF extension. In order to make it work in Chrome, you need to enable the PRF extension in the browser settings.
 
@@ -19,3 +17,4 @@ At the time of writing (2024-10-04), only some browsers support the required PRF
 2. Enable the `Experimental Web Platform features` flag.
 3. Restart the browser.
 4. Now it should be possible to use the built-in chrome password manager to unlock the vault.
+5. Go to Menu -> Security Settings -> Quick Vault Unlock and enable it.
diff --git a/docs/misc/dev/run-github-actions-locally.md b/docs/misc/dev/run-github-actions-locally.md
index c519486b..24a3d1b1 100644
--- a/docs/misc/dev/run-github-actions-locally.md
+++ b/docs/misc/dev/run-github-actions-locally.md
@@ -1,6 +1,6 @@
 ---
 layout: default
-title: 1. Run GitHub Actions Locally
+title: Run GitHub Actions Locally
 parent: Development
 grand_parent: Miscellaneous
 nav_order: 9
diff --git a/docs/misc/dev/upgrade-ef-client-model.md b/docs/misc/dev/upgrade-ef-client-model.md
index 521ee103..015588cc 100644
--- a/docs/misc/dev/upgrade-ef-client-model.md
+++ b/docs/misc/dev/upgrade-ef-client-model.md
@@ -19,4 +19,4 @@ To upgrade the AliasClientDb EF model, follow these steps:
 dotnet ef migrations add "1.0.0-<migration-name>"
 ```
 4. On the next login of a user, they will be prompted (required) to upgrade their database schema to the latest version.
-Make sure to manually test this.
+Make sure to manually test that the migration works as expected.
diff --git a/docs/misc/dev/upgrade-ef-server-model.md b/docs/misc/dev/upgrade-ef-server-model.md
index 80415a50..62d6f314 100644
--- a/docs/misc/dev/upgrade-ef-server-model.md
+++ b/docs/misc/dev/upgrade-ef-server-model.md
@@ -1,6 +1,6 @@
 ---
 layout: default
-title: Upgrade the AliasClientDb EF model
+title: Upgrade the AliasServerDb EF model
 parent: Development
 grand_parent: Miscellaneous
 nav_order: 3
diff --git a/docs/misc/release/create-new-release.md b/docs/misc/release/create-new-release.md
index 2f27d30b..d07ccbe6 100644
--- a/docs/misc/release/create-new-release.md
+++ b/docs/misc/release/create-new-release.md
@@ -17,7 +17,7 @@ Follow the steps in the checklist below to prepare a new release.
 ## Docker Images
 If docker containers have been added or removed:
 - [ ] Verify that `.github/workflows/publish-docker-images.yml` contains references to all docker images that need to be published.
-- [ ] Update `install.sh` and verify that the `images()` array that takes care of pulling the images from the GitHub Container Registry is updated.
+- [ ] Update `install.sh` and verify that the `images=()` array that takes care of pulling the images from the GitHub Container Registry is updated.
 
 ## Manual Testing (since v0.10.0+)
 - [ ] Verify that the db migration from SQLite to PostgreSQL works. This needs to be tested manually until the SQLite support is removed. Test with: `./install.sh db-migrate` on an existing installation that has a SQLite database in `./database/AliasServerDb.sqlite`.
diff --git a/install.sh b/install.sh
index f5a9851d..a2bc7fcf 100755
--- a/install.sh
+++ b/install.sh
@@ -1,5 +1,5 @@
 #!/bin/bash
-# @version 0.9.4
+# @version 0.10.0
 
 # Repository information used for downloading files and images from GitHub
 REPO_OWNER="lanedirt"
@@ -1784,6 +1784,10 @@ handle_migrate_db() {
             ${GITHUB_CONTAINER_REGISTRY}-installcli:0.10.0 migrate-sqlite "/sqlite/${SQLITE_DB_NAME}" "Host=postgres;Database=aliasvault;Username=aliasvault;Password=${POSTGRES_PASSWORD}"
      fi
 
+    # Starting services again
+    printf "${CYAN}> Starting services...${NC}\n"
+    docker compose start api admin task-runner smtp reverse-proxy
+
     printf "${GREEN}> Check migration output above for details.${NC}\n"
 }
 
diff --git a/src/Shared/AliasVault.Shared.Core/AppInfo.cs b/src/Shared/AliasVault.Shared.Core/AppInfo.cs
index 6b9a84b2..2acf0c54 100644
--- a/src/Shared/AliasVault.Shared.Core/AppInfo.cs
+++ b/src/Shared/AliasVault.Shared.Core/AppInfo.cs
@@ -25,12 +25,12 @@ public static class AppInfo
     /// <summary>
     /// Gets the minor version number.
     /// </summary>
-    public const int VersionMinor = 9;
+    public const int VersionMinor = 10;
 
     /// <summary>
     /// Gets the patch version number.
     /// </summary>
-    public const int VersionPatch = 4;
+    public const int VersionPatch = 0;
 
     /// <summary>
     /// Gets the build number, typically used in CI/CD pipelines.