delete_module.2: Small rewording of description of effect of O_TRUNC

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man2/delete_module.2 b/man2/delete_module.2
index b5a28bdac1d6af6d07397c36d715f963428cfc4f..98f91a164bd8f84ae57b365d302a996d109494d8 100644 (file)
--- a/man2/delete_module.2
+++ b/man2/delete_module.2
@@ -20,7 +20,7 @@
 .\" Formatted or processed versions of this manual, if unaccompanied by
 .\" the source, must acknowledge the copyright and authors of this work.
 .\"
-.TH DELETE_MODULE 2 2012-10-24 "Linux" "Linux Programmer's Manual"
+.TH DELETE_MODULE 2 2012-11-08 "Linux" "Linux Programmer's Manual"
 .SH NAME
 delete_module \- unload a kernel module
 .SH SYNOPSIS
@@ -100,12 +100,11 @@ The module is unloaded in the usual way.
 The
 .B O_TRUNC
 flag has one further effect on the rules described above.
-By default,
-attempting to remove a module that has an
+By default, if a module has an
 .I init
 function but no
 .I exit
-function fails.
+function, then an attempt to remove the module will fail.
 However, if
 .BR O_TRUNC
 was specified, this requirement is bypassed.