diff options
Diffstat (limited to 'doc/man/man3/qcopchannel.3qt')
| -rw-r--r-- | doc/man/man3/qcopchannel.3qt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/man/man3/qcopchannel.3qt b/doc/man/man3/qcopchannel.3qt index f621d319a..2a3515c58 100644 --- a/doc/man/man3/qcopchannel.3qt +++ b/doc/man/man3/qcopchannel.3qt @@ -109,7 +109,7 @@ Example: .fi This example assumes that the \fImsg\fR is a DCOP-style function signature and the \fIdata\fR contains the function's arguments. (See send().) .PP -Using the DCOP convention is a recommendation, but not a retquirement. Whatever convention you use the sender and receiver \fImust\fR agree on the argument types. +Using the DCOP convention is a recommendation, but not a requirement. Whatever convention you use the sender and receiver \fImust\fR agree on the argument types. .PP See also send(). .SH "void QCopChannel::received ( const QCString & msg, const QByteArray & data )\fC [signal]\fR" @@ -134,7 +134,7 @@ Example: .fi Here the channel is "System/Shell". The \fImsg\fR is an arbitrary string, but in the example we've used the DCOP convention of passing a function signature. Such a signature is formatted as functionname(types) where types is a list of zero or more comma-separated type names, with no whitespace, no consts and no pointer or reference marks, i.e. no "*" or "&". .PP -Using the DCOP convention is a recommendation, but not a retquirement. Whatever convention you use the sender and receiver \fImust\fR agree on the argument types. +Using the DCOP convention is a recommendation, but not a requirement. Whatever convention you use the sender and receiver \fImust\fR agree on the argument types. .PP See also receive(). .SH "bool QCopChannel::send ( const QCString & channel, const QCString & msg )\fC [static]\fR" |