diff --git a/doc/wifi.md b/doc/wifi.md
index 7025bc2a..4e69ccb1 100644
--- a/doc/wifi.md
+++ b/doc/wifi.md
@@ -558,6 +558,38 @@ admin@example:/config/interface/wifi0/> set wifi access-point roaming dot11v
 
 Allows APs to suggest better APs to clients, improving roaming decisions.
 
+#### Band Steering (MBO)
+
+802.11v also carries MBO (Multi-Band Operation) band steering, which
+nudges dual-band clients toward 5GHz over 2.4GHz when signal quality
+permits.  It is **enabled by default** whenever `dot11v` is enabled:
+
+```
+admin@example:/config/interface/wifi0/> set wifi access-point roaming dot11v
+```
+
+To turn it off while keeping BSS Transition Management:
+
+```
+admin@example:/config/interface/wifi0/> set wifi access-point roaming dot11v band-steering false
+```
+
+> [!NOTE]
+> Band steering is only meaningful when the same SSID is offered on two
+> or more bands (one access-point per radio).  On a single-band network
+> there is no other band to steer toward, and it has no effect.
+
+### Opportunistic Key Caching (OKC)
+
+OKC reduces re-authentication time for roaming clients that do not
+support 802.11r.  The AP caches the PMK from previous associations and
+shares it with other APs in the same mobility group.  It is **enabled by
+default** and only activates when both AP and client support it:
+
+```
+admin@example:/config/interface/wifi0/> set wifi access-point roaming okc false
+```
+
 ### Recommended Configuration
 
 For optimal roaming experience, enable all three features:
@@ -593,17 +625,15 @@ using HWMP (Hybrid Wireless Mesh Protocol), which is built into the
 Linux mac80211 subsystem.  There is no central controller; nodes
 discover peers and find paths on their own.
 
-The standard defines three node roles:
+The standard defines two node roles:
 
 - **Mesh Point (MP)** - a basic mesh node that forwards traffic within
   the mesh
 - **Mesh Portal (MPP)** - a mesh node that bridges traffic between the
   mesh and an external network (e.g., a wired LAN)
-- **Mesh Gate** - a mesh node that advertises external connectivity so
-  other nodes proactively maintain a path toward it
 
-In practice, a node bridging the mesh interface to a LAN is a mesh
-portal, and enabling `gate-announcements` on it makes it a mesh gate.
+In practice, a node bridging the mesh interface to a LAN acts as a mesh
+portal.
 
 > [!NOTE]
 > Not all WiFi hardware supports 802.11s mesh.  The driver must implement
@@ -671,8 +701,6 @@ admin@example:/config/interface/wifi-mesh/> <b>leave</b>
   must use the same mesh ID
 - `forwarding`: L2 mesh forwarding (default: true).  When enabled, the
   interface can be added to a bridge as a mesh portal
-- `gate-announcements`: Advertise this node as a mesh gate (default:
-  false).  Enable on nodes with a wired uplink
 - `security secret`: Keystore reference for the WPA3-SAE passphrase
 
 ### Mesh portal (bridge integration)
@@ -682,13 +710,9 @@ a bridge:
 
 <pre class="cli"><code>admin@example:/config/> <b>edit interface wifi-mesh</b>
 admin@example:/config/interface/wifi-mesh/> <b>set bridge-port bridge br0</b>
-admin@example:/config/interface/wifi-mesh/> <b>set wifi mesh-point gate-announcements true</b>
 admin@example:/config/interface/wifi-mesh/> <b>leave</b>
 </code></pre>
 
-With `gate-announcements` enabled, the node sends GANN (Gate
-Announcement) frames so other mesh nodes maintain a path toward it.
-
 ### Mesh with roaming APs
 
 You can combine 802.11s mesh backhaul with roaming-enabled access