Add suggestions

Signed-off-by: Manuel Lorenzo <mlorenzofr@redhat.com>

Author: mlorenzofr

docs/supply-chain.md

@@ -11,9 +11,9 @@ In this project, we used the [qtodo](https://github.com/validatedpatterns-demos/
 * [Red Hat Trusted Artifact Signer (RHTAS)](https://docs.redhat.com/en/documentation/red_hat_trusted_artifact_signer/1) is a solution for signing and verifying software artifacts to ensure their integrity and authenticity.
 * [Red Hat Trusted Profile Analyzer (RHTPA)](https://docs.redhat.com/en/documentation/red_hat_trusted_profile_analyzer/2) is a product that helps DevSecOps teams gain visibility into software supply chain risks by analyzing _Software Bill of Materials_ (SBOMs) and crossing data with _Vulnerability Exploitability eXchange_ (VEX) and _Common Vulnerabilities and Exposures_ (CVE) databases.
 
-### Auxiliary
+### Supporting Components
 
-In our demo, we will use a number of additional ZTVP components. These components are auxiliary, helping us to prepare a ZT-compliant environment, but they are also cross-cutting and can be replaced by other compatible solutions.
+In our demo, we will use a number of additional ZTVP components. These components are auxiliary, and help us prepare an environment compatible with Zero Trust (ZT), but they are also cross-cutting and can be replaced by other compatible solutions.
 
 * [Red Hat Zero Trust Workload Identity Manager](https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/security_and_compliance/zero-trust-workload-identity-manager) is a solution that automates the provisioning and management of verifiable identities based on SPIRE/SPIFFE for workloads on OpenShift. It will be used to manage the signature and verification. It could be replaced by your own OIDC.
 * [Red Hat Quay](https://docs.redhat.com/en/documentation/red_hat_quay/3) is container registry platform for storing and distributing container images and cloud-native artifacts. We will use it to store the image, signature, and attestations associated with our application. An alternate image registry can be used if desired.
@@ -22,7 +22,7 @@ In our demo, we will use a number of additional ZTVP components. These component
 
 ## Automatic approach
 
-To automate the application building and certification process, we will use _Red Hat Openshift Pipelines_.
+To automate the application building and certifying process, we will use _Red Hat OpenShift Pipelines_.
 
 ZTVP will create a `Pipeline` in our cluster called **qtodo-supply-chain** that will orchestrate the various tasks necessary to build the application from its source code, generate a container image, and publish the resulting image to the defined OCI registry. Within the pipeline, an SBOM containing the build's contents will be generated, binaries and the build attestation will be signed, and the validity of those signatures will be verified.
 
@@ -70,12 +70,20 @@ spec:
       secretName: qtodo-registry-auth
 ```
 
+As was described previously, verify the values associated with the PVC storage and registry configuration.
+
 Using the previously created definition, start a new execution of the pipeline using `oc` CLI:
 
 ```shell
 oc create -f qtodo-pipeline.yaml
 ```
 
+You can review the current pipeline logs using the [Tekton CLI](https://tekton.dev/docs/cli/).
+
+```shell
+tkn pipeline logs -n layered-zero-trust-hub -L -f
+```
+
 ### Pipeline tasks
 
 The pipeline we have prepared has the following steps: