summaryrefslogtreecommitdiff
path: root/prog_guide4.txt
diff options
context:
space:
mode:
authorKarolin Seeger <kseeger@samba.org>2013-02-06 09:08:15 +0100
committerAndrew Bartlett <abartlet@samba.org>2013-02-18 22:07:39 +1100
commit68b2e30ae62d8a563cb7ee35e10c45fe0266c612 (patch)
treeea4cde9a85b13f7b79b09ee2863aba862c7a0790 /prog_guide4.txt
parentdcc94f093317ffa2bbbc776fb82657088eb63305 (diff)
downloadsamba-68b2e30ae62d8a563cb7ee35e10c45fe0266c612.tar.gz
docs: Fix typo.
Signed-off-by: Karolin Seeger <kseeger@samba.org>
Diffstat (limited to 'prog_guide4.txt')
-rw-r--r--prog_guide4.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/prog_guide4.txt b/prog_guide4.txt
index c8c91c42d1c..0a33284e579 100644
--- a/prog_guide4.txt
+++ b/prog_guide4.txt
@@ -267,7 +267,7 @@ parser where to find the following four variables, but they should
In Samba3 there were unwritten rules about which variables in a
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
+the redundant artifact variables are gone. The high level caller just
sets up the real variables and the marshalling code worries about
generating the right offsets.
@@ -286,10 +286,10 @@ read the comment in smb_interfaces.h about that now.
So, here is another rule to code by. When writing an interface
structure think carefully about what variables in the structure can be
-left out as they are redundent. If some length is effectively defined
+left out as they are redundant. If some length is effectively defined
twice on the wire then only put it once in the packet. If a length can
be inferred from a null termination then do that and leave the length
-out of the structure completely. Don't put redundent stuff in
+out of the structure completely. Don't put redundant stuff in
structures!