From 9d07e5eb63d144eced10f6286c176745e46fef77 Mon Sep 17 00:00:00 2001
From: Manjula Sridhar <manjula.sridhar@gmail.com>
Date: Thu, 28 Feb 2019 13:22:38 +0530
Subject: [PATCH] Update reentrancy.html

---
 findings/reentrancy.html | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/findings/reentrancy.html b/findings/reentrancy.html
index 20d4d57..dcd0a30 100644
--- a/findings/reentrancy.html
+++ b/findings/reentrancy.html
@@ -12,7 +12,8 @@ <h5>also known as or related to <strong>race to empty</strong>, <strong>recursiv
 			<footer class="blockquote-footer">Phil Daian</cite></footer>
 		</p>
 		<hr>
-		<p>The Reentrancy attack, probably the most famous Ethereum vulnerability, surprised everyone when discovered for the first time. It was first unveiled during a multimillion dollar heist which led to a hard fork of Ethereum. Reentrancy occurs when external contract calls are allowed to make new calls to the calling contract before the initial execution is complete. For a function, this means that the contract state may change in the middle of its execution as a result of a call to an untrusted contract or the use of a low level function with an external address.</p>
+		<p> Reentrancy is a vulnerability which allows an execution of a function before the previous execution of it is complete. Renatrancy is a concept in many programming languages which refers to a code that can be executed safely before the previous execution is complete. Basically this function can be executed parallelly without causing harm to the overall state ahcine of the program.
+		 The Reentrancy attack, probably the most famous Ethereum vulnerability, surprised everyone when discovered for the first time. It was first unveiled during a multimillion dollar heist which led to a hard fork of Ethereum. Reentrancy occurs when external contract calls are allowed to make new calls to the calling contract before the initial execution is complete. For a function, this means that the contract state may change in the middle of its execution as a result of a call to an untrusted contract or the use of a low level function with an external address.</p>
 		<p><strong>Loss</strong>: estimated at 3.5M ETH (~50M USD at the time)</p>
 		<p><strong>Timeline of discovery</strong>:</p>
 
@@ -77,4 +78,4 @@ <h5>also known as or related to <strong>race to empty</strong>, <strong>recursiv
 			<li><a href="https://blog.citymayor.co/posts/how-someone-tried-to-exploit-a-flaw-in-our-smart-contract-and-steal-all-of-its-ether/" target="_blank">How Someone Tried to Exploit a Flaw in Our Smart Contract and Steal All of Its Ether</a></li>
 		</ul>
 	</div>
-</article>
\ No newline at end of file
+</article>