Apply suggestions

Author: GitHub Actions

modules/importing-repositories/procedure-bulk-import-scaffolder-template.adoc

@@ -32,11 +32,11 @@ For example, for `https://github.com/redhat-developer/rhdh-plugins`, the `organi
 +
 For example, for `https://github.com/redhat-developer/rhdh-plugins`, the `gitProviderHost` is `github.com`. You can use this parameter to write `Git-provider-agnostic` templates.
 
-To use parameters in a Scaffolder template:
+To use these parameters in a Scaffolder template:
 [source,yaml]
 ----
 parameters:
-  - title: Repository Details
+  - title: Repository details
     required:
       - repoUrl
       - branchName
@@ -50,7 +50,7 @@ parameters:
         description: `github.com?owner=Org&repo=repoName` | `gitlab.com?owner=Org&repo=repoName`
       organization:
         type: string
-        title: Owner of the Repository
+        title: Owner of the repository
       name:
         type: string
         title: Name of the repository

modules/importing-repositories/procedure-data-handoff-and-custom-workflow-design.adoc

@@ -6,12 +6,12 @@
 
 When you configure the Bulk Import plugin by setting the importAPI field to `scaffolder`, the Bulk Import Backend ensures all necessary context is passed directly to the Scaffolder API.
 
-Your control over input data:: The Orchestrator workflow receives the input data required to automate processing for every selected repository. The payload includes, at minimum, the complete list of repository URLs and the user identity.
+Your control over input data:: The Orchestrator workflow receives the input data required to automate processing for every selected repository. For each repository in that list, the bulk import launches the scaffolder template once and passes the data for that single repository to the template run.
 
 As an administrator, you can define the Scaffolder template workflow and structure the workflow to do the following:
 
-Consume the input:: Accept the repositories array as primary input.
+Consume the input:: The Scaffolder template receives the repository data as template parameters for the current execution.
 
-Iterate and process:: Loop through the list, executing the custom logic for example, creating the `catalog-info.yaml` if needed, then running compliance checks, then registering with the catalog.
+Iterate and process:: The orchestrator handles iterating through the repository list and launches the template for each repository. Within a single template run, implement the custom logic for that single repository. For example, create the `catalog-info.yaml` if needed, run compliance checks, then register with the catalog.
 
 Manage lifecycle:: The Scaffolder template workflow owns the entire import lifecycle for the repository list, providing a single point of management and traceability.