Some final documentation updates

docs/Board - AlienWii32.md

@@ -8,15 +8,17 @@ Here are the hardware specifications:
 - MPU6050 accelerometer/gyro sensor unit
 - 8x 4.2A brushed ESCs, integrated, to run the strongest micro motors
 - extra-wide traces on the PCB, for maximum power throughput
-- USB port, integrated (subject to change)
+- USB port, integrated
 - (*) serial connection for external DSM2/DSMX sat receiver (e.g. Spektrum SAT, OrangeRx R100 or Lemon RX)
 - alternatively PPM receiver connection (i.e. Deltang Rx31)
 - ground and 3.3V for the receiver
 - hardware bind plug for easy binding
 - motor connections are at the corners for a clean look with reduced wiring
-- dimensions: 30x32mm
+- dimensions: 29x33mm
 - direct operation from an single cell lipoly battery
 
-(*) Spektrum Compatible DSM2 satellites are supported out of the box. DSMX sat will work with DSM2 protocol with default settings (DSM2, 11bit, 22ms is preset). Changes can be done as usual via CLI or the Cleanflight configurator. Deltang receivers in serial mode will work like any other Spektrum satellite receiver (10bit, 22ms) only the bind process will be different. 
+(*) Spektrum Compatible DSM2 satellites are supported out of the box. DSMX sat will work with DSM2 protocol with default settings (DSM2, 11bit, 11ms is preset). 
 
-The pin layout is very similar as the NAZE32 or the related clones (MW32, Flip32, etc.). The hardware bind pin is connected to pin 41 (PB5). The AlienWii32 firmware will be built with TARGET=NAZE and OPTIONS="AlienWii32". The firmware image will come with alternative default settings which will give the user a plug and play experience. There is no computer needed to get this into the air with an small Quadcopter. Anyhow to use the AlienWii32 in an Hexa- or Octocopter or to do some more tuning additional configuration changes can be done as usual.
+Deltang receivers in serial mode will work like any other Spektrum satellite receiver (10bit, 22ms) only the bind process will be different. 
+
+The pin layout is very similar as the NAZE32 or the related clones (MW32, Flip32, etc.). The hardware bind pin is connected to pin 41 (PB5). The AlienWii32 firmware will be built with TARGET=NAZE and OPTIONS="AlienWii32". The firmware image will come with alternative default settings which will give the user a plug and play experience. There is no computer needed to get this into the air with an small Quadcopter. An preconfigured custom mixer for an Octocopter is part of the default settings to allow clean straight wiring with the AlienWii32. The mixer can be activated with "mixer custom" in the CLI. To use the AlienWii32 in an Hexa- or Octocopter or to do some more tuning additional configuration changes can be done as usual in the CLI or the Cleanflight configurator. 

docs/Spektrum bind.md

@@ -2,7 +2,7 @@
 
 Spektrum bind with hardware bind plug support.
  
-The Spektrum bind code is actually only enabled for the NAZE, NAZE32PRO, CJMCU, CC3D targets.
+The Spektrum bind code is actually enabled for the NAZE, NAZE32PRO, CJMCU, EUSTM32F103RC, SPARKY, CC3D targets.
 
 ## Configure the bind code
 
@@ -24,14 +24,20 @@ The hardware bind plug will be enabled via defining HARDWARE_BIND_PLUG during bu
 
 ## Function
 
-The bind code will actually work for NAZE, NAZE32PRO, CJMCU targets (USART2) and CC3D target (USART3, flex port). The spektrum_sat_bind CLI parameter is defining the number of bind impulses (1-10) send to the satellite receiver. Setting spektrum_sat_bind to zero will disable the bind mode in any case. The bind mode will not be activated after an software reset. Please refer to the table below for the different possible values. If the hardware bind plug is configured the bind mode will only be activated if the plug is set during the firmware start-up. The bind plug should be always removed for normal flying. If no hardware bind plug is used the spektrum_sat_bind parameter will trigger the bind process during the next hardware reset and will be automatically disabled after this. Please refer to the satellite receiver documentation for more details of the specific receiver in bind mode. Usually the bind mode will be indicated with some flashing LEDs.
+The bind code will actually work for NAZE, NAZE32PRO, CJMCU, EUSTM32F103RC, SPARKY targets (USART2) and CC3D target (USART3, flex port). The spektrum_sat_bind CLI parameter is defining the number of bind impulses (1-10) send to the satellite receiver. Setting spektrum_sat_bind to zero will disable the bind mode in any case. The bind mode will only be activated after an power on or hard reset. Please refer to the table below for the different possible values.
+
+If the hardware bind plug is configured the bind mode will only be activated if the plug is set during the firmware start-up. The value of the spektrum_sat_bind parameter will be permanently preserved. The bind plug should be always removed for normal flying.
+
+If no hardware bind plug is used the spektrum_sat_bind parameter will trigger the bind process during the next hardware reset and will be automatically reset to "0" after this.
+
+Please refer to the satellite receiver documentation for more details of the specific receiver in bind mode. Usually the bind mode will be indicated with some flashing LEDs.
 
 ## Table with spektrum_sat_bind parameter value
 
 | Value | Receiver mode  | Notes              |
-| ----- | ---------------| --------|
+| ----- | ---------------| -------------------|
 | 3     | DSM2 1024/22ms |                    |
-| 5     | DSM2 2048/11ms | default |
+| 5     | DSM2 2048/11ms | default AlienWii32 |
 | 7     | DSMX 22ms      |                    |
 | 9     | DSMX 11ms      |                    |
 
@@ -40,4 +46,4 @@ http://wiki.openpilot.org/display/Doc/Spektrum+Satellite
 
 ### Supported Hardware
 
-NAZE, NAZE32PRO, CJMCU, CC3D targets (AlienWii32 with hardware bind plug)
+NAZE, NAZE32PRO, CJMCU, SPARKY, EUSTM32F103RC, CC3D targets (AlienWii32 with hardware bind plug)