diff options
| author | Volker Lendecke <vl@samba.org> | 2016-09-11 09:28:35 +0200 |
|---|---|---|
| committer | Jeremy Allison <jra@samba.org> | 2016-09-16 01:31:13 +0200 |
| commit | 60fe6e9fab12fa566dc894f934a77b74e2310b10 (patch) | |
| tree | fdd87c3af083663cfc54ccf1b8e3760757dddd3c /lib | |
| parent | 2a2ac63975b8ff41ede8e93ef2b33148c89f185f (diff) | |
| download | samba-60fe6e9fab12fa566dc894f934a77b74e2310b10.tar.gz | |
tevent_tutorial: Fix typos
Signed-off-by: Volker Lendecke <vl@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/tevent/doc/tevent_context.dox | 2 | ||||
| -rw-r--r-- | lib/tevent/doc/tevent_queue.dox | 5 |
2 files changed, 4 insertions, 3 deletions
diff --git a/lib/tevent/doc/tevent_context.dox b/lib/tevent/doc/tevent_context.dox index 1036d3c106d..39eb85eb477 100644 --- a/lib/tevent/doc/tevent_context.dox +++ b/lib/tevent/doc/tevent_context.dox @@ -67,7 +67,7 @@ event again. There are 2 types of loop available for use in tevent library: <li>int tevent_loop_once()</li> </ul> -Both of functions accept just one parametr (tevent context) and the only +Both of functions accept just one parameter (tevent context) and the only difference lies in the fact that the first loop can theoretically last for ever but the second one will wait just for a single one event to catch and then the loop breaks and the program continue. diff --git a/lib/tevent/doc/tevent_queue.dox b/lib/tevent/doc/tevent_queue.dox index fef98c81e06..9c247e5212a 100644 --- a/lib/tevent/doc/tevent_queue.dox +++ b/lib/tevent/doc/tevent_queue.dox @@ -11,7 +11,8 @@ beginning of the queue as fast as possible. In tevent library it is similar, but the queue is not automatically set for any event. The queue has to be created on purpose, and events which should follow the order of the FIFO queue have to be explicitly pinpointed. Creating such a queue is crucial in -situations when sequential processing is absolutely essential for the succesful +situations when sequential processing is absolutely essential for the +successful completion of a task, e.g. for a large quantity of data that are about to be written from a buffer into a socket. The tevent library has its own queue structure that is ready to use after it has been initialized and started up @@ -20,7 +21,7 @@ once. @subsection cr_queue Creation of Queues The first and most important step is the creation of the tevent queue -(represented by struct tevent queue), which will then be in running mode. +(represented by struct tevent_queue), which will then be in running mode. @code struct tevent_queue* tevent_queue_create (TALLOC_CTX *mem_ctx, const char *name) |