Merge pull request #91899 from mramendi/RHDEVDOCS-6418

RHDEVDOCS 6418 fix example for custom parameter filtering

Author: mburke5678

modules/op-custom-parameter-expansion.adoc

@@ -14,7 +14,7 @@ You can use custom parameters in the following scenarios:
 
 [NOTE]
 ====
-Use the custom parameter expansion feature only when you cannot use the Tekton `PipelineRun` parameters because Tekton parameters are defined in a `Pipeline` resource and customized alongside it inside a Git repository. However, custom parameters are defined and customized where the `Repository` CR is located. So, you cannot manage your CI/CD pipeline from a single point. 
+Use the custom parameter expansion feature only when you cannot use the Tekton `PipelineRun` parameters because Tekton parameters are defined in a `Pipeline` resource and customized alongside it inside a Git repository. However, custom parameters are defined and customized where the `Repository` CR is located. So, you cannot manage your CI/CD pipeline from a single point.
 ====
 
 The following example shows a custom parameter named `company` in the `Repository` CR:
@@ -31,7 +31,7 @@ spec:
 
 The value `ABC Company` replaces the parameter name `company` in your pipeline run and in the remotely fetched tasks.
 
-You can also retrieve the value for a custom parameter from a Kubernetes secret, as shown in the following example: 
+You can also retrieve the value for a custom parameter from a Kubernetes secret, as shown in the following example:
 
 [source,yaml]
 ----
@@ -60,10 +60,7 @@ spec:
   params:
     - name: company
       value: "ABC Company"
-      filter:
-        - name: event
-          value: |
-      pac.event_type == "pull_request"
+      filter: pac.event_type == "pull_request"
 ...
 ----