Revise update instructions for version 3.1000

Updated module references and corrected grammatical errors in the documentation for version 3.1000.

Author: OlegoO

docs/release-information/update-to-version-3-1000/update-platform-and-modules-to-3-1000.md

@@ -31,21 +31,21 @@ Stability is a cornerstone of this update. By leveraging the advancements in .NE
 
 1. **Install .NET 10:** Begin by ensuring that you have .NET 10 installed on your system. Follow the official installation guidelines to set up the environment for the upgrade: https://dotnet.microsoft.com/en-us/download/dotnet/10.0
 2. **Update Virto Commerce Platform to v3.1000 or later**
-3. **Update Customer Module and XAPI to v3.1000 or later**
+3. **Update [Customer](https://github.com/VirtoCommerce/vc-module-customer) and [XAPI](https://github.com/VirtoCommerce/vc-module-x-api) modules to v3.1000 or later**
 4. **Update other Virto Commerce Modules to [Stable Release 12](https://docs.virtocommerce.org/platform/user-guide/1.0/versions/v3-2025-S12/) and later**. 
 
-> By default, Virto Commerce Platform on .NET10 are backward compatible with previous platform stable release on .NET8 (3.800+). However, it is recommended to update custom modules to the latest versions to leverage new features and improvements.
+> By default, Virto Commerce Platform on .NET10 is backwards compatible with previous platform stable releases on .NET8 (3.800+). However, it is recommended to update custom modules to the latest versions to leverage new features and improvements.
 
 ## Known Limitations and Breaking Changes
 
-If you find any new breaking changes, submit an question on [Virto Commerce Community](https://www.virtocommerce.org/c/support/12).
+If you find any new breaking changes, submit a question on [Virto Commerce Community](https://www.virtocommerce.org/c/support/12).
 
 ### Pomelo.EntityFrameworkCore.MySql v9.0.0
 Virto Commerce uses Pomelo.EntityFrameworkCore.MySql 9.0.0 for MySql.
 
 ### Exception is thrown when applying migrations if there are pending model changes
 
-Starting with EF Core 9.0, if the model has pending changes compared to the last migration an exception is thrown when dotnet ef database update, Migrate or MigrateAsync is called:
+Starting with EF Core 9.0, if the model has pending changes compared to the last migration, an exception is thrown when dotnet ef database update, Migrate or MigrateAsync is called:
 
 The model for context 'DbContext' has pending changes. Add a new migration before updating the database. This exception can be suppressed or logged by passing event ID 'RelationalEventId.PendingModelChangesWarning' to the 'ConfigureWarnings' method in 'DbContext.OnConfiguring' or 'AddDbContext'.
 
@@ -56,12 +56,12 @@ You can find more information about PendingModelChangesWarning warning by [follo
 ### Breaking changes in Microsoft.OpenApi
 
 Virto Commerce updated Microsoft.OpenApi from version 1.0.0 to 2.3.0 that includes some breaking changes. You will need to update and rebuild your custom module if you use Microsoft.OpenApi.
-You can find more information about Breaking changes in Microsoft.OpenApi by [following link](https://github.com/microsoft/OpenAPI.NET/blob/main/docs/upgrade-guide-2.md).
+You can find more information about breaking changes in Microsoft.OpenApi by [following link](https://github.com/microsoft/OpenAPI.NET/blob/main/docs/upgrade-guide-2.md).
 
 ## Remove BuildHost-net472 and BuildHost-netcore
 
 After update Microsoft.EntityFrameworkCore.Design to 10.x, you will see that your project includes two folders BuildHost-net472 and BuildHost-netcore under obj folder.
-These folders are created by Microsoft.EntityFrameworkCore.Design package to support design-time services for different target frameworks. 
+These folders are created by Microsoft.EntityFrameworkCore.Design a package to support design-time services for different target frameworks. 
 
 You can remove these two folders by modifying your .csproj file to include the following PackageReference for Microsoft.EntityFrameworkCore.Design with PrivateAssets set to all:
 
@@ -80,17 +80,17 @@ You can get the ModuleTypeLoadingException exception after updating platform and
 Unhandled exception. VirtoCommerce.Platform.Core.Modularity.Exceptions.ModuleTypeLoadingException: Failed to load type for module SomeModule.
 Cannot load "Microsoft.IO.RecyclableMemoryStream" for module ...
 ```
-In .NET 10, Microsoft refresh and excluded some assemblies (dll) that are no longer needed.
+In .NET 10, Microsoft refreshed and excluded some assemblies (dll) that are no longer needed.
 
-To resolve the issue you can:
+To resolve the issue, you can:
 
-Option 1. Add module.keep file to your custom module project with the following content, it adds required dll into module package:
+Option 1. Add module.keep file in your custom module project with the following content, it adds the required dll into module package:
 
 ```txt
 Microsoft.IO.RecyclableMemoryStream.dll
 ```
 
-Option 2. Update your module to .NET 10 using instructions below.
+Option 2. Update your module to .NET 10 using the instructions below.
 
 ## 415 Client Error: Unsupported Media Type
 
@@ -120,7 +120,7 @@ vc-build Update -Stable -v 12
 
 ### Option 2. Update via package.json
 
-If you use package.json file for automated deployment, change versions of the platform and Virto Commerce modules to 3.1000.0+. Based on latest Stable 8 or Edge release strategy.
+If you use package.json file for automated deployment, change versions of the platform and Virto Commerce modules to 3.1000.0+. Based on latest Stable 12 or Edge release strategy.
 
 ### Option 3. Manually update
 
@@ -167,19 +167,13 @@ Download and execute the [vc-net10-update.ps1 Power Shell script](vc-net10-updat
 ./vc-net10-update.ps1
 ```
 
-![step1 run ps1 script](../../media/updatenet10-step1-run-ps1-script.png)
-
-![step2 run ps1 script result](../../media/updatenetStable relea-step2-ps1-script-result.png)
-
 This script automates several these tasks, including (of course you can do it manually):
 
 1. Updating the Target Framework to .NET 10 for every project.
 2. Updating project dependencies, including Microsoft NuGet dependencies to version 10.0.0 and VirtoCommerce NuGet dependency to version 3.1000.0 and latest.
-3. Updating other third-party dependencies to save version that used by Virto Commerce Platform.
+3. Updating other third-party dependencies to the version used by Virto Commerce Platform .NET10.
 4. Updating the module.manifest file to align with the changes in .NET 10.
 
-![step3 review modified files](../../media/updatenetStable relea-step3-modified-files.png)
-
 ### Build Solution
 
 1. Build the solution and meticulously address any compilation errors and warnings if required. This step ensures that the solution is compatible with the updated framework.