chore: Turn on MD024 for non-siblings

Inline disabled in the case of old tab style headings

.markdownlint.json

@@ -1,7 +1,9 @@
 {
     "default": true,
     "MD013": false,
-    "MD024": false,
+    "MD024": {
+        "allow_different_nesting": true
+    },
     "MD025": { "front_matter_title": "" },
     "MD028": false,
     "MD033": { "allowed_elements": ["sup", "sub", "a"] },

entity-framework/core/managing-schemas/migrations/index.md

@@ -112,6 +112,8 @@ Since this isn't the project's first migration, EF Core now compares your update
 
 You can now apply your migration as before:
 
+<!--markdownlint-disable MD024-->
+
 #### [.NET Core CLI](#tab/dotnet-core-cli)
 
 ```dotnetcli
@@ -124,6 +126,8 @@ dotnet ef database update
 Update-Database
 ```
 
+<!--markdownlint-enable MD024-->
+
 ***
 
 Note that this time, EF detects that the database already exists. In addition, when our first migration was applied above, this fact was recorded in a special migrations history table in your database; this allows EF to automatically apply only the new migration.

entity-framework/core/managing-schemas/migrations/managing.md

@@ -44,6 +44,8 @@ The timestamp in the filename helps keep them ordered chronologically so you can
 
 You are free to move Migrations files and change their namespace manually. New migrations are created as siblings of the last migration. Alternatively, you can specify the namespace at generation time as follows:
 
+<!--markdownlint-disable MD024-->
+
 ### [.NET Core CLI](#tab/dotnet-core-cli)
 
 ```dotnetcli
@@ -56,6 +58,8 @@ dotnet ef migrations add InitialCreate --namespace Your.Namespace
 Add-Migration InitialCreate -Namespace Your.Namespace
 ```
 
+<!--markdownlint-enable MD024-->
+
 ***
 
 ## Customize migration code