Fix grammatical and spelling errors in the HID documentation files. Signed-off-by: SurajSonawane2415 <surajsonawane0215@xxxxxxxxx> --- Documentation/hid/hiddev.rst | 4 ++-- Documentation/hid/intel-ish-hid.rst | 2 +- Documentation/hid/uhid.rst | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/hid/hiddev.rst b/Documentation/hid/hiddev.rst index 9b82c7f89..073485f84 100644 --- a/Documentation/hid/hiddev.rst +++ b/Documentation/hid/hiddev.rst @@ -15,10 +15,10 @@ To support these disparate requirements, the Linux USB system provides HID events to two separate interfaces: * the input subsystem, which converts HID events into normal input device interfaces (such as keyboard, mouse and joystick) and a -normalised event interface - see Documentation/input/input.rst +normalized event interface - see Documentation/input/input.rst * the hiddev interface, which provides fairly raw HID events -The data flow for a HID event produced by a device is something like +The data flow for an HID event produced by a device is something like the following:: usb.c ---> hid-core.c ----> hid-input.c ----> [keyboard/mouse/joystick/event] diff --git a/Documentation/hid/intel-ish-hid.rst b/Documentation/hid/intel-ish-hid.rst index 2adc174fb..fdabf6ec6 100644 --- a/Documentation/hid/intel-ish-hid.rst +++ b/Documentation/hid/intel-ish-hid.rst @@ -21,7 +21,7 @@ mainly use HID over I2C or USB. But ISH doesn't use either I2C or USB. Overview ======== -Using a analogy with a usbhid implementation, the ISH follows a similar model +Using an analogy with a usbhid implementation, the ISH follows a similar model for a very high speed communication:: ----------------- ---------------------- diff --git a/Documentation/hid/uhid.rst b/Documentation/hid/uhid.rst index 2243a6b75..2681038cd 100644 --- a/Documentation/hid/uhid.rst +++ b/Documentation/hid/uhid.rst @@ -106,7 +106,7 @@ UHID_INPUT2: UHID_GET_REPORT_REPLY: If you receive a UHID_GET_REPORT request you must answer with this request. - You must copy the "id" field from the request into the answer. Set the "err" + You must copy the "id" field from the request into the answer. Set the "err" field to 0 if no error occurred or to EIO if an I/O error occurred. If "err" is 0 then you should fill the buffer of the answer with the results of the GET_REPORT request and set "size" correspondingly. -- 2.34.1
