style: format code and documentation files

Author: SeddikBellamine

src/get-started/overview/glossary.md

@@ -450,4 +450,3 @@ mainchain.
 
 See [Sidechain](#sidechain), [Bellecour Sidechain](#bellecour-sidechain) or
 [Minting](#minting) for more information.
-

src/protocol/proof-of-contribution.md

@@ -75,7 +75,8 @@ consensus on a given result. Two blog articles detail its logic:
 
 The
 [nominal workflow](https://github.com/iExecBlockchainComputing/iexec-doc/raw/master/techreport/nominalworkflow-ODB.png)
-is also available in the [technical report section](/get-started/overview/glossary)
+is also available in the
+[technical report section](/get-started/overview/glossary)
 
 Below are the details of the implementations:
 

src/protocol/tee/intel-sgx.md

@@ -15,9 +15,9 @@ decentralized cloud.
 
 ## What is Intel SGX?
 
-[Intel® SGX](https://software.intel.com/en-us/sgx) creates a special secure zone
-in memory called an "enclave" - think of it as a vault that only the CPU can
-access. Neither the operating system nor any other software can see what's
+[Intel® SGX](https://software.intel.com/en-us/sgx) creates a special secure
+zone in memory called an "enclave" - think of it as a vault that only the CPU
+can access. Neither the operating system nor any other software can see what's
 happening inside this protected area. Your code and data are completely private
 and secure.
 
@@ -66,10 +66,11 @@ graph TB
 
 ### SGX limitations
 
-With native Intel® SGX technology, the OS is not a part of the Trusted Computing
-Base (TCB), hence system calls and kernel services are not available from an
-Intel® SGX enclave. This can be limiting as the application will not be able to
-use file system and sockets directly from the code running inside the enclave.
+With native Intel® SGX technology, the OS is not a part of the Trusted
+Computing Base (TCB), hence system calls and kernel services are not available
+from an Intel® SGX enclave. This can be limiting as the application will not be
+able to use file system and sockets directly from the code running inside the
+enclave.
 
 ### iExec's SGX infrastructure