Updated Home (markdown)

Home.md

@@ -38,7 +38,7 @@ Please read the [Adafruit NeoPixel Best Practices](https://learn.adafruit.com/ad
 
 ## Why this library?
 There are multiple competing libraries, FastLED being the biggest.  
-On ESP822, your choices are:
+On ESP822, your choices main are:
 * NeoPixelBus
     * Smaller than FastLED, more features and pixel support than esp8266_ws2812_i2s
     * Uses the DMA via the UART, avoiding interrupts (NMIs). FastLED uses interrupts which can be problematic if you use other code that relies on interrupts, or wifi (although FastLED allows other fast interrupts to fire in between pixel updates)
@@ -50,6 +50,8 @@ On ESP822, your choices are:
      * Very rich API, although at a cost of bigger library size
      * Identical API available across most arduino compatible CPUs
      * Interrupt driven on ESP8266, so it's sensitive to timing (not an issue on ESP32 which uses RMT)
+* Adafruit::NeoPixel
+     * Basic interrupt driven library which does not support any other interrupt driven code to work. Not recommended.
 
 On ESP32, if you are ok with the bigger code size and different API, FastLED with RMT is likely a better bet as it supports 8 parallel channels for better refresh rate on bigger strings (useful past 256 pixels).
 If you have 4096 pixels or more, you can use the 16 way output driver from Yves as described on this [on this page](http://marc.merlins.org/perso/arduino/post_2018-07-30_Building-a-64x64-Neopixel-Neomatrix-_4096-pixels_-running-NeoMatrix-FastLED-IR.html#esp32driver)