docs: fix broken link

www/docs/customization/index.md

@@ -1,4 +1,4 @@
-# JSONSchema
+# Customization
 
 GoReleaser can be customized by tweaking a `.goreleaser.yaml` file.
 
@@ -15,6 +15,7 @@ GoReleaser also has a [jsonschema][] file, which you can use to have better
 editor support:
 
 === "OSS"
+
     ```sh
     https://goreleaser.com/static/schema.json
     ```
@@ -26,6 +27,7 @@ editor support:
     ```
 
 === "Pro"
+
     ```sh
     https://goreleaser.com/static/schema-pro.json
     ```
@@ -44,13 +46,14 @@ You can also generate it for your specific version using the
 You can pin the version by getting the schema from the GitHub tag, for example,
 for v1.12.0:
 
-
 === "OSS"
+
     ```sh
     https://raw.githubusercontent.com/goreleaser/goreleaser/v1.12.0/www/docs/static/schema.json
     ```
 
 === "Pro"
+
     ```sh
     https://raw.githubusercontent.com/goreleaser/goreleaser/v1.12.0/www/docs/static/schema-pro.json
     ```

www/docs/how-it-works.md

@@ -7,7 +7,7 @@ use cases easy.
 GoReleaser expects a couple of things:
 
 - a `.goreleaser.yaml` file with the configuration (see the
-  [customization section](/customization) for more info)
+  [customization section](./customization/index.md) for more info)
 - a clean working tree
 - a SemVer-compatible version (e.g. `10.21.34-prerelease+buildmeta`)
 
@@ -24,6 +24,6 @@ A GoReleaser run is split into 4 major steps:
 - **announcing**: announces your release to the configured channels
 
 Some steps might be skipped with `--skip-foo`-like flags (check the
-[command line docs](/cmd/goreleaser/) for details).
+[command line docs](./cmd/goreleaser.md) for details).
 
 If any of the previous steps fails, the next steps will not run.

www/mkdocs.yml

@@ -86,7 +86,7 @@ nav:
         - limitations/cgo.md
         - limitations/semver.md
   - Customization:
-      - JSONSchema: customization/jsonschema.md
+      - customization/index.md
       - Basics:
           - customization/includes.md
           - customization/templates.md