diff --git a/modules/installation-user-infra-machines-advanced.adoc b/modules/installation-user-infra-machines-advanced.adoc
index cf1194a15b6e..5ad163a61cae 100644
--- a/modules/installation-user-infra-machines-advanced.adoc
+++ b/modules/installation-user-infra-machines-advanced.adoc
@@ -87,11 +87,8 @@ officially supported for mounting `/var` or a subdirectory of `/var`, such as `/
 ====
 For disk sizes larger than 100GB, and especially disk sizes larger than 1TB, create a separate `/var` partition. See "Creating a separate `/var` partition" and this link:https://access.redhat.com/solutions/5587281[Red Hat Knowledgebase article] for more information.
 ====
-+
-[IMPORTANT]
-====
-Kubernetes supports only two file system partitions. If you add more than one partition to the original configuration, Kubernetes cannot monitor all of them.
-====
+
+* Kubernetes supports storing the containers directory on a separate disk. You must have a single filesystem for `/var`, so that you can use a separate partition for `/var/lib/containers`. Kubernetes supports only these two configurations. Kubernetes does not monitor any other type of file system partition.
 
 * Retaining existing partitions: For a brownfield installation where you are reinstalling {product-title} on an existing node and want to retain data partitions installed from your previous operating system, there are both boot arguments and options to `coreos-installer` that allow you to retain existing data partitions.