Emend the documentation for release v0.9.11.

mkdocs/achandling.md

@@ -597,9 +597,9 @@ portal.begin();
 
 ### <i class="fa fa-wrench"></i> Retrieve the values with WebServer::on handler
 
-ESP8266WebServer class and the WebServer class assume that the implementation of the ReqestHandler class contained in the WebServer library will handle the URL requests. Usually, it is sketch code registered by ESP8266WebServer::on function.
+ESP8266WebServer class and the WebServer (for ESP32) class assume that the implementation of the ReqestHandler class contained in the WebServer library will handle the URL requests. Usually, it is sketch code registered by ESP8266WebServer::on (or WebServer::on for ESP32) function.
 
-When the page transitions from the custom Web page created by AutoConnectAux to the handler registered by ESP2866WebServer::on function, a little trick is needed to retrieve the values of AutoConnectElements. (i.e. the URI of the ESP8266WebServer::on handler is specified in the [uri](acelements.md#uri) attribute of [AutoConnectSubmit](acelements.md#autoconnectsubmit)) AutoConnect cannot intervene in the procedure in which the ESP8266WebServer class calls the on-page handler by the sketch. Therefore, it is necessary to retrieve preliminary the values of AutoConnectElements using the [AutoConnectAux::fetchElement](apiaux.md#fetchelement) function for value processing with the on-page handler.
+When the page transitions from the custom Web page created by AutoConnectAux to the handler registered by ESP2866WebServer::on function, a little trick is needed to retrieve the values of AutoConnectElements. (i.e. the URI of the ESP8266WebServer::on handler is specified in the [uri](acelements.md#uri) attribute of [AutoConnectSubmit](acelements.md#autoconnectsubmit)) AutoConnect cannot intervene in the procedure in which the ESP8266WebServer class calls the on-page handler by the sketch. Therefore, it is necessary to retrieve preliminary the values of AutoConnectElements using the [**AutoConnectAux::fetchElement**](apiaux.md#fetchelement) function for value processing with the on-page handler.
 
 The following sketch is an example of extracting values inputted on a custom web page with an on-page handler and then processing it.
 

mkdocs/advancedusage.md

@@ -515,7 +515,7 @@ portal.begin();
 
 The AutoConnect ticker indicates the WiFi connection status in the following three flicker patterns:
 
-- Short blink: The ESP module stays in APSTA mode.
+- Short blink: The ESP8266/ESP32 module stays in APSTA mode.
 - Short-on and long-off: No STA connection state. (i.e. WiFi.status != WL_CONNECTED)
 - No blink: WiFi connection with access point established and data link enabled. (i.e. WiFi.status = WL_CONNECTED)
 
@@ -529,13 +529,13 @@ The flicker cycle length is defined by some macros in `AutoConnectDefs.h` header
 ```
 
 - `AUTOCONNECTT_FLICKER_PERIODAP`:  
-  Assigns a flicker period when the ESP module stays in APSTA mode.
+  Assigns a flicker period when the ESP8266/ESP32 module stays in APSTA mode.
 - `AUTOCONNECT_FLICKER_PERIODDC`:  
   Assigns a flicker period when WiFi is disconnected.
 - `AUTOCONNECT_FLICKER_WIDTHAP` and `AUTOCONNECT_FLICKER_WIDTHDC`:  
   Specify the duty rate for each period[ms] in 8-bit resolution.
 
-[AutoConnectConfig::tickerPort](apiconfig.md#tickerport) specifies a port that outputs the flicker signal. If you are using an LED-equipped ESP module board, you can assign a LED pin to the tick-port for the WiFi connection monitoring without the external LED. The default pin is arduino valiant's **LED\_BUILTIN**. You can refer to the Arduino IDE's variant information to find out which pin actually on the module assign to **LED\_BUILTIN**.[^3]
+[AutoConnectConfig::tickerPort](apiconfig.md#tickerport) specifies a port that outputs the flicker signal. If you are using an LED-equipped ESP8266/ESP32 module board, you can assign a LED pin to the tick-port for the WiFi connection monitoring without the external LED. The default pin is arduino valiant's **LED\_BUILTIN**. You can refer to the Arduino IDE's variant information to find out which pin actually on the module assign to **LED\_BUILTIN**.[^3]
 
 [^3]: It's defined in the `pins_arduino.h` file, located in the sub-folder named **variants** wherein Arduino IDE installed folder.
 

mkdocs/apiconfig.md

@@ -260,7 +260,7 @@ Set flicker signal output according to WiFi connection status during AutoConnect
     <dt>**Type**</dt>
     <dd>bool</dd>
     <dt>**Value**</dt>
-    <dd><span class="apidef">true</span><span class="apidesc">Output the flicker signal while [AutoConnect::begin](api.md#begin) operation. The **AUTOCONNECT_TICKER_PORT** macro in the `AutoConnectDefs.h` header file assigns pins for signal output. The default pin is arduino valiant's LED_BUILTIN. For boards without the LED\_BUILTIN pin, assume pin #2.</span></dd>
+    <dd><span class="apidef">true</span><span class="apidesc">Output the flicker signal while [AutoConnect::begin](api.md#begin) operation. The **AUTOCONNECT_TICKER_PORT** macro defined in the `AutoConnectDefs.h` header file assigns pins for signal output. The default pin is arduino variants LED_BUILTIN. For boards without the LED\_BUILTIN pin, assume pin #2.</span></dd>
     <dd><span class="apidef">false</span>No flicker signal output.<span class="apidesc"></span></dd>
 </dl>
 

mkdocs/apielements.md

@@ -80,7 +80,7 @@ Returns type of AutoConnectElement.
 ### <i class="fa fa-code"></i> Constructor
 
 ```cpp
-  explicit AutoConnectCheckboxBasis(const char* name = "", const char* value = "", const char* label = "", const bool checked = false, const ACPosterior_t post = AC_Tag_BR)
+AutoConnectCheckbox(const char* name = "", const char* value = "", const char* label = "", const bool checked = false, const ACPosition_t labelPosition = AC_Behind, const ACPosterior_t post = AC_Tag_BR)
 ```
 <dl class="apidl">
     <dt>**Parameters**</dt>
@@ -88,6 +88,7 @@ Returns type of AutoConnectElement.
     <dd><span class="apidef">value</span><span class="apidesc">Value of the element.</span></dd>
     <dd><span class="apidef">label</span><span class="apidesc">A label string prefixed to the checkbox.</span></dd>
     <dd><span class="apidef">check</span><span class="apidesc">Checked state of the checkbox.</span></dd>
+    <dd><span class="apidef">labelPosition</span><span class="apidesc">Specifies the position of the label to generate.</span></dd>
     <dd><span class="apidef">post</span><span class="apidesc">Specifies the tag to be output afterward the element.</span></dd>
 </dl>
 
@@ -117,6 +118,18 @@ A label is an optional string. A label is always arranged on the right side of t
     <dd><span class="apidef">String</span><span class="apidesc"></span></dd>
 </dl>
 
+#### <i class="fa fa-caret-right"></i> labelPosition
+
+Specifies the position of the label to generate with ACPostion_t enumeration value.
+<dl class="apidl">
+    <dt>**Type**</dt>
+    <dd><span class="apidef">ACPosition_t</span><span class="apidesc">
+        
+- **`AC_Infront`** : Place a label in front of the check box.
+- **`AC_Behind`** : Place a label behind the check box.
+</span></dd>
+</dl>
+
 #### <i class="fa fa-caret-right"></i> name
 
 The element name.