diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml
index b37fc44d3..2f586aea7 100644
--- a/chapter01/changelog.xml
+++ b/chapter01/changelog.xml
@@ -83,6 +83,9 @@ first a summary, then a detailed log.
+April 16, 2005 [matt]: Reword handling of hotpluggable devices
+now that we install the hotplug package (Andrew Benton)
+
April 16, 2005 [matt]: Minor wording/typo fixes (Allard Welter)
diff --git a/chapter07/udev.xml b/chapter07/udev.xml
index 825ccb20f..a89486d22 100644
--- a/chapter07/udev.xml
+++ b/chapter07/udev.xml
@@ -154,22 +154,11 @@ into the kernel or because it was loaded via the
S05modules bootscript), udev will
be called upon to create the relevant device node(s) according to the
sysfs data available in
-/sys. If the driver for the
-just plugged in device is available as a module but currently unloaded,
-then attaching the device to the system will only cause the kernel's
-bus driver to generate a hotplug event that notifies userspace of the
-new device connection and it not being attached to a driver. In
-effect, nothing happens and the device itself is not usable
-yet.
+/sys.
-If building a system that has a lot of drivers compiled as
-modules rather than directly built into the kernel, using the
-S05modules may not be practical. The Hotplug
-package (see ) can
-be beneficial in these cases. When the Hotplug package is installed,
-it will respond to the aforementioned kernel's bus driver hotplug
-events. The Hotplug package will load the appropriate module and make
-this device available by creating the device node(s) for it.
+If the driver for the just plugged in device is available as a module but
+currently unloaded, the Hotplug package will load the appropriate module
+and make this device available by creating the device node(s) for it.