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

[mimir at samba.org]

Author: mimir
Date: 2005-02-13 00:52:45 +0000 (Sun, 13 Feb 2005)
New Revision: 5367

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

Log:
Minor typo fixes.


rafal


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-02-13 00:50:38 UTC (rev 5366)
+++ branches/SAMBA_4_0/prog_guide.txt	2005-02-13 00:52:45 UTC (rev 5367)
@@ -232,7 +232,7 @@
 are extremely important differences in the approach that are worth
 pointing out.
 
-In the Samba3 msrpc code we used explicit parse strucrures for all
+In the Samba3 msrpc code we used explicit parse structures for all
 msrpc functions. The problem is that we didn't just put all of the
 real variables in these structures, we also put in all the artifacts
 as well. A good example is the security descriptor strucrure that
@@ -263,7 +263,7 @@
 *NOT* be in the interface structure.
 
 In Samba3 there were unwritten rules about which variables in a
-strucrure a high level caller has to fill in and which ones are filled
+structure a high level caller has to fill in and which ones are filled
 in by the marshalling code. In Samba4 those rules are gone, because
 the redundent artifact variables are gone. The high level caller just
 sets up the real variables and the marshalling code worries about