From ac69987700168e016786a901cff77497fa3c2926 Mon Sep 17 00:00:00 2001
From: lapingenieur <68191390+lapingenieur@users.noreply.github.com>
Date: Tue, 1 Dec 2020 21:49:43 +0100
Subject: [PATCH] corrected spelling mistake

---
 README.MD | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.MD b/README.MD
index a0ed77d3a..28bd42af9 100644
--- a/README.MD
+++ b/README.MD
@@ -32,6 +32,6 @@ This is a port of Nofrendo from https://www.baisoku.org/
 
 - The firmware part is just a regular application called "External", looking for a tar archive at address 0x90200000. If found, each file is displayed in a menu.
 - To launch a file, the external application fetches the firsts 4 bytes of the file, and use it as a function pointer to the address of the entrypoint. The entrypoint is then called with an array of function pointers as en API, and a pointer to a pre-allocated heap.
-- Each application is totally independent (and needs to bring it's own libc, ...). data and bss sections are allocated in ITCM RAM, and the heap is pre-allocated from epsilon. The state of the application is totally reset upon entry.
+- Each application is totally independent (and needs to bring its own libc, ...). data and bss sections are allocated in ITCM RAM, and the heap is pre-allocated from epsilon. The state of the application is totally reset upon entry.
 - To build a usable tar archive, relocation needs to be done to account the real adresses in flash of the binaries. There is a script called "archive" in this repository, which calls the linker on partially linked elf, to build final correctly relocated elf files (then added to the tar archive).
 - The file in the tar must be marked as executable to be executable.