diff --git a/docs/en/release-info/upgrading.md b/docs/en/release-info/upgrading.md
index 496b3b2961..28404c20b4 100644
--- a/docs/en/release-info/upgrading.md
+++ b/docs/en/release-info/upgrading.md
@@ -20,7 +20,7 @@ Run this command in the terminal while you are in the root folder of your soluti
 
 When you upgrade to a new version, it is good to check if there is a database schema change and upgrade your database schema if your database provider is **Entity Framework Core**;
 
-* Use `Add-Migration "Upgraded_To_Abp_8_2"` or a similar command in the Package Manager Console (PMC) to create a new migration (Set the `EntityFrameworkCore` as the Default project in the PMC and `.DbMigrator` as the Startup Project in the Solution Explorer, in the Visual Studio).
+* Use `Add-Migration "Upgraded_To_Abp_8_3"` or a similar command in the Package Manager Console (PMC) to create a new migration (Set the `EntityFrameworkCore` as the Default project in the PMC and `.DbMigrator` as the Startup Project in the Solution Explorer, in the Visual Studio).
 * Apply the database migrations to your database. If available, you can run the `.DbMigrator` application to upgrade the database and seed the initial data.
 
 > If `Add-Migration` generates an empty migration (that means no schema change), you can use `Remove-Migration` to delete it before executing the `.DbMigrator`.
@@ -57,4 +57,4 @@ Preview releases and nightly builds can help you to try new features and adapt y
 
 ## See Also
 
-* [Migration Guides](migration-guides)
\ No newline at end of file
+* [Migration Guides](migration-guides)