Convert header to warnings (#866)

* Convert to warnings * More * More
nunit · Dec 5, 2023 · 22d30ca · 22d30ca
1 parent d4672a8
commit 22d30ca
Showing 1 changed file with 14 additions and 14 deletions.
diff --git a/docs/articles/vs-test-adapter/Adapter-Engine-Compatibility.md b/docs/articles/vs-test-adapter/Adapter-Engine-Compatibility.md
@@ -40,17 +40,17 @@ table above.
 Note that most of what the console can do, can be done using the `dotnet test` command with the appropriate runsettings
 added, see [Tips&Tricks](https://docs.nunit.org/articles/vs-test-adapter/Tips-And-Tricks.html).
 
-## :warning: Warning
-
-If you try to add another engine version package, it may seem that the adapter and test are still working.  That is just
-by luck, and it does so because the interfaces between the version you have added are the same as the embedded version.
-But if you try to use a feature that is not in the embedded version, it will fail.
-
-Most likely you will see messages about "no tests found", or it may simply crash during test.
-
-## :warning: Warning
-
-Version 4.4.1 use an engine version that is not released yet.  This is because the engine has a bug that prevents it
-from working with the adapter.  The bug is fixed in the engine, but the fix is not yet released.  The adapter will be
-updated to use the released engine version as soon as it is released. You may try to use 3.15.2, but we can currently
-not confirm that it works.
+> [!WARNING]
+> If you try to add another engine version package, it may seem that the adapter and test are still working.  That is just
+> by luck, and it does so because the interfaces between the version you have added are the same as the embedded version.
+> But if you try to use a feature that is not in the embedded version, it will fail.
+>
+> Most likely you will see messages about "no tests found", or it may simply crash during test.
+
+<!-- markdownlint-disable MD028 -->
+
+> [!WARNING]
+> Version 4.4.1 use an engine version that is not released yet.  This is because the engine has a bug that prevents it
+> from working with the adapter.  The bug is fixed in the engine, but the fix is not yet released.  The adapter will be
+> updated to use the released engine version as soon as it is released. You may try to use 3.15.2, but we can currently
+> not confirm that it works.