diff --git a/src/topics/Snapping.md b/src/topics/Snapping.md
index 1a8c550e..7e6234c3 100644
--- a/src/topics/Snapping.md
+++ b/src/topics/Snapping.md
@@ -11,16 +11,18 @@ QWC2 ships a plugin for snapping support while drawing (redlining / measuring /
       "max": <max_scale>
     }
   ],
-  "featureCount": <feature_count>
+  "featureCount": <feature_count>,
+  "wfsMaxScale": <wfs_max_scale>
 }
 ...
 ```
 where:
 
-- `layername` is the name of the theme sublayer from which to retreive the snapping geometries
-- `min` is the minimum scale denominator (inclusive) from which this layer should be used for snapping
-- `max` is the maximum scale denominator (exclusive) up to which this layer should be used for snapping
+- `layername` is the name of the theme sublayer from which to retreive the snapping geometries.
+- `min` is the minimum scale denominator (inclusive) from which this layer should be used for snapping.
+- `max` is the maximum scale denominator (exclusive) up to which this layer should be used for snapping.
 - `feature_count` is the maximum number of snapping geometries to retreive for the current map extent (default: 500).
+- `wfs_max_scale` is the maximum scale denominator (exclusive) up to which loaded WFS layers should be used for snapping.
 
 *Note*: Snapping works by querying the geometries of all snapping layers inside the scale range via WMS GetFeatureInfo and refreshing the geometries every time the map extent changes. Therefore, it is recommended to ensure the geometry complexity of the snap layers is appropriate for the specified scale ranges to avoid overloading the server with the GetFeatureInfo requests. Also, the QGIS project will need to be configured so that snap layers are queryable and that feature info responses contain geometries.