From 325be07019e46f454e74c841a712c461a4bd91bc Mon Sep 17 00:00:00 2001
From: Krissssz <70952326+Fulop-Krisztian@users.noreply.github.com>
Date: Wed, 18 Jun 2025 22:35:02 +0200
Subject: [PATCH] docs(customizing_plugins): clarify nested key behavior when
 using function notation

---
 src/content/docs/configuration/customizing_plugins.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/docs/configuration/customizing_plugins.mdx b/src/content/docs/configuration/customizing_plugins.mdx
index bb8ad5ab3..27c4cd1d8 100644
--- a/src/content/docs/configuration/customizing_plugins.mdx
+++ b/src/content/docs/configuration/customizing_plugins.mdx
@@ -192,7 +192,7 @@ opts = {
 }
 ```
 
-One thing to be careful for that the `table` merging handles that the function notation will not is the automatic creation of nested/parent keys. For example, if we want to set `indent.enable = true` in our `opts` with the function notation, it would look something like this:
+One thing to watch out for (that `table` merging handles automatically, but the function notation does not) is the creation of nested/parent keys. When using a function to modify `opts`, you’re responsible for ensuring that nested tables exist before setting any values on them. For example, if we want to set `indent.enable = true` in our `opts` with the function notation, it would look something like this:
 
 ```lua
 return {