README improvement

Author: EmilieNumworks

README.md

@@ -58,10 +58,10 @@ make run
 The file .nwa expects the following symbols to be defined by the app:
 - `eadk_app_name`: this is the address of the string representing the name of the app. It will be displayed in the Home of Epsilon
 - `eadk_app_api_level`: this is a 4-byte integer stating which version of eadk/eadk.s the external app relies on.
-- `eadk_app_icon`: this is the address of a char table of the icon pixels. This table can by generated by the [inliner.py](/eadk/inliner.py) script from a png file. The png file has to be 55x56 sized. The script converts the png into pixels and compress them using the LZ4 protocole.
+- `eadk_app_icon`: this is the address of a char table of the icon pixels. This table can by generated by the [inliner.py](/eadk/inliner.py) script from a png file. The png file has to be 55x56 sized. The script converts the PNG file into RGB565 bitmap data, then LZ4-compresses it.
 - `_eadk_main` is the entry point of the application.
 
-Optionally, if the external app needs abritary binary code, it can define the `eadk_external_data`. If so, the [NumWorks online uploader](https://my.numworks.com/apps) will ask for the external data to be provided after dropping the .nwa. (In development, you will need to modify `eadk-bin.ld` in order to link the `eadk_external_data`.)
+Optionally, if the external app needs custom binary data, it can define the `eadk_external_data`. If so, the [NumWorks online uploader](https://my.numworks.com/apps) will ask for the external data to be provided after dropping the .nwa. (In development, you will need to modify `eadk-bin.ld` in order to link the `eadk_external_data`.)
 
 ### Symbols that can be used by the external app