fix 2 links

versatiles-org · Oct 19, 2024 · 91a474a · 91a474a
1 parent 9d2f555
commit 91a474a
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/compendium/versatiles_frontend_specification.md b/compendium/versatiles_frontend_specification.md
@@ -204,7 +204,7 @@ Based on this example, the following glyphs must be available:
 - Each sprite should be contained in its own subdirectory: `/assets/sprites/{sprite_id}/`.
 - The metadata for each sprite is defined in JSON format following the [sprite source specification](https://maplibre.org/maplibre-style-spec/sprite/#sprite-source-format) and should be served as `/assets/sprites/{sprite_id}/sprite.json`.
 - Sprite IDs (`{sprite_id}`) should be OS/UNIX/URL safe, using only lowercase letters, digits, and underscores.
-- Additionally, you should provide a list of all available sprites in the [`/assets/sprites.json`](#file-assetsspritesjson) file.
+- Additionally, you should provide a list of all available sprites in the [`/assets/sprites/index.json`](#file-assetsspritesindexjson) file.
 - Refer to the [MapLibre Style Spec](https://maplibre.org/maplibre-style-spec/sprite/) for more detailed information on sprites.
 
 

diff --git a/compendium/versatiles_layer_specification.md b/compendium/versatiles_layer_specification.md
@@ -292,7 +292,7 @@ The Frontend Layer serves as the graphical interface, presenting map tiles to th
 ### Requirements/Recommendations
 
 - The frontend SHOULD be capable to draw Shortbread vector tiles and raster tiles.
-- See [VersaTiles Frontend Specifications](#versatiles-frontend-specification) for more information.
+- See [VersaTiles Frontend Specifications](versatiles_frontend_specification.md) for more information.
 
 
 ### Status