Basic doc changes to keep up to date.

Dan

2 files changed, 19 insertions, 14 deletions

diff --git a/docs/announce b/docs/announce
index 78775aa5ca3..5740f37dc61 100644
--- a/docs/announce
+++ b/docs/announce
@@ -4,19 +4,21 @@
 What is Samba?
 --------------
 
-Samba is a Unix based SMB file server. This allows a Unix host to
-act as a file and print server for SMB clients. This includes
+Samba is a SMB file server that runs on Unix and other operating systems. 
+It allows these operating systems (currently Unix, Netware, OS/2 and 
+AmigaDOS) to act as a file and print server for SMB clients. There are many
 Lan-Manager compatible clients such as LanManager for DOS, Windows for
 Workgroups, Windows NT, Windows 95, OS/2, Pathworks and many more.
 
-The package also includes a Unix SMB client and a netbios nameserver.
+The package also includes a SMB client for accessing other SMB servers 
+and a netbios nameserver for browsing support.
 
 What can it do for me?
 ----------------------
 
 If you have any PCs running SMB clients, such as a PC running Windows
-for Workgroups, then you can mount file space or printers from a unix
-host, so that directories, files and printers on the unix host are
+for Workgroups, then you can mount file space or printers on a Samba
+host, so that directories, files and printers on the host are
 available on the PC.
 
 The client part of the package will also allow you to attach to other
@@ -31,7 +33,7 @@ What are it's features?
 
 Samba supports many features that are not supported in other SMB
 implementations (all of which are commercial). Some of it's features
-include host as well as username/password security, a unix client,
+include host as well as username/password security, a client,
 automatic home directory exporting, automatic printer exporting, dead
 connection timeouts, umask support, guest connections, name mangling
 and hidden and system attribute mapping. Look at the man pages
@@ -66,7 +68,7 @@ Samba software is free software. It is available under the
 GNU Public licence in source code form at no cost. Please read the
 file COPYING that comes with the package for more information.
 
-What flavours of unix does it support?
+What operating systems does it support?
 ---------------------------------------
 
 The code has been written to be as portable as possible. It has been
@@ -79,7 +81,9 @@ Sequent, HP-UX, SGI, FreeBSD, NeXT, ISC, A/UX, SCO, Intergraph,
 Domain/OS and DGUX.
 
 Some of these have received more testing than others. If it doesn't
-work with your unix then it should be easy to fix.
+work with your unix then it should be easy to fix. It has also been ported
+to Netware, OS/2 and the Amiga. A VMS port is underway. See the web site
+for more details.
 
 Who wrote it?
 -------------
@@ -125,5 +129,5 @@ newsgroup comp.protocols.smb.
 A WWW site with lots of Samba info can be found at 
 http://samba.canberra.edu.au/pub/samba/
 
-Andrew Tridgell (Contact: samba-bugs@anu.edu.au)
-January 1995
+The Samba Team (Contact: samba-bugs@anu.edu.au)
+June 1996
diff --git a/docs/textdocs/security_level.txt b/docs/textdocs/security_level.txt
index b565ea79668..34d7ce70932 100644
--- a/docs/textdocs/security_level.txt
+++ b/docs/textdocs/security_level.txt
@@ -42,14 +42,14 @@ share. It will send a password along with each "tree connection"
 operation. The client is expecting a password to be associated with
 each share, independent of the user. This means that samba has to work
 out what username the client probably wants to use. It is never
-explicitly sent the username. A "real" SMB server like NT actually
-associates passwords directly with shares in share level security, but
+explicitly sent the username. Some commercial SMB servers such as NT actually
+associate passwords directly with shares in share level security, but
 samba always uses the unix authentication scheme where it is a
 username/password that is authenticated, not a "share/password".
 
 Many clients send a "session setup" even if the server is in share
 level security. They normally send a valid username but no
-password. Samba records this username is a list of "possible
+password. Samba records this username in a list of "possible
 usernames". When the client then does a "tree connection" it also adds
 to this list the name of the share they try to connect to (useful for
 home directories) and any users listed in the "user =" smb.conf
@@ -75,4 +75,5 @@ passwords in encrypted form. You have to compile samba with encryption
 enabled to support this feature, and you have to maintain a separate
 smbpasswd file with SMB style encrypted passwords. It is
 cryptographically impossible to translate from unix style encryption
-to SMB style encryption.
+to SMB style encryption, although there are some fairly simple management
+schemes by which the two could be kept in sync.