Update 5. Writing Secure Smart Contracts.md

Author: gupta19esha

Diff for: Start Building on Core/4. Interface and ERC20 standard/5. Writing Secure Smart Contracts.md

@@ -83,7 +83,7 @@ function reveal(uint256 _value, bytes32 _salt) public {
 
 ## Best Practices for Secure Smart Contract Development
 
-![img](https://github.com/0xmetaschool/Learning-Projects/blob/main/assests_for_all/Core%20C2%20assets%20-%20Start%20Building%20on%20Core/Core%20C2%20L13%20Image%201.png?raw=true)
+![img](https://github.com/0xmetaschool/Learning-Projects/blob/main/assests_for_all/Core%20C2%20assets%20-%20Start%20Building%20on%20Core/Core%20C2%20L13%20Image%201.webp?raw=true)
 
 1. **Code Reviews and Audits**
 Think of it like getting a second opinion from a doctor. Another set of eyes can catch things you might have missed.
@@ -104,7 +104,7 @@ You should use formal verification tools and write comprehensive tests to simula
 
 ## Tools and Techniques
 
-![img](https://github.com/0xmetaschool/Learning-Projects/blob/main/assests_for_all/Core%20C2%20assets%20-%20Start%20Building%20on%20Core/Core%20C2%20L13%20Image%202.png?raw=true)
+![img](https://github.com/0xmetaschool/Learning-Projects/blob/main/assests_for_all/Core%20C2%20assets%20-%20Start%20Building%20on%20Core/Core%20C2%20L13%20Image%202.webp?raw=true)
 
 1. **Static Analysis Tools (e.g., [MythX](https://mythx.io/), [Slither](https://github.com/crytic/slither))**
 These tools are like spell checkers for your code, automatically finding errors and vulnerabilities. You should regularly run static analysis tools on your smart contracts to catch potential issues early.