Fix/format bgd phase3 (#278)

* fix line break

* Fix typo

* fix lint

* Remove spacing

src/20240325_AaveV3Ethereum_AaveBGDPhase3/AaveBGDPhase3.md

@@ -17,8 +17,6 @@ After successful collaboration with the Aave DAO on the previous BGD Labs <> Aav
 
 This proposal includes 2 scopes:
 
-&nspb;
-
 ### SCOPE 1. Aave technical maintenance, improvements, security coordination and tech advisory to the DAO
 
 This scope is the continuist component historically performed by BGD for the DAO, and will be composed of the following items:
@@ -45,8 +43,6 @@ This scope is the continuist component historically performed by BGD for the DAO
 - Generally advise other contributors, whenever feedback from an entity expert on the Aave protocol is required. This includes but is not limited to contributors on the risk, treasury, security reviews and miscellaneous fields.
 - Review governance proposals on pre-onchain stage, not as a full security audit, but in order to verify that we don’t see any integration problem with Aave’s smart contracts and good practises.
 
-&nspb;
-
 **What is NOT part of the scope**
 
 - We are a technical provider of the community, we don’t do any type of business development and/or growth, that should be responsibility of other parties.
@@ -57,8 +53,6 @@ This scope is the continuist component historically performed by BGD for the DAO
 - We are not running services on behalf of the DAO, we design them to be ran in a decentralised manner, or by parties with the proper role to do so.
   Any tool we decide to run on our infrastructure (e.g. hosting of one instance of the Aave Governance v3 interface) is our own decision, outside of the scope of engagement.
 
-&nspb;
-
 ---
 
 _Scope 1. Aave technical maintenance, improvements, security coordination and tech advisory to the DAO_
@@ -69,8 +63,6 @@ _Scope 1. Aave technical maintenance, improvements, security coordination and te
 
 ---
 
-&nspb;
-
 ### SCOPE 2. Aave Safety Module - Code A
 
 As commented before, we believe now the Aave DAO is in a really solid stage of their current systems, quite future-proof and ready to scale:
@@ -82,8 +74,6 @@ As commented before, we believe now the Aave DAO is in a really solid stage of t
 
 More in the line of innovative projects like Aave Governance v3, we propose to create a completely new system in an Aave component which requires improvement: the Aave Safety Module.
 
-&nspb;
-
 **Aave Safety Module: Code A**
 
 Safety Module Code A is the major project on the innovation side of this scope, but different to previous cases, our proposed approach is different: at the moment, we will not disclose a detailed description of it, as we think this is the right strategic approach for the DAO.
@@ -100,9 +90,6 @@ However, we can say the following about Code A:
 
 We are aware this requires some trust by the community on our research and execution capabilities (which is reflected on the payment schedule), but considering that the main beneficiary will be explicitly the DAO and our history of services, we think it is acceptable.
 
-&nspb;
-&nspb;
-
 ---
 
 _Scope 2. Safety Module Code A_
@@ -117,8 +104,6 @@ However, delivery and communications will definitely be iterative, with extensiv
 
 ---
 
-&nspb;
-
 ### Technical specification
 
 The proposal payload sets up the payment schedule for the 2 scopes, interacting with the Aave Ethereum Collector for the stablecoins components and the AAVE Ecosystem Collector for the AAVE ones:
@@ -131,9 +116,6 @@ The proposal payload sets up the payment schedule for the 2 scopes, interacting
 - Creation of a 1'140'000 aUSDC v3 Ethereum 4-months deferred payment; 60% of the 1'900'000 total stablecoins component in Scope 2.
 - Creation of a 4'500 AAVE 4-months deferred payment; 60% of the 7'500 total AAVE component in Scope 2.
 
-&nspb;
-&nspb;
-
 _Disclaimer_
 
 - If approved, this governance proposal will act as a binding agreement between BGD Labs Technology and the Aave DAO for the previously defined scope.