RHIDP-5422: Apply add'l SME comments

Author: linfraze

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

@@ -37,7 +37,7 @@ global:
 Preinstalled add-ons, such as `ReportIssue`, are included in the default package configuration. Additional add-ons are installed by manually adding them to the configuration file.
 ====
 
-. In the `techdocsAddons` section of the Helm chart, add `importName: _<external_techdocs_add-on>` for each external TechDocs add-on that you want to install. For example:
+. In the `techdocsAddons` section of the Helm chart, add `importName: _<external_techdocs_add-on>` for each external TechDocs add-on that you want to add from the specified plugin package. For example:
 +
 [source,yaml,subs="+quotes,+attributes"]
 ----

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

@@ -43,7 +43,7 @@ data:
 ====
 Preinstalled add-ons, such as `ReportIssue`, are included in the default package configuration. Additional add-ons are installed by manually adding them to the configuration file.
 ====
-. In the `techdocsAddons` section of the ConfigMap, add `importName: _<external_techdocs_add-on>` for each external TechDocs add-on that you want to install. For example:
+. In the `techdocsAddons` section of the ConfigMap, add `importName: _<external_techdocs_add-on>` for each external TechDocs add-on that you want to add from the specified plugin package. For example:
 +
 [source,yaml,subs="+quotes,+attributes"]
 ----

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

@@ -13,7 +13,6 @@ You can install compatible third-party TechDocs add-on on your {product} instanc
 * 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:
@@ -32,7 +31,7 @@ npx @janus-idp/cli@latest package export-dynamic-plugin
 +
 [NOTE]
 ====
-The `@latest` tag uses the latest version of the `package.json` file for compatibility with the most recent features and fixes.
+The `@latest` tag pulls the latest version of the @janus-idp/cli package, which is compatible with the most recent features and fixes. Use a version that is compatible with your {product} version.
 ====
 . 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:
 +
@@ -73,17 +72,15 @@ plugins:
                 techdocsAddons:
                   - importName: _<third-party_add-on_name>_
                    config:
-                    props:
-                     config:
-                      theme: _<theme_name>_
-                      themeVariables: { lineColor: "_<line_color_variable>_"}
+                      props:
+                       _<techdocs_add-on_property_key>_: _<techdocs_add-on_property_value>_
 ----
 +
 where
 
-_<user_name>>_ :: Specifies your Quay user name or organization name.
+_<user_name>_ :: Specifies your Quay user name or organization name.
 _<techdocs_add-on_image>_ :: Specifies the name of the image for the third-party add-on that you want to use, for example, `mermaid`.
 _<techdocs_add-on_package>_ :: Specifies the , for example, `backstage-plugin-techdocs-addon-mermaid`.
 _<third-party_add-on_name>_ :: Specifies the name of the third-party add-on that you want to use, for example, `Mermaid`.
-_<theme_name>_ :: Specifies the name of the visual theme that you want to apply to your third-party TechDocs add-on, for example, `forest`. Depending on the third-party add-on, this field can be optional or required.
-_<line_color_variable>_ :: Specifies the line color that you want to use in the visual theme, for example, #000000. Depending on the third-party add-on, this field can be optional or required.
+_<techdocs_add-on_property_key>_ :: Specifies the name of the custom property that can be passed to the third-party add-on, for example, `themeVariables`. Properties are specific to each add-on. You can list multiple properties for an add-on.
+_<techdocs_add-on_property_value>_ :: Specifies the value of a property key for the third-party add-on, for example, `lineColor: #000000`.

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

@@ -6,7 +6,7 @@
 [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 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.
+If you no longer want to use the functionality of a TechDocs add-on that is imported from a particular plugin that you installed on your {product} instance with the Helm chart, you can temporarily disable 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 `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:
@@ -31,7 +31,7 @@ global:
 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:
+** To remove one or more TechDocs add-ons from your {product} instance, delete `importName: _<external_techdocs_add-on>_` for each external TechDocs add-on that you want to remove from the `techdocsAddons` section of your Helm chart. For example:
 +
 [source,yaml,subs="+quotes,+attributes"]
 ----

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

@@ -6,7 +6,7 @@
 [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 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.
+If you no longer want to use the functionality of a TechDocs add-on that is imported from a particular plugin that you installed on your {product} instance with the Operator, you can temporarily disable 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
 
@@ -41,7 +41,7 @@ data:
 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:
+** To remove one or more TechDocs add-ons from your {product} instance, delete `importName: _<external_techdocs_add-on>_` for each external TechDocs add-on that you want to remove from the `techdocsAddons` section of your ConfigMap. For example:
 +
 [source,yaml,subs="+quotes,+attributes"]
 ----

modules/techdocs/proc-techdocs-addon-use-report-issue.adoc

@@ -10,7 +10,7 @@ If you find an error in your organization's TechDocs documentation, you can use
 
 .Prerequisites
 * The `ReportIssue` add-on is installed and enabled in your TechDocs plugin.
-* You have permissions to write to the repository where documentation issues are reported.
+* You have permissions to create issues in the repository where documentation issues are reported.
 
 .Procedure
 . In your TechDocs documentation, highlight the text that you want to report an issue for.