summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRafal Szczesniak <mimir@samba.org>2005-02-13 00:52:45 +0000
committerGerald (Jerry) Carter <jerry@samba.org>2007-10-10 13:09:47 -0500
commit8f2ee50a275a2181bbdf77e0fa34cbd4ee4a7f9c (patch)
tree82a24530b4388fe1eefbe5b0a06e828fb7f8e209
parent2e61d60cdc0b4e00186e19f4de7bd62e9cdd1ddc (diff)
downloadsamba-8f2ee50a275a2181bbdf77e0fa34cbd4ee4a7f9c.tar.gz
samba-8f2ee50a275a2181bbdf77e0fa34cbd4ee4a7f9c.tar.bz2
samba-8f2ee50a275a2181bbdf77e0fa34cbd4ee4a7f9c.zip
r5367: Minor typo fixes.
rafal (This used to be commit 64263be5346dc19af49ec929bc4caf31f93b16c6)
-rw-r--r--prog_guide.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/prog_guide.txt b/prog_guide.txt
index 7aefe9db41..d4a170b278 100644
--- a/prog_guide.txt
+++ b/prog_guide.txt
@@ -232,7 +232,7 @@ msrpc code from Samba3", and while to some extent this is true there
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 @@ parser where to find the following four variables, but they should
*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