From 68b2e30ae62d8a563cb7ee35e10c45fe0266c612 Mon Sep 17 00:00:00 2001 From: Karolin Seeger Date: Wed, 6 Feb 2013 09:08:15 +0100 Subject: docs: Fix typo. Signed-off-by: Karolin Seeger --- prog_guide4.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'prog_guide4.txt') diff --git a/prog_guide4.txt b/prog_guide4.txt index c8c91c42d1..0a33284e57 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! -- cgit