[#3881] "Incompatible": Revise, expand, wrap

diff --git a/doc/sphinx/arm/config-backend.rst b/doc/sphinx/arm/config-backend.rst
index 699981c56d6f22fe3b3bada229abdfa352583358..cdf46d132e3ac2a836134dffadbdc982b8b62e7a 100644 (file)
--- a/doc/sphinx/arm/config-backend.rst
+++ b/doc/sphinx/arm/config-backend.rst
@@ -136,7 +136,12 @@ write out a JSON config file.  That would conflict with any subnets defined by
 the CB.  Use :ischooklib:`libdhcp_cb_cmds.so` to manage the
 subnets information in the database instead.
 
-The Stork management suite does not currently support the CB.  Stork operates by direct configuration modification, with accompanying ``config-write`` of the JSON config file.  That would create duplicate definitions vs the CB.  Support for the CB is planned for a future release of Stork.
+The Stork management suite does not currently support the CB.  Stork operates
+by direct configuration modification, with accompanying ``config-write`` of
+the JSON config file.  That would create duplicate definitions vs the CB.
+Support for the CB is planned for a future release of Stork.
+
+In certain carefully-controlled scenarios, it may be possible to use these tools with the CB.  Namely, if they are used in strictly "read-only" fashion, to retrieve Kea information, but never to modify it.  However, no protection against accidental modification is provided, so this is not recommended.
 
 Custom Options
 ^^^^^^^^^^^^^^