Merge pull request #86439 from mramendi/pipelines-1/17-RN-typos

Pipelines RN 1.17 upstream typo fixes

Author: bergerhoffer

modules/op-release-notes-1-17.adoc

@@ -96,7 +96,7 @@ spec:
 
 * With this update, after the execution of a pipeline run or task run, the YAML manifest of the resource contains a label showing the ID of the user who executed it. For a `PipelineRun` resource, the label is `tekton.dev/PipelineRunUID`. For a `TaskRun` resource, the label is `tekton.dev/TaskRunUID`.
 
-* With this update, when you use the `spec.pipeline,performance` spec in the `TektonConfig` CR to specify performance tuning values such as `threads-per-controller`, `kube-api-qps`, and `kube-api-burst`, {pipelines-shortname} applies these values to the resolver controller as well as the other controllers.
+* With this update, when you use the `spec.pipeline.performance` spec in the `TektonConfig` CR to specify performance tuning values such as `threads-per-controller`, `kube-api-qps`, and `kube-api-burst`, {pipelines-shortname} applies these values to the resolver controller as well as the other controllers.
 
 [id="operator-new-features-1-17_{context}"]
 === Operator
@@ -121,7 +121,7 @@ $ tkn task start skopeo-copy -p ARGS="--all --preserve-digests"
 [id="tekton-results-new-features-1-17_{context}"]
 === {tekton-results}
 
-* With this update, you can configure {tekton-results} to include certain labels and annotation from the YAML manifests of pipelines and tasks in the `summary fields` column in the results tables. By default, the value of the `tekton.dev/pipeline` label is used. To make this change, modify the `TektonResult` CR as shown in the following example:
+* With this update, you can configure {tekton-results} to include certain labels and annotations from the YAML manifests of pipelines and tasks in the `summary fields` column in the results tables. By default, the value of the `tekton.dev/pipeline` label is used. To make this change, modify the `TektonResult` CR as shown in the following example:
 +
 .Example of configuring summary labels and annotations in the `TektonResult` CR
 [source,yaml]
@@ -131,17 +131,17 @@ kind: TektonResult
 metadata:
   name: result
 spec:
-     options:
-        deployments:
-           tekton-results-watcher:
-              spec:
-                  template:
-                     spec:
-                        containers:
-                        - name: watcher
-                          args:
-                          - "--summary_labels=org.tekton.sample_label,tekton.dev/pipeline"
-                          - "--summary_annotations=org.tekton.sample_annotation"
+  options:
+    deployments:
+      tekton-results-watcher:
+        spec:
+          template:
+            spec:
+              containers:
+              - name: watcher
+                args:
+                - "--summary_labels=org.tekton.sample_label,tekton.dev/pipeline"
+                - "--summary_annotations=org.tekton.sample_annotation"
 ----
 
 [id="tekton-chains-new-features-1-17_{context}"]
@@ -229,10 +229,10 @@ For more information about using the tasks in the `openshift-pipelines` namespac
 
 * Before this update, if a `CustomRun` resource referred to a pipeline or task resource that returned an array as a result, a result type mismatch was reported in the log. With this update, the array result is processed correctly.
 
-* Before this update, when a task run failed, in some cases the statuses of some of the steps in the task were not recorded correctly in the `TaskRun` YAML manifesto. With this update, the statuses are correctly recorded. 
+* Before this update, when a task run failed, in some cases the statuses of some of the steps in the task were not recorded correctly in the `TaskRun` YAML manifest. With this update, the statuses are correctly recorded.
 
 * Before this update, if a step in a task failed, the subsequent steps were sometimes not marked as skipped in the YAML manifest of the task run or pipeline run. With this update, the steps are marked as skipped.
-
+c
 * Before this update, if a pipeline run included a task that failed validation, a subsequent `finally` task did not run, even though it is expected to run after any failures of the previous tasks. With this update, the `finally` task runs.
 
 * Before this update, when using {pac} with GitLab, if the `.tekton` directory contained more than 20 files, some pipeline runs failed to start. With this update, the pipeline runs start correctly.
@@ -255,8 +255,8 @@ For more information about using the tasks in the `openshift-pipelines` namespac
 
 * Before this update, if you specified default container resource requirements in the `TektonConfig` CR and then applied a `LimitRange` setting to a pipeline or task, the `LimitRange` setting was sometimes not applied because the default requirements overrode it. With this update, the `LimitRange` setting overrides the default container resource requirements.
 
-* Before this update, if a pipeline run or task run failed to execute because of a validation error, {pipelines-shortname} recorded and displayed a generic `Failed` status for the pipeline run or task run. With this update, {pipelines-shortname} records a `Failed Validation` status. 
+* Before this update, if a pipeline run or task run failed to execute because of a validation error, {pipelines-shortname} recorded and displayed a generic `Failed` status for the pipeline run or task run. With this update, {pipelines-shortname} records a `Failed Validation` status.
 
 * Before this update, when you used the `tkn bundle` command to read the content of a large-sized Tekton bundle, the command might fail. With this update, the `tkn` command-line utilities correctly handles large Tekton bundles.
 
-* Before this update, when you used the `tkn` command-line utility to view a completed pipeline run, tasks that were skipped because of conditions you set up in the pipeline were displayed as `Succeeded(Completed)`. With this update, they are no longer displayed as completed. 
+* Before this update, when you used the `tkn` command-line utility to view a completed pipeline run, tasks that were skipped because of conditions you set up in the pipeline were displayed as `Succeeded(Completed)`. With this update, they are no longer displayed as completed.