diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt
index 5515304..0a95a0e 100644
--- a/doc/mgmt-api.txt
+++ b/doc/mgmt-api.txt
@@ -347,8 +347,9 @@ Set Connectable Command
 	and for LE controllers it changes the advertising type. For
 	dual mode controllers it affects both settings.
 
-	For LE capable controllers the connectable setting only takes
-	affect when advertising is enabled.
+	For LE capable controllers the connectable setting takes affect
+	when advertising is enabled (peripheral) or when directed
+	advertising events are received (central).
 
 	This command can be used when the controller is not powered and
 	all settings will be programmed once powered.
@@ -1852,14 +1853,27 @@ Add Device Command
 	Possible values for the Action parameter:
 		0	Background scan for device
 		1	Auto-connect device
+		2	Auto-connect device and encrypt connection
 
 	With the Action 0, when the device is found, a new Device Found
-	event will be send indicating this device is available. Devices
-	using direct advertising will be connected.
+	event will be send indicating this device is available.
 
 	With the Action 1, when the device is found, it will be connected
 	and if successful a Device Connected event will be send.
 
+	With the Action 2, when the device is found and it is paired (has
+	a long term key), it will be connected, encryption will be started
+	and if successful a Device Connected event will be send.
+
+	Add a device the requires a encryption, but has no long term
+	key can be added with Action 2, but it will not be connected
+	until it has been paired.
+
+	Devices using directed advertising will be automatically connected
+	if the connectable setting is enabled. If connectable is not set,
+	then devices using undirected advertising will only connect when
+	using Action 1 or Action 2.
+
 	This command can be used when the controller is not powered and
 	all settings will be programmed once powered.