docs: zensical and content updates (#2584)

- Adds `mbtiles/sql` snippets to base path
- Clarifies table sources to include views
- Fixes `edit_uri` for "Edit this page"

Author: todtb

docs/content/mbtiles-schema.md

@@ -7,27 +7,23 @@ The `mbtiles` tool builds on top of the original [MBTiles specification](https:/
 Flat schema is the closest to the original MBTiles specification. It stores all tiles in a single table. This schema is the most efficient when the tileset contains no duplicate tiles.
 
 ```sql
---8<-- "mbtiles/sql/init-flat.sql"
+--8<-- "init-flat.sql"
 ```
 
 ## flat-with-hash
 
 Similar to the `flat` schema, but also includes a `tile_hash` column that contains a hash value of the `tile_data` column. Use this schema when the tileset has no duplicate tiles, but you still want to be able to validate the content of each tile individually.
 
 ```sql
---8<-- "mbtiles/sql/init-flat-with-hash.sql"
+--8<-- "init-flat-with-hash.sql"
 ```
 
 ## normalized
 
 Normalized schema is the most efficient when the tileset contains duplicate tiles. It stores all tile blobs in the `images` table, and stores the tile Z,X,Y coordinates in a `map` table. The `map` table contains a `tile_id` column that is a foreign key to the `images` table. The `tile_id` column is a hash of the `tile_data` column, making it possible to both validate each individual tile like in the `flat-with-hash` schema, and also to optimize storage by storing each unique tile only once.
 
-```sql
---8<-- "mbtiles/sql/init-normalized.sql"
-```
-
 Optionally, `.mbtiles` files with `normalized` schema can include a `tiles_with_hash` view. All `normalized` files created by the `mbtiles` tool will contain this view.
 
 ```sql
---8<-- "mbtiles/sql/init-normalized.sql:26:"
+--8<-- "init-normalized.sql"
 ```

docs/content/sources-pg-functions.md

@@ -1,6 +1,6 @@
 # PostgreSQL Function Sources
 
-Function Source is a database function which can be used to
+A Function Source is a database function which can be used to
 query [vector tiles](https://github.com/mapbox/vector-tile-spec). When started, Martin will look for the functions with
 a suitable signature.
 

docs/content/sources-pg-tables.md

@@ -1,6 +1,6 @@
 # PostgreSQL Table Sources
 
-Table Source is a database table which can be used to query [vector tiles](https://github.com/mapbox/vector-tile-spec). If a [PostgreSQL connection string](pg-connections.md) is given, Martin will publish all tables as data sources if they have at least one geometry column. If geometry column SRID is 0, a default SRID must be set, or else that geo-column/table will be ignored. All non-geometry table columns will be published as vector tile feature tags (properties).
+A Table Source is a database table or view which can be used to query [vector tiles](https://github.com/mapbox/vector-tile-spec). If a [PostgreSQL connection string](pg-connections.md) is given, Martin will publish all tables as data sources if they have at least one geometry column. If geometry column SRID is 0, a default SRID must be set, or else that geo-column/table will be ignored. All non-geometry table columns will be published as vector tile feature tags (properties).
 
 ## Modifying Tilejson
 

zensical.toml

@@ -12,6 +12,7 @@ site_dir = "target/book"
 site_name = "Martin Tile Server Documentation"
 site_description = "Documentation for Martin Tile Server"
 repo_url = "https://github.com/maplibre/martin"
+edit_uri = "edit/main/docs/content"
 site_author = "Maplibre Contributors"
 copyright = "Copyright © 2026 MapLibre Contributors"
 
@@ -377,7 +378,7 @@ pygments_lang_class = true
 [project.markdown_extensions.pymdownx.inlinehilite]
 
 [project.markdown_extensions.pymdownx.snippets]
-base_path = ["docs/content", "/"]
+base_path = ["docs/content", "mbtiles/sql", "/"]
 
 [project.markdown_extensions.pymdownx.superfences]
 custom_fences = [