Apply technical reviewers suggestions

Author: GitHub Actions

modules/orchestrator/con-environment-variables-supported-by-the-build-script.adoc

@@ -7,7 +7,7 @@ The `build-sh` script supports the following environment variables to customize
 
 `QUARKUS_EXTENSIONS`::
 
-The `QUARKUS_EXTENSIONS` variable specifies additional Quarkus extensions required by the workflow. This variable takes the format of a comma-separated list of fully qualified extension IDs as shown in the following example:
+The `QUARKUS_EXTENSIONS` variable specifies additional link:https://quarkus.io/extensions/[Quarkus] extensions required by the workflow. This variable takes the format of a comma-separated list of fully qualified extension IDs as shown in the following example:
 +
 [source,yaml]
 ----
@@ -18,10 +18,11 @@ Add Kafka messaging support or other integrations at build time.
 
 `MAVEN_ARGS_APPEND`::
 
-The `MAVEN_ARGS_APPEND` variable appends additional arguments to the *Maven build* command.
-This variable takes the format of the string of Maven CLI arguments as shown in the following example:
+The `MAVEN_ARGS_APPEND` variable appends additional arguments to the *Maven build* command. This variable takes the format of a string of Maven CLI arguments as shown in the following example:
 +
 [source,yaml]
 ----
 export MAVEN_ARGS_APPEND="-DmaxYamlCodePoints=35000000"
-----
+----
++
+Control build behavior. For example, set `maxYamlCodePoints` parameter that controls the maximum input size for YAML input files to 35000000 characters (~33MB in UTF-8).

modules/orchestrator/con-generated-workflow-manifests.adoc

@@ -59,11 +59,11 @@ podTemplate:
 persistence:
   postgresql:
     secretRef:
-      name: `sonataflow-psql-postgresql` #  Update to match the name of the Secret of your deployment.
+      name: `sonataflow-psql-postgresql` #  Replace with the Secret name of your deployment.
       userKey: `__<your_postgres_username>__` # Replace with the key for your deployment.
       passwordKey: `__<your_postgres_password>__` # Replace with the password of your deployment.
     serviceRef:
-      name: `sonataflow-psql-postgresql` #  Update to match the name of the Secret of your deployment.
+      name: `sonataflow-psql-postgresql` #  Replace with the Secret name of your deployment.
       port: 5432
       databaseName: sonataflow
       databaseSchema: basic

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

@@ -16,22 +16,22 @@ You can now deploy the workflow on a cluster, since the image has been pushed to
 
 For further instructions on installing these components, see the {orchestrator-book-link}#con-orchestrator-plugin-components.adoc_orchestrator-rhdh[Orchestrator plugin components on {ocp-short}].
 
-* You must apply the workflow manifests in a namespace that contains a `SonataflowPlatform` custom resource (CR), which manages the link:https://docs.redhat.com/en/documentation/red_hat_openshift_serverless/1.36/html-single/serverless_logic/index#serverless-logic-configuring-workflow-services[supporting services]. By default, OpenShift Serverless Logic services are installed in the `sonataflow-infra` namespace.
+* You must apply the workflow manifests in a namespace that contains a `SonataflowPlatform` custom resource (CR), which manages the link:https://docs.redhat.com/en/documentation/red_hat_openshift_serverless/1.36/html-single/serverless_logic/index#serverless-logic-configuring-workflow-services[supporting services].
 
 .Procedure
 
 . Use the `kubectl create` command specifying the target namespace to apply the Kubernetes manifests as shown in the following example:
 +
 [source,bash]
 ----
-kubectl create -n <your-namespace> -f ./01_basic/manifests/.
+kubectl create -n <your_namespace> -f ./01_basic/manifests/.
 ----
 
 . After deployment, monitor the status of the workflow pods as shown in the following example:
 +
 [source,yaml]
 ----
-kubectl get pods -n <your-namespace> -l app=basic
+kubectl get pods -n <your_namespace> -l app=basic
 ----
 +
 The pod may initially appear in an `Error` state because of missing or incomplete configuration  in the Secret or ConfigMap.
@@ -40,7 +40,7 @@ The pod may initially appear in an `Error` state because of missing or incomplet
 +
 [source,yaml]
 ----
-oc logs -n <your-namespace> basic-f7c6ff455-vwl56
+oc logs -n <your_namespace> basic-f7c6ff455-vwl56
 ----
 +
 The following is an example of the output:
@@ -59,7 +59,7 @@ The error indicates a missing property: `quarkus.openapi-generator.notifications
 +
 [source,yaml]
 ----
-oc get -n <your-namespace> configmaps basic-props -o yaml
+oc get -n <your_namespace> configmaps basic-props -o yaml
 ----
 +
 The sample output looks as in the following example:
@@ -81,7 +81,7 @@ Resolve the placeholders using values provided using a Secret.
 +
 [source,yaml]
 ----
-kubectl edit secrets -n <your-namespace> basic-secrets
+kubectl edit secrets -n <your_namespace> basic-secrets
 ----
 . Restart the workflow Pod for Secret changes to take effect in OpenShift Serverless Logic `v1.36`.
 
@@ -91,7 +91,7 @@ kubectl edit secrets -n <your-namespace> basic-secrets
 +
 [source,yaml]
 ----
-oc get pods -n <your-namespace> -l app=basic
+oc get pods -n <your_namespace> -l app=basic
 ----
 +
 The expected status for a successfully deployed workflow Pod is as shown in the following example: