Incorporated Judy's comments

Author: pabel-rh

assemblies/assembly-tracking-component-origin-and-software-template-version.adoc

@@ -5,7 +5,7 @@
 
 Platform engineers use custom actions within the Software Template scaffolding process to establish and track the dependency link between a generated entity (Component or Resource) and its source template. This relationship is called scaffolding provenance.
 
-Platform administrators use the existing custom actions `catalog:scaffolded-from` and `catalog:template:version` in the scaffolder backend module. These actions track the template version and the corresponding entity version, which simplifies lifecycle management.
+Platform administrators use custom actions such as `catalog:scaffolded-from` and `catalog:template:version` in the scaffolder backend module to track the template version and the corresponding entity version, which simplifies lifecycle management.
 
 include::modules/tracking-component-origin-and-software-template-version/proc-configuring-provenance-and-software-template-versioning.adoc[leveloffset=+1]
 

modules/tracking-component-origin-and-software-template-version/proc-configuring-provenance-and-software-template-versioning.adoc

@@ -12,11 +12,10 @@ As a platform engineer, you must modify the Software Template YAML definition to
 .Procedure
 
 . Locate the Software Template object YAML file where you want to add the provenance information and add a step that uses the `catalog:scaffolded-from` action. This action links the resulting catalog entity back to the source template.
-. Optional: To track the template version (for example, v1.0 versus v1.5), include the `catalog:template:version` action in the `steps` section.
+. Optional: To track the template version (for example, v1.0 versus v1.5), include the `catalog:template:version` action in the `steps` section. The following code block is an example to adding versioning action to the `steps` section:
 +
 [source,yaml]
 ----
-# Example: Adding the versioning action to the steps section
 steps:
   - id: create-provenance-annotation
     name: Append the entityRef of this template to the entityRef
@@ -25,16 +24,20 @@ steps:
     name: Create Template Version Annotation
     action: catalog:template:version
     input:
-      templateVersion: ${{ parameters.version }} # Reads the version parameter
+      templateVersion: ${{ parameters.version }}
   - ... other steps ...
 ----
 +
+where:
+
+`steps:input:templateVersion`:: Reads the version parameter
++
 [NOTE]
 ====
-This action reads a version parameter defined in the template and applies it as an annotation to the resulting catalog entity.
+The `catalog:template:version` 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. 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::
+. 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]
 ----
@@ -47,11 +50,12 @@ catalog:
         - allow: [Template]
 # ...
 ----
++
 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.locations.rules.allow`:: To allow new Software Templates to be added to the catalog, you must add a `Template` rule.
+`catalog.locations.type`:: Enter the `url` type if you are importing templates from a repository, such as GitHub or GitLab.
+`catalog.locations.target`:: Enter the URL for the template.
+`catalog.locations.rules.allow`:: Enter the `Template` rule to allow new Software Templates to be added to the catalog.
 
 .Verification
 

modules/tracking-component-origin-and-software-template-version/proc-viewing-software-template-dependencies.adoc

@@ -9,4 +9,4 @@ As a developer, you can track which entities were created from a specific Softwa
 To view all components created from a specific template, complete the following steps:
 
 . In the {product} navigation menu, click *Catalog*, use the filters to find and select the Software Template you wish to inspect.
-. In the Software Template detail page, click the *Dependencies* tab. This view lists all catalog entities (components, resources, systems, etc.) that reference this template, including any version information if configured.
+. In the Software Template detail page, click the *Dependencies* tab. This view lists all catalog entities such as components, resources, and systems that reference this template, including any version information if configured.