fixing ConceptLinks

Author: klgill

docs_user/assemblies/assembly_migrating-ceph-cluster.adoc

@@ -31,9 +31,9 @@ already part of the {CephCluster} cluster.
 
 Before you begin the migration, complete the tasks in your {rhos_prev_long} {rhos_prev_ver} environment. For more information, see xref:red-hat-ceph-storage-prerequisites_configuring-network[{Ceph} prerequisites].
 
-include::../modules/con_ceph-migration-dcn.adoc[leveloffset=+1]
+include::../modules/ref_ceph-migration-dcn.adoc[leveloffset=+1]
 
-include::../modules/con_ceph-daemon-cardinality.adoc[leveloffset=+1]
+include::../modules/ref_ceph-daemon-cardinality.adoc[leveloffset=+1]
 
 include::assembly_migrating-ceph-monitoring-stack.adoc[leveloffset=+1]
 

docs_user/assemblies/assembly_rhoso-180-adoption-overview.adoc

@@ -18,11 +18,11 @@ include::../modules/con_adoption-limitations.adoc[leveloffset=+1]
 
 //include::../modules/con_known-issues-adoption.adoc[leveloffset=+1]
 
-include::../modules/con_adoption-prerequisites.adoc[leveloffset=+1]
+include::../modules/ref_adoption-prerequisites.adoc[leveloffset=+1]
 
 include::../modules/con_adoption-guidelines.adoc[leveloffset=+1]
 
-include::../modules/con_adoption-process-overview.adoc[leveloffset=+1]
+include::../modules/ref_adoption-process-overview.adoc[leveloffset=+1]
 
 include::../modules/con_dcn-adoption-overview.adoc[leveloffset=+1]
 

docs_user/assemblies/assembly_storage-requirements.adoc

@@ -19,11 +19,11 @@ Before you can deploy the services in {rhos_long}, you must review the storage r
 
 include::../modules/con_storage-driver-certification.adoc[leveloffset=+1]
 
-include::../modules/con_block-storage-service-requirements.adoc[leveloffset=+1]
+include::../modules/ref_block-storage-service-requirements.adoc[leveloffset=+1]
 
 include::../modules/con_block-storage-service-limitations.adoc[leveloffset=+1]
 
-include::../modules/con_openshift-preparation-for-block-storage-adoption.adoc[leveloffset=+1]
+include::../modules/ref_openshift-preparation-for-block-storage-adoption.adoc[leveloffset=+1]
 
 include::../modules/proc_preparing-block-storage-service-by-customizing-configuration.adoc[leveloffset=+1]
 

docs_user/modules/con_bare-metal-provisioning-service-configurations.adoc

@@ -4,7 +4,7 @@
 = {bare_metal} configurations
 
 [role="_abstract"]
-You configure the {bare_metal_first_ref} by using configuration snippets. For more information about configuring the control plane with the {bare_metal}, see link:{customizing-rhoso}/index[{customizing-rhoso-t}].
+You configure the {bare_metal_first_ref} by using configuration snippets.
 
 Some {bare_metal} configuration is overridden in {OpenStackPreviousInstaller}, for example, PXE Loader file names are often overridden at intermediate layers. You must pay attention to the settings you apply in your {rhos_long} deployment. The `ironic-operator` applies a reasonable working default configuration, but if you override them with your prior configuration, your experience might not be ideal or your new {bare_metal} fails to operate. Similarly, additional configuration might be necessary, for example, if you enable and use additional hardware types in your `ironic.conf` file.
 
@@ -38,3 +38,7 @@ The instances of `kernel_append_params`, formerly `pxe_append_params` in the `[p
 
 [WARNING]
 You cannot migrate hardware types that are set with the `ironic.conf` file `enabled_hardware_types` parameter, and hardware type driver interfaces starting with `staging-` into the adopted configuration.
+
+[role="_additional-resources"]
+.Additional resources
+* link:{customizing-rhoso}/index[{customizing-rhoso-t}]

docs_user/modules/con_block-storage-service-config-generation-helper-tool.adoc

@@ -1,4 +1,4 @@
-:_mod-docs-content-type: CONCEPT
+:_mod-docs-content-type: REFERENCE
 [id="block-storage-configuration-generation-helper-tool_{context}"]
 
 = About the {block_storage} configuration generation helper tool

docs_user/modules/con_changes-to-cephFS-via-NFS.adoc

@@ -22,4 +22,7 @@ Before you begin the adoption, review the following information to understand th
 
 * While the old `ceph-nfs` service only supported NFS version 4.1 and later, the new clustered NFS service supports NFS protocols 3 and 4.1 and later. Mixing protocol versions with an export results in unintended consequences. You should mount a given share across all clients by using a consistent NFS protocol version.
 
-For more information on setting up a clustered NFS service, see xref:creating-a-ceph-nfs-cluster_ceph-prerequisites[Creating an NFS Ganesha cluster].
+
+[role="_additional-resources"]
+.Additional resources
+* xref:creating-a-ceph-nfs-cluster_ceph-prerequisites[Creating an NFS Ganesha cluster]

docs_user/modules/con_fips-support.adoc

@@ -10,4 +10,6 @@ There is a major difference with how FIPS was configured in {OpenStackPreviousIn
 
 If your cluster is FIPS enabled, you must deploy a FIPS {rhocp_long} cluster to adopt your {OpenStackShort} {rhos_prev_ver} FIPS control plane.
 
-For more information about enabling FIPS in {OpenShiftShort}, see link:https://docs.openshift.com/container-platform/latest/installing/installing-fips.html[Support for FIPS cryptography] in _OpenShift Container Platform Documentation_.
+[role="_additional-resources"]
+.Additional resources
+* link:https://docs.openshift.com/container-platform/latest/installing/installing-fips.html[Support for FIPS cryptography]

docs_user/modules/con_identity-service-authentication.adoc

@@ -15,4 +15,6 @@ Red Hat does not support customized roles or policies. Syntax errors or misappli
 
 After you adopt a {OpenStackPreviousInstaller}-based OpenStack deployment to a {rhos_long_noacro} deployment, the {identity_service} performs user authentication and authorization by using Secure RBAC (SRBAC). If SRBAC is already enabled, then there is no change to how you perform operations. If SRBAC is disabled, then adopting a {OpenStackPreviousInstaller}-based OpenStack deployment might change how you perform operations due to changes in API access policies.
 
-For more information on SRBAC, see link:{defaultURL}/performing_security_operations/assembly_srbac-in-rhoso_performing-security-services#assembly_srbac-in-rhoso_performing-security-services[Secure role based access control in Red Hat OpenStack Services on OpenShift] in _Performing security operations_.
+[role="_additional-resources"]
+.Additional resources
+* link:{defaultURL}/performing_security_operations/assembly_srbac-in-rhoso_performing-security-services#assembly_srbac-in-rhoso_performing-security-services[Secure role based access control in Red Hat OpenStack Services on OpenShift] 

docs_user/modules/con_key-manager-service-support-for-crypto-plugins.adoc

@@ -1,4 +1,4 @@
-:_mod-docs-content-type: CONCEPT
+:_mod-docs-content-type: REFERENCE
 [id="key-manager-service-support-for-crypto-plug-ins_{context}"]
 
 = Key Manager service support for crypto plug-ins

docs_user/modules/con_post-adoption-tasks.adoc

@@ -15,9 +15,9 @@ Perform the following post-adoption tasks to ensure that your {rhos_long} enviro
 * Verify that you migrated all services from the Controller nodes, and then power off the nodes. If any services are still running in the Controller nodes, such as Open Virtual Networking (ML2/OVN), {object_storage_first_ref}, or {Ceph}, do not power off the nodes.
 * Optional: Run tempest to verify that the entire adoption process is working correctly.
 
+[role="_additional-resources"]
 .Additional resources
-
 * link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/updating_your_environment_to_the_latest_maintenance_release/index[Updating your environment to the latest maintenance release]
 * xref:enabling-high-availability-for-instances_data-plane[Enabling the high availability for Compute instances service]
-* link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html-single/configuring_security_services/index#assembly_enabling-TLS-on-a-deployed-RHOSO-environment[Enabling TLS on a deployed RHOSO environment] in _Configuring security services_
+* link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html-single/configuring_security_services/index#assembly_enabling-TLS-on-a-deployed-RHOSO-environment[Enabling TLS on a deployed RHOSO environment]
 * link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/validating_and_troubleshooting_the_deployed_cloud/index[Validating and troubleshooting the deployed cloud]