1
0
mirror of https://github.com/samba-team/samba.git synced 2025-08-02 00:22:11 +03:00

docs: Fix typo.

Signed-off-by: Karolin Seeger <kseeger@samba.org>
This commit is contained in:
Karolin Seeger
2013-02-06 09:08:15 +01:00
committed by Andrew Bartlett
parent dcc94f0933
commit 68b2e30ae6
2 changed files with 4 additions and 4 deletions

View File

@ -14,7 +14,7 @@
<para>Under normal circumstances, the Windows NT/2000 client will
open a handle on the printer server with OpenPrinterEx() asking for
Administrator privileges. If the user does not have administrative
access on the print server (i.e is not root or the priviledge
access on the print server (i.e is not root or has granted the
SePrintOperatorPrivilege), the OpenPrinterEx()
call fails and the client makes another open call with a request for
a lower privilege level. This should succeed, however the APW

View File

@ -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!