diff --git a/Working-for-Web-(HTML5).md b/Working-for-Web-(HTML5).md
index 1160542..ce1b313 100644
--- a/Working-for-Web-(HTML5).md
+++ b/Working-for-Web-(HTML5).md
@@ -123,7 +123,7 @@ Avoiding `while()` loop will give better control of the program to the browser a
 
 There could be some situations where the game `while()` loop could not be avoided and users need it to deal with it. For those situations, emscripten implemented two solutions: [`EMTERPRETER`](https://emscripten.org/docs/porting/emterpreter.html#emterpreter-async-run-synchronous-code) and the new [`ASYNCIFY`](https://emscripten.org/docs/porting/emterpreter.html#comparison-to-asyncify). Both methods basically detect synchronous code and move those pieces of code to an asynchronous mode at compilation.
 
-raylib examples [`Makefile`](https://github.com/raysan5/raylib/blob/master/examples/Makefile) has been adapted to use [`ASYNCIFY`](https://github.com/raysan5/raylib/blob/master/examples/Makefile#L236) and, despite the theorical performace lost, the tested results are great.
+raylib examples [`Makefile`](https://github.com/raysan5/raylib/blob/master/examples/Makefile) have been adapted to use [`ASYNCIFY`](https://github.com/raysan5/raylib/blob/master/examples/Makefile#L236), they work great (because they are very small samples), but note that there is a performance penalization.
 
 ### Compiling raylib game