Restructure the Orchestrator

Author: GitHub Actions

modules/orchestrator/con-architecture-overview.adoc

@@ -13,16 +13,12 @@ Orchestrator backend plugins::: Get workflow data into {product-short}.
 
 Notifications plugins::: Inform users about workflow events.
 
-Sonataflow::
-
-The Sonataflow orchestrator and its subcomponents handle the workflows.
-The {product} Orchestrator and the {product} Helm chart manage the following subcomponents lifecycle:
-
-OpenShift Serverless Logic Operator::: Manages the Sonataflow custom resource (CR), where each CR represents a deployed workflow.
+Openshift Serverless Logic Operator:: Serves as the workflow engine, and its subcomponents handle running, executing and providing persistence for the workflows. The {product} Operator and the {product} Helm chart manage the following lifecycle of these subcomponents:
 
 Sonataflow Runtime/Workflow Application::: Functions as a deployed workflow. Operates as an HTTP server, handling requests for running workflow instances. It is managed as a Kubernetes (K8s) deployment by the Openshift Serverless Logic Operator.
 
 Data Index Service::: Serves as a repository for workflow definitions, instances, and associated jobs. It exposes a GraphQL API used by the Orchestrator backend plugin to retrieve workflow definitions and instances.
+
 Job Service::: Orchestrates scheduled tasks for workflows.
 
 OpenShift Serverless::: Provides serverless capabilities essential for workflow communication. It employs Knative eventing to interface with the Data Index service and uses Knative functions to introduce more complex logic to workflows.

modules/orchestrator/con-getting-started.adoc

@@ -13,5 +13,5 @@ To start using Orchestrator in {product-very-short}, you must:
 ====
 When using the {product-very-short} Operator, the required infrastructure components are provisioned automatically once the Orchestrator plugins are enabled in the {product-custom-resource-type} CR.
 
-When using the {product-very-short} Helm chart, the required infrastructure components are installed automatically using the dedicated `orchestrator-infra` Helm chart prior to enabling the Orchestrator plugins in the main {product-very-short} chart.
+When using the {product-very-short} Helm chart, the required infrastructure components are installed automatically using the dedicated `redhat-developer-hub-orchestrator-infra` Helm chart prior to enabling the Orchestrator plugins in the main {product-very-short} chart.
 ====

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

@@ -7,7 +7,7 @@ You can use Orchestrator Infrastructure for {product} to install components for
 
 .Procedure
 
-. Run the `helm install` command for the `orchestrator-infra` chart. This command initiates the installation of the Red Hat Serverless Operator and Red Hat Serverless Logic Operator components.
+. Run the `helm install` command for the `redhat-developer-hub-orchestrator-infra` Helm chart. This command initiates the installation of the Red Hat Serverless Operator and Red Hat Serverless Logic Operator components.
 +
 [source,terminal,subs="attributes+"]
 ----

modules/orchestrator/proc-install-rhdh-with-orchestrator-helm-cli.adoc

@@ -14,7 +14,7 @@ This is a one-off requirement and must be completed before enabling the Orchestr
 
 .Procedure
 
-. Run the `helm install` command for the `orchestrator-infra` chart. This command initiates the installation of the Red Hat Serverless Operator and Red Hat Serverless Logic Operator components.
+. Run the `helm install` command for the `redhat-developer-hub-orchestrator-infra` Helm chart. This command initiates the installation of the Red Hat Serverless Operator and Red Hat Serverless Logic Operator components.
 +
 [source,terminal,subs="attributes+"]
 ----