Spellcheck docs (#1652)

* Spelling mistakes

docs/reference/bluetooth/about-bluetooth.md

@@ -73,10 +73,10 @@ Full documentation for the @boardname@ Bluetooth profile as used by this applica
 The @boardname@'s accelerometer (motion detector), magnetometer (digital compass), two buttons on the front, LED Display, IO pins on the edge connector, internal message bus and internal temperature sensor are all exposed as Services so that applications can exploit these features of the device. In addition: 
 
 * the Bluetooth SIG defined Device Information Service is included to allow applications to obtain information such as firmware version details over Bluetooth
-* there's a Device Firmware Update (DFU) service which allows new @boardname@ code to be flahsed to the device over Bluetooth instead of over USB
+* there's a Device Firmware Update (DFU) service which allows new @boardname@ code to be flashed to the device over Bluetooth instead of over USB
 * there's a UART service which allows arbitrary data to be exchanged with the @boardname@ in a way resembling traditional serial communications.
 
-Everything you can do with the @boardname@ over Bluetooth is achieved through read, write and notify operations. Not all characteristics support all three so check the profile documentation. Often there are Characteristics whose purpose is to allow you to write configuration values which control other behviours. Technically these are called Control Points. For example you can specify the frequency with which accelerometer data is sampled before it is transmitted as a Notification message to your application.
+Everything you can do with the @boardname@ over Bluetooth is achieved through read, write and notify operations. Not all characteristics support all three so check the profile documentation. Often there are Characteristics whose purpose is to allow you to write configuration values which control other behaviours. Technically these are called Control Points. For example you can specify the frequency with which accelerometer data is sampled before it is transmitted as a Notification message to your application.
 
 ## Want to Know More?
 
@@ -96,4 +96,4 @@ https://www.youtube.com/watch?v=aep_GVowKfs
 
 ```package
 bluetooth
-```
+```

docs/reference/bluetooth/start-io-pin-service.md

@@ -7,7 +7,7 @@ For another device like a smartphone to use any of the Bluetooth "services" whic
 
 ## ~
 
-The Bluetooth IO pin service makes it possible for another device such as a smartphone to communicate with other electronic 'things' connected to a @boardname@'s edge connector. You could for example, use your smartphone to switch on or off a light which is connected to the @boardname@ or your smartphone could receive data collected from a sensor connected to the @boardname@. In fact you could do both of these things at the same time since the Bluetooth IO pin service lets you interact with multiple 'pins' on the edge conector in different ways all at the same time. 
+The Bluetooth IO pin service makes it possible for another device such as a smartphone to communicate with other electronic 'things' connected to a @boardname@'s edge connector. You could for example, use your smartphone to switch on or off a light which is connected to the @boardname@ or your smartphone could receive data collected from a sensor connected to the @boardname@. In fact you could do both of these things at the same time since the Bluetooth IO pin service lets you interact with multiple 'pins' on the edge connector in different ways all at the same time. 
 
 No additional code is needed on the @boardname@ to use the Bluetooth IO pin service from another device. 
 

docs/reference/pins/i2c-write-number.md

@@ -37,7 +37,7 @@ Send the value `2055` to the 7-bit I2C address as a 32-bit number. The `32`, big
 pins.i2cWriteNumber(32, 2055, NumberFormat.Int32BE, false);
 ```
 
-### Reapeted writes
+### Repeated writes
 
 Send three byte values to a device at address `33`.
 
@@ -51,4 +51,4 @@ pins.i2cWriteNumber(33, 87, NumberFormat.Int32BE, false);
 
 [i2c read number](/reference/pins/i2c-read-number)
 
-[What's I2C?](http://www.i2c-bus.org/), [number format](/types/buffer/number-format)
+[What's I2C?](http://www.i2c-bus.org/), [number format](/types/buffer/number-format)

docs/reference/radio/on-received-buffer.md

@@ -14,7 +14,7 @@ The data contained in **receivedBuffer** is put there as a data [type](/types).
 
 ## Example: Remote level
 
-Two @boardname@s work like remote levels. They lie flat and detect any change in the horizontal position of the plane that they sit in. Each board sends its level measurements to the other. Each level measurment is shown on the screen.
+Two @boardname@s work like remote levels. They lie flat and detect any change in the horizontal position of the plane that they sit in. Each board sends its level measurements to the other. Each level measurement is shown on the screen.
 
 ```typescript
 let ax = 0;

docs/reference/serial/write-value.md

@@ -10,7 +10,7 @@ It is common when reporting or recording data to use a _Name Value Pair_ (NVP).
 
 ``temperature:-15``
 
-Associating a name with a value helps to identify related data when different data sources are recorded. For example, if you're reporting both temperature and light intensity, the _name:value_ format helps spreadsheets or other data analysis programs distingush between them and group the same types of values together properly. Reporting two data sources might look like this in the output:
+Associating a name with a value helps to identify related data when different data sources are recorded. For example, if you're reporting both temperature and light intensity, the _name:value_ format helps spreadsheets or other data analysis programs distinguish between them and group the same types of values together properly. Reporting two data sources might look like this in the output:
 
 ```
 temperature:-15