Minor change

Author: pabel-rh

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, 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::
+. In your `{product} {my-app-config-file}` file, configure the `catalog.locations` section to point to the Software Template that you want to add. You might need to add `Template` to the global `catalog.rules.allow` list or add a granular rule to the location to allow for Software Templates ingestion, as shown in the following example::
 +
 [source,yaml]
 ----
@@ -49,12 +49,6 @@ where:
 `catalog.locations.type`:: If you are importing templates from a repository, such as GitHub or GitLab, use the `url` type.
 `catalog.locations.target`:: Specify the URL for the template.
 `catalog.rules.allow`:: To allow new Software Templates to be added to the catalog, you must add a `Template` rule.
-+
-[NOTE]
-====
-If Software Templates do not appear in the Catalog after this configuration, you must include the `Template` entity type in your application global `catalog.rules.allow` list, alongside any other existing catalog entity types.
-====
-
 
 .Verification