diff --git a/doc/guide.html b/doc/guide.html
index e66dad55d..86eb74c45 100644
--- a/doc/guide.html
+++ b/doc/guide.html
@@ -189,7 +189,7 @@ BLOCKQUOTE.figure DIV.center DIV.center HR{display:none;}
5.2 epmd
5.3 Erlang Cookie
5.4 Erlang Node Name
-5.5 Securing Sensible Files
+5.5 Securing Sensitive Files
Chapter 6 Clustering
-
@@ -3741,8 +3741,8 @@ to difficult unauthorized access to your Erlang node.
However, it is not ultimately effective to prevent access to the Erlang node,
because it may be possible to fake the fact that you are on another network
using a modified version of Erlang epmd.
-The recommended way to secure the Erlang node is to block the port 4369.
-
ejabberd stores sensible data in the file system either in plain text or binary files.
+The recommended way to secure the Erlang node is to block the port 4369.
+
ejabberd stores sensitive data in the file system either in plain text or binary files.
The file system permissions should be set to only allow the proper user to read,
write and execute those files and directories.
-
ejabberd configuration file: /etc/ejabberd/ejabberd.cfg
-
diff --git a/doc/guide.tex b/doc/guide.tex
index 64d84cfbc..ef950647e 100644
--- a/doc/guide.tex
+++ b/doc/guide.tex
@@ -4814,9 +4814,9 @@ using a modified version of Erlang \term{epmd}.
The recommended way to secure the Erlang node is to block the port 4369.
-\makesection{secure-files}{Securing Sensible Files}
+\makesection{secure-files}{Securing Sensitive Files}
-\ejabberd{} stores sensible data in the file system either in plain text or binary files.
+\ejabberd{} stores sensitive data in the file system either in plain text or binary files.
The file system permissions should be set to only allow the proper user to read,
write and execute those files and directories.