From f979bb871fd2838f4dc587e633ef88fe3a3af799 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]" <>
Date: Thu, 19 Oct 2023 16:57:43 +0000
Subject: [PATCH] chore: generated vimdoc

---
 doc/legendary-extensions.txt | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/doc/legendary-extensions.txt b/doc/legendary-extensions.txt
index 3be72ef..8831553 100644
--- a/doc/legendary-extensions.txt
+++ b/doc/legendary-extensions.txt
@@ -1,4 +1,4 @@
-*legendary-extensions.txt*                        Last change: 2023 October 10
+*legendary-extensions.txt*                        Last change: 2023 October 11
 
 ==============================================================================
 Table of Contents                     *legendary-extensions-table-of-contents*
@@ -93,7 +93,7 @@ Automatically load key mappings defined in lazy.nvim
     require('legendary').setup({
       extensions = {
         lazy_nvim = true,
-      }
+      },
     })
 <
 
@@ -101,7 +101,11 @@ Automatically load key mappings defined in lazy.nvim
 `WHICH-KEY.NVIM`                         *legendary-extensions-which-key.nvim*
 
 Automatically load key mappings defined by which-key.nvim
-<https://github.com/folke/which-key.nvim> into `legendary.nvim`.
+<https://github.com/folke/which-key.nvim> into `legendary.nvim`. For
+`auto_register` to work, `which-key.nvim` must be loaded on `runtimepath`
+before `legendary.nvim` initializes, but `legendary.nvim` must initialize the
+extension before `require('which-key').register()` is called. Alternatively,
+you can just pass your `which-key` tables to `legendary` directly.
 
 >lua
     require('legendary').setup({