Apply Jana's suggestions

Author: GitHub Actions

modules/orchestrator/con-architecture-overview.adoc

@@ -3,7 +3,7 @@
 [id="con-architecture-overview.adoc_{context}"]
 = Architecture overview
 
-The Orchestrator architecture is composed of several integral components, each contributing to the seamless running and management of workflows.
+The Orchestrator architecture is composed of several integral components, each contributing to the running and management of workflows.
 
 {product} ({product-very-short}):: Serves as the primary interface. {product-custom-resource-type} fulfills the following roles:
 
@@ -12,16 +12,16 @@ The Orchestrator architecture is composed of several integral components, each c
 
 OpenShift Serverless Logic Operator:: Manages the Sonataflow custom resource (CR), where each CR represents a deployed workflow.
 
-Sonataflow Runtime/Workflow Application:: Functions as a deployed workflow. Operates as an HTTP server, catering to requests for running workflow instances. Sonataflow Runtime is managed as a Kubernetes (K8s) deployment by the Openshift Serverless Logic Operator. Within the Orchestrator deployment, each Sonataflow custom resource (CR) corresponds to a singular workflow. However, outside this scope, Sonataflow Runtime can handle multiple workflows. The Orchestrator backend plugin facilitates the interaction with Sonataflow Runtime for workflow execution.
+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:: Furnishes serverless capabilities essential for workflow communication. It employs Knative eventing to interface with the Data Index service and uses Knative functions to introduce more intricate logic to 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.
 
-PostgreSQL Server:: Provides a robust and reliable database solution essential for data persistence within the Orchestrator ecosystem. The system uses PostgreSQL Server for storing both Sonataflow information and {product-custom-resource-type} data.
+PostgreSQL Server:: Provides a database solution essential for data persistence within the Orchestrator ecosystem. The system uses PostgreSQL Server for storing both Sonataflow information and {product-custom-resource-type} data.
 
 KeyCloak:: Provides authentication and security services within applications. KeyCloak must be provisioned externally to manage authentication, as the Orchestrator Operator does not install it.
 
-OpenShift AMQ Streams (Strimzi/Kafka):: Ensures the reliability of the eventing system. While the eventing can work without Kafka by using direct HTTP calls, this approach is not reliable. The AMQ Streams Operator is not natively present or integrated into the deployment current iteration.
+OpenShift AMQ Streams (Strimzi/Kafka):: Provides enhanced reliability of the eventing system. While the eventing can work without Kafka by using direct HTTP calls, this approach is not reliable. The AMQ Streams Operator is not natively present or integrated into the deployment current iteration.

modules/orchestrator/proc-enabling-orchestrator-plugins.adoc

@@ -11,7 +11,7 @@
 * `"backstage-plugin-orchestrator-form-widgets"`
 
 .Procedure
-* To enable the Orchestrator plugins, locate your {product-short} configuration and set the `plugins.disabled` parameter to `false` for each required plugin package.
+* Locate your {product-short} configuration and set the `plugins.disabled` parameter to `false` for each required plugin package.
 +
 For example, to enable the core Orchestrator frontend plugin:
 +