review suggestions incorporated

Author: hmanwani-rh

modules/dynamic-plugins/proc-export-third-party-plugins-rhdh.adoc

@@ -3,17 +3,23 @@
 
 To use plugins in {product}, you can export plugins as derived dynamic plugin packages. These packages contain the plugin code and dependencies, ready for dynamic plugin integration into {product-short}.
 
-Backend plugins::
+.Prerequisites
+* The `@janus-idp/cli` package is installed. Use the latest version (`@latest` tag) for compatibility with the most recent features and fixes.
+* Node.js and NPM is installed and configured.
+* The third-party plugin is compatible with your {product} version. For more information, see link:https://github.com/janus-idp/backstage-showcase/blob/main/docs/dynamic-plugins/versions.md[Version compatibility matrix].
+* The third-party plugin must have a valid `package.json` file in its root directory, containing all required metadata and dependencies.
 +
 --
-To ensure compatibility with the dynamic plugin support and enable their use as dynamic plugins, existing backend plugins must be compatible with the backend system. Additionally, these plugins must be rebuilt using a dedicated CLI command.
-
-The backend system entry point (created using `createBackendPlugin()` or `createBackendModule()`)  must be exported as the default export from either the main package or an `alpha` package (if the plugin instance support is still provided using `alpha` APIs). This doesn't add any additional requirement on top of the standard plugin development guidelines of the plugin instance.
-
+Backend plugins::
++
+To ensure compatibility with the dynamic plugin support and enable their use as dynamic plugins, existing backend plugins must be compatible with the new Backstage backend system. Additionally, these plugins must be rebuilt using a dedicated CLI command.
++
+The new Backstage backend system entry point (created using `createBackendPlugin()` or `createBackendModule()`)  must be exported as the default export from either the main package or an `alpha` package (if the plugin instance support is still provided using `alpha` APIs). This doesn't add any additional requirement on top of the standard plugin development guidelines of the plugin instance.
++
 The dynamic export mechanism identifies private dependencies and sets the `bundleDependencies` field in the `package.json` file. This export mechanism ensures that the dynamic plugin package is published as a self-contained package, with its private dependencies bundled in a private `node_modules` folder.
-
++
 Certain plugin dependencies require specific handling in the derived packages, such as:
-
++
 * *Shared dependencies* are provided by the {product-very-short} application and listed as `peerDependencies` in `package.json` file, not bundled in the dynamic plugin package. For example, by default, all `@backstage` scoped packages are shared.
 +
 You can use the `--shared-package` flag to specify shared dependencies, that are expected to be provided by {product} application and not bundled in the dynamic plugin package.
@@ -23,32 +29,30 @@ To treat a `@backstage` package as private, use the negation prefix (`!`). For e
 * *Embedded dependencies* are bundled into the dynamic plugin package with their dependencies hoisted to the top level. By default, packages with `-node` or `-common` suffixes are embedded.
 +
 You can use the `--embed-package` flag to specify additional embedded packages. For example, packages from the same workspace that do not follow the default naming convention.
-
++
 The following is an example of exporting a dynamic plugin with shared and embedded packages:
-
++
 .Example dynamic plugin export with shared and embedded packages
 [source,bash]
 ----
 npx @janus-idp/cli@latest export-dynamic-plugin --shared-package '!/@backstage/plugin-notifications/' <1> --embed-package @backstage/plugin-notifications-backend <2>
 ----
-
++
 <1> `@backstage/plugin-notifications` package is treated as a private dependency and is bundled in the dynamic plugin package, despite being in the `@backstage` scope.
 <2> `@backstage/plugin-notifications-backend` package is marked as an embedded dependency and is bundled in the dynamic plugin package.
---
 
 Front-end plugins::
 +
---
 Front-end plugins can use `scalprum` for configuration, which the CLI can generate automatically during the export process. The generated default configuration is logged when running the following command:
-
++
 .Example command to log the default configuration
 [source,bash]
 ----
 npx @janus-idp/cli@latest export-dynamic
 ----
-
++
 The following is an example of default `scalprum` configuration:
-
++
 .Default `scalprum` configuration
 [source,json]
 ----
@@ -59,9 +63,9 @@ The following is an example of default `scalprum` configuration:
   }
 }
 ----
-
++
 You can add a `scalprum` section to the `package.json` file. For example:
-
++
 .Example `scalprum` customization
 [source,json]
 ----
@@ -74,11 +78,11 @@ You can add a `scalprum` section to the `package.json` file. For example:
   }
 }
 ----
-
++
 Dynamic plugins might need adjustments for {product-short} needs, such as static JSX for mountpoints or dynamic routes. These changes are optional but might be incompatible with static plugins.
-
++
 To include static JSX, define an additional export and use it as the dynamic plugin's `importName`. For example:
-
++
 .Example static and dynamic plugin export
 [source,tsx]
 ----
@@ -97,12 +101,6 @@ export const DynamicEntityTechdocsContent = {
 ----
 --
 
-.Prerequisites
-* The `@janus-idp/cli` package is installed. Use the latest version (`@latest` tag) for compatibility with the most recent features and fixes.
-* The third-party plugin must have a valid package.json file in its root directory, containing all required metadata and dependencies.
-* Node.js and NPM is installed and configured.
-* The third-party plugin is compatible with your {product} version. For more information, see link:https://github.com/janus-idp/backstage-showcase/blob/main/docs/dynamic-plugins/versions.md[Version compatibility matrix].
-
 .Procedure
 * Use the `package export-dynamic-plugin` command from the `@janus-idp/cli` package to export the plugin:
 +