.\"
.SH DESCRIPTION
.B iwevent
-display Wireless Events received through the RTNetlink socket. Each
-line display the specific Wireless Event which describe what has
+displays Wireless Events received through the RTNetlink socket. Each
+line displays the specific Wireless Event which describes what has
happened on the specified wireless interface.
.br
This command doesn't take any arguments.
.\" DISPLAY part
.\"
.SH DISPLAY
-There is two classes of Wireless Events.
+There are two classes of Wireless Events.
.PP
The first class is events related to a change of wireless settings on
the interface (typically done through
.TP
.B New Access Point/Cell address
The interface has joined a new Access Point or Ad-Hoc Cell, or lost
-its association with it. This is the same MAC address that is reported
+its association with it. This is the same address that is reported
by
.BR iwconfig .
.TP
.TP
.B Registered node
The interface has successfully registered a new wireless
-client/peer. Will be generated mostly when the interface act as an
-Access Point (mode master).
+client/peer. Will be generated mostly when the interface acts as an
+Access Point (mode Master).
.TP
.B Expired node
The registration of the client/peer on this interface has
-expired. Will be generated mostly when the interface act as an Access
-Point (mode master).
+expired. Will be generated mostly when the interface acts as an Access
+Point (mode Master).
.TP
.B Spy threshold crossed
-The signal strength for one of the address in the spy list went under
-the low threshold or went above than the high threshold.
+The signal strength for one of the addresses in the spy list went
+under the low threshold or went above the high threshold.
.PP
Most wireless drivers generate only a subset of those events, not all
of them, the exact list depends on the specific hardware/driver