Update bulk import

Author: GitHub Actions

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

@@ -4,7 +4,7 @@
 
 = Data handoff and custom workflow design
 
-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 Orchestrator.
+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.
 +
@@ -21,10 +21,10 @@ Your control over input data:: The Orchestrator workflow receives the input data
 }
 ----
 
-As an administrator, you can define the Orchestrator workflow and structure the workflow to do the following:
+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.
 
 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.
 
-Manage lifecycle:: The Orchestrator workflow owns the entire import lifecycle for the repository list, providing a single point of management and traceability.
+Manage lifecycle:: The Scaffolder template workflow owns the entire import lifecycle for the repository list, providing a single point of management and traceability.

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

@@ -3,7 +3,7 @@
 [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 specifically for the Bulk Import plugin. You can provide the scaffolder template within the configuration of your application.
+As an administrator, you can create a scaffolder template specifically for the Bulk Import plugin. You can provide the Scaffolder template within the configuration of your application.
 
 You can run the following tasks with this integration:
 
@@ -15,7 +15,7 @@ You can execute a custom automation workflow of a Scaffolder template on multipl
 
 .Prerequisites
 
-* You created a Scaffolder template specifically designed for the Bulk Import function and provided the scaffolder template within the configuration of your application. This template is the core definition of your customized import scenario.
+* You created a Scaffolder template specifically designed for the Bulk Import function and provided the Scaffolder template within the configuration of your application. This template is the core definition of your customized import scenario.
 
 .Procedure
 
@@ -28,26 +28,26 @@ To configure the Bulk Import workflow:
 ----
 bulkImport:
   importTemplate: your-template-entity-reference-or-template-name
-  importAPI: 'scaffolder'
+  importAPI: `open-pull-requests` | `scaffolder`;
 ----
 where:
 
 `importTemplate:`::
-Enter your template entity reference or name of your Scaffolder template.
+Enter your Scaffolder template entity reference.
 
 `importAPI`::
 Set the API to 'scaffolder' to trigger the defined workflow for high-fidelity automation. This field defines the import workflow and currently supports two following options:
 
 `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. Select this option to use the custom import scenario defined in your Scaffolder template.
+`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.
 +
 [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:
+For the {product-very-short} instance to use the Scaffolder functionality, you must run it with the following environment variable enabled:
 
 [source,yaml]
 ----