This commit was manufactured by cvs2svn to create tag

[bacula/docs] / docs / developers / daemonprotocol.tex

diff --git a/docs/developers/daemonprotocol.tex b/docs/developers/daemonprotocol.tex
index 299e7529a6ea264c89eb5af29b01048a5bf3bbf1..715b8ce84d44456b2672d8c6d2d231b0c29dc91f 100644 (file)
--- a/docs/developers/daemonprotocol.tex
+++ b/docs/developers/daemonprotocol.tex
@@ -37,7 +37,7 @@ integer is zero or negative, it indicates a special request, a sort of network
 signaling capability. In this case, no data packet will follow. The low level
 BSOCK routines expect that only a single thread is accessing the socket at a
 time. It is advised that multiple threads do not read/write the same socket.
-If you must do this, you must provide some sort of locking mechanism. I would
+If you must do this, you must provide some sort of locking mechanism. It would
 not be appropriate for efficiency reasons to make every call to the BSOCK
 routines lock and unlock the packet.