Improve docs

Author: ThomasFarstrike

docs/getting-started/installation.md docs/getting-started/running.mddocs/getting-started/installation.md renamed to docs/getting-started/running.md

@@ -1,10 +1,10 @@
-# Installation
+# Running it
 
 MicroPythonOS can be installed on supported microcontrollers (e.g., ESP32) and on desktop systems (Linux, Raspberry Pi, MacOS, etc).
 
 To simply install prebuilt software, read on!
 
-## Installing on ESP32
+## Running on ESP32
 
 Just use the [WebSerial installer at install.micropythonos.com](https://install.micropythonos.com).
 

docs/os-development/installing-on-esp32.md

@@ -38,6 +38,9 @@ But if you need to install a version that's not available there, or you built yo
 
     In development, you probably want to override the "frozen" libraries and apps that are compiled in, and replace them with source files, which you can edit.
 
+    This makes MicroPythonOS startup a lot slower, as the Python scripts have to be compiled at runtime instead of at build time.
+    But once MicroPythonOS and the code you're testing has loaded, the speed will be normal again.
+
     There's a convenient script that will do this for you.
     
     Usage:

docs/os-development/macos-allow-anyway.png

@@ -36,9 +36,17 @@
     ```
     </pre>
 
-    On MacOS, if you get an error about a missing /opt/homebrew/opt/libffi/lib/libffi.8.dylib then fix that with: `brew install libffi`
+### Notes on MacOS
 
-## Testing on Desktop
+If you get an error about a missing /opt/homebrew/opt/libffi/lib/libffi.8.dylib then fix that with: `brew install libffi`
+
+If you get an error about the code being unsigned, then allow it like this:
+
+![Allow Anyway on MacOS](macos-allow-anyway.png)
+
+    
+
+## Making Changes on Desktop
 
 You'll notice that whenever you change a file in `internal_filesystem/`, the changes are immediately visible on desktop when you reload the file or restart the app.
 
@@ -56,7 +64,7 @@ When you run `./scripts/run_desktop.sh`, the OS runs the MicroPythonOS scripts *
 4. See your changes immediately!
 
 
-## Testing on Hardware
+## Making Changes on ESP32
 
 Once you've tested your changes on desktop and they work correctly, or you're doing things you can't test on desktop, then you can deploy to physical hardware.
 

docs/os-development/running-on-desktop.md

@@ -40,7 +40,7 @@ nav:
   - Overview: overview.md
   - Getting Started:
       - Overview: getting-started/index.md
-      - Installation: getting-started/installation.md
+      - Running: getting-started/running.md
       - Supported Hardware: getting-started/supported-hardware.md
   - Apps:
       - Overview: apps/index.md