From fd982a990d9e3a5d6adcc1b37a618cbf66f4ce56 Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Mon, 23 Oct 2017 08:45:41 +0000
Subject:  Clarify mdevd doc

---
 doc/mdevd.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/mdevd.html b/doc/mdevd.html
index 3e8d594..d444693 100644
--- a/doc/mdevd.html
+++ b/doc/mdevd.html
@@ -58,7 +58,7 @@ coldplug uevents. </li>
 <ul>
  <li> mdevd reads and parses its configuration file <tt>/etc/mdev.conf</tt>. </li>
  <li> It then reads its stdin, waiting for uevents.
- <li> It exits when it has finished scanning. </li>
+ <li> It exits when the stream of uevents ends. (EOF on stdin.) </li>
 </ul>
 
 <h2> Exit codes </h2>
@@ -89,7 +89,7 @@ Default verbosity is 1. 0 will only print fatal error messages, 3 or more
 is seriously verbose debugging. </li>
  <li> <tt>-n</tt>&nbsp;: dry run. mdevd will not create or delete
 device nodes, and it will not spawn commands. Instead, it will print to stdout
-the commands it would have spawned. </li>
+the actions it would have performed. </li>
  <li> <tt>-f</tt>&nbsp;<em>conffile</em>&nbsp;: read the configuration
 file from <em>conffile</em>. Default is <tt>/etc/mdev.conf</tt>.
 <em>conffile</em> must be an absolute path. </li>
-- 
cgit v1.2.3