Apply Peer and Tech suggestions

Author: GitHub Actions

modules/orchestrator/proc-enable-orchestrator-plugin.adoc

@@ -15,7 +15,7 @@ You can enable the Orchestrator plugin in {product-very-short} by configuring dy
 [source,yaml]
 ----
 - package: "@redhat/backstage-plugin-orchestrator@<plugin_version>"
-    disabled: false
+  disabled: false
 ----
 
 .Example: Complete configuration of the Orchestrator plugin

modules/orchestrator/proc-install-components-for-orchestrator-plugin.adoc

@@ -15,7 +15,7 @@ To run the Orchestrator plugin successfully on {ocp-short}, you must install com
 +
 [NOTE]
 ====
-You must preinstall the components, or install them by using one of the supported methods described in the following section (manual installation, helper script, or Helm chart).
+You must preinstall the components, or install them by using one of the supported methods.
 ====
 
 .Procedure
@@ -24,7 +24,7 @@ To install components (Operators) that provide the dependencies required by the
 
 * Manual installation
 * {product-very-short} helper script
-* {product-very-short} Orchestrator Infra Helm Chart
+* Orchestrator Infrastructure for {product}
 +
 These components enable the creation of the `SonataFlowPlatform` custom resource and several supporting `NetworkPolicy` resources.
 
@@ -65,10 +65,10 @@ curl -sSLO https://raw.githubusercontent.com/redhat-developer/rhdh-operator/refs
 $ ./plugin-infra.sh
 ----
 
-.{product-very-short} Orchestrator Infra Helm Chart
-You can use {product-very-short} Orchestrator Infra Helm chart to install components for the Orchestrator plugins in empty clusters.
+.Orchestrator Infrastructure for {product}
+You can use Orchestrator Infrastructure for {product} to install components for the Orchestrator plugins in empty clusters.
 
 [IMPORTANT]
 ====
-The Orchestrator Infra Helm chart is suitable for production use. By default, it does *not* auto-install or auto-upgrade the Operator: you must approve the install plans.
+Orchestrator Infrastructure for {product} is suitable for production use. By default, it does *not* auto-install or auto-upgrade the required Serverless Operators: you or a cluster administrator must approve the install plans.
 ====