README: fix target dir mentions and some other inconsistencies

Author: mochou-p

README.md

@@ -28,7 +28,7 @@
 
 Macroquad is a normal rust dependency, therefore an empty macroquad project may be created with:
 
-```bash
+```sh
 # Create empty cargo project
 cargo init --bin
 ```
@@ -61,23 +61,23 @@ async fn main() {
 ```
 
 And to run it natively:
-```bash
+```sh
 cargo run
 ```
 
 For more examples take a look at [Macroquad examples folder](https://github.com/not-fl3/macroquad/tree/master/examples)
 
 ### Linux
 
-```bash
+```sh
 # ubuntu system dependencies
 apt install pkg-config libx11-dev libxi-dev libgl1-mesa-dev libasound2-dev
 
 # fedora system dependencies
 dnf install libX11-devel libXi-devel mesa-libGL-devel alsa-lib-devel
 
 # arch linux system dependencies
- pacman -S pkg-config libx11 libxi mesa-libgl alsa-lib
+pacman -S pkg-config libx11 libxi mesa-libgl alsa-lib
 ```
 
 ### Windows
@@ -99,7 +99,7 @@ rustup target add wasm32-unknown-unknown
 cargo build --target wasm32-unknown-unknown
 ```
 
-This will produce .wasm file in `target/debug/wasm32-unknown-unknown/CRATENAME.wasm` or in `target/release/wasm32-unknown-unknown/CRATENAME.wasm` if built with `--release`.
+This will produce .wasm file in `target/wasm32-unknown-unknown/debug/CRATENAME.wasm` or in `target/wasm32-unknown-unknown/release/CRATENAME.wasm` if built with `--release`.
 
 And then use the following .html to load it:
 
@@ -149,10 +149,10 @@ basic-http-server .
 
 To run on the simulator:
 
-```
+```sh
 mkdir MyGame.app
 cargo build --target x86_64-apple-ios --release
-cp target/release/mygame MyGame.app
+cp target/x86_64-apple-ios/release/mygame MyGame.app
 # only if the game have any assets
 cp -r assets MyGame.app
 cat > MyGame.app/Info.plist << EOF
@@ -200,7 +200,7 @@ Rust's `async/await` is used to solve just one problem - cross platform main loo
 
 
 The problem: on WASM and android it's not really easy to organize the main loop like this:
-```
+```rust
 fn main() {
     // do some initialization