Update docs/stepactions.md

Co-authored-by: Jerop Kipruto <[email protected]>

docs/stepactions.md

@@ -137,7 +137,7 @@ Note that the `securityContext` from `StepAction` will overwrite the `securityCo
 
 ### Declaring VolumeMounts
 
-You can define `VolumeMounts` in `StepAction`, note that the `name` of the `VolumeMount` MUST be a **single param reference** to a string param ( for example, `$(params.registryConfig)` is valid but `$(params.registryConfig)-foo` or `"unparametrized-name"` is invalid). This is to avoid the case where `VolumeMount` from 2 different `StepActions` using the same mounted volume but different names. In this case the Task Author doesn't need to provide 2 separate volume devices.
+You can define `VolumeMounts` in `StepActions`. The `name` of the `VolumeMount` MUST be a single reference to a string `Parameter`. For example, `$(params.registryConfig)` is valid while `$(params.registryConfig)-foo` and `"unparametrized-name"` are invalid. This is to ensure reusability of `StepActions` such that `Task` authors have control of which `Volumes` they bind to the `VolumeMounts`.
 
 ```yaml
 apiVersion: tekton.dev/v1alpha1