Update abp-10-6.md

docs/en/release-info/migration-guides/abp-10-6.md

@@ -7,7 +7,7 @@
 
 # ABP Version 10.6 Migration Guide
 
-This document is a guide for upgrading ABP v10.5 solutions to ABP v10.6. One item in this release is labeled as a breaking change. The new background job features are opt-in and default runtime behavior is unchanged, but the background jobs infrastructure extends public contracts and database models for optional scenarios.
+This document is a guide for upgrading ABP v10.5 solutions to ABP v10.6. There are some important changes that may require action in specific application scenarios.
 
 > **Package Version Changes:** Before upgrading, review the [Package Version Changes](../../package-version-changes.md) document to see version changes on dependent NuGet and NPM packages and align your project with ABP's internal package versions.
 
@@ -222,41 +222,6 @@ There are no explicitly marked breaking changes on the PRO side in this release
 - Re-test OpenIddict application administration pages after upgrading.
 - Review who can access the new token-generation action in your authorization setup.
 
-### Low-Code Runtime History
-
-**Who is affected**
-
-- Applications using the LowCode module and Admin Console designer.
-- Teams relying on writable low-code layers and designer undo/redo workflows.
-
-**What changed**
-
-- The designer adds runtime model history with undo/redo, save points, compare, revert, and selective apply flows.
-- History starts after deployment; older saves are not reconstructed.
-- MongoDB history persistence is not implemented yet in this release scope.
-
-**What to do**
-
-- Re-test low-code designer save, undo/redo, compare, and revert flows after upgrading.
-- Plan operational expectations for history retention and deployment timing.
-
-### Low-Code Layer Contracts and Designer Policy Enforcement
-
-**Who is affected**
-
-- Applications using inherited low-code layers, page groups, and multi-layer customization.
-
-**What changed**
-
-- Layer override/edit policies are enforced in backend validation and Admin Console designer controls.
-- Disabled or orphaned overrides can be cleaned up and reported through model health snapshots.
-- Broken parent/group/page reference chains are hidden from runtime APIs while remaining visible in designer diagnostics.
-
-**What to do**
-
-- Re-test inherited entity/page/page-group customization flows.
-- Review model health warnings after upgrading and clean up orphaned or disallowed overrides if needed.
-
 ### AI Management Indexing Resilience
 
 **Who is affected**