Remove the "easy to debug" when talking about C

Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>

1 files changed, 6 insertions, 6 deletions

diff --git a/README.md b/README.md
index 47f6a91..80d9274 100644
--- a/README.md
+++ b/README.md
@@ -31,12 +31,12 @@ most learning resources are also given in assembly.
 
 That being said, one good argument could be made that you could write the most
 performance critical bits in assembly and leave the business code in C so it's
-easier to understand or debug. That certainly is a possibility, but in the end
-the mixing of both languages can go wrong in different and hidden ways, makes
-building, linking and debugging more complex, and, in my humble opinion, for not
-too much to gain. Or at least that's how I feel, and programming in C might just
-be fine for some people, but I prefer doing everything in assembly on
-NES/Famicom development.
+easier to understand. That certainly is a possibility but in the end the mixing
+of both languages can go wrong in different and subtle ways, makes building,
+linking and debugging more complex, and, in my humble opinion, for not too much
+to gain. Or at least that's how I feel, and programming in C might just be fine
+for some people, but I prefer doing everything in assembly on NES/Famicom
+development.
 
 That's why for the rest of this guide we will be talking about assembly and
 never about C or any other languages.