Apply suggestions from code review

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

Author: themr0c

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

@@ -21,17 +21,17 @@ This option allows you to select one or more repositories from the selected orga
 . 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
-.. Verifying that the repository contains a `.github/CODEOWNERS` file if the *Use CODEOWNERS file as Entity Owner* checkbox is selected for that repository.
+.. Verifying that the repository is not empty
+.. Verifying that the repository contains a `.github/CODEOWNERS` file if the *Use CODEOWNERS file as Entity Owner* checkbox is selected for that repository
 
-** If any errors occur, the pull requests are not created, and you will see a _Failed to create PR_ error message detailing the issues.
+** If any errors occur, the pull requests are not created, and you 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 are created, and you will be redirected to the list of added repositories.
+** If there are no errors, the pull requests are created, and you are 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
+* The *Added repositories* list displays the repositories you 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.
 

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

@@ -1,6 +1,6 @@
 [id="managing-the-added-repositories]
 = Managing the added repositories
-
+You can oversee and manage the repositories that are imported to the {product-short}.
 .Prerequisites
 * You have xref:importing-multiple-github-repositories[imported GitHub repositories].
 
@@ -15,7 +15,7 @@ Note that it may take a few minutes for the entities to be available in the cata
 Waiting for approval:: There is an open pull request adding a `catalog-info.yaml` file to the repository.
 You can:
 * 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.
+* Delete the Import job, this action 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} 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.
@@ -24,7 +24,7 @@ This can be the case if the repository was imported from other sources but does
 [NOTE]
 ====
 * 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:
+* 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) might 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.
 ====

modules/importing-repositories/procedure-understanding-bulk-import-audit-logs.adoc

@@ -2,7 +2,7 @@
 = Understanding the Bulk Import audit Logs
 
 The Bulk Import backend plugin adds the following events to the {product-short} audit logs.
-See link:{linkgettingstartedguide}#assembly-audit-log[Audit Logs in {product}] for more information on how to configure and view such audit logs.
+See link:{linkgettingstartedguide}#assembly-audit-log[Audit Logs in {product}] for more information on how to configure and view audit logs.
 
 *Bulk Import Events*: