manual, set internal collections to filename.md template

collections/system_administrators/terraform/resources/terraform_k8s.md

@@ -199,7 +199,7 @@ We will be mainly interested in the master node public ip `computed IP` and the
 
 ## More Info
 
-A complete list of k8s resource parameters can be found [here](https://github.com/threefoldtech/terraform-provider-grid/blob/development/docs/resources/kubernetes.md).
+A complete list of k8s resource parameters can be found [here](kubernetes.md).
 
 ## Demo Video 
 

collections/system_administrators/terraform/resources/terraform_qsfs.md

@@ -2,8 +2,8 @@
 
 <h2> Table of Contents </h2>
 
-- [QSFS on Micro VM](./terraform_qsfs_on_microvm.md)
-- [QSFS on Full VM](./terraform_qsfs_on_full_vm.md)
+- [QSFS on Micro VM](terraform_qsfs_on_microvm.md)
+- [QSFS on Full VM](terraform_qsfs_on_full_vm.md)
 
 ***
 

collections/system_administrators/terraform/resources/terraform_qsfs_on_full_vm.md

@@ -23,7 +23,7 @@ The main goal of this guide is to show you all the necessary steps to deploy a F
 
 ## Prerequisites
 
-- [Install Terraform](../terraform_install.md)
+- [Install Terraform](terraform_install.md)
 
 You need to download and install properly Terraform. Simply follow the documentation depending on your operating system (Linux, MAC and Windows).
 
@@ -36,7 +36,7 @@ Deploying a FullVM is a bit different than deploying a MicroVM, let take a look
 - QSFS disk is based on `virtiofs`, and you can't use QSFS disk as the first mount in a FullVM, instead you need a regular disk.
 - Any extra disks/mounts will be available on the vm but unlike mounts on MicroVMs, extra disks won't be mounted automatically. you will need to mount it manually after the deployment.
 
-Let modify the qsfs-on-microVM [example](./terraform_qsfs_on_microvm.md) to deploy a QSFS on FullVM this time:
+Let modify the qsfs-on-microVM [example](terraform_qsfs_on_microvm.md) to deploy a QSFS on FullVM this time:
 
 - Inside the `grid_deployment` resource we will need to add a disk for the vm root fs.
 

collections/system_administrators/terraform/resources/terraform_qsfs_on_microvm.md

@@ -23,7 +23,7 @@ In this ThreeFold Guide, we will learn how to deploy a Quantum Safe File System
 
 In this guide, we will be using Terraform to deploy a QSFS workload on a micro VM that runs on the TFGrid. Make sure to have the latest Terraform version.
 
-- [Install Terraform](../terraform_install.md)
+- [Install Terraform](terraform_install.md)
 
 
 

collections/system_administrators/terraform/resources/terraform_resources_readme.md

@@ -2,12 +2,12 @@
 
 <h2> Table of Contents </h2>
 
-- [Using Scheduler](./terraform_scheduler.md)
+- [Using Scheduler](terraform_scheduler.md)
 - [Virtual Machine](./terraform_vm.html)
 - [Web Gateway](./terraform_vm_gateway.html)
 - [Kubernetes Cluster](./terraform_k8s.html)
 - [ZDB](./terraform_zdb.html)
-- [Quantum Safe Filesystem](./terraform_qsfs.md)
-  - [QSFS on Micro VM](./terraform_qsfs_on_microvm.md)
-  - [QSFS on Full VM](./terraform_qsfs_on_full_vm.md)
+- [Quantum Safe Filesystem](terraform_qsfs.md)
+  - [QSFS on Micro VM](terraform_qsfs_on_microvm.md)
+  - [QSFS on Full VM](terraform_qsfs_on_full_vm.md)
 - [CapRover](./terraform_caprover.html)

collections/system_administrators/terraform/resources/terraform_vm.md

@@ -171,7 +171,7 @@ It's bit long for sure but let's try to dissect it a bit
 
 ## Which flists to use
 
-see [list of flists](../../../developers/flist/grid3_supported_flists.md)
+see [list of flists](grid3_supported_flists.md)
 
 ## Remark multiple VMs
 
@@ -204,7 +204,7 @@ So to add a VM
 ```
 
 - We give it a name within our deployment `vm1`
-- `flist` is used to define the flist to run within the VM. Check the [list of flists](../../../developers/flist/grid3_supported_flists.md)
+- `flist` is used to define the flist to run within the VM. Check the [list of flists](grid3_supported_flists.md)
 - `cpu` and `memory` are used to define the cpu and memory
 - `publicip` is usued to define if it requires a public IP or not
 - `entrypoint` is used define the entrypoint which in most of the cases in `/sbin/zinit init`, but in case of flists based on vms it can be specific to each flist

collections/system_administrators/terraform/resources/terraform_vm_gateway.md

@@ -15,7 +15,7 @@ In this section, we provide the basic information for a VM web gateway using Ter
 
 ## Expose with Prefix
 
-A complete list of gateway name workload parameters can be found [here](https://github.com/threefoldtech/terraform-provider-grid/blob/development/docs/resources/name_proxy.md).
+A complete list of gateway name workload parameters can be found [here](name_proxy.md).
 
 ```
  terraform {
@@ -93,7 +93,7 @@ Here
 
 ## Expose with Full Domain
 
-A complete list of gateway fqdn workload parameters can be found [here](https://github.com/threefoldtech/terraform-provider-grid/blob/development/docs/resources/fqdn_proxy.md).
+A complete list of gateway fqdn workload parameters can be found [here](fqdn_proxy.md).
 
 it is more like the above example the only difference is you need to create an `A record` on your name provider for `remote.omar.grid.tf` to gateway node `7` IPv4.