trivial text cleanups

Signed-off-by: Kay Sievers <kay.sievers@suse.de>

README

@@ -85,7 +85,8 @@ To use:
 
 If nothing seems to happen, make sure your build worked properly by
 running the udev-test.pl script as root in the test/ subdirectory of the
-udev source tree.
+udev source tree. Running udevstart should populate an empty /dev
+directory. You may test, if a node is recreated after running udevstart.
 
 Development and documentation help is very much appreciated, see the TODO
 file for a list of things left to be done.

etc/udev/udev-devfs.rules

@@ -4,9 +4,6 @@
 # it. Use custom rules to name your device or look at the persistent device
 # naming scheme, which is implemented for disks and add your subsystem.
 
-# There are a number of modifiers that are allowed to be used in some of the
-# fields.  See the udev man page for a full description of them.
-
 # ide block devices
 BUS="ide", KERNEL="hd*", PROGRAM="/etc/udev/ide-devfs.sh %k %b %n", NAME="%k", SYMLINK="%c{1} %c{2}"
 

extras/run_directory/README

@@ -1,5 +1,5 @@
 Use these binaries only if you need backward compatibility with
-older udev versions. The use of /etc/dev.d/ is no longer recommended
+older udev versions. The use of /etc/dev.d/ is no longer recommended.
 Use explicit udev rules with RUN keys to hook into the processing.
 
   /etc/dev.d/ + /etc/hotplug.d/ directory multiplexing is completely
@@ -12,6 +12,6 @@ Use explicit udev rules with RUN keys to hook into the processing.
     The recommended way to handle this is to convert all the calls from
     the directories to explicit udev rules and get completely rid of the
     multiplexing. (To catch a ttyUSB event, you now no longer need to
-    fork and exit 300 tty script instances you are not interested in, it
-    is just one rule that matches exactly the device.)
+    fork and exit 300 tty script instances on bootup you are not interested
+    in, it is just one rule that matches exactly that single device.)