deletions | additions       diff --git a/Overview_A_control_flow_hijacking__.md b/Overview_A_control_flow_hijacking__.md  index c440cba..6fdc640 100644  --- a/Overview_A_control_flow_hijacking__.md  +++ b/Overview_A_control_flow_hijacking__.md 
...
A control-flow hijacking attack is considered successful when malicious code begins executing. A meaningful attack often requires the execution of system calls \cite{Szekeres_2013}. Pledges can be applied to mitigate the effectiveness of attacks through security vulnerabilities by reducing the available resources, i.e. types of system calls, to the attacker.  Security vulnerability attacks can possibly occur at any buffer through a buffer overflow. The ideal location to add a pledge call is directly after a system call in order to disclude its use so it can't cannot  be used by any security vulnerability attack following that system call. However, if there is a subsequent use of that same system call later in the execution of the program, the pledge should only be placed after that last execution. If the pledge was placed after the first execution of a system call, the normal execution of the program would fail on any subsequent execution of the same system call.  Loops and recursion must be known during the analysis so that any system call within a loop or recursive function is not removed from use by a pledge before the loop or recursive function is finished executing. Therefore, an amount of context needs to be known about whether or not the program is in a loop or recursive function.