update - replace 'exploit' by 'vulnerability'

Author: tjcloa

SIP-0044.md

@@ -13,7 +13,7 @@ Created: 2022-04-07
 
 The Staking contract has been paused to prevent malicious use of the information disclosed by this SIP.
 
-If approved, this proposal will upgrade the Staking contract to an implementation that prevents a critical exploit.
+If approved, this proposal will upgrade the Staking contract to an implementation that prevents a critical vulnerability.
 
 The chosen mitigation strategy restricts the ability for an attacker to creatively combine calls in a single block or create loops which could potentially be harmful, while not hindering the normal usage and composability of the contract.
 
@@ -26,7 +26,7 @@ Fixing the underlying causes is a large undertaking, requiring a partial rewrite
 
 ## Details
 
-In order to close the exploit and its various variants, we have opted for a mitigation strategy that thwarts them by forbidding a number of scenarios which we think have no real practical use for the users, while being necessary to enable the exploit. Namely, if this SIP is approved, it will forbid a number of actions from happening **in the same block** as a call to the `stake(...)` function, for the same `lockDate` timestamp:
+In order to close the vulnerability and its various variants, we have opted for a mitigation strategy that thwarts them by forbidding a number of scenarios which we think have no real practical use for the users, while being necessary to enable the exploit. Namely, if this SIP is approved, it will forbid a number of actions from happening **in the same block** as a call to the `stake(...)` function, for the same `lockDate` timestamp:
 - extend staking duration,
 - delegate voting power (which can still be done directly in the `stake(...)` function call as a parameter),
 - withdraw,