fixed minor issues

Author: hmanwani-rh

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

@@ -2,7 +2,7 @@
 = Third-party plugins in {product}
 :context: assembly-third-party-plugins-installation
 
-In {product}, third-party dynamic plugins can be integrated seamlessly, enabling the use of external plugins alongside native ones. This flexibility allows you to enhance the platform’s functionality without modifying its core structure. To add third-party dynamic plugins, you can either export them as standalone packages or wrap them in custom wrappers, especially if you want to adjust the plugin’s dependencies or configurations for compatibility.
+In {product}, third-party dynamic plugins can be integrated seamlessly, enabling the use of external plugins alongside native ones. This flexibility allows you to enhance the platform functionality without modifying its core structure. To add third-party dynamic plugins, you can either export them as standalone packages or wrap them in custom wrappers, especially if you want to adjust the dependencies or configurations of a plugin for compatibility.
 
 The third-party plugins are typically packaged as dynamic plugins, which means they can be loaded at runtime, enabling you to easily manage external modules without rebuilding the entire application. The process involves creating a wrapper that exports the plugin code, ensuring that dependencies are correctly bundled or marked as shared, depending on their relationship to the {product-short} environment.
 
@@ -24,13 +24,13 @@ The new backend system is created using `createBackendPlugin()` or `createBacken
 
 The backend plugins contains two types of dependencies, including:
 
-* *Shared dependencies* are provided by the Backstage application and listed as `peerDependencies` in `package.json` file, not bundled in the dynamic plugin package. By default, all `@backstage` packages are shared.
+* *Shared dependencies* are provided by an application and listed as `peerDependencies` in `package.json` file, not bundled in the dynamic plugin package. For example, by default, all `@backstage` packages are shared.
 +
 You can use the `--shared-package` flag to specify shared dependencies. To treat a `@backstage` package as private, use the negation prefix (`!`).
 
 * *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, including those in the same monorepo that do not follow the default naming convention.
+You can use the `--embed-package` flag to specify additional embedded packages, including those in the same repository that do not follow the default naming convention.
 
 The following is an example of exporting a dynamic plugin with shared and embedded packages:
 
@@ -44,20 +44,20 @@ npx @janus-idp/cli@latest export-dynamic-plugin --shared-package '!/@backstage/p
 <2> `@backstage/plugin-notifications-backend` package is marked as an embedded dependency and is bundled in the dynamic plugin package.
 --
 
-Frontend plugins::
+Front-end plugins::
 +
 --
-Frontend plugins can leverage Scalprum for configuration, which the CLI can generate automatically during the export process. The generated default configuration is logged when running the following command:
+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:
+The following is an example of default `scalprum` configuration:
 
-.Default Scalprum configuration
+.Default `scalprum` configuration
 [source,json]
 ----
 "scalprum": {
@@ -68,9 +68,9 @@ The following is an example of default Scalprum configuration:
 }
 ----
 
-To customize Scalprum, add a `scalprum` section to the `package.json` file. For example:
+You can add a `scalprum` section to the `package.json` file. For example:
 
-.Example Scalprum customization
+.Example `scalprum` customization
 [source,json]
 ----
 "scalprum": {