fix: update links to lazy documentation

Author: mehalter

src/content/docs/configuration/customizing_plugins.mdx

@@ -23,7 +23,7 @@ Lazy is particularly feature rich in that it helps with plugin life cycle manage
 - Lazily loading plugins meaning that plugins can be loaded only when needed, such as on some editor event happening, benefiting `nvim` startup time.
 - Compiles plugin `lua` code into native code for your system, helping with execution speed of plugin code.
 
-To see all available options for defining plugins in Lazy.nvim please refer to the [Lazy.nvim Plugin Spec](https://github.com/folke/lazy.nvim#-plugin-spec). Here we will go over examples of defining new plugins, overriding plugins, and disabling plugins.
+To see all available options for defining plugins in Lazy.nvim please refer to the [Lazy.nvim Plugin Spec](https://lazy.folke.io/spec). Here we will go over examples of defining new plugins, overriding plugins, and disabling plugins.
 
 ## Defining Plugins
 
@@ -56,7 +56,7 @@ The `return` statement is returning a table of tables. The outer table is a list
 
 The first entry in the plugin specification is the name of the plugin to load, specified in short URL form. The next two entries in the table, `name` and `opts` are Lazy recognized keys that direct Lazy on how to configure this plugin. `opts` can be a table or a function (`opts` is a table in the example above) that contains the configuration for the plugin. The structure of what is inside of `opts` is up to each plugin.
 
-To learn more about plugin specifications, see the [Lazy documentation](https://github.com/folke/lazy.nvim#-plugin-spec).
+To learn more about plugin specifications, see the [Lazy documentation](https://lazy.folke.io/spec).
 
 That's it! When `nvim` is started, the `catppuccin` plugin will be downloaded from GitHub, installed, configured, and loaded.
 
@@ -364,7 +364,7 @@ return {
 
 ## Lazy Loading
 
-Lazy loading can be used to delay plugin loading to speed up start up time. There are a few basic methods of lazy loading that can be easily added. The main keys here are `lazy`, `cmd`, `ft`, `keys`, and `event`. More details of these and more options can be found in the [Lazy Documentation](https://github.com/folke/lazy.nvim#-plugin-spec). Here are a few examples:
+Lazy loading can be used to delay plugin loading to speed up start up time. There are a few basic methods of lazy loading that can be easily added. The main keys here are `lazy`, `cmd`, `ft`, `keys`, and `event`. More details of these and more options can be found in the [Lazy Documentation](https://lazy.folke.io/spec). Here are a few examples:
 
 ```lua title="lua/plugins/lazy_loaded.lua" /((lazy|cmd|ft|event) = \S+)/ {15-20}
 return {

src/content/docs/index.mdx

@@ -234,7 +234,7 @@ Looking a bit deeper, the `plugins` directory is where all plugins, except Astro
 
 Each file in the plugins directory can specify the installation and configuration of one or more plugins. The template generally installs and configures a single plugin per `lua` file. Further, the name of the file generally matches the name of the plugin. The one exception is `user.lua` which has multiple plugins in it - but they could be split into separate files if you wish!
 
-Be sure to check out the [Configuration/Customizing Plugins page](/configuration/customizing_plugins) and the [Lazy.nvim Documentation](https://github.com/folke/lazy.nvim?tab=readme-ov-file#-plugin-spec) for more details in how to define and configure plugins using `lazy.nvim`.
+Be sure to check out the [Configuration/Customizing Plugins page](/configuration/customizing_plugins) and the [Lazy.nvim Documentation](https://lazy.folke.io/spec) for more details in how to define and configure plugins using `lazy.nvim`.
 
 There is nothing special about the template! It's merely a quick way to get started, and, well, recommended to get you up and running quicker. Once you have a working configuration that may be the time when you start to move things around.