[src/trunk]: src/sys/modules/examples Improve wording

[pgoyette <pgoyette%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/5b55b4bbefe2
branches:  trunk
changeset: 744599:5b55b4bbefe2
user:      pgoyette <pgoyette%NetBSD.org@localhost>
date:      Fri Feb 07 19:22:21 2020 +0000

description:
Improve wording

diffstat:

 sys/modules/examples/README |  10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)

diffs (33 lines):

diff -r c03337b4a837 -r 5b55b4bbefe2 sys/modules/examples/README
--- a/sys/modules/examples/README       Fri Feb 07 19:00:18 2020 +0000
+++ b/sys/modules/examples/README       Fri Feb 07 19:22:21 2020 +0000
@@ -1,4 +1,4 @@
-       $NetBSD: README,v 1.11 2020/02/06 22:52:25 kamil Exp $
+       $NetBSD: README,v 1.12 2020/02/07 19:22:21 pgoyette Exp $
 
                            Kernel Developer's Manual
 
@@ -33,10 +33,10 @@
 
          # make S=/data/netbsd/src/sys
 
-     The code of a module does not need to be in src/sys unless you use
+     The code of a module does not need to be in src/sys unless it uses
      the autoconf(9) framework.
 
-     A cross-built of a module for a target platform is possible with the
+     A cross-build of a module for a target platform is possible with the
      build.sh framework. You need to generate the toolchain and set
      appropriately PATH to point bin/ in the TOOLDIR path. An example command
      to cross-build a module with the amd64 toolchain is as follows:
@@ -46,8 +46,8 @@
 
      The example modules should not be used on a production machine.
 
-     All modules that create a cdevsw should be verified that the major number
-     should not conflict with a real device.
+     All modules that create a cdevsw (or bdevsw) should be verified that
+     the major number(s) should not conflict with a real device.
 
 SEE ALSO
      modctl(2), module(7), modload(8), modstat(8), modunload(8), module(9),