clear md from rst

Author: wm-wm-wm

mddocs/docs/en/changelog.md

@@ -1,7 +1,7 @@
 # Changelog
 
-[0.1.o][0.1.o]
-[0.2.o][0.2.o]
+[0.1.0][0.1.0]
+[0.2.0][0.2.0]
 [0.2.1][0.2.1]
-[0.3.o][0.3.o]
+[0.3.0][0.3.0]
 [0.3.1][0.3.1]

mddocs/docs/en/changelog/0.1.0.md

@@ -1,3 +1,3 @@
-# 0.1.0 (2024-12-25)
+# 0.1.0 (2024-12-25) { #0.1.0 }
 
 🎉 Data.Rentgen first release! 🎉

mddocs/docs/en/changelog/0.2.0.md

@@ -1,4 +1,4 @@
-# 0.2.0 (2025-03-25)
+# 0.2.0 (2025-03-25) { #0.2.0 }
 
 ## TL;DR
 

mddocs/docs/en/changelog/0.2.1.md

@@ -1,4 +1,4 @@
-# 0.2.1 (2025-04-07)
+# 0.2.1 (2025-04-07) { #0.2.1 }
 
 ## Improvements
 

mddocs/docs/en/changelog/0.3.0.md

@@ -1,4 +1,4 @@
-# 0.3.0 (2025-07-04)
+# 0.3.0 (2025-07-04) { #0.3.0 }
 
 ## Features
 

mddocs/docs/en/changelog/0.3.1.md

@@ -1,4 +1,4 @@
-# 0.3.1 (2025-07-04)
+# 0.3.1 (2025-07-04) { #0.3.1 }
 
 ## Breaking changes
 

mddocs/docs/en/integrations/flink1/index.md

@@ -9,7 +9,7 @@ Using [OpenLineage integration with Apache Flink 1.x](https://openlineage.io/doc
 
 ## Limitations
 
-- Only `standalone-job` (application mode) is supported, but not `jobmanager` (session mode): [https://github.com/OpenLineage/OpenLineage/issues/2150](OpenLineageissue)
+- Only `standalone-job` (application mode) is supported, but not `jobmanager` (session mode): (https://github.com/OpenLineage/OpenLineage/issues/2150)[OpenLineageissue]
 
 ## Entity mapping
 

mddocs/docs/en/reference/architecture.md

@@ -5,12 +5,12 @@
 Data.Rentgen is build using following components:
 
 - [OpenLineage](https://openlineage.io/docs/) clients & integrations with third-party modules (e.g. Apache Spark, Apache Airflow).
-- [`message-broker`](message-broker), receiving events in JSON format.
-- [`message-consumer`](message-consumer), parsing JSON messages.
-- [`database`](database) for storing consumed & cleaned up data.
-- [`server`](server), serving database data.
-- [`frontend`](frontend), accessing REST API to navigate created entities & lineage graph.
-- [`http2kafka`](http2kafka) (optional), proxy for sending OpenLineage events to Kafka using HTTP API.
+- [`message-broker`][message-broker], receiving events in JSON format.
+- [`message-consumer`][message-consumer], parsing JSON messages.
+- [`database`][database] for storing consumed & cleaned up data.
+- [`server`][server], serving database data.
+- [`frontend`][frontend], accessing REST API to navigate created entities & lineage graph.
+- [`http2kafka`][http2kafka] (optional), proxy for sending OpenLineage events to Kafka using HTTP API.
 
 ## Architecture diagram
 

mddocs/docs/en/reference/database/index.md

@@ -16,22 +16,22 @@ Migration script is a thin wrapper around [Alembic cli](https://alembic.sqlalche
 
 ## Partitions
 
-After migrations are performed, it is required to run [`create-partitions-cli`](create-partitions-cli) which creates partitions for some tables in the database.
+After migrations are performed, it is required to run [`create-partitions-cli`][create-partitions-cli] which creates partitions for some tables in the database.
 By default, it creates monthly partitions, for current and next month. This can be changed by overriding command args.
 
 This script should run on schedule, depending on partitions granularity.
 Scheduling can be done by adding a dedicated entry to [crontab](https://help.ubuntu.com/community/CronHowto).
 
-It's strongly recommended also to add old partitions cleanup script to cron [`cleanup-partitions-cli`](cleanup-partitions-cli).
+It's strongly recommended also to add old partitions cleanup script to cron [`cleanup-partitions-cli`][cleanup-partitions-cli].
 Scheduling setup is same is for creating of partitions.
 
 ## Analytic views
 
-Along with migrations few analytics views are created. These are managed by [`refresh-analytic-views-cli`](refresh-analytic-views-cli), and should be executed by schedule.
+Along with migrations few analytics views are created. These are managed by [`refresh-analytic-views-cli`][refresh-analytic-views-cli], and should be executed by schedule.
 
 ## Seeding
 
-By default, database is created with no data. To seed database with some examples, use [`db-seed-cli`](db-seed-cli).
+By default, database is created with no data. To seed database with some examples, use [`db-seed-cli`][db-seed-cli].
 
 ## Requirements
 
@@ -64,19 +64,21 @@ By default, database is created with no data. To seed database with some example
 
   Options can be set via `.env` file or `environment` section in `docker-compose.yml`
 
-=== "docker-compose.yml"
+??? note "docker-compose.yml"
 
-  ```yaml
-    .. literalinclude:: ../../../docker-compose.yml
-        :emphasize-lines: 1-69,176
-  ```
+    ```yaml hl_lines="1-69 176" linenums="1"
+    ----8<----
+    docker-compose.yml
+    ----8<----
+    ```
 
-=== ".env.docker"
+??? note ".env.docker"
 
-  ```yaml
-    .. literalinclude:: ../../../.env.docker
-        :emphasize-lines: 1-5,23
-  ```
+    ```ini hl_lines="1-5 23" linenums="1"
+    ----8<----
+    .env.docker
+    ----8<----
+    ```
 
 - Add scripts to crontab:
 
@@ -110,7 +112,7 @@ By default, database is created with no data. To seed database with some example
   ...
   ```
 
-- Configure [`Database connection`](configuration-database) using environment variables, e.g. by creating `.env` file:
+- Configure [`Database connection`][configuration-database] using environment variables, e.g. by creating `.env` file:
 
   ```console title="/some/.env"
 
@@ -177,5 +179,5 @@ By default, database is created with no data. To seed database with some example
 [Create partitions cli][create-partitions-cli]
 [Cleanup partitions cli][cleanup-partitions-cli]
 [Refresh analytic views cli][refresh-analytic-views-cli]
-[Seed cli][seed-cli]
-[Structure][structure]
+[Seed cli][db-seed-cli]
+[Structure][database-structure]

mddocs/docs/en/reference/http2kafka/configuration/debug.md

@@ -38,7 +38,7 @@ File ".../site-packages/uvicorn/middleware/proxy_headers.py", line 84, in __call
 
 ## Print debug logs on backend
 
-See [`configuration-server-logging`](configuration-server-logging), but replace log level `INFO` with `DEBUG`.
+See [`configuration-server-logging`][configuration-server-logging], but replace log level `INFO` with `DEBUG`.
 
 ## Fill up `X-Request-ID` header on backend