Updating docs to show avdLaunchTimeout real value
MODIFY
docs/en/writing-running-appium/caps.md
docs/en/writing-running-appium/caps.md
@@ -77,7 +77,7 @@ These Capabilities are available only on Android-based drivers (like
|`remoteAdbHost`|Optional remote ADB server host|e.g.: 192.168.0.101|
|`androidDeviceSocket`|Devtools socket name. Needed only when tested app is a Chromium embedding browser. The socket is open by the browser and Chromedriver connects to it as a devtools client.|e.g., `chrome_devtools_remote`|
|`avd`| Name of avd to launch|e.g., `api19`|
-|`avdLaunchTimeout`| How long to wait in milliseconds for an avd to launch and connect to ADB (default `120000`)| `300000`|
+|`avdLaunchTimeout`| How long to wait in milliseconds for an avd to launch and connect to ADB (default `60000`)| `300000`|
|`avdReadyTimeout`| How long to wait in milliseconds for an avd to finish its boot animations (default `120000`)| `300000`|
|`avdArgs`| Additional emulator arguments used when launching an avd|e.g., `-netfast`|
|`useKeystore`| Use a custom keystore to sign apks, default `false`|`true` or `false`|

Updating docs to show avdLaunchTimeout real value (#11738)