docs: fix unresolved file references (#13488)

1 files changed, 3 insertions, 3 deletions

diff --git a/database/README.md b/database/README.md
index 119e21336b..1453f9b39b 100644
--- a/database/README.md
+++ b/database/README.md
@@ -38,13 +38,13 @@ The default mode `[db].mode = dbengine` has been designed to scale for longer re
 for parent Agents in the _Parent - Child_ setups
 
 The other available database modes are designed to minimize resource utilization and should only be considered on
-[Parent - Child](/docs/metrics-storage-management/how-streaming-works) setups at the children side and only when the
+[Parent - Child](/docs/metrics-storage-management/how-streaming-works.mdx) setups at the children side and only when the
 resource constraints are very strict.
 
 So,
 
 - On a single node setup, use `[db].mode = dbengine`.
-- On a [Parent - Child](/docs/metrics-storage-management/how-streaming-works) setup, use `[db].mode = dbengine` on the
+- On a [Parent - Child](/docs/metrics-storage-management/how-streaming-works.mdx) setup, use `[db].mode = dbengine` on the
   parent to increase retention, a more resource efficient mode like, `dbengine` with light retention settings, and
   `save`, `ram` or `none` modes for the children to minimize resource utilization.
 
@@ -64,7 +64,7 @@ Metrics retention is controlled only by the disk space allocated to storing metr
 CPU required by the agent to query longer timeframes.
 
 Since Netdata Agents usually run on the edge, on production systems, Netdata Agent **parents** should be considered.
-When having a [**parent - child**](/docs/metrics-storage-management/how-streaming-works.md) setup, the child (the
+When having a [**parent - child**](/docs/metrics-storage-management/how-streaming-works.mdx) setup, the child (the
 Netdata Agent running on a production system) delegates all of its functions, including longer metrics retention and
 querying, to the parent node that can dedicate more resources to this task. A single Netdata Agent parent can centralize
 multiple children Netdata Agents (dozens, hundreds, or even thousands depending on its available resources).