"client" must be "user" and some other corrections

diff --git a/docs/manual/consoleconf.tex b/docs/manual/consoleconf.tex
index c564f955df21a7005739b53d50939205f884d232..563c81ad18fea248deb067577921a4de1899f105 100644 (file)
--- a/docs/manual/consoleconf.tex
+++ b/docs/manual/consoleconf.tex
@@ -242,7 +242,7 @@ Console {
 \normalsize
 
 Where the Password in the Director section is deliberately incorrect, and the
-Console resource is given a name, in this case {\bf restricted-client}. Then
+Console resource is given a name, in this case {\bf restricted-user}. Then
 in the Director's bacula-dir.conf file (not directly accessible by the user),
 we define: 
 
@@ -264,10 +264,10 @@ Console {
 \normalsize
 
 the user logging into the Director from his Console will get logged in as {\bf
-restricted-client}, and he will only be able to see or access a Job with the
+restricted-user}, and he will only be able to see or access a Job with the
 name {\bf Restricted Client Save} a Client with the name {\bf
 restricted-client}, a Storage device {\bf main-storage}, any Schedule or Pool,
-a FileSet named {\bf Restricted Client's File}, a Catalog named {\bf
+a FileSet named {\bf Restricted Client's FileSet}, a Catalog named {\bf
 DefaultCatalog}, and the only command he can use in the Console is the {\bf
 run} command. In other words, this user is rather limited in what he can see
 and do with Bacula.