RHIDP-5422: Apply SME comments

Author: linfraze

assemblies/assembly-techdocs-addons.adoc

@@ -13,7 +13,7 @@ The following table describes the TechDocs add-ons that are available for {produ
 
 | `<ReportIssue />`
 | `backstage-plugin-techdocs-module-addons-contrib`
-| Select a portion of text on a TechDocs page and open an issue against the repository that contains the documentation, populating the issue description with the selected text according to a configurable template.
+| Select a portion of text on a TechDocs page and open an issue against the repository that contains the documentation. The issue template is automatically populated with the selected text.
 | Preinstalled
 
 | `<TextSize />`

modules/techdocs/proc-techdocs-addon-install-third-party.adoc

@@ -11,10 +11,17 @@ You can install compatible third-party TechDocs add-on on your {product} instanc
 .Prerequisites
 * The third-party TechDocs add-on has a valid `package.json` file in its root directory, containing all required metadata and dependencies.
 * You have installed the @janus-idp/cli package.
+* You have installed the `yarn` package manager.
 * You have installed and configured Node.js and NPM.
 * You have installed the `scalprum` CLI tool for configuring front-end plugins.
 
 .Procedure
+. Install the third-party plugin that you want to use to import your third-party add-on by entering the following command:
++
+[source,terminal,subs="+quotes,+attributes"]
+----
+yarn install
+----
 . Obtain the source code for the third-party TechDocs add-on that you want to use.
 . Export the TechDocs add-on as a dynamic plugin using the following command:
 +
@@ -27,21 +34,6 @@ npx @janus-idp/cli@latest package export-dynamic-plugin
 ====
 The `@latest` tag uses the latest version of the `package.json` file for compatibility with the most recent features and fixes.
 ====
-+
-.Example output
-[source,terminal,subs="+quotes,+attributes"]
-----
-Using scalpum config inlined in the `package.json`
-Packing main package to dist-dynamic/package.json
-Customizing main package in dist-dynamic/package.json for dynamic loading
-Generating dynamic frontend plugin assets in _<path_to_add-on_package>_/_<third-party_add-on_package>_/dist-dynamic/dist-scalprum
-...
-----
-+
-where
-
-_<path_to_add-on_package>_ :: Specifies the package for the third-party add-on that you want to export, for example, `backstage-plugin-techdocs-module-addon-mermaid`.
-
 . To package the third-party TechDocs add-on as a dynamic plugin, navigate to the root directory where the plugin is stored (not the dist-dynamic directory) and run the `npx` command with the `--tag` option to specify the image name and tag. For example:
 +
 [source,terminal,subs="+quotes,+attributes"]

modules/techdocs/proc-techdocs-addon-remove-helm.adoc

@@ -6,10 +6,32 @@
 [id="proc-techdocs-addon-remove-helm_{context}"]
 == Removing an external TechDocs add-on from your Helm chart
 
-If you no longer want to use the functionality of a TechDocs add-on that you installed on your {product} instance using the Helm chart, remove it from your Helm chart.
+If you no longer want to use the functionality of a TechDocs add-on that are imported from a particular plugin that you installed on your {product} instance with the Helm chart, you can temporarily disabled it or permanently remove it from your Helm chart. The `disabled` status is controlled at the plugin level, therefore, disabling the plugin disables all of the TechDocs add-ons in the disabled plugin package.
 
 .Procedure
-* In the `techdocsAddons` section of the Helm chart, delete `importName: _<external_techdocs_add-on>` for each external TechDocs add-on that you want to remove. For example:
+* In the `plugins` section of the Helm chart, do one of the following actions based on whether you want to disable or remove a TechDocs add-on:
+** To temporarily disable all of the TechDocs add-ons in a particular plugin package, change the value of the `disabled` field to `true`. For example:
++
+[source,yaml,subs="+quotes,+attributes"]
+----
+global:
+  dynamic:
+    plugins:
+      - package: ./dynamic-plugins/dist/backstage-plugin-techdocs-module-addons-contrib
+        disabled: true
+        pluginConfig:
+          dynamicPlugins:
+            frontend:
+              backstage.plugin-techdocs-module-addons-contrib:
+                techdocsAddons:
+                  - importName: ReportIssue
+                  - importName: _<external_techdocs_add-on>_
+----
++
+where:
+
+_<external_techdocs_add-on>_:: Specifies the external TechDocs add-on that you want to remove, for example, `TextSize`.
+** To permanently remove one or more TechDocs add-ons from a plugin package, delete `importName: _<external_techdocs_add-on>` for each external TechDocs add-on that you want to remove. For example:
 +
 [source,yaml,subs="+quotes,+attributes"]
 ----

modules/techdocs/proc-techdocs-addon-remove-operator.adoc

@@ -6,14 +6,42 @@
 [id="proc-techdocs-addon-remove-operator_{context}"]
 == Removing an external TechDocs add-on from your ConfigMap
 
-If you no longer want to use the functionality of a TechDocs add-on that you installed on your {product} instance using the Operator, remove it from your ConfigMap.
+If you no longer want to use the functionality of a TechDocs add-on that are imported from a particular plugin that you installed on your {product} instance with the Operator, you can temporarily disabled it or permanently remove it from your ConfigMap. The `disabled` status is controlled at the plugin level, therefore, disabling the plugin disables all of the TechDocs add-ons in the disabled plugin package.
 
 .Procedure
 
 . From the Developer perspective in the {ocp-short} web console, click *ConfigMaps*.
 . From the *ConfigMaps* page, click the ConfigMap that contains the TechDocs add-on that you want to remove.
 . Select the *YAML view* option in the *Configure via* field.
-. In the `techdocsAddons` section of the ConfigMap, delete `importName: _<external_techdocs_add-on>` for each external TechDocs add-on that you want to remove. For example:
+. In the `plugins` section of the ConfigMap, do one of the following actions based on whether you want to disable or remove a TechDocs add-on:
+** To temporarily disable all of the TechDocs add-ons in a particular plugin package, change the value of the `disabled` field to `true`. For example:
++
+[source,yaml,subs="+quotes,+attributes"]
+----
+kind: ConfigMap
+apiVersion: v1
+metadata:
+  name: dynamic-plugins-rhdh
+data:
+  dynamic-plugins.yaml: |
+    includes:
+      - dynamic-plugins.default.yaml
+    plugins:
+      - package: ./dynamic-plugins/dist/backstage-plugin-techdocs-module-addons-contrib
+        disabled: true
+        pluginConfig:
+          dynamicPlugins:
+            frontend:
+              backstage.plugin-techdocs-module-addons-contrib:
+                techdocsAddons:
+                  - importName: ReportIssue
+                  - importName: _<external_techdocs_add-on>_
+----
++
+where:
+
+_<external_techdocs_add-on>_:: Specifies the external TechDocs add-on that you want to remove, for example, `TextSize`.
+** To permanently remove one or more TechDocs add-ons from a plugin package, delete `importName: _<external_techdocs_add-on>` for each external TechDocs add-on that you want to remove. For example:
 +
 [source,yaml,subs="+quotes,+attributes"]
 ----