[pipelines-docs-1.19] RHDEVDOCS 6421 use secret_ref: instead of secretRef:

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. Therefore, you cannot manage your CI/CD pipeline from a single point.
 ====
 
 The following example shows a custom parameter named `company` in the `Repository` CR:
@@ -39,15 +39,15 @@ You can also retrieve the value for a custom parameter from a Kubernetes secret,
 spec:
   params:
     - name: company
-      secretRef:
+      secret_ref:
         name: my-secret
         key: companyname
 ...
 ----
 
 {pac} parses and uses custom parameters in the following manner:
 
-* If you have a `value` and a `secretRef` defined, {pac} uses the `value`.
+* If you have a `value` and a `secret_ref` defined, {pac} uses the `value`.
 * If you do not have a `name` in the `params` section, {pac} does not parse the parameter.
 * If you have multiple `params` with the same `name`, {pac} uses the last parameter.