1 files changed, 3 insertions, 4 deletions
diff --git a/docs/feature_rgb_matrix.md b/docs/feature_rgb_matrix.md
index 3132360a3..3a40be5f5 100644
--- a/docs/feature_rgb_matrix.md
+++ b/docs/feature_rgb_matrix.md
@@ -554,12 +554,11 @@ In order to change the delay of temperature decrease define
 ## Custom RGB Matrix Effects :id=custom-rgb-matrix-effects
-By setting `RGB_MATRIX_CUSTOM_USER` (and/or `RGB_MATRIX_CUSTOM_KB`) in `rules.mk`, new effects can be defined directly from userspace, without having to edit any QMK core files.
+By setting `RGB_MATRIX_CUSTOM_USER = yes` in `rules.mk`, new effects can be defined directly from your keymap or userspace, without having to edit any QMK core files.
-To declare new effects, create a new `rgb_matrix_user/kb.inc` that looks something like this:
+To declare new effects, create a `rgb_matrix_user.inc` file in the user keymap directory or userspace folder.
-`rgb_matrix_user.inc` should go in the root of the keymap directory.
+?> Hardware maintainers who want to limit custom effects to a specific keyboard can create a `rgb_matrix_kb.inc` file in the root of the keyboard directory, and add `RGB_MATRIX_CUSTOM_KB = yes` to the keyboard level `rules.mk`.
-`rgb_matrix_kb.inc` should go in the root of the keyboard directory.
 To use custom effects in your code, simply prepend `RGB_MATRIX_CUSTOM_` to the effect name specified in `RGB_MATRIX_EFFECT()`. For example, an effect declared as `RGB_MATRIX_EFFECT(my_cool_effect)` would be referenced with:

diff --git a/docs/feature_rgb_matrix.md b/docs/feature_rgb_matrix.md index 3132360a3..3a40be5f5 100644 --- a/docs/feature_rgb_matrix.md +++ b/docs/feature_rgb_matrix.md
@@ -554,12 +554,11 @@ In order to change the delay of temperature decrease define
554		554
555	## Custom RGB Matrix Effects :id=custom-rgb-matrix-effects	555	## Custom RGB Matrix Effects :id=custom-rgb-matrix-effects
556		556
557	By setting `RGB_MATRIX_CUSTOM_USER` (and/or `RGB_MATRIX_CUSTOM_KB`) in `rules.mk`, new effects can be defined directly from userspace, without having to edit any QMK core files.	557	By setting `RGB_MATRIX_CUSTOM_USER = yes` in `rules.mk`, new effects can be defined directly from your keymap or userspace, without having to edit any QMK core files.
558		558
559	To declare new effects, create a new `rgb_matrix_user/kb.inc` that looks something like this:	559	To declare new effects, create a `rgb_matrix_user.inc` file in the user keymap directory or userspace folder.
560		560
561	`rgb_matrix_user.inc` should go in the root of the keymap directory.	561	?> Hardware maintainers who want to limit custom effects to a specific keyboard can create a `rgb_matrix_kb.inc` file in the root of the keyboard directory, and add `RGB_MATRIX_CUSTOM_KB = yes` to the keyboard level `rules.mk`.
562	`rgb_matrix_kb.inc` should go in the root of the keyboard directory.
563		562
564	To use custom effects in your code, simply prepend `RGB_MATRIX_CUSTOM_` to the effect name specified in `RGB_MATRIX_EFFECT()`. For example, an effect declared as `RGB_MATRIX_EFFECT(my_cool_effect)` would be referenced with:	563	To use custom effects in your code, simply prepend `RGB_MATRIX_CUSTOM_` to the effect name specified in `RGB_MATRIX_EFFECT()`. For example, an effect declared as `RGB_MATRIX_EFFECT(my_cool_effect)` would be referenced with:
565		564