Update suggestions

Author: GitHub Actions

assemblies/assembly-bulk-importing-from-github.adoc

@@ -19,4 +19,4 @@ include::modules/importing-repositories/concept-bulk-import-scaffolder-template.
 
 include::modules/importing-repositories/procedure-integrating-bulk-import-with-orchestrator-workflows.adoc[leveloffset=+1]
 
-include::modules/importing-repositories/procedure-data-handoff-and-custom-workflow-design.adoc[leveloffset=+1]
+include::modules/importing-repositories/concept-data-handoff-and-custom-workflow-design.adoc[leveloffset=+1]

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

@@ -1,7 +1,7 @@
 :_mod-docs-content-type: CONCEPT
 
 [id="bulk-import-scaffolder-template"]
-= Understanding Bulk Import Scaffolder template input parameters
+= Configure input parameters for Bulk Import Scaffolder template
 
 As an administrator, you can use the Bulk Import plugin to run a Scaffolder template task with specified parameters, which you must define within the template.
 
@@ -13,26 +13,18 @@ The Bulk Import plugin analyzes Git repository information and provides the foll
 ----
   ${gitProviderHost}?owner=${owner}&repo=${repository-name}
 ----
-+
-For example, when you run the process, the plugin transforms `https://github.com/redhat-developer/rhdh-plugins` into `github.com?owner=redhat-developer&repo=rhdh-plugins`.
 
 `name`:: The repository name.
-+
-For example, the `name` is `rhdh-plugins`.
 
 `organization`:: The repository owner, which can be a user nickname or organization name.
-+
-For example, the `organization` is `redhat-developer`.
 
 `branchName`:: The proposed repository branch. By default, the proposed repository branch is `bulk-import-catalog-entity`.
 
 `targetBranchName`:: The default branch of the Git repository.
 
-`gitProviderHost`:: The Git provider host parsed from the repository URL.
-+
-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.
+`gitProviderHost`:: The Git provider host parsed from the repository URL. You can use this parameter to write `Git-provider-agnostic` templates.
 
-Using these parameters in a Scaffolder template:
+Example of a Scaffolder template:
 [source,yaml]
 ----
 parameters:

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

@@ -1,15 +1,13 @@
-:_mod-docs-content-type: PROCEDURE
+:_mod-docs-content-type: CONCEPT
 
 [id="full-data-handoff-and-custom-workflow-design"]
 
 = Data handoff and custom workflow design
 
-When you configure the Bulk Import plugin by setting the importAPI field to `scaffolder`, the Bulk Import Backend passed all necessary context directly to the Scaffolder API.
+When you configure the Bulk Import plugin by setting the importAPI field to `scaffolder`, the Bulk Import Backend passes all necessary context directly to the Scaffolder API.
 
 As an administrator, you can define the Scaffolder template workflow and structure the workflow to do the following:
 
 Define template parameters to consume input:: Structure the Scaffolder template to receive the repository data as template parameters for the current workflow run. The template must be generic, and not specific to a single repository, so that it can successfully run for every repository in the bulk list.
 
-Automate processing for each repository:: Implement the custom logic needed for a single repository within the template. The Orchestrator iterates through the repository list, launching the template once for each repository and passes only the data for that single repository to the template run. This allows you to automate tasks like creating the `catalog-info.yaml`, running compliance checks, or registering the entity with the catalog.
-
-Centralize import workflow management:: Use the Scaffolder template to define and manage the entire import lifecycle for the repository list, providing you with a single point of management and traceability for the bulk operation. This method offers greater flexibility in defining the import scenario.
+Automate processing for each repository:: Implement the custom logic needed for a single repository within the template. The Orchestrator iterates through the repository list, launching the template once for each repository and passes only the data for that single repository to the template run. This allows you to automate tasks such as creating the `catalog-info.yaml`, running compliance checks, or registering the entity with the catalog.

modules/importing-repositories/procedure-integrating-bulk-import-with-orchestrator-workflows.adoc

@@ -3,34 +3,35 @@
 [id="integrating-bulk-import-with-orchestrator-workflows"]
 = Setting up a custom Scaffolder workflow for Bulk Import
 
-As an administrator, you can create a Scaffolder template that reflects the repository conventions of your organization and add it into the {product} catalog for use by the Bulk Import plugin.
-
-The Scaffolder workflow offers flexibility because the specific import steps are defined by your template content.
+As an administrator, you can create a custom Scaffolder template in line with the repository conventions of your organization and add the template into the {product} catalog for use by the Bulk Import plugin on multiple selected repositories.
 
 You can define various custom tasks, including, but not limited to the following:
 
 * Importing existing catalog entities from a repository
 * Creating pull requests for cleanup
 * Calling webhooks for external system integration
 
-You can run a custom automation workflow of a Scaffolder template on multiple selected repositories using the bulk import plugin.
-
 .Prerequisites
 
 * You created a custom Scaffolder template for the Bulk Import plugin.
 
+* For the {product-very-short} instance to use the Scaffolder functionality, you must run it with the following environment variable enabled:
++
+[source,yaml]
+----
+export NODE_OPTIONS=--no-node-snapshot
+----
+
 .Procedure
 
-* Configure your {my-app-config-file} configuration to instruct the Bulk Import plugin to use your custom templates.
-+
-Optional: You can direct the Bulk Import plugin to hand off the entire list of selected repositories to a custom Orchestrator workflow.
+* Configure your {my-app-config-file} configuration to instruct the Bulk Import plugin to use your custom template.
 +
 To configure the Bulk Import workflow:
 +
 [source,yaml]
 ----
 bulkImport:
-  importTemplate: your-template-entity-reference-or-template-name
+  importTemplate: <your_template_entity_reference_or_template_name>
   importAPI: `open-pull-requests` | `scaffolder`;
 ----
 +
@@ -45,19 +46,14 @@ Set the API to 'scaffolder' to trigger the defined workflow for high-fidelity au
 `open-pull-requests`:: This is the default import workflow, which includes the logic for creating pull requests for every selected repository.
 
 `scaffolder`:: This workflow uses an import scenario defined in the Scaffolder template to create import jobs. Select this option to use the custom import scenario defined in your Scaffolder template.
+
+Optional: You can direct the Bulk Import plugin to hand off the entire list of selected repositories to a custom Orchestrator workflow.
 +
 [IMPORTANT]
 ====
 The Scaffolder template must be generic and not specific to a single repository if you want your custom Scaffolder template to run successfully for every repository in the bulk list.
 ====
 
-* For the {product-very-short} instance to use the Scaffolder functionality, you must run it with the following environment variable enabled:
-
-[source,yaml]
-----
-export NODE_OPTIONS=--no-node-snapshot
-----
-
 .Verification
 
-* The Bulk Import plugin runs the custom Scaffolder template for the list of repositories using the `/task-imports` API endpoint (the `createTaskImportJobs` method).
+* The Bulk Import plugin runs the custom Scaffolder template for the list of repositories using the `/task-imports` API endpoint.