diff --git a/doc/source/deploy_install_guides/r3_release/bare_metal/aio_simplex_install_kubernetes.rst b/doc/source/deploy_install_guides/r3_release/bare_metal/aio_simplex_install_kubernetes.rst
index 5dce5fba8..daa3d40ac 100644
--- a/doc/source/deploy_install_guides/r3_release/bare_metal/aio_simplex_install_kubernetes.rst
+++ b/doc/source/deploy_install_guides/r3_release/bare_metal/aio_simplex_install_kubernetes.rst
@@ -268,7 +268,9 @@ OpenStack-specific host configuration
      manifest.
    * Shares the core(s) assigned to the platform.
 
-   If you require better performance, OVS-DPDK should be used:
+   If you require better performance, OVS-DPDK (OVS with the Data Plane
+   Development Kit, which is supported only on bare metal hardware) should be
+   used:
 
    * Runs directly on the host (it is not containerized).
    * Requires that at least 1 core be assigned/dedicated to the vSwitch function.
@@ -282,8 +284,7 @@ OpenStack-specific host configuration
    Do not run any vSwitch directly on the host, instead, use the containerized
    OVS defined in the helm charts of stx-openstack manifest.
 
-   To deploy OVS-DPDK (OVS with the Data Plane Development Kit, which is
-   supported only on bare metal hardware), run the following command:
+   To deploy OVS-DPDK, run the following command:
 
    ::
 
@@ -294,8 +295,33 @@ OpenStack-specific host configuration
    default to automatically assigning 1 vSwitch core for AIO controllers and 2
    vSwitch cores for computes.
 
-   When using OVS-DPDK, virtual machines must be configured to use a flavor with
-   property: hw:mem_page_size=large
+   When using OVS-DPDK, configure vSwitch memory per NUMA node with the following
+   command:
+
+   ::
+
+      system host-memory-modify -f <function> -1G <1G hugepages number> <hostname or id> <processor>
+
+   For example:
+
+   ::
+
+      system host-memory-modify -f vswitch -1G 1 compute-0 0
+
+   VMs created in an OVS-DPDK environment must be configured to use huge pages
+   to enable networking and must use a flavor with property: hw:mem_page_size=large
+
+   Configure the huge pages for VMs in an OVS-DPDK environment with the command:
+
+   ::
+
+      system host-memory-modify -1G <1G hugepages number> <hostname or id> <processor>
+
+   For example:
+
+   ::
+
+      system host-memory-modify compute-0 0 -1G 10
 
    .. note::
 
diff --git a/doc/source/deploy_install_guides/r3_release/bare_metal/controller_storage_install_kubernetes.rst b/doc/source/deploy_install_guides/r3_release/bare_metal/controller_storage_install_kubernetes.rst
index fd3819d3f..e3831d838 100644
--- a/doc/source/deploy_install_guides/r3_release/bare_metal/controller_storage_install_kubernetes.rst
+++ b/doc/source/deploy_install_guides/r3_release/bare_metal/controller_storage_install_kubernetes.rst
@@ -217,7 +217,9 @@ OpenStack-specific host configuration
      manifest.
    * Shares the core(s) assigned to the platform.
 
-   If you require better performance, OVS-DPDK should be used:
+   If you require better performance, OVS-DPDK (OVS with the Data Plane
+   Development Kit, which is supported only on bare metal hardware) should be
+   used:
 
    * Runs directly on the host (it is not containerized).
    * Requires that at least 1 core be assigned/dedicated to the vSwitch function.
@@ -231,26 +233,50 @@ OpenStack-specific host configuration
    Do not run any vSwitch directly on the host, instead, use the containerized
    OVS defined in the helm charts of stx-openstack manifest.
 
-   To deploy OVS-DPDK (OVS with the Data Plane Development Kit, which is
-   supported only on bare metal hardware), run the following command:
+   To deploy OVS-DPDK, run the following command:
 
    ::
 
      system modify --vswitch_type ovs-dpdk
-	   system host-cpu-modify -f vswitch -p0 1 controller-0
+     system host-cpu-modify -f vswitch -p0 1 controller-0
 
    Once vswitch_type is set to OVS-DPDK, any subsequent nodes created will
    default to automatically assigning 1 vSwitch core for AIO controllers and 2
    vSwitch cores for computes.
 
-   When using OVS-DPDK, Virtual Machines must be configured to use a flavor with
-   property: hw:mem_page_size=large.
+   When using OVS-DPDK, configure vSwitch memory per NUMA node with the following
+   command:
+
+   ::
+
+      system host-memory-modify -f <function> -1G <1G hugepages number> <hostname or id> <processor>
+
+   For example:
+
+   ::
+
+      system host-memory-modify -f vswitch -1G 1 compute-0 0
+
+   VMs created in an OVS-DPDK environment must be configured to use huge pages
+   to enable networking and must use a flavor with property: hw:mem_page_size=large
+
+   Configure the huge pages for VMs in an OVS-DPDK environment with the command:
+
+   ::
+
+      system host-memory-modify -1G <1G hugepages number> <hostname or id> <processor>
+
+   For example:
+
+   ::
+
+      system host-memory-modify compute-0 0 -1G 10
 
    .. note::
 
-   	  After controller-0 is unlocked, changing vswitch_type requires
-   	  locking and unlocking all computes (and/or AIO controllers) to
-   	  apply the change.
+      After controller-0 is unlocked, changing vswitch_type requires
+      locking and unlocking all computes (and/or AIO Controllers) to
+      apply the change.
 
 .. incl-config-controller-0-storage-end: