From 263a5dc0f71e62f846a71be4a4556a706808345d Mon Sep 17 00:00:00 2001 From: Pekka Riikonen Date: Fri, 24 Jan 2003 09:13:02 +0000 Subject: [PATCH] typos --- lib/doc/command_reply_args.html | 2 +- lib/doc/notifyargs.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/doc/command_reply_args.html b/lib/doc/command_reply_args.html index 95cc4bcc..5a964271 100644 --- a/lib/doc/command_reply_args.html +++ b/lib/doc/command_reply_args.html @@ -65,7 +65,7 @@ example:
 
The following table describes all commands and arguments that the client library sends in the 'command_reply' client operation to the application. -By default all arguments that the libary sends to application are valid +By default all arguments that the library sends to application are valid pointers. However, it is possible that some pointers may be NULL. If this is the case it is separately mentioned that the argument may be NULL. In this case application must ignore that argument. The 'command_reply' diff --git a/lib/doc/notifyargs.html b/lib/doc/notifyargs.html index afb89a3e..ebe124ac 100644 --- a/lib/doc/notifyargs.html +++ b/lib/doc/notifyargs.html @@ -54,7 +54,7 @@ example:
 
The following table describes all notify types and arguments that the client library sends in the 'notify' client operation to the application. -By default all arguments that the libary sends to application are valid +By default all arguments that the library sends to application are valid pointers. However, it is possible that some pointers may be NULL. If this is the case it is separately mentioned that the argument may be NULL. In this case application must ignore that argument. The SilcNotifyType -- 2.24.0