Forward port changes from v0.6 release branch

Merge minor fixes from release-0.6 branch.

Author: bettio

doc/src/atomvm-tooling.md

@@ -304,7 +304,7 @@ remote: Total 17 (delta 6), reused 16 (delta 6), pack-reused 0
 origin/HEAD set to main
 ```
 
-You can now use the `atomvm.packbeam` target to create a packbeam (ending in `.avm`) file:
+You can now use the `mix atomvm.packbeam` task to create a packbeam (ending in `.avm`) file:
 
 ```shell
 $ mix atomvm.packbeam
@@ -328,7 +328,7 @@ $ ls -l HelloWorld.avm
 
 ```{seealso}
 See the [`ExAtomVM`](https://github.com/atomvm/ExAtomVM) page for more detailed instructions about how to use the
-`atomvm.packbeam` target.
+`mix atomvm.packbeam` task.
 ```
 
 ### Running on the `generic_unix` platform
@@ -349,10 +349,10 @@ The [`ExAtomVM`](https://github.com/atomvm/ExAtomVM) plugin supports flash targe
 
 #### ESP32 flash task
 
-To flash AtomVM packbeam file to an ESP32 device, use the `mix.esp32.flash` target.  Users will typically specify the device port and baud rate as command-line options to this target.
+To flash AtomVM packbeam file to an ESP32 device, use the `mix atomvm.esp32.flash` task.  Users will typically specify the device port and baud rate as command-line options to this target.
 
 ```{important}
-In order to use the `mix.esp32.flash` target, you will need to install the [`esptool`](https://github.com/espressif/esptool) program.
+In order to use the `mix atomvm.esp32.flash` task, you will need to install the [`esptool`](https://github.com/espressif/esptool) program.
 ```
 
 For example:
@@ -362,14 +362,10 @@ $ mix atomvm.esp32.flash --port /dev/ttyUSB0 --baud 921600
 ```
 
 ```{tip}
-A baud rate of 921600 works well for most ESP32 devices, some can work reliably at higher rates of 1500000, or even
-2000000, but some devices (especially those with a 26Mhz crystal frequency, rather than the more common 40 Mhz
-crystal) may need to use a slower baud rate such as 115200.
+A baud rate of 921600 works well for most ESP32 devices, some can work reliably at higher rates of 1500000, or even 2000000, but some devices (especially those with a 26Mhz crystal frequency, rather than the more common 40 Mhz crystal) may need to use a slower baud rate such as 115200.
 ```
 
-> Note.  A baud rate of 921600 works well for most ESP32 devices, some can work reliably at higher rates of 1500000, or even 2000000, but some devices (especially those with a 26Mhz crystal frequency, rather than the more common 40 Mhz crystal) may need to use a slower baud rate such as 115200.
-
-See the [`ExAtomVM`](https://github.com/atomvm/ExAtomVM) page for more detailed instructions about how to use the `mix.esp32.flash` target.
+See the [`ExAtomVM`](https://github.com/atomvm/ExAtomVM) page for more detailed instructions about how to use the `mix atomvm.esp32.flash` task.
 
 You can now use a serial console program such as [minicom](https://en.wikipedia.org/wiki/Minicom) or [screen](https://en.wikipedia.org/wiki/GNU_Screen) to view console output from a device.
 
@@ -404,10 +400,10 @@ You can now use a serial console program such as [minicom](https://en.wikipedia.
 
 #### STM32 flash task
 
-To flash AtomVM packbeam file to an STM32 device, use the `atomvm.stm32.flash` mix target.
+To flash AtomVM packbeam file to an STM32 device, use the `mix atomvm.stm32.flash` task.
 
 ```{important}
-In order to use the `mix.stm32.flash` target, you will need to install the  `st-flash` tool from the open source
+In order to use the `mix atomvm.stm32.flash` task, you will need to install the  `st-flash` tool from the open source
 (bsd-3 licensed) [stlink](https://github.com/stlink-org/stlink) suite of stm32 utilities.
 ```
 

doc/src/build-instructions.md

@@ -650,8 +650,8 @@ documentation.
 
 The instructions for adding custom Nifs and ports differ in slight detail, but are otherwise quite similar.  In general, they involve:
 
-1. Adding the custom Nif or Port to the `components` directory of the AtomVM source tree;
-1. Adding the component to the corresponding `main/component_nifs.txt` or `main/component_ports.txt` files;
+1. Adding the custom Nif or Port to the `components` directory of the AtomVM source tree.
+1. Run `idf.py reconfigure` to pick up any menuconfig options, many extra drivers have an option to disable them (they are enabled by default). Optionally use `idf.py menuconfig` and confirm the driver is enabled and save when quitting.
 1. Building the AtomVM binary.
 
 ```{attention}
@@ -685,10 +685,12 @@ To add support for a new peripheral or protocol using custom AtomVM Nif, you nee
     Instructions for implementing Nifs is outside of the scope of this document.
     ```
 
-* Add your `<moniker>` to the `main/component_nifs.txt` file in the `src/platforms/esp32` directory.
-```{attention}
-The `main/component_nifs.txt` file will not exist until after the first clean build.
-```
+* Add the `REGISTER_NIF_COLLECTION` using the parameters `NAME`, `INIT_CB`, `DESTROY_CB`, `RESOLVE_NIF_CB` macro to the end of your nif code. Example:
+
+    ```c
+        REGISTER_NIF_COLLECTION(my_nif, NULL, NULL, my_nif_get_nif);
+    ```
+
 
 #### Adding a custom AtomVM Port
 
@@ -711,10 +713,12 @@ To add support for a new peripheral or protocol using an AtomVM port, you need t
     Instructions for implementing Ports is outside of the scope of this document.
     ```
 
-* Add your `<moniker>` to the `main/component_ports.txt` file in the `src/platforms/esp32` directory.
-```{attention}
-The `main/component_ports.txt` file will not exist until after the first clean build.
-```
+* Add the `REGISTER_PORT_COLLECTION` using the parameters `NAME`, `INIT_CB`, `DESTROY_CB`, `RESOLVE_NIF_CB` macro to the end of your nif code. Example:
+
+    ```c
+        REGISTER_PORT_COLLECTION(my_port, my_port_init, NULL, my_port_create_port);
+    ```
+
 
 ## Building for STM32