diff --git a/src/content/docs/start/migrate/from-tauri-1.mdx b/src/content/docs/start/migrate/from-tauri-1.mdx
index 272a0b9908..fa76cd3572 100644
--- a/src/content/docs/start/migrate/from-tauri-1.mdx
+++ b/src/content/docs/start/migrate/from-tauri-1.mdx
@@ -63,8 +63,6 @@ The Tauri v2 CLI includes a `migrate` command that automates most of the process
     cargo tauri migrate'
 />
 
-{/* TODO: 2.0 */}
-
 Learn more about the `migrate` command in the [Command Line Interface reference](/reference/cli/#migrate)
 
 ## Summary of Changes
@@ -199,6 +197,10 @@ In order to support it, we renamed the Rust `Window` type to `WebviewWindow` and
 
 The `WebviewWindow` JS API type is now re-exported from `@tauri-apps/api/webviewWindow` instead of `@tauri-apps/api/window`.
 
+### New origin URL on Windows
+
+On Windows the frontend files in production apps are now hosted on `http://tauri.localhost` instead of `https://tauri.localhost`. Because of this IndexedDB, LocalStorage and Cookies will be reset unless `dangerousUseHttpScheme` was used in v1. To prevent this you can set `app > windows > useHttpsScheme` to `true` or use `WebviewWindowBuilder::use_https_scheme` to keep using the `https` scheme.
+
 ## Detailed Migration Steps
 
 Common scenarios you may encounter when migrating your Tauri 1.0 app to Tauri 2.0.