Apply suggestions from code review

Co-authored-by: Heena Manwani <[email protected]>

Author: themr0c

modules/importing-repositories/procedure-importing-multiple-repositories-from-github.adoc

@@ -18,20 +18,20 @@ This option allows you to select one or more repositories from the selected orga
 The pull request details form is preloaded with some data, and you can also preview the content of the `catalog-info.yaml`.
 If the repository already has a `.github/CODEOWNERS` file, you can select the *Use CODEOWNERS file as Entity Owner* checkbox to use it, rather than having the `content-info.yaml` contain a specific entity owner.
 . Click on *Save*.
-. Click on *Create pull requests*.
-At this point, a set of dry-run checks will be run against the selected repositories to make sure they meet the requirements to be imported, that is:
-.. Checking that there is no entity in the Developer Hub catalog with the name specified in the repository `catalog-info.yaml`
+. Click *Create pull requests*.
+At this point, a set of dry-run checks runs against the selected repositories to ensure they meet the requirements for import, such as:
+.. Verifying that there is no entity in the {product-short} catalog with the name specified in the repository `catalog-info.yaml`
 .. Checking that the repository is not empty
-.. Checking that the repository already has a `.github/CODEOWNERS` file if the *Use CODEOWNERS file as Entity Owner* checkbox was selected for that repository.
+.. Verifying that the repository contains a `.github/CODEOWNERS` file if the *Use CODEOWNERS file as Entity Owner* checkbox is selected for that repository.
 
-** If there are any errors, the pull requests will not be created, but you will see a _Failed to create PR_ error message indicating the failures.
-Clicking on *Edit* will show more details about the reasons.
+** If any errors occur, the pull requests are not created, and you will see a _Failed to create PR_ error message detailing the issues.
+To view more details about the reasons, click *Edit*.
 
-** If there are no errors, the pull requests will be created, and you will be redirected to the list of Added repositories.
+** If there are no errors, the pull requests are created, and you will be redirected to the list of added repositories.
 
 . Review and merge each pull request that creates a `catalog-info.yml` file.
 
 .Verification
 * The *Added repositories* list displays the repositories you just imported, each with an appropriate status: either _Waiting for approval_ or _Added_.
-* For each _Waiting for approval_ Import job listed, there is a corresponding pull request adding the `catalog-info.yaml` file in the corresponding repository
+* For each _Waiting for approval_ import job listed, there is a corresponding pull request adding the `catalog-info.yaml` file in the corresponding repository
 

modules/importing-repositories/procedure-managing-the-imported-repository-list.adoc

@@ -1,30 +1,30 @@
 = Managing the list of Added repositories
 
 .Prerequisites
-* xref:enabling-ang-giving-access-to-the-bulk-import-feature[You enabled the Bulk Import feature].
-* xref:enabling-ang-giving-access-to-the-bulk-import-feature[Your {product-short} user has access to the Bulk Import feature].
+* You have xref:enabling-ang-giving-access-to-the-bulk-import-feature[enabled the Bulk Import feature].
+* You have xref:enabling-ang-giving-access-to-the-bulk-import-feature[access to the Bulk Import feature].
 
 
 .Procedure
-. Click on *Bulk Import* in the left sidebar to display all the current repositories that are being tracked as Import jobs, along with their status.
+. Click *Bulk Import* in the left sidebar to display all the current repositories that are being tracked as Import jobs, along with their status.
 
-Added:: The repository has been added to the Developer Hub catalog.
+Added:: The repository is added to the {product-short} catalog after the import pull request is merged or if the repository already contained a `catalog-info.yaml` file during the bulk import. 
 This can be the case after the import PR has been merged, or if the repository already had a `catalog-info.yaml` when it was bulk-imported.
-Please note that it might take a few minutes until the entities are available in the catalog.
+Note that it may take a few minutes for the entities to be available in the catalog.
 
-Waiting for approval:: There is an open pull request adding a `catalog-info.yaml`.
+Waiting for approval:: There is an open pull request adding a `catalog-info.yaml` file to the repository.
 You can:
-* Click on the *pencil icon* on the right to see details about this pull request or edit the pull request content right from {product-short}.
-* Delete the Import job, in which case the import PR will be closed as well.
+* Click the *pencil icon* on the right to see details about the pull request or edit the pull request content right from {product-short}.
+* Delete the Import job, this closes the import PR as well.
 * To transition the Import job to the _Added_ state, merge the import pull request from the Git repository.
 
-Empty:: {product-short} was not able to determine the Import job status.
+Empty:: {product-short} is unable to determine the import job status because the repository is imported from other sources but does not have a `catalog-info.yaml` file and lacks any import pull request adding it.
 This can be the case if the repository was imported from other sources but does not have any `catalog-info.yaml` file and does not have any import PR adding it.
 
 [NOTE]
 ====
-* After an import pull request is merged, the Import status will be _Added_ in the list of Added Repositories, but it might take a few seconds until the corresponding entities show up in the Developer Hub Catalog.
-* A Location added through other sources (like statically in an `app-config.yaml` file, dynamically when link:{linkgettingstartedguide}#enabling-github-discovery-in-red-hat-developer-hub[enabling GitHub discovery], or registered manually via the "Register an existing component" page) may show up in the Bulk Import list of Added Repositories if both conditions are met:
+* After an import pull request is merged, the import status is marked as _Added_ in the list of Added Repositories, but it might take a few seconds for the corresponding entities to appear in the {product-short} Catalog.
+* A location added through other sources (like statically in an `app-config.yaml` file, dynamically when link:{linkgettingstartedguide}#enabling-github-discovery-in-red-hat-developer-hub[enabling GitHub discovery], or registered manually using the "Register an existing component" page) may show up in the Bulk Import list of Added Repositories if the following conditions are met:
 ** The target repository is accessible from the configured GitHub integrations.
-** The Location URL points to a `catalog-info.yaml` file at the root of the repository default branch.
+** The location URL points to a `catalog-info.yaml` file at the root of the repository default branch.
 ====