Update README.md

Added a video on how to fix faulty MAX30100 boards.

README.md

@@ -28,8 +28,8 @@ Since I am not a psychic, all inquiries containing some form of vague "your code
 
 1) Underpowered MCU (see previous paragraphs).
 2) Misunderstanding of oximetry, especially motion artifacts. Don't expect a useful signal when the sensor is moving. Don't expect a useful signal from the very first batch, it may take some time - say, a minute - for the whole system to get going.
-3) Faulty hardware (see https://reedpaper.wordpress.com/2018/08/22/pulse-oximeter-max30100-max30102-how-to-fix-wrong-board/, for example). Some cloned sensors may have the RED and IR channels swapped; see Rob Cazzaro's post: https://github.com/aromring/MAX30102_by_RF/issues/13#issue-601473302 (his is a prime example of an excellent bug report, by the way).
-4) Incorrect connections.
+3) Faulty hardware, such as faulty wiring in some cheap clones (see https://reedpaper.wordpress.com/2018/08/22/pulse-oximeter-max30100-max30102-how-to-fix-wrong-board/ as well as https://www.youtube.com/watch?v=ZqdmA4NAqb0 for details) or swapped RED and IR channels (see Rob Cazzaro's post: https://github.com/aromring/MAX30102_by_RF/issues/13#issue-601473302) _Rob's post is a prime example of an excellent bug report, by the way!_
+5) Incorrect connections.
 
 At minimum, in order to accept a bug report I need you to: