X-Git-Url: https://gerrit.o-ran-sc.org/r/gitweb?a=blobdiff_plain;f=doc%2Fsrc%2Flibrary%2Fadvanced_use.im;h=50aabd6e2b4935be7adc4bb791b149f9d8c7892a;hb=2b3c393e660c5e1037191f43cc70537da8316b89;hp=6eac394875addcd4ce55a9c4e0123ed6ff3ee8ea;hpb=fe6a856df463a0d7e06b28aac8590ac9c0f08dd6;p=ric-plt%2Flib%2Frmr.git

diff --git a/doc/src/library/advanced_use.im b/doc/src/library/advanced_use.im
index 6eac394..50aabd6 100644
--- a/doc/src/library/advanced_use.im
+++ b/doc/src/library/advanced_use.im
@@ -70,7 +70,7 @@ it is not possible to guarantee that a response message is delivered
 to the correct thread.  The RMR function &func(rmr_mt_call) accepts an
 additional parameter which identifies the calling thread in order to
 ensure that the response is delivered properly.  In addition, the
-application must specifically initialize the multi-threaded call
+application must specifically initialise the multi-threaded call
 environment by passing the &cw(RMRFL_MTCALL) flag as an option to the
 &func(rmr_init) function &note .sm .
 .if pfm
@@ -95,7 +95,7 @@ not responses to the call are continued to be delivered via normal
 
 &space
 While the process is blocked waiting for the response, it is entirely
-possible that asynchronous, nonmatching, messages will arrive.  When
+possible that asynchronous, non-matching, messages will arrive.  When
 this happens, RMR will queues the messages and return them to the
 application over the next calls to &func(rmr_rcv_msg:.)