diff --git a/docs/feature_rgb_matrix.md b/docs/feature_rgb_matrix.md
index 49d2fd9e99..de36f95fb7 100644
--- a/docs/feature_rgb_matrix.md
+++ b/docs/feature_rgb_matrix.md
@@ -158,7 +158,7 @@ Where `X_Y` is the location of the LED in the matrix defined by [the datasheet](
 ---
 ### IS31FL3736 :id=is31fl3736
 
-There is basic support for addressable RGB matrix lighting with the I2C IS31FL3737 RGB controller. To enable it, add this to your `rules.mk`:
+There is basic support for addressable RGB matrix lighting with the I2C IS31FL3736 RGB controller. To enable it, add this to your `rules.mk`:
 
 ```make
 RGB_MATRIX_ENABLE = yes
@@ -213,7 +213,7 @@ Here is an example using 2 drivers.
 
 #define DRIVER_COUNT 2
 #define DRIVER_1_LED_TOTAL 30
-#define DRIVER_2_LED_TOTAL 36
+#define DRIVER_2_LED_TOTAL 32
 #define RGB_MATRIX_LED_COUNT (DRIVER_1_LED_TOTAL + DRIVER_2_LED_TOTAL)
 ```
 !> Note the parentheses, this is so when `RGB_MATRIX_LED_COUNT` is used in code and expanded, the values are added together before any additional math is applied to them. As an example, `rand() % (DRIVER_1_LED_TOTAL + DRIVER_2_LED_TOTAL)` will give very different results than `rand() % DRIVER_1_LED_TOTAL + DRIVER_2_LED_TOTAL`.