diff --git a/README.md b/README.md
index d16477bce8d7e1e0b5b55c8fd10b99ca013fe2d8..308bde8dd2ea91876d7a17432df3c870eb778c8c 100644
--- a/README.md
+++ b/README.md
@@ -360,7 +360,9 @@ config qos_rule 'qos_rule1'
 	option type 'dscp_pcp'
 	option output '8'
 	option always_match '1'
-	option dscp_pcp '1,2,3,4,5,6'
+	list dscp_pcp '58,1'
+	list dscp_pcp '58,2'
+	list dscp_pcp '10-21,5'
 ```
 
 The `output` value determines the target PCP. If the rule has `output`
@@ -788,6 +790,21 @@ ubus call map.controller dpp_enrollee_uri_eth '{"uri":"DPP:C:81/1,115/36;V:2;K:M
 Once provided, map-controller will be able to perform DPP Ethernet onboarding,
 triggered by AP-Autoconfig Search and DPP Direct Encapsulated messages.
 
+## Control Depth of a Multi-AP Network
+
+Limit the max number of Wi-Fi backhaul links that are allowed in "daisy-chained"
+topology. By default the feature is disabled, which means that the EasyMesh
+network is not limited to any number of Wi-Fi backhaul hops.
+
+```
+config controller 'controller'
+	option enabled '1'
+	...
+	option max_node_bh_hops '2'        # number of allowed Wi-Fi hops
+```
+
+NOTE: Ethernet daisy-chains are still supported at any length, and forming a
+daisy-chain with Eth to Wi-Fi is still possible.
 
 ## UBUS APIs