Topology modularization

Author: GitHub Actions

modules/importing-repositories/procedure-enabling-the-bulk-import-from-github-feature.adoc

@@ -6,7 +6,7 @@
 You can enable the Bulk Import feature for users and give them the necessary permissions to access it.
 
 .Prerequisites
-* You have {introduction-to-plugins-book-link}#enabling-github-repository-discovery[enabled GitHub repository discovery].
+* You have {integrating-with-github-book-link}#enabling-github-repository-discovery[enabled GitHub repository discovery].
 
 .Procedure
 . The Bulk Import plugins are installed but disabled by default.

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

@@ -26,7 +26,7 @@ Empty:: {product-short} is unable to determine the import job status because the
 [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 `{my-app-config-file}` file, dynamically when {introduction-to-plugins-book-link}#enabling-github-repository-discovery[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:
+* A location added through other sources (like statically in an `{my-app-config-file}` file, dynamically when {integrating-with-github-book-link}#enabling-github-repository-discovery[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.
 ====