diff --git a/doc/source/admin/ovn/baremetal.rst b/doc/source/admin/ovn/baremetal.rst
index 81688be0704..e9dd949ff3b 100644
--- a/doc/source/admin/ovn/baremetal.rst
+++ b/doc/source/admin/ovn/baremetal.rst
@@ -7,9 +7,8 @@ Baremetal provisioning guide for OVN
 The purpose of this page is to describe how the baremetal provisioning
 can be configured with ML2/OVN.
 
-Currently, baremetal provisioning with ML2/OVN can be achieved using
-the OVN's built-in DHCP server for IPv4 or using Neutron's DHCP agent
-for either IPv4 or IPv6.
+Baremetal provisioning with ML2/OVN can be achieved using the OVN's
+built-in DHCP server or Neutron's DHCP agent.
 
 How to configure it
 -------------------
@@ -41,9 +40,9 @@ serve metadata to the baremetal nodes booting off those external ports.
 Using OVN built-in DHCP for PXE booting
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Currently, only IPv4 is supported for PXE booting a baremetal node using
-the OVN's built-in DHCP server. It's also required to have OVN running
-the version **22.06** or above.
+This feature requires OVN running the version **23.06** or above for IPv4
+and IPv6 support. If only IPv4 is needed, the OVN version **22.06**
+is the minimum required.
 
 The version of OVN used for baremetal provisioning should include the
 following commits [[#]_] [[#]_].
@@ -55,9 +54,8 @@ And last, make sure that configuration option
 Using Neutron DHCP Agent for PXE booting
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-If using the OVN built-in DHCP server is not desirable or if
-PXE booting nodes off IPv6 is required, the operator will need
-to deploy Neutron's DHCP agents on the controller nodes and also
+If using the OVN built-in DHCP server is not desirable, the operator will
+need to deploy Neutron's DHCP agents on the controller nodes and also
 disable the OVN's DHCP server for the baremetal ports by setting the
 ``[ovn]/disable_ovn_dhcp_for_baremetal_ports`` configuration option to
 **True** (defaults to False).