s

collections/tech/zos/benefits/zero_chance.md

@@ -1,5 +1,5 @@
     
-## Deterministic Deployment
+## Zero-Chance = Deterministic Deployment
 
 ![](img/smartcontract_deploy.png)  
     
@@ -16,10 +16,6 @@ Metadata is exposed. The system sees the full tree of the image, but data itself
     It is a static agreement between farmer and user about deployment of an IT workload 
   - no dynamic behavior for deployment at runtime
   - no process can start unless the files are 100% described on flist level
-    
-
-
-
 
 ### There are multiple ways to create an flist: 
 

collections/tech/zos/benefits/zos_zero_tech.md

@@ -1,4 +1,4 @@
-# ZOS Protect
+# Zero-Tech
 
 - The operating system of the 3node (Zero-OS) is made to exist in environments without the presence of technical knowhow. 3nodes are made to exist everywhere where network meet a power socket. The OS does not have a login shell and does not allow people to log in with physical access to a keyboard and screen nor does it allows logins over the network. There is no way the 3node accepts user initiated login attempts.
 - For certified capacity a group of known strategic vendors are able to lock the [BIOS](https://en.wikipedia.org/wiki/BIOS) of their server range and make sure no-one but them can unlock and change features present in the BIOS. Some vendors have an even higher degree of security and can store private keys in chips in side the computer to provider unique identification based on private keys or have mechanisms to check wether the server has been opened / tampered with in the transportation from the factory / vendor to the Farmer. All of this leads to maximum protection on the hardware level.