Merge pull request #291 from rneacy/master

Switch I2C diagram; update DAPLink diagram

Author: microbit-mark

hardware/assets/i2c-block.svg

@@ -17,7 +17,7 @@ The V1.5 micro:bit has a footprint for two different motion sensors: one made by
 
 ### I2C block diagram
 
-![I2C block](/docs/hardware/assets/i2c-block.svg)
+![I2C block](/docs/hardware/assets/nrf51i2c.png)
 
 ### Table of addresses used
 

hardware/assets/i2c-diagram.png

@@ -19,7 +19,7 @@ The external lines run to the edge connector and can be used for accessories.
 
 ### I2C block diagram
 
-![I2C block](/docs/hardware/assets/i2c-block.svg)
+![I2C block](/docs/hardware/assets/i2c-diagram.png)
 
 ### Table of addresses used
 

hardware/assets/nrf51i2c.png

@@ -19,7 +19,7 @@ The chip that developers' code runs on, and that all the peripherals are connect
 
 The **Target MCU** is a **Nordic Semiconductor nRF52833** <span class="v2">V2</span> or **Nordic Semiconductor nRF51822** <span class="v1">V1</span>.
 
-<img src="/docs/software/assets/Interface.svg" alt="DAPlink interface" style="background:#eeeeff; padding:20px;">
+![v2 interface](/docs/software/assets/v2-interface.png)
 
 The target and interface MCUs are connected by two interfaces: