diff --git a/docs_user/modules/con_adoption-limitations.adoc b/docs_user/modules/con_adoption-limitations.adoc
index 678502a09..ae82d32bf 100644
--- a/docs_user/modules/con_adoption-limitations.adoc
+++ b/docs_user/modules/con_adoption-limitations.adoc
@@ -8,9 +8,7 @@ Before you proceed with the adoption, check which features are Technology Previe
 
 Technology Preview::
 +
-The following features are Technology Previews and have not been tested within the context of the {rhos_long} adoption:
-+
-* FC-based drivers for {block_storage_first_ref}
+The following features are Technology Previews and have not been tested within the context of the {rhos_long} adoption.
 +
 The following {compute_service_first_ref} features are Technology Previews:
 +
diff --git a/docs_user/modules/con_openshift-preparation-for-block-storage-adoption.adoc b/docs_user/modules/con_openshift-preparation-for-block-storage-adoption.adoc
index 22b4036b4..5b5711eac 100644
--- a/docs_user/modules/con_openshift-preparation-for-block-storage-adoption.adoc
+++ b/docs_user/modules/con_openshift-preparation-for-block-storage-adoption.adoc
@@ -85,6 +85,7 @@ spec:
 
 FC:::
 ** The {block_storage} volume and {block_storage} backup services must run in an {OpenShiftShort} host that has host bus adapters (HBAs). If some nodes do not have HBAs, then use labels to restrict where these services run. For more information, see link:{defaultOCPURL}/nodes/index#nodes-scheduler-node-selectors-about_nodes-scheduler-node-selectors[About node selectors].
+** If the {image_service} is configured to use {block_storage} as a back end with FC, the {image_service} must also run on an {OpenShiftShort} host that has HBAs and follow the same node selection requirements as the {block_storage}.
 ** If you have virtualized {OpenShiftShort} clusters that use FC you need to expose the host HBAs inside the virtual machine.
 ** For production deployments that use FC volumes, configure multipathing for better I/O.