Orchestrator flavor in RHDH Operator

Author: GitHub Actions

modules/orchestrator/con-orchestrator-plugin-components.adoc

@@ -1,7 +1,7 @@
 [id='con-orchestrator-plugin-components.adoc_{context}']
 = Orchestrator plugin components
 
-The following Orchestrator plugin components are included by default in `dynamic-plugins.default.yaml`:
+The following Orchestrator plugin components are included by default in the `dynamic-plugins.default.yaml` file:
 
 * `@redhat/backstage-plugin-orchestrator`
 * `@redhat/backstage-plugin-orchestrator-backend-dynamic`

modules/orchestrator/con-plugin-dependencies.adoc

@@ -3,10 +3,10 @@
 
 To run the Orchestrator plugin instance, you need to install the following dependencies:
 
-* A SonataflowPlatform custom resource created in the namespace of the Backstage CR.
-* A set of NetworkPolicies to allow traffic between infra resources, such as knative and serverless logic Operator, created in the namespace of Backstage CR, traffic for monitoring, and intra-namespace traffic.
+* A _SonataflowPlatform_ custom resource created in the namespace of the Backstage CR.
+* A set of _NetworkPolicies_ to allow traffic between infra resources, such as knative and serverless logic Operator, created in the namespace of Backstage CR, traffic for monitoring, and intra-namespace traffic.
 
-The orchestrator-backend plugin uses the service `sonataflow-platform-data-index-service`, which is created by the _SonataFlowPlatform_ CR. The service communicates with the SonataFlow platform.
+The orchestrator-backend plugin uses the service `sonataflow-platform-data-index-service`, which is created by the _SonataFlowPlatform_ custom resource. The service communicates with the SonataFlow platform.
 
 [IMPORTANT]
 ====
@@ -35,4 +35,4 @@ The default implementation of the Orchestrator plugin dependencies uses the foll
 
 For more information about automatically creating 'plugin dependencies' resources when the Backstage CR is applied to the cluster, see link:https://github.com/redhat-developer/rhdh-operator/blob/release-1.7/docs/dynamic-plugins.md#dynamic-plugins-dependency-management[Dynamic plugins dependency management].
 
-To enable the Backstage Operator to work with the SonataFlow platform, you must grant the appropriate permissions to its ServiceAccount. The Backstage Operator automatically creates the required Role and RoleBinding resource in the `profile/rhdh/plugin-rbac directory` directory when creating the SonataFlowPlatform CR in the Backstage CR namespace.
+To enable the Backstage Operator to work with the SonataFlow platform, you must grant the appropriate permissions to its `ServiceAccount`. The Backstage Operator automatically creates the required Role and _RoleBinding_ resource in the `profile/rhdh/plugin-rbac directory` directory when creating the _SonataFlowPlatform_ custom resource in the Backstage custom resource namespace.

modules/orchestrator/proc-install-rhdh-in-air-gapped-environment.adoc

@@ -64,7 +64,7 @@ helm pull <chart> --version <version>
 helm push <chart>.tgz oci://internal-chart-repo.example.com/rhdh
 ----
 
-. Ensure NetworkPolicies, Role, and RoleBinding resources for the SonataFlow platform are included in your deployment configuration. The {product-short} Operator applies these automatically when the `SonataFlowPlatform` CR is created.
+. Ensure _NetworkPolicies_, Role, and _RoleBinding_ resources for the _SonataFlow_ platform are included in your deployment configuration. The {product-short} Operator applies these automatically when the _SonataFlowPlatform_ CR is created.
 
 [NOTE]
 ====