review suggestions incorporated

Author: hmanwani-rh

modules/dynamic-plugins/proc-create-plugin-js-package.adoc

@@ -15,7 +15,7 @@ The derived dynamic plugin JavaScript packages must not be published to the publ
 +
 --
 .Example command to publish a plugin package to an NPM registry
-[source,bash]
+[source,terminal]
 ----
 npm publish --registry <npm_registry_url>
 ----

modules/dynamic-plugins/proc-create-plugin-oci-image.adoc

@@ -11,7 +11,7 @@
 +
 --
 .Example command to package an exported third-party plugin
-[source,bash]
+[source,terminal]
 ----
 npx @janus-idp/cli@latest package package-dynamic-plugins --tag quay.io/example/image:v0.0.1
 ----
@@ -22,13 +22,13 @@ In the previous command, the `--tag` argument specifies the image name and tag.
 +
 --
 .Example command to push an image to a registry using podman
-[source,bash]
+[source,terminal]
 ----
 podman push quay.io/example/image:v0.0.1
 ----
 
 .Example command to push an image to a registry using docker
-[source,bash]
+[source,terminal]
 ----
 docker push quay.io/example/image:v0.0.1
 ----

modules/dynamic-plugins/proc-create-plugin-tgz-file.adoc

@@ -10,14 +10,14 @@
 +
 --
 .Example command to create a `tgz` archive
-[source,bash]
+[source,terminal]
 ----
 npm pack
 ----
 You can obtain the integrity hash from the output of the `npm pack` command by using the `--json` flag as follows:
 
 .Example command to obtain the integrity hash of a `tgz` archive
-[source,bash]
+[source,terminal]
 ----
 npm pack --json | head -n 10
 ----
@@ -38,7 +38,7 @@ plugins:
 +
 --
 .Example command to package a dynamic plugin
-[source,bash]
+[source,terminal]
 ----
 npm pack --pack-destination ~/test/dynamic-plugins-root/
 ----
@@ -48,7 +48,7 @@ npm pack --pack-destination ~/test/dynamic-plugins-root/
 To create a plugin registry using HTTP server on {ocp-short}, run the following commands:
 
 .Example commands to build and deploy an HTTP server in {ocp-short}
-[source,bash]
+[source,terminal]
 ----
 oc project rhdh
 oc new-build httpd --name=plugin-registry --binary

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

@@ -33,7 +33,7 @@ You can use the `--embed-package` flag to specify additional embedded packages.
 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]
+[source,terminal]
 ----
 npx @janus-idp/cli@latest export-dynamic-plugin --shared-package '!/@backstage/plugin-notifications/' <1> --embed-package @backstage/plugin-notifications-backend <2>
 ----
@@ -46,7 +46,7 @@ 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]
+[source,terminal]
 ----
 npx @janus-idp/cli@latest export-dynamic
 ----
@@ -106,7 +106,7 @@ export const DynamicEntityTechdocsContent = {
 +
 --
 .Example command to export a third-party plugin
-[source,bash]
+[source,terminal]
 ----
 npx @janus-idp/cli@latest package export-dynamic-plugin
 ----

modules/dynamic-plugins/proc-load-plugin-js-package.adoc

@@ -10,7 +10,7 @@ For more information about packaging a third-party plugin, see xref:assembly-pac
 . Run the following command to obtain the integrity hash from the NPM registry:
 +
 --
-[source,bash]
+[source,terminal]
 ----
 npm view --registry <registry-url> <npm package>@<version> dist.integrity
 ----

modules/dynamic-plugins/ref-example-third-party-plugin-installation.adoc

@@ -7,7 +7,7 @@ This section describes the process for integrating the link:https://github.com/b
 +
 --
 .Obtain the third-party plugin source code
-[source,bash]
+[source,terminal]
 ----
 $ git clone https://github.com/backstage/community-plugins
 $ cd community-plugins/workspaces/todo
@@ -19,14 +19,14 @@ $ yarn install
 +
 --
 .Export the backend plugin
-[source,bash]
+[source,terminal]
 ----
 $ cd todo-backend
 $ npx @janus-idp/cli@latest package export-dynamic-plugin
 ----
 
 .Output of exporting the backend plugin commands
-[source,bash]
+[source,terminal]
 ----
 Building main package
   executing     yarn build ✔
@@ -51,14 +51,14 @@ Saving self-contained config schema in /Users/user/Code/community-plugins/worksp
 You can run the following commands to set default dynamic UI configurations, create front-end plugin assets, and to generate a configuration schema for a front-end plugin:
 
 .Export the front-end plugin
-[source,bash]
+[source,terminal]
 ----
 $ cd ../todo
 $ npx @janus-idp/cli@latest package export-dynamic-plugin
 ----
 
 .Output of exporting the front-end plugin commands
-[source,bash]
+[source,terminal]
 ----
 No scalprum config. Using default dynamic UI configuration:
 {
@@ -84,14 +84,14 @@ Saving self-contained config schema in /Users/user/Code/community-plugins/worksp
 +
 --
 .Build an OCI image
-[source,bash]
+[source,terminal]
 ----
 $ cd ../..
 $ npx @janus-idp/cli@latest package package-dynamic-plugins --tag quay.io/user/backstage-community-plugin-todo:v0.1.1
 ----
 
 .Output of building an OCI image commands
-[source,bash]
+[source,terminal]
 ----
   executing     podman --version ✔
 Using existing 'dist-dynamic' directory at plugins/todo
@@ -120,13 +120,13 @@ plugins:
 ----
 
 .Push the OCI image to a container registry:
-[source,bash]
+[source,terminal]
 ----
 $ podman push quay.io/user/backstage-community-plugin-todo:v0.1.1
 ----
 
 .Output of pushing the OCI image command
-[source,bash]
+[source,terminal]
 ----
 Getting image source signatures
 Copying blob sha256:86a372c456ae6a7a305cd464d194aaf03660932efd53691998ab3403f87cacb5