From: Tomasz Unger <redacted>

Fix spelling mistakes in comment block (lines 64, 69, 72):
- 'recieves' -> 'receives'
- 'recieving' -> 'receiving'
- 'recived' -> 'received'

Found by manual inspection.

Signed-off-by: Tomasz Unger <redacted>
---
  drivers/nfc/trf7970a.c | 6 +++---
  1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/nfc/trf7970a.c b/drivers/nfc/trf7970a.c
index d17c701c7888..c3bf48f49eca 100644
--- a/drivers/nfc/trf7970a.c
+++ b/drivers/nfc/trf7970a.c

@@ -61,15 +61,15 @@
   * support that.  So, if an abort is received before trf7970a_send_cmd()
   * has sent the command to the tag, it simply returns -ECANCELED.  If the
   * command has already been sent to the tag, then the driver continues
- * normally and recieves the response data (or error) but just before
+ * normally and receives the response data (or error) but just before
   * sending the data upstream, it frees the rx_skb and sends -ECANCELED
   * upstream instead.  If the command failed, that error will be sent
   * upstream.
   *
- * When recieving data from a tag and the interrupt status register has
+ * When receiving data from a tag and the interrupt status register has
   * only the SRX bit set, it means that all of the data has been received
   * (once what's in the fifo has been read).  However, depending on timing
- * an interrupt status with only the SRX bit set may not be recived.  In
+ * an interrupt status with only the SRX bit set may not be received.  In
   * those cases, the timeout mechanism is used to wait 20 ms in case more
   * data arrives.  After 20 ms, it is assumed that all of the data has been
   * received and the accumulated rx data is sent upstream.  The