Apply Piotr and Yona's suggestions

Author: GitHub Actions

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

@@ -20,7 +20,7 @@ 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.
+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:
 
 [source,yaml]

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

@@ -22,7 +22,7 @@ Values are not required at this stage as you can set them later after applying C
 
 [Important]
 ====
-In OpenShift Serverless Logic `v1.35`, after updating a secret, you must manually restart the workflow Pod for changes to apply.
+In OpenShift Serverless Logic `v1.36`, after updating a secret, you must manually restart the workflow Pod for changes to apply.
 ====
 
 `01-configmap_basic-props.yaml`::
@@ -54,21 +54,21 @@ podTemplate:
 ----
 
 .The persistence configuration example:
-[source,yaml]
+[source,yaml,subs="+quotes"]
 ----
 persistence:
   postgresql:
     secretRef:
-      name: sonataflow-psql-postgresql
-      userKey: postgres-username
-      passwordKey: postgres-password
+      name: `sonataflow-psql-postgresql` #  Update to match the name of the Secret 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
+      name: `sonataflow-psql-postgresql` #  Update to match the name of the Secret of your deployment.
       port: 5432
       databaseName: sonataflow
       databaseSchema: basic
 ----
 
-If you must connect to an external database, replace `serviceRef` with a `jdbcUrl`. See the link:https://sonataflow.org/serverlessworkflow/latest/cloud/operator/enabling-jobs-service.html#_using_the_persistence_field_defined_in_the_sonataflowplatform_cr[SonataFlow Guides] for more information.
+If you must connect to an external database, replace `serviceRef` with a `jdbcUrl`. See link:https://docs.redhat.com/en/documentation/red_hat_openshift_serverless/1.36/html-single/serverless_logic/index#serverless-logic-managing-persistence[Managing workflow persistence].
 
-By default, the script generates all the manifests without a namespace. You can specify a namespace to the script by using the `--namespace` flag if you know the target namespace in advance. Otherwise, you must provide the namespace when applying the manifests to the cluster. See link:https://sonataflow.org/serverlessworkflow/latest/cloud/operator/configuring-workflows.html[Configuring workflow services].
+By default, the script generates all the manifests without a namespace. You can specify a namespace to the script by using the `--namespace` flag if you know the target namespace in advance. Otherwise, you must provide the namespace when applying the manifests to the cluster. See link:https://docs.redhat.com/en/documentation/red_hat_openshift_serverless/1.36/html-single/serverless_logic/index#serverless-logic-configuring-workflow-services[Configuring workflow services].

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

@@ -9,29 +9,29 @@ You can now deploy the workflow on a cluster, since the image has been pushed to
 
 * You have an {ocp-short} cluster with the following versions of components installed:
 
-*   {product} ({product-very-short}) `v1.5`
-*   Orchestrator plugins `v1.4` or `v1.5`
-*   OpenShift Serverless `v1.35`
-*   OpenShift Serverless Logic `v1.35`
+*   {product} ({product-very-short}) `v1.7`
+*   Orchestrator plugins `v1.7.1`
+*   OpenShift Serverless `v1.36`
+*   OpenShift Serverless Logic `v1.36`
 
 For further instructions on installing these components, see the {orchestrator-book-link}#con-orchestrator-plugin-components[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://sonataflow.org/serverlessworkflow/latest/cloud/operator/supporting-services.html[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]. By default, OpenShift Serverless Logic services are installed in the `sonataflow-infra` namespace.
 
 .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 sonataflow-infra -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 sonataflow-infra -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 sonataflow-infra 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 sonataflow-infra 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,17 +81,17 @@ Resolve the placeholders using values provided using a Secret.
 +
 [source,yaml]
 ----
-kubectl edit secrets -n sonataflow-infra 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.35`.
+. Restart the workflow Pod for Secret changes to take effect in OpenShift Serverless Logic `v1.36`.
 
 .Verification
 
 . Verify the deployment status by checking the pods again as shown in the following example:
 +
 [source,yaml]
 ----
-oc get pods -n sonataflow-infra -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: