diff --git a/docs/guides/customizing-kano.md b/docs/guides/customizing-kano.md
index 5b41889d..abb267b8 100644
--- a/docs/guides/customizing-kano.md
+++ b/docs/guides/customizing-kano.md
@@ -93,7 +93,7 @@ You now should be able to see a map highlighting some administrative boundaries
 
 If you have to ingest large datasets you should consider processing data using our [ETL Krawler](https://kalisio.github.io/krawler/) or ad-hoc processors. For instance, [k-population](https://github.com/kalisio/k-population) ingest population data from a big GeoPackage into our database. You will find the associated layer definition in the built-in layers.
 
-#### Time-varying data
+### Time-varying data
 
 One of the best feature of Kano is interactive visualisation, meaning that data can be updated in real-time according to user actions or data updates. A typical use case is the visualisation of time-varying spatial datasets. In this section we will use some data providing the number of hospitalizations by department in France during the COVID-19 (from 20-03-2020 to 20-04-2020) to perform such a visualisation.
 
diff --git a/docs/guides/kano-api.md b/docs/guides/kano-api.md
index a6630b9d..8656d0e3 100644
--- a/docs/guides/kano-api.md
+++ b/docs/guides/kano-api.md
@@ -117,7 +117,7 @@ Typical use case is to retrieve the raw observations. You can filter spatially (
 ```
 :::
 
-#### Request observations at a station
+### Request observations at a station
 
 Typical use case is to display a timeserie for the station.
 
@@ -182,7 +182,7 @@ Typical use case is to display a timeserie for the station.
 ```
 :::
 
-#### Request latest observations at (a) station(s)
+### Request latest observations at (a) station(s)
 
 Typical use case is to retrieve most recent observations for the station, or display the observations on a map if not filtering by a station ID.