Fixed some grammar mistakes. Signed-off-by: Beno?t Bourbi? <benoit.bourbie at gmail.com> --- include/net/wimax.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/include/net/wimax.h b/include/net/wimax.h index bbb74f9..4588407 100644 --- a/include/net/wimax.h +++ b/include/net/wimax.h @@ -103,7 +103,7 @@ * over multicast groups. This allows to have multiple applications * monitoring them. * - * Each command/signal gets assigned it's own attribute policy. This + * Each command/signal gets assigned its own attribute policy. This * way the validator will verify that all the attributes in there are * only the ones that should be for each command/signal. Thing of an * attribute mapping to a type+argumentname for each command/signal. @@ -123,7 +123,7 @@ * * If network interface X is a WiMAX device, there will be a Generic * Netlink family named "WiMAX X" and the device will present a - * "wimax" directory in it's network sysfs directory + * "wimax" directory in its network sysfs directory * (/sys/class/net/DEVICE/wimax) [used by HAL]. * * The inexistence of any of these means the device does not support @@ -228,7 +228,7 @@ * WiMAX stack. * * When initializing the hardware (_probe), after calling - * wimax_dev_add(), query the device for it's RF Kill switches status + * wimax_dev_add(), query the device for its RF Kill switches status * and feed it back to the WiMAX stack using * wimax_report_rfkill_{hw,sw}(). If any switch is missing, always * report it as ON. @@ -306,7 +306,7 @@ struct wimax_dev; * DRIVERNAME-BUSNAME:BUSID (dev->bus->name, dev->bus_id). * * @id_table_node: [private] link to the list of wimax devices kept by - * id-table.c. Protected by it's own spinlock. + * id-table.c. Protected by its own spinlock. * * @mutex: [private] Serializes all concurrent access and execution of * operations. -- 1.8.2.470.g21ccebe.dirty