docs: Improve autoloading/event documentation

The thing that says "event handlers can't be autoloaded, put it in config.fish". I make good words.

1 files changed, 2 insertions, 2 deletions

diff --git a/doc_src/index.hdr.in b/doc_src/index.hdr.in
index 978a9845..b3f0db92 100644
--- a/doc_src/index.hdr.in
+++ b/doc_src/index.hdr.in
@@ -251,7 +251,7 @@ The default value for `$fish_function_path` is `~/.config/fish/functions` `/etc/
 
 It is very important that function definition files only contain the definition for the specified function and nothing else. Otherwise, it is possible that autoloading a function files requires that the function already be loaded, which creates a circular dependency.
 
-Autoloading also won't work for <a href=#event>event handlers</a>, since fish cannot know that a function is supposed to be executed when an event occurs when it hasn't yet loaded the function.
+Autoloading also won't work for <a href=#event>event handlers</a>, since fish cannot know that a function is supposed to be executed when an event occurs when it hasn't yet loaded the function. See there for details.
 
 
 \subsubsection syntax-conditional Conditional execution of code and flow control
@@ -1115,7 +1115,7 @@ function --on-signal WINCH my_signal_handler
 end
 \endfish
 
-Please note that event handlers only become active when a function is loaded which means you might need to manually <a href='commands.html#source'>source</a> a function's file instead of relying on <a href=#syntax-function-autoloading>autoloading</a>.
+Please note that event handlers only become active when a function is loaded, which means you might need to otherwise <a href='commands.html#source'>source</a> or execute a function instead of relying on <a href=#syntax-function-autoloading>autoloading</a>. One approach is to put it into your <a href="index.html#initialization">initialization file</a>.
 
 For more information on how to define new event handlers, see the documentation for the <a href='commands.html#function'>function</a> command.