fixes to get hero working

collections/companies/threefold_dmcc.md

@@ -49,5 +49,5 @@ Please see below the ThreeFold DMCC license:
 ![](img/threefold_dmcc_license_certificate.jpg)
 
 
-!!wiki.def alias:threefold_fzc,tf_fzc,threefold_dubai,tf_dubai
+!!wiki.def alias:threefold_dmcc,tf_dmcc
 

collections/faq/faq.md

@@ -1494,7 +1494,7 @@ You can read this [documentation](farmers@@5_set_bios_uefi) to learn more about
 
 ### For my 3Node server, do I need to enable virtualization in BIOS or UEFI?
 
-Yes, you should enable virtualization. On Intel, it is denoted as *CPU virtualization* and on ASUS, it is denoted as *SVM*. Make sure virtualization is enabled and look for the precise terms in your specific BIOS/UEFI.
+Yes, you should enable virtualization. On Intel, it is denoted as _CPU virtualization_ and on ASUS, it is denoted as *SVM*. Make sure virtualization is enabled and look for the precise terms in your specific BIOS/UEFI.
 
 
 
@@ -1780,7 +1780,7 @@ Short answer: no. Long answer: [click here](https://forum.threefold.io/t/does-it
 
 ### My 3Node lost power momentarily and I had to power it back on manually. Is there a better way to proceed?
 
-In your BIOS, go in *Security Settings* and choose *Last* for *AC Power Recovery*. If you want, set a delay between 60 and 240 seconds. This will ensure your 3Node does not power on and off frantically if your power flickers on and off, thus potentially damaging the unit. On other BIOS, it's *After Power Loss*, and you should choose *Previous State*.
+In your BIOS, go in *Security Settings* and choose *Last* for _AC Power Recovery_. If you want, set a delay between 60 and 240 seconds. This will ensure your 3Node does not power on and off frantically if your power flickers on and off, thus potentially damaging the unit. On other BIOS, it's *After Power Loss*, and you should choose *Previous State*.
 
 *Depending on your 3Node, the parameter might have a different name.
 

collections/farmers/3node_building/gpu_farming.md

@@ -1,6 +1,6 @@
 <h1>GPU Farming</h1>
 
-Welcome to the *GPU Farming* section of the ThreeFold Manual! 
+Welcome to the _GPU Farming_ section of the ThreeFold Manual! 
 
 In this guide, we delve into the realm of GPU farming, shedding light on the significance of Graphics Processing Units (GPUs) and how they can be seamlessly integrated into the ThreeFold ecosystem.
 

collections/farmers/complete_diy_guides/3node_diy_desktop/3node_diy_desktop.md

@@ -289,13 +289,13 @@ As a general advice, you can Load Defaults (Settings) on your BIOS, then make su
 
 * Choose the correct combination of BIOS/UEFI and bootstrap image on [https://bootstrap.grid.tf/](https://bootstrap.grid.tf/)
   * Newer system will use UEFI --> the Dell Optiplex 7020 uses UEFI
-    * Bootstrap image: *EFI IMG* and *EFI FILE*
+    * Bootstrap image: _EFI IMG_ and _EFI FILE_
   * Older system will use Legacy BIOS
     * Bootstrap image: *ISO* and *USB*
 * Set *Multi-Processor* and *Hyperthreading* at Enabled
   * Sometimes, it will be written *Virtual Cores*, or *Logical Cores*. 
 * Set *Virtualization* at Enabled
-  * On Intel, it is denoted as *CPU virtualization* and on ASUS, it is denoted as *SVM*. 
+  * On Intel, it is denoted as _CPU virtualization_ and on ASUS, it is denoted as *SVM*. 
   * Make sure virtualization is enabled and look for the precise terms in your specific BIOS/UEFI.
 * Enable *Network Stack* (sometimes called *Network Boot*)
 * Set *AC Recovery* at *Last Power State*

docs/hero_create_mdbook.md

@@ -94,7 +94,7 @@ Hero uses three main directories to build an mdbook `books`, `collections` and `
     - `context.md` sets the proper configuration for the mdbook using the command `configure`
       - This file is the same throughout all the `info_tfgrid` repository.
         ```
-        !!books.configure
+        \!!books.configure
             buildroot:'~/hero/var/mdbuild'
             publishroot:'~/hero/www/info'
             install:true
@@ -107,11 +107,11 @@ Hero uses three main directories to build an mdbook `books`, `collections` and `
       - It also point the URLs where the markdown files are located 
         - In the directory `collections` as we've seen above
       ```
-      !!book.generate name:'new_mdbook' title:'New mdbook'
+      \!!book.generate name:'new_mdbook' title:'New mdbook'
               url:'https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/heroscript/new_mdbook'
 
 
-      !!doctree.add
+      \!!doctree.add
           url:'https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/collections/new_mdbook'
 
       ```

docs/hero_mdbook_fullvm.md

@@ -163,7 +163,7 @@ There are some distinctions between mdbook and hero mdbook. This is subject to c
 - hero mdbook cannot use parentheses in tables of contents (e.g. in SUMMARY.md)
 - hero mdbook uses the following include template:
     ```
-    !!wiki.include page:'collection_name:file_name.md'
+    \!!wiki.include page:'collection_name:file_name.md'
     ```
 - hero mdbook cannot parse codes with tabs or spaces
 - list contents are parsed as paragraphs (e.g. defs, comments, text, links), they can't contain code blocks

heroscript/sshkey/sshkey.md

@@ -1,6 +1,6 @@
 
 ```js
-!!sshagent.key_define
+\!!sshagent.key_define
     name:'books'
     privkey:'
         -----BEGIN OPENSSH PRIVATE KEY-----

heroscript/sysadmins/context.md

@@ -1,7 +1,7 @@
 
 ```js
 
-!!books.configure
+\!!books.configure
 	buildroot:'~/hero/var/mdbuild'
 	publishroot:'~/hero/www/info'
 	install:true