Update src/content/developers/docs/smart-contracts/testing/index.md

Author: minimalsm

src/content/developers/docs/smart-contracts/testing/index.md

@@ -121,7 +121,7 @@ Bug bounty programs often attract a broad class of ethical hackers and independe
 
 ## Testing vs. formal verification {#testing-vs-formal-verification}
 
-While testing is useful for confirming that a contract returns the expected results for some data inputs, it cannot conclusively prove the same for inputs not used during tests. Testing a smart contract cannot guarantee "functional correctness", meaning it cannot show that a program behaves as required for *all* sets of input values and conditions. 
+While testing helps confirm that a contract returns the expected results for some data inputs, it cannot conclusively prove the same for inputs not used during tests. Testing a smart contract cannot guarantee "functional correctness", meaning it cannot show that a program behaves as required for *all* sets of input values and conditions.  
 
 As such, developers are encouraged to incorporate **formal verification** into their approach for assessing the correctness of smart contracts. Formal verification uses [formal methods](https://www.brookings.edu/techstream/formal-methods-as-a-path-toward-better-cybersecurity/)—mathematically rigorous techniques for specifying and verifying software.