docs: update migration guides

ghiscoding · ghiscoding · commit 1cf106500101 · 2026-03-09T17:04:13.000-04:00
diff --git a/docs/migrations/migration-to-10.x.md b/docs/migrations/migration-to-10.x.md
@@ -33,8 +33,8 @@ For years, I had to keep some references in a Shared Service as `shared.allColum
 
 _following changes should be transparent to most users, I'm just listing them in case of side effects._
 
-1. Reimplementing `SlickCompositeEditorComponent` modal and migrating from a `<div>` to a `<dialog>` which is native code, it has better accessibility (aria) support and a baseline support showing as "widely available". A fallback to `<div>` is also available in case `<dialog>` doens't work for everybody (e.g. it doesn't work in Salesforce LWC, hence the available fallback)
-2. Reimplementing Grid Menu to use CSS flexbox instead of using `calc(100% - 18px)` to position the button which wasn't ideal, neither customizable, but the new approach is to simply use CSS flexbox which is a much better approach to properly align everything.
+1. Migrated from a `<div>` to a `<dialog>` in the `SlickCompositeEditorComponent` modal component. The dialog is native code and it has better accessibility (aria) support with a baseline support showing as "widely available". A fallback to `<div>` is also available in case `<dialog>` doens't work for everybody (e.g. it doesn't work in Salesforce LWC, hence the available fallback)
+2. Remove the use of `calc(100% - 18px)` to position the Grid Menu and simply use CSS flexbox to position the grid menu button which is a much better approach to properly align everything.
 
 ## Changes
 
diff --git a/frameworks/angular-slickgrid/docs/migrations/migration-to-10.x.md b/frameworks/angular-slickgrid/docs/migrations/migration-to-10.x.md
@@ -38,8 +38,8 @@ For years, I had to keep some references in a Shared Service as `shared.allColum
 
 _following changes should be transparent to most users, I'm just listing them in case of side effects._
 
-1. Reimplementing `SlickCompositeEditorComponent` modal and migrating from a `<div>` to a `<dialog>` which is native code, it has better accessibility (aria) support and a baseline support showing as "widely available". A fallback to `<div>` is also available in case `<dialog>` doens't work for everybody (e.g. it doesn't work in Salesforce LWC, hence the available fallback)
-2. Reimplementing Grid Menu to use CSS flexbox instead of using `calc(100% - 18px)` to position the button which wasn't ideal, neither customizable, but the new approach is to simply use CSS flexbox which is a much better approach to properly align everything.
+1. Migrated from a `<div>` to a `<dialog>` in the `SlickCompositeEditorComponent` modal component. The dialog is native code and it has better accessibility (aria) support with a baseline support showing as "widely available". A fallback to `<div>` is also available in case `<dialog>` doens't work for everybody (e.g. it doesn't work in Salesforce LWC, hence the available fallback)
+2. Remove the use of `calc(100% - 18px)` to position the Grid Menu and simply use CSS flexbox to position the grid menu button which is a much better approach to properly align everything.
 
 ### Row Detail (now optional)
 
diff --git a/frameworks/aurelia-slickgrid/docs/migrations/migration-to-10.x.md b/frameworks/aurelia-slickgrid/docs/migrations/migration-to-10.x.md
@@ -34,8 +34,8 @@ For years, I had to keep some references in a Shared Service as `shared.allColum
 
 _following changes should be transparent to most users, I'm just listing them in case of side effects._
 
-1. Reimplementing `SlickCompositeEditorComponent` modal and migrating from a `<div>` to a `<dialog>` which is native code, it has better accessibility (aria) support and a baseline support showing as "widely available". A fallback to `<div>` is also available in case `<dialog>` doens't work for everybody (e.g. it doesn't work in Salesforce LWC, hence the available fallback)
-2. Reimplementing Grid Menu to use CSS flexbox instead of using `calc(100% - 18px)` to position the button which wasn't ideal, neither customizable, but the new approach is to simply use CSS flexbox which is a much better approach to properly align everything.
+1. Migrated from a `<div>` to a `<dialog>` in the `SlickCompositeEditorComponent` modal component. The dialog is native code and it has better accessibility (aria) support with a baseline support showing as "widely available". A fallback to `<div>` is also available in case `<dialog>` doens't work for everybody (e.g. it doesn't work in Salesforce LWC, hence the available fallback)
+2. Remove the use of `calc(100% - 18px)` to position the Grid Menu and simply use CSS flexbox to position the grid menu button which is a much better approach to properly align everything.
 
 ### Row Detail (now optional)
 
diff --git a/frameworks/slickgrid-react/docs/migrations/migration-to-10.x.md b/frameworks/slickgrid-react/docs/migrations/migration-to-10.x.md
@@ -34,8 +34,8 @@ For years, I had to keep some references in a Shared Service as `shared.allColum
 
 _following changes should be transparent to most users, I'm just listing them in case of side effects._
 
-1. Reimplementing `SlickCompositeEditorComponent` modal and migrating from a `<div>` to a `<dialog>` which is native code, it has better accessibility (aria) support and a baseline support showing as "widely available". A fallback to `<div>` is also available in case `<dialog>` doens't work for everybody (e.g. it doesn't work in Salesforce LWC, hence the available fallback)
-2. Reimplementing Grid Menu to use CSS flexbox instead of using `calc(100% - 18px)` to position the button which wasn't ideal, neither customizable, but the new approach is to simply use CSS flexbox which is a much better approach to properly align everything.
+1. Migrated from a `<div>` to a `<dialog>` in the `SlickCompositeEditorComponent` modal component. The dialog is native code and it has better accessibility (aria) support with a baseline support showing as "widely available". A fallback to `<div>` is also available in case `<dialog>` doens't work for everybody (e.g. it doesn't work in Salesforce LWC, hence the available fallback)
+2. Remove the use of `calc(100% - 18px)` to position the Grid Menu and simply use CSS flexbox to position the grid menu button which is a much better approach to properly align everything.
 
 ### Row Detail (now optional)
 
diff --git a/frameworks/slickgrid-vue/docs/migrations/migration-to-10.x.md b/frameworks/slickgrid-vue/docs/migrations/migration-to-10.x.md
@@ -35,8 +35,8 @@ For years, I had to keep some references in a Shared Service as `shared.allColum
 
 _following changes should be transparent to most users, I'm just listing them in case of side effects._
 
-1. Reimplementing `SlickCompositeEditorComponent` modal and migrating from a `<div>` to a `<dialog>` which is native code, it has better accessibility (aria) support and a baseline support showing as "widely available". A fallback to `<div>` is also available in case `<dialog>` doens't work for everybody (e.g. it doesn't work in Salesforce LWC, hence the available fallback)
-2. Reimplementing Grid Menu to use CSS flexbox instead of using `calc(100% - 18px)` to position the button which wasn't ideal, neither customizable, but the new approach is to simply use CSS flexbox which is a much better approach to properly align everything.
+1. Migrated from a `<div>` to a `<dialog>` in the `SlickCompositeEditorComponent` modal component. The dialog is native code and it has better accessibility (aria) support with a baseline support showing as "widely available". A fallback to `<div>` is also available in case `<dialog>` doens't work for everybody (e.g. it doesn't work in Salesforce LWC, hence the available fallback)
+2. Remove the use of `calc(100% - 18px)` to position the Grid Menu and simply use CSS flexbox to position the grid menu button which is a much better approach to properly align everything.
 
 ### Row Detail (now optional)
 
