Replace whitelist with allowlist

[netconf.git] / docs / user-guide.rst

diff --git a/docs/user-guide.rst b/docs/user-guide.rst
index 74bb5e037197211c3b8abb10af8ab68b0260817a..48c2266a84c28fb8fa6bb89e8cfcddeff08db947 100644 (file)
--- a/docs/user-guide.rst
+++ b/docs/user-guide.rst
@@ -1309,9 +1309,9 @@ Configure device to connect over SSH protocol
 Netconf Call Home Server uses device provided SSH server key (host key)
 to identify device. The pairing of name and server key is configured in
 ``/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices``.
-This list is colloquially called a whitelist.
+This list is colloquially called a allowlist.
 
-If the Call-Home Server finds the SSH host key in the whitelist, it continues
+If the Call-Home Server finds the SSH host key in the allowlist, it continues
 to negotiate a NETCONF connection over an SSH session. If the SSH host key is
 not found, the connection between the Call Home server and the device is dropped
 immediately. In either case, the device that connects to the Call home server
@@ -1570,7 +1570,7 @@ available for network management.
 Rogue Devices
 '''''''''''''
 
-Devices which are not on the whitelist might try to connect to the Call-Home Server. In
+Devices which are not on the allowlist might try to connect to the Call-Home Server. In
 these cases, the server will keep a record by instantiating an operational device. There
 will be no corresponding config device for these rogues. They can be identified readily
 because their device id, rather than being user-supplied, will be of the form