fix includes syntax

_archive/technology/qsss/interfaces_usecases/nft_storage.md

@@ -94,4 +94,4 @@ The object (video,image) can easily be embedded in any website or other represen
 
 
 
-!!!def alias:nft_storage,nft_storage_system
+!!def alias:nft_storage,nft_storage_system

_archive/technology/qsss/interfaces_usecases/s3_interface.md

@@ -12,4 +12,4 @@ A typical setup would look like:
 
 > TODO: link to manual on cloud how to deploy minio, using helm (3.0 release)
 
-!!!def alias:s3_storage
+!!def alias:s3_storage

_archive/technology/qsss/product/file_system/qss_filesystem.md

@@ -34,6 +34,6 @@ By using our filesystem inside a Virtual Machine or Kubernetes the TFGrid user c
 
 Any storage workload can be deployed on top of the zstor.
 
-!!!def alias:quantumsafe_filesystem,planetary_fs,planet_fs,quantumsafe_file_system,zstor,qsfs
+!!def alias:quantumsafe_filesystem,planetary_fs,planet_fs,quantumsafe_file_system,zstor,qsfs
 
-!!!include:qsss_toc
+!!wiki.include page:qsss_toc

_archive/technology/qsss/product/qss_algorithm.md

@@ -77,6 +77,6 @@ If someone now wants to download the data the first 10 locations who answer fast
 The overhead here is much more compared to previous example but stil order of magnitude lower compared to other cdn systems.
 
 
-!!!def alias:quantumsafe_storage_algo,quantumsafe_storage_algorithm,space_algo,space_algorithm,quantum_safe_storage_algo,qs_algo,qs_codec
+!!def alias:quantumsafe_storage_algo,quantumsafe_storage_algorithm,space_algo,space_algorithm,quantum_safe_storage_algo,qs_algo,qs_codec
 
-!!!include:qsss_toc
+!!wiki.include page:qsss_toc

_archive/technology/qsss/product/qss_datarot.md

@@ -5,4 +5,4 @@ The storage system provided by ThreeFold intercepts this silent data corruption,
 
 > see also https://en.wikipedia.org/wiki/Data_degradation
 
-!!!def alias:bitrot,datarot
+!!def alias:bitrot,datarot

_archive/technology/qsss/product/qss_zero_knowledge_proof.md

@@ -8,4 +8,4 @@ The quantum save storage system is zero knowledge proof compliant. The storage s
 
 The zero proof knowledge compliancy comes from the fact the all the physical storage nodes (3nodes) can proof that they store a valid part of what data the quantum safe storage engine (QSSE) has stored on multiple independent devices.  The QSSE can validate that all the QSSE storage devices have a valid part of the original information.  The storage devices however have no idea what the original stored data is as they only have a part (description) of the origina data and have no access to the original data part or the complete origal data objects.
 
-!!!def
+!!def

_archive/technology/qsss/qsss.md

@@ -1,2 +1,2 @@
 
-!!!include:qsss_home
+!!wiki.include page:qsss_home

_archive/technology/qsss/qsss2_home.md

@@ -4,7 +4,7 @@
 
 Imagine a storage system with the following benefits
 
-!!!include:qss_benefits_
+!!wiki.include page:qss_benefits_
 
 > This is not a dream but does exist and is the underpinning of the TFGrid.
 
@@ -13,9 +13,9 @@ Our storage architecture follows the true peer-to-peer design of the TF grid. An
 Peer-to-peer provides the unique proposition of selecting storage providers that match your application and service of business criteria. For example, you might be looking to store data for your application in a certain geographic area (for governance and compliance) reasons. Also, you might want to use different "storage policies" for different types of data. Examples are live versus archived data. All of these uses cases are possible with this storage architecture and could be built by using the same building blocks produced by farmers and consumed by developers or end-users.
 
 
-!!!include:qsss_toc
+!!wiki.include page:qsss_toc
 
-!!!def alias:qsss,quantum_safe_storage_system
+!!def alias:qsss,quantum_safe_storage_system