manual, set internal collections to filename.md template

collections/developers/internals/zos/development/readme.md

@@ -1,6 +1,6 @@
 Development
 ===========
 
-* [Quick start](./quickstart.md)
-* [Testing](./testing.md)
-* [Binary packages](./packages.md)
+* [Quick start](quickstart.md)
+* [Testing](testing.md)
+* [Binary packages](packages.md)

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

@@ -85,4 +85,4 @@ Here is a list of the major ZOS modules.
 
 ## Capacity
 
-In [this document](./capacity.md), you can find detail description of how ZOS does capacity planning.
+In [this document](capacity.md), you can find detail description of how ZOS does capacity planning.

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

@@ -2,7 +2,7 @@
 
 <h2> Table of Contents </h2>
 
-- [Introduction to networkd](./introduction.md)
-- [Vocabulary Definitions](./definitions.md)
-- [Wireguard Mesh Details](./mesh.md)
-- [Farm Network Setup](./setup_farm_network.md)
+- [Introduction to networkd](introduction.md)
+- [Vocabulary Definitions](definitions.md)
+- [Wireguard Mesh Details](mesh.md)
+- [Farm Network Setup](setup_farm_network.md)

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

@@ -180,7 +180,7 @@ type Workload struct {
 ### API
 Node is always connected to the RMB network with the node `twin`. Means the node is always reachable over RMB with the node `twin-id` as an address.
 
-The [node client](https://github.com/threefoldtech/zos/blob/main/client/node.go) should have a complete list of all available functions. documentations of the API can be found [here](./api.md)
+The [node client](https://github.com/threefoldtech/zos/blob/main/client/node.go) should have a complete list of all available functions. documentations of the API can be found [here](api.md)
 
 ## Raid Controller Configuration
 

collections/developers/internals/zos/manual/workload_types.md

@@ -66,7 +66,7 @@ For more details on all parameters needed to run a `zmachine` please refer to [`
 
 #### Building your `flist`
 
-Please refer to [this document](./manual.md) here about how to build an compatible `zmachine flist`
+Please refer to [this document](manual.md) here about how to build an compatible `zmachine flist`
 
 ### `zlogs` type
 

collections/developers/internals/zos/manual/zmachine/readme.md

@@ -10,4 +10,4 @@
 For more details on all parameters needed to run a `zmachine` please refer to [`zmachine` data](https://github.com/threefoldtech/zos/blob/main/pkg/gridtypes/zos/zmachine.go)
 
 # Building your `flist`.
-Please refer to [this document](../manual.md) here about how to build an compatible `zmachine flist`
+Please refer to [this document](manual.md) here about how to build an compatible `zmachine flist`

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

@@ -80,10 +80,10 @@ Notes:
 
 ## Registered Tests
 
-- [Public IP Validation](./publicips.md)
-- [CPUBenchmark](./cpubench.md)
-- [IPerf](./iperf.md)
-- [Health Check](./healthcheck.md)
+- [Public IP Validation](publicips.md)
+- [CPUBenchmark](cpubench.md)
+- [IPerf](iperf.md)
+- [Health Check](healthcheck.md)
 
 ## Test Suite
 

collections/developers/internals/zos/release/readme.md

@@ -3,7 +3,7 @@
 We use a simple pipeline release workflow. Building and file distribution are made using GitHub Actions.
 Usable files are available on the [Zero-OS Hub](https://hub.grid.tf/tf-zos).
 
-This pipeline is made to match the 3 different type of running mode of 0-OS. For more information head to the [upgrade documentation](../identity/upgrade.md).
+This pipeline is made to match the 3 different type of running mode of 0-OS. For more information head to the [upgrade documentation](upgrade.md).
 
 ## Development build