Apply React format in style

docs/essif-lab-functional-architecture.md

@@ -304,7 +304,7 @@ This chapter explains at a high level how electronic business transactions are b
 
 ### 5.1.  Overview
 
-<img src="https://essif-lab.pages.grnet.gr/framework//images/high-level-trx-overview.png" alt="eSSIF-Lab - high level trx overview" style="zoom:40%;"/>The adjacent figure shows how a transaction is conducted at the highest abstraction level. One party, called the ‘Requester’, sends a request for a product or service to another party (that we will call the ‘Provider’). Then, they start to negotiate a ‘transaction agreement’, which means that they exchange data through various channels for the purpose of establishing the details of the product/service to be provided and the compensation, data needed to mitigate transaction risks, etc., all of which is necessary for the parties to (individually/subjectively) decide whether or not to commit to the transaction. Section 3.2 provides more detail about this phase.
+<img src="https://essif-lab.pages.grnet.gr/framework//images/high-level-trx-overview.png" alt="eSSIF-Lab - high level trx overview" style={{"zoom":"40%"}}/>The adjacent figure shows how a transaction is conducted at the highest abstraction level. One party, called the ‘Requester’, sends a request for a product or service to another party (that we will call the ‘Provider’). Then, they start to negotiate a ‘transaction agreement’, which means that they exchange data through various channels for the purpose of establishing the details of the product/service to be provided and the compensation, data needed to mitigate transaction risks, etc., all of which is necessary for the parties to (individually/subjectively) decide whether or not to commit to the transaction. Section 3.2 provides more detail about this phase.
 
 After commitment, the producer works to provide the product or service, and the requester arranges the compensation. This phase is entirely up to the business, and hence out of scope of this document.