Merge pull request #184 from Chr1st1anSears/update-ec-doc-again

Update step #5 per HACBS-2307

Author: Chr1st1anSears

docs/modules/ROOT/pages/how-to-guides/proc_managing-compliance-with-the-enterprise-contract.adoc

@@ -18,7 +18,9 @@ The Enterprise Contract (EC) is an artifact verifier and customizable policy che
 . Select *Add integration test*.
 . In the *Integration test name* field, enter a name of your choosing.
 . In the *GitHub URL* field, enter *https://github.com/redhat-appstudio/build-definitions*
-. In the *Path in repository* field, enter */pipelines/enterprise-contract.yaml*
+. In the *Path in repository* field, to use the default EC configuration, enter */pipelines/enterprise-contract.yaml*
+.. You can also enter any of the paths in the link:https://github.com/enterprise-contract/config#readme[list of Enterprise Contract Configuration Files], to use a configuration that matches your specific needs more closely.
+.. For example, to verify your artifacts with the policy rules that Red Hat uses, enter */pipelines/enterprise-contract-redhat.yaml*
 . Optional: If passing the this test is optional, and you do not want to prevent the application from being deployed or released, then select *Mark as optional for release*.
 . Select *Add Integration test*.
 . Trigger a new build by commiting a change in the GitHub repository of the application you are working with.