summaryrefslogtreecommitdiff
path: root/docs/docbook/projdoc/locking.xml
diff options
context:
space:
mode:
authorJohn Terpstra <jht@samba.org>2003-07-14 05:17:52 +0000
committerJohn Terpstra <jht@samba.org>2003-07-14 05:17:52 +0000
commit379367dd7607514c17bc8ea8aa60212b1c6070a7 (patch)
tree0184bfc11946f9f440dc838c014c2c70ac4f0303 /docs/docbook/projdoc/locking.xml
parent9e51951e6e4e5c1fcf89e37123f59c08df56e09e (diff)
downloadsamba-379367dd7607514c17bc8ea8aa60212b1c6070a7.tar.gz
samba-379367dd7607514c17bc8ea8aa60212b1c6070a7.tar.bz2
samba-379367dd7607514c17bc8ea8aa60212b1c6070a7.zip
Typo fixes from Vorlon.
(This used to be commit 4cdadbbbe9d6311b32dfe8e9823ed55dab1c6f1c)
Diffstat (limited to 'docs/docbook/projdoc/locking.xml')
-rw-r--r--docs/docbook/projdoc/locking.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/docbook/projdoc/locking.xml b/docs/docbook/projdoc/locking.xml
index 002894affe..0e508f682a 100644
--- a/docs/docbook/projdoc/locking.xml
+++ b/docs/docbook/projdoc/locking.xml
@@ -62,7 +62,7 @@ that are specified when a file is open.
</para>
<para>
-Record locking semantics under Unix is very different from record locking under
+Record locking semantics under Unix are very different from record locking under
Windows. Versions of Samba before 2.2 have tried to use the native fcntl() unix
system call to implement proper record locking between different Samba clients.
This can not be fully correct due to several reasons. The simplest is the fact
@@ -90,7 +90,7 @@ will make lock checking calls on every read and write.
</para>
<para>
-You can also disable by range locking completely using <parameter>locking = no</parameter>.
+You can also disable byte range locking completely using <parameter>locking = no</parameter>.
This is useful for those shares that don't support locking or don't need it
(such as cdroms). In this case Samba fakes the return codes of locking calls to
tell clients that everything is OK.