svn commit: samba r6226 - in branches/SAMBA_4_0: .

[sharpe at samba.org]

Author: sharpe
Date: 2005-04-06 16:48:28 +0000 (Wed, 06 Apr 2005)
New Revision: 6226

WebSVN: http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=rev&root=samba&rev=6226

Log:

A couple of small typos ...


Modified:
   branches/SAMBA_4_0/prog_guide.txt


Changeset:
Modified: branches/SAMBA_4_0/prog_guide.txt
===================================================================
--- branches/SAMBA_4_0/prog_guide.txt	2005-04-06 16:28:04 UTC (rev 6225)
+++ branches/SAMBA_4_0/prog_guide.txt	2005-04-06 16:48:28 UTC (rev 6226)
@@ -207,7 +207,7 @@
 In Samba3 many of the core wire structures in the SMB protocol were
 never explicitly defined in Samba. Instead, our parse and generation
 functions just worked directly with wire buffers. The biggest problem
-with this is that is tied our parse code with out "business logic"
+with this is that is tied our parse code with our "business logic"
 much too closely, which meant the code got extremely confusing to
 read.
 
@@ -395,7 +395,7 @@
 each SMB.
 
 As an example go and have a look at reply_getatr_send() and
-reply_getatr() in smbd/reply.c. Read them? Good.
+reply_getatr() in smb_server/reply.c. Read them? Good.
 
 Notice that reply_getatr() sets up the req->async structure to contain
 the send function. Thats how the backend gets to do an async reply, it