Update the build and deploy section

Author: GitHub Actions

assemblies/assembly-building-and-deploying-serverless-workflows.adoc

@@ -9,9 +9,7 @@ endif::[]
 :context: orchestrator-rhdh
 = Build and deploy serverless workflows
 
-The Orchestrator provides a way to run workflows directly from {product-custom-resource-type} and {product}. This guide details the full workflow lifecycle: moving a workflow from your local machine to deployment on a cluster, where it becomes available in the Orchestrator plugin.
-
-The overall process involves the following main steps, all of which can often be run using a single script:
+To make a workflow available in the Orchestrator plugin, the full workflow lifecycle, moving the workflow from your local machine to deployment on a cluster, involves the following main steps. These steps can often be run using a single script.
 
 * Building workflow images
 * Generating workflow manifests

modules/orchestrator/con-build-sh-script-and-its-uses.adoc

@@ -9,7 +9,7 @@ The `build-sh` script does the following in order:
 * Builds the workflow image using `podman` or `docker`.
 * Optional: The script pushes the images to an image registry and deploys the workflow using `kubectl`.
 
-By reviewing the script help menu, you can see the available flags and their functions:
+You can review the script configuration options and see available flags and their functions by accessing the help menu:
 
 [source,bash]
 ----

modules/orchestrator/con-project-structure-overview.adoc

@@ -3,7 +3,7 @@
 [id="con-project-structure-overview.adoc_{context}"]
 = Project structure overview
 
-We focus on a *Quarkus project layout* (Maven project structure), specifically the following `01_basic` workflow example:
+The project utilizes a *Quarkus project layout* (Maven project structure). This structure is illustrated by the following `01_basic` workflow example:
 
 [source, yaml]
 ----

modules/orchestrator/proc-deploying-workflows-on-a-cluster.adoc

@@ -3,7 +3,7 @@
 [id="proc-deploying-workflows-on-a-cluster.adoc_{context}"]
 = Deploying workflows on a cluster
 
-You can now deploy the workflow on a cluster, since the image has been pushed to the image registry and the deployment manifests have been made available.
+You can deploy the workflow on a cluster, since the image has been pushed to the image registry and the deployment manifests have been made available.
 
 .Prerequisites