Minor change

pabel-rh · pabel-rh · commit 6d7a81ec4e16 · 2025-11-03T20:03:57.000+05:30
diff --git a/modules/tracking-component-origin-and-software-template-version/proc-configuring-provenance-and-software-template-versioning.adoc b/modules/tracking-component-origin-and-software-template-version/proc-configuring-provenance-and-software-template-versioning.adoc
@@ -31,7 +31,7 @@ steps:
 This action reads a version parameter defined in the template and applies it as an annotation to the resulting catalog entity.
 ====
 
-. In your `{product} {my-app-config-file}` file, modify the `catalog.rules` section to include a rule for Software Templates, and configure the `catalog.locations` section to point to the Software Template that you want to add, as shown in the following example:
+. In your `{product} {my-app-config-file}` file, configure the `catalog.locations` section to point to the Software Template that you want to add and add a granular rule to the location to allow for Software Templates, as shown in the following example::
 +
 [source,yaml]
 ----

Original file line number	Diff line number	Diff line change
`@@ -31,7 +31,7 @@ steps:`
`31`	`31`	`This action reads a version parameter defined in the template and applies it as an annotation to the resulting catalog entity.`
`32`	`32`	`====`
`33`	`33`
`34`		-. In your `{product} {my-app-config-file}` file, modify the `catalog.rules` section to include a rule for Software Templates, and configure the `catalog.locations` section to point to the Software Template that you want to add, as shown in the following example:
	`34`	+. In your `{product} {my-app-config-file}` file, configure the `catalog.locations` section to point to the Software Template that you want to add and add a granular rule to the location to allow for Software Templates, as shown in the following example::
`35`	`35`	`+`
`36`	`36`	`[source,yaml]`
`37`	`37`	`----`