[src/trunk]: src/sys/dev/ieee1394 Change some wording on fw's to make it more...

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

details:   https://anonhg.NetBSD.org/src/rev/a1d7a6bf2ae9
branches:  trunk
changeset: 521674:a1d7a6bf2ae9
user:      jmc <jmc%NetBSD.org@localhost>
date:      Sun Feb 03 07:29:14 2002 +0000

description:
Change some wording on fw's to make it more logical sounding.

diffstat:

 sys/dev/ieee1394/IMPLEMENTATION |  6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diffs (20 lines):

diff -r 59f692826686 -r a1d7a6bf2ae9 sys/dev/ieee1394/IMPLEMENTATION
--- a/sys/dev/ieee1394/IMPLEMENTATION   Sun Feb 03 07:25:11 2002 +0000
+++ b/sys/dev/ieee1394/IMPLEMENTATION   Sun Feb 03 07:29:14 2002 +0000
@@ -1,4 +1,4 @@
-$NetBSD: IMPLEMENTATION,v 1.5 2001/08/24 10:24:46 wiz Exp $
+$NetBSD: IMPLEMENTATION,v 1.6 2002/02/03 07:29:14 jmc Exp $
 
 At time point in time, there are 3 controller drivers planned:
 
@@ -28,8 +28,8 @@
 #
 # An ip capable interface can be added to the local bus as a service to offer
 # on the bus. (the code will only attach to the local bridge so 2 boxes plugged
-# into each other would only each have fw0, but would see there's another one
-# out there when they probe the config rom's)
+# into each other would only each have fw0, but would see the other side as
+# fwnodeX when it probes for remote devices)
 #
 fw* at fwbus?
 #