diff --git a/topics/appendix/resources/explore_api.md b/topics/appendix/resources/explore_api.md
index 1d682bde5..4d454f486 100644
--- a/topics/appendix/resources/explore_api.md
+++ b/topics/appendix/resources/explore_api.md
@@ -1,4 +1,4 @@
-
+
# Explore the IntelliJ Platform API
@@ -16,7 +16,8 @@ This usually happens in two situations:
This guide provides a list of proven strategies that can help you overcome these challenges and gather enough information to continue your work.
Furthermore, the tips below will help build your confidence as you explore the IntelliJ Platform.
-> In some cases, implementing an actual IntelliJ Platform plugin might not be necessary, as [alternative solutions](plugin_alternatives.md) exist.
+
+
> See also [](plugin_required_experience.md) about necessary technology knowledge.
## 1 Extension Points (EPs)
diff --git a/topics/basics/getting_started/plugin/developing_plugins.md b/topics/basics/getting_started/plugin/developing_plugins.md
index 5f3f0b107..8576c8ed3 100644
--- a/topics/basics/getting_started/plugin/developing_plugins.md
+++ b/topics/basics/getting_started/plugin/developing_plugins.md
@@ -1,4 +1,4 @@
-
+
# Developing a Plugin
@@ -9,9 +9,7 @@ It is highly recommended to always use the latest available version, as the plug
Before starting with the actual development, make sure to understand all requirements to achieve best [](plugin_user_experience.md).
-> In some cases, implementing an actual IntelliJ Platform plugin might not be necessary, as [alternative solutions](plugin_alternatives.md) exist.
->
-{title="Plugin Alternatives"}
+
## Gradle IntelliJ Plugin
diff --git a/topics/basics/plugin_required_experience.md b/topics/basics/plugin_required_experience.md
index a770c2720..520cc0b52 100644
--- a/topics/basics/plugin_required_experience.md
+++ b/topics/basics/plugin_required_experience.md
@@ -1,6 +1,6 @@
-# Required Experience
+
-
+# Required Experience
Required technology knowledge.
@@ -20,6 +20,4 @@ Developing a plugin will sometimes require digging into the [IntelliJ Platform c
It's highly recommended to get familiar with the [](explore_api.md) section before you start the plugin implementation.
-> In some cases, implementing an actual IntelliJ Platform plugin might not be necessary, as [alternative solutions](plugin_alternatives.md) exist.
->
-{style="note"}
+
diff --git a/topics/basics/plugin_types.md b/topics/basics/plugin_types.md
index e0537cccc..4b0e42b4f 100644
--- a/topics/basics/plugin_types.md
+++ b/topics/basics/plugin_types.md
@@ -1,4 +1,4 @@
-
+
# Plugin Types
@@ -15,8 +15,7 @@ The most common types of plugins include:
* User interface add-ons
* Themes
-> In some cases, implementing an actual IntelliJ Platform plugin might not be necessary, as [alternative solutions](plugin_alternatives.md) exist.
->
+
## Custom Language Support
diff --git a/topics/intro/intellij_platform.md b/topics/intro/intellij_platform.md
index 29b96add8..c4f7c3b11 100644
--- a/topics/intro/intellij_platform.md
+++ b/topics/intro/intellij_platform.md
@@ -33,9 +33,13 @@ Plugins can extend the platform in many ways, from adding a simple menu item to
Many of the existing IntelliJ Platform features are implemented as plugins that can be included or excluded depending on the needs of the end product.
See the [](plugins_quick_start.md) for more details.
+
+
> In some cases, implementing an actual IntelliJ Platform plugin might not be necessary, as [alternative solutions](plugin_alternatives.md) exist.
>
-{style="note"}
+{style="note" title="Plugin Alternatives"}
+
+
## Open Source