review suggestions incorporated

hmanwani-rh · hmanwani-rh · commit fed4ea4c1ba5 · 2024-12-11T15:17:43.000+05:30
diff --git a/assemblies/dynamic-plugins/assembly-install-third-party-plugins-rhdh.adoc b/assemblies/dynamic-plugins/assembly-install-third-party-plugins-rhdh.adoc
@@ -8,7 +8,7 @@ The location of the `dynamic-plugin-config.yaml` file depends on the deployment
 
 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:
 
-* `package`: The plugin's package definition, which can be an OCI image, a TGZ file, a JavaScript package, or a directory path
+* `package`: The plugin's package definition, which can be an OCI image, a TGZ file, a JavaScript package, or a directory path.
 * `disabled`: A boolean value indicating whether the plugin is enabled or disabled.
 * `integrity`: The integrity hash of the package, required for TGZ file and JavaScript packages.
 * `pluginConfig`: The plugin's configuration. For backend plugins, this is optional; for frontend plugins, it is required. The `pluginConfig` is a fragment of the `app-config.yaml` file, and any added properties are merged with the {product-very-short} `app-config.yaml` file.
diff --git a/modules/dynamic-plugins/proc-create-plugin-js-package.adoc b/modules/dynamic-plugins/proc-create-plugin-js-package.adoc
@@ -34,6 +34,6 @@ You can add the following to your `package.json` file before running the `export
 }
 ----
 
-If you modify the `publishConfig` after exporting the dynamic plugin, re-run the `export-dynamic-plugin` command to ensure the correct configuration is included.
+If you modify `publishConfig` after exporting the dynamic plugin, re-run the `export-dynamic-plugin` command to ensure the correct configuration is included.
 ====
 --
diff --git a/modules/dynamic-plugins/proc-load-plugin-oci-image.adoc b/modules/dynamic-plugins/proc-load-plugin-oci-image.adoc
@@ -23,7 +23,7 @@ plugins:
 
 . Configure authentication for private registries by setting the `REGISTRY_AUTH_FILE` environment variable to the path of the registry configuration file. For example, `~/.config/containers/auth.json` or `~/.docker/config.json`.
 
-. To perform an integrity check, use the image digest in place of the tag in `dynamic-plugins.yaml` file as follows:
+. To perform an integrity check, use the image digest in place of the tag in the `dynamic-plugins.yaml` file as follows:
 +
 --
 .Example configuration in `dynamic-plugins.yaml` file

Original file line number	Diff line number	Diff line change
@@ -34,6 +34,6 @@ You can add the following to your `package.json` file before running the `export
`34`	`34`	`}`
`35`	`35`	`----`
`36`	`36`
`37`		-If you modify the `publishConfig` after exporting the dynamic plugin, re-run the `export-dynamic-plugin` command to ensure the correct configuration is included.
	`37`	+If you modify `publishConfig` after exporting the dynamic plugin, re-run the `export-dynamic-plugin` command to ensure the correct configuration is included.
`38`	`38`	`====`
`39`	`39`	`--`
Original file line number	Diff line number	Diff line change
`@@ -23,7 +23,7 @@ plugins:`
`23`	`23`
`24`	`24`	. Configure authentication for private registries by setting the `REGISTRY_AUTH_FILE` environment variable to the path of the registry configuration file. For example, `~/.config/containers/auth.json` or `~/.docker/config.json`.
`25`	`25`
`26`		-. To perform an integrity check, use the image digest in place of the tag in `dynamic-plugins.yaml` file as follows:
	`26`	+. To perform an integrity check, use the image digest in place of the tag in the `dynamic-plugins.yaml` file as follows:
`27`	`27`	`+`
`28`	`28`	`--`
`29`	`29`	.Example configuration in `dynamic-plugins.yaml` file