zos

collections/developers/internals/zos/internals/internals.md

@@ -74,14 +74,14 @@ Modules of zos are completely internal. There is no way for an external user to
 
 Here is a list of the major ZOS modules.
 
-- [Identity](identity/index.md)
-- [Node](node/index.md)
-- [Storage](storage/index.md)
-- [Network](network/index.md)
-- [Flist](flist/index.md)
-- [Container](container/index.md)
-- [VM](vmd/index.md)
-- [Provision](provision/index.md)
+- [Identity](identity_readme.md)
+- [Node](node_readme.md)
+- [Storage](storage_readme.md)
+- [Network](network_readme.md)
+- [Flist](flist_readme.md)
+- [Container](container_readme.md)
+- [VM](vmd_readme.md)
+- [Provision](provision_readme.md)
 
 ## Capacity
 

collections/developers/internals/zos/internals/network/introduction.md

@@ -27,7 +27,7 @@ Once initialized, with the network daemon running (a process that will handle al
 
 ## Networkd functionality
 
-The network daemon is in itself responsible for a few tasks, and working together with the [provision daemon](../provision) it mainly sets up the local infrastructure to get the user network resources, together with the wireguard configurations for the user's mesh network.
+The network daemon is in itself responsible for a few tasks, and working together with the [provision daemon](provision_readme.md) it mainly sets up the local infrastructure to get the user network resources, together with the wireguard configurations for the user's mesh network.
 
 The Wireguard mesh is an overlay network. That means that traffic of that network is encrypted and encapsulated in a new traffic frame that the gets transferred over the underlay network, here in essence the network that has been set up during boot of the node.