docs: i2c: summary: extend introduction

- state the "official" name (I²C, not I2C, according to the spec) at
   the beginning but keep using the more practical I2C elsewhere
 - mention some known different names
 - add link to the specification document

Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
Reviewed-by: Jean Delvare <jdelvare@suse.de>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>

Documentation/i2c/summary.rst

@@ -2,12 +2,18 @@
 I2C and SMBus
 =============
 
-I2C (pronounce: I squared C) is a protocol developed by Philips. It is a
+I²C (pronounce: I squared C and written I2C in the kernel documentation) is
-slow two-wire protocol (variable speed, up to 400 kHz), with a high speed
+a protocol developed by Philips. It is a slow two-wire protocol (variable
-extension (3.4 MHz).  It provides an inexpensive bus for connecting many
+speed, up to 400 kHz), with a high speed extension (3.4 MHz).  It provides
-types of devices with infrequent or low bandwidth communications needs.
+an inexpensive bus for connecting many types of devices with infrequent or
-I2C is widely used with embedded systems.  Some systems use variants that
+low bandwidth communications needs.  I2C is widely used with embedded
-don't meet branding requirements, and so are not advertised as being I2C.
+systems.  Some systems use variants that don't meet branding requirements,
+and so are not advertised as being I2C but come under different names,
+e.g. TWI (Two Wire Interface), IIC.
+
+The official I2C specification is the `"I2C-bus specification and user
+manual" (UM10204) <https://www.nxp.com/docs/en/user-guide/UM10204.pdf>`_
+published by NXP Semiconductors.
 
 SMBus (System Management Bus) is based on the I2C protocol, and is mostly
 a subset of I2C protocols and signaling.  Many I2C devices will work on an