review suggestions incorporated

Author: hmanwani-rh

assemblies/dynamic-plugins/assembly-install-third-party-plugins-rhdh.adoc

@@ -4,7 +4,7 @@
 
 You can install a third-party plugins in {product} without rebuilding the {product-very-short} application.
 
-The location of the `dynamic-plugin-config.yaml` file depends on the deployment method. For more details, refer to xref:proc-config-dynamic-plugins-rhdh-operator_rhdh-installing-rhdh-plugins[] and xref:con-install-dynamic-plugin-helm_rhdh-installing-rhdh-plugins[].
+The location of the `dynamic-plugin-config.yaml` file depends on the deployment method. For more details, refer to xref:proc-config-dynamic-plugins-rhdh-operator_rhdh-installing-rhdh-plugins[Installing dynamic plugins with the {product} Operator] and xref:con-install-dynamic-plugin-helm_rhdh-installing-rhdh-plugins[Installing dynamic plugins using the Helm chart].
 
 Plugins are defined in the `plugins` array within the `dynamic-plugin-config.yaml` file. Each plugin is represented as an object with the following properties:
 
@@ -15,7 +15,7 @@ Plugins are defined in the `plugins` array within the `dynamic-plugin-config.yam
 
 [NOTE]
 ====
-You can also load dynamic plugins from a plain directory, though this is intended for development or testing purposes and is not recommended for production, except for plugins included in the {product-very-short} container image.
+You can also load dynamic plugins from another directory, though this is intended for development or testing purposes and is not recommended for production, except for plugins included in the {product-very-short} container image.
 ====
 
 //OCI image

assemblies/dynamic-plugins/assembly-package-publish-third-party-dynamic-plugin.adoc

@@ -7,7 +7,7 @@ After xref:proc-export-third-party-plugins-rhdh_assembly-third-party-plugins[exp
 * Open Container Initiative (OCI) image (recommended)
 * TGZ file
 * JavaScript package
-
++
 [IMPORTANT]
 ====
 Exported dynamic plugin packages must only be published to private NPM registries.

assemblies/dynamic-plugins/assembly-third-party-plugins.adoc

@@ -2,7 +2,7 @@
 = Third-party plugins in {product}
 :context: assembly-third-party-plugins
 
-You can integrate third-party dynamic plugins in {product}. This flexibility allows you to enhance the platform functionality without modifying its source code and rebuilding. To add third-party dynamic plugins, you can export them as derived package.
+You can integrate third-party dynamic plugins into {product} to enhance its functionality without modifying its source code or rebuilding it. To add these plugins, export them as derived packages.
 
 While exporting the plugin package, you must ensure that dependencies are correctly bundled or marked as shared, depending on their relationship to the {product-short} environment.
 

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

@@ -6,9 +6,9 @@ To use plugins in {product}, you can export plugins as derived dynamic plugin pa
 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 backend system. Additionally, these plugins must be rebuilt using a dedicated CLI command.
+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 new 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 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.
 
@@ -29,7 +29,7 @@ The following is an example of exporting a dynamic plugin with shared and embedd
 .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>
+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.
@@ -104,8 +104,9 @@ export const DynamicEntityTechdocsContent = {
 * 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:
-
+* Use the `package export-dynamic-plugin` command from the `@janus-idp/cli` package to export the plugin:
++
+--
 .Example command to export a third-party plugin
 [source,bash]
 ----
@@ -120,5 +121,6 @@ The resulting derived package will be located in the `dist-dynamic` subfolder. T
 ====
 The derived dynamic plugin JavaScript packages must not be published to the public NPM registry. For more appropriate packaging options, see xref:assembly-package-publish-third-party-dynamic-plugin[]. If you must publish to the NPM registry, use a private registry.
 ====
+--