Fix minor typos in RMR man pages

[ric-plt/lib/rmr.git] / doc / src / man / rmr_free_msg.3.xfm

diff --git a/doc/src/man/rmr_free_msg.3.xfm b/doc/src/man/rmr_free_msg.3.xfm
index 2f18b73..000856c 100644 (file)
--- a/doc/src/man/rmr_free_msg.3.xfm
+++ b/doc/src/man/rmr_free_msg.3.xfm
@@ -1,7 +1,7 @@
 .if false
 ==================================================================================
-       Copyright (c) 2019 Nokia 
-       Copyright (c) 2018-2019 AT&T Intellectual Property.
+   Copyright (c) 2019 Nokia
+   Copyright (c) 2018-2019 AT&T Intellectual Property.
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.
@@ -18,20 +18,20 @@
 .fi
 
 .if false
-       Mnemonic        rmr_free_msg_man.xfm
-       Abstract        The manual page for the rmr_free_msg function.
-       Author          E. Scott Daniels
-       Date            28 January 2019
+    Mnemonic    rmr_free_msg_man.xfm
+    Abstract    The manual page for the rmr_free_msg function.
+    Author      E. Scott Daniels
+    Date        28 January 2019
 .fi
 
 .gv e LIB lib
-.im &{lib}/man/setup.im 
+.im &{lib}/man/setup.im
 
 &line_len(6i)
 
 &h1(RMR Library Functions)
 &h2(NAME)
-       rmr_free_msg
+    rmr_free_msg
 
 &h2(SYNOPSIS )
 &indent
@@ -44,14 +44,14 @@ void rmr_free_msg( rmr_mbuf_t* mbuf );
 
 &h2(DESCRIPTION)
 The message buffer is returned to the pool, or the associated memory is
-released depending on the needs of the underlying messaging system. 
-This allows the user application to release a buffer that is not going 
+released depending on the needs of the underlying messaging system.
+This allows the user application to release a buffer that is not going
 to be used.
-It is safe to pass a nil pointer to this function, and doing so does 
+It is safe to pass a nil pointer to this function, and doing so does
 not result in a change to the value of &cw(errrno.)
 &space
 
-After calling, the user application should &bold(not) use any of the 
+After calling, the user application should &bold(not) use any of the
 pointers (transaction ID, or payload) which were available.