Fixed typos in README.md and FEATURES.md

FEATURES.md

@@ -27,7 +27,7 @@ All absolute jumps are folded away, only displaying relevant instructions.
 
 ![](caps/disasm_taken_folded.png)  
 
-Additioanlly, if the current instruction is conditional, Pwndbg displays whether or not it is evaluated with a green check or a red X, and folds away instructions as necessary.
+Additionally, if the current instruction is conditional, Pwndbg displays whether or not it is evaluated with a green check or a red X, and folds away instructions as necessary.
 
 ![](caps/disasm_taken_after.png)  
 ![](caps/disasm_taken_before.png)  
@@ -35,7 +35,7 @@ Additioanlly, if the current instruction is conditional, Pwndbg displays whether
 
 ## Emulation
 
-Pwndbg leverages Unicorn Engine in order to only show instructions which will actually be emulated.  At each debugger stop (e.g. breakpoint or single-step) the next few instructions are silently emulated, and only instrucitons which will actually be executed are displayed.
+Pwndbg leverages Unicorn Engine in order to only show instructions which will actually be emulated.  At each debugger stop (e.g. breakpoint or single-step) the next few instructions are silently emulated, and only instructions which will actually be executed are displayed.
 
 This is incredibly useful when stepping through jump tables, PLT entries, and even while ROPping!
 

README.md

@@ -14,7 +14,7 @@ Vanilla GDB is terrible to use for reverse engineering and exploit development.
 
 Pwndbg is a Python module which is loaded directly into GDB, and provides a suite of utilities and crutches to hack around all of the cruft that is GDB and smooth out the rough edges.
 
-Many other projects from the past (e.g., [gdbinit][gdbinit], [PEDA][PEDA]) and presesnt (e.g. [GEF][GEF]) exist to fill some these gaps.  Unfortunately, they're all either unmaintained, unmaintainable, or not well suited to easily navigating the code to hack in new features (respectively).
+Many other projects from the past (e.g., [gdbinit][gdbinit], [PEDA][PEDA]) and present (e.g. [GEF][GEF]) exist to fill some these gaps.  Unfortunately, they're all either unmaintained, unmaintainable, or not well suited to easily navigating the code to hack in new features (respectively).
 
 Pwndbg exists not only to replace all of its predecessors, but also to have a clean implementation that runs quickly and is resilient against all the weird corner cases that come up.