r25031: Use pointers to services rather than service numbers when possible.

[kai/samba.git] / README

diff --git a/README b/README
index 8819b1bfd22e42a1cc7bf2373b2dae7f85a087ec..596dbd570c54cdf0e8fe2f19877f1f633e2d4e79 100644 (file)
--- a/README
+++ b/README
@@ -8,7 +8,7 @@ which aims to document what should and should not work.
 
 With 4 years of development under our belt since Tridge first proposed
 a new Virtual File System (VFS) layer for Samba3 (a project which
 
 With 4 years of development under our belt since Tridge first proposed
 a new Virtual File System (VFS) layer for Samba3 (a project which

-eventually lead to our Active Directory efforts), we was felt that we
+eventually lead to our Active Directory efforts), we felt that we

 should create something we could 'show off' to our users.  This is a
 Technology Preview (TP), aimed at allowing you, our users, managers and
 developers to see how we have progressed, and to invite your feedback and
 should create something we could 'show off' to our users.  This is a
 Technology Preview (TP), aimed at allowing you, our users, managers and
 developers to see how we have progressed, and to invite your feedback and


@@ -49,7 +49,7 @@ protection on the main user database, but due to time constraints,
 none on the registry at this stage.  We also do not currently have
 ACLs on the SWAT web-based management tool. This means that Samba 4
 Technology Preview is not secure, and should not be exposed to
 none on the registry at this stage.  We also do not currently have
 ACLs on the SWAT web-based management tool. This means that Samba 4
 Technology Preview is not secure, and should not be exposed to

-untrusted networks..
+untrusted networks.

 
 Within the above proviso, file system access should occur as the
 logged in user, much as Samba3 does.
 
 Within the above proviso, file system access should occur as the
 logged in user, much as Samba3 does.