Update docs for latest versions

docs/cli/internal-cli-arguments.md

@@ -25,6 +25,18 @@ this flag is automatically enabled internally to find resources from the app dir
 Therefore, you can double click on the binary instead of `neu run` while developing apps.
 :::
 
+### `--config-file=<filename>`
+
+Uses a custom configuration file instead of the default `neutralino.config.json` file for loading the app
+configuration JSON. This CLI option is helpful for setting a development-only configuration file
+(i.e., `--config-file=neutralino-dev.config.json`).
+
+:::info
+The `neu build` command won't typically
+include custom configuration files for the final application bundle &mdash; it only embeds the default
+`neutralino.config.json` file allowing you to store production app configuration.
+:::
+
 ### `--path=<path>`
 
 Overrides the resources path with a relative path or absolute path. This will change the `NL_PATH` global variable.
@@ -166,6 +178,11 @@ Automatically opens the developer tools window.
 
 Overrides the saved window state feature setting.
 
+### `--window-extend-user-agent-with=<suffix>`
+
+Overrides the custom user agent setting.
+
+
 
 ## Chrome mode
 

docs/configuration/neutralino.config.json.md

@@ -246,6 +246,9 @@ the framework will dispatch the `windowClose` event.
 Save and load the primary window state (width, height, x, y, values and maximized status) automatically.
 The default value is `true`.
 
+### `modes.window.extendUserAgentWith: string`
+Extends the default webview-specific user agent string with a custom suffix. If this value is not set,
+the webview sets the default user agent from the platform-specific rendering engine (i.e., WebKit on GNU/Linux).
 
 ## Chrome mode
 The following configuration values are used when the application starts with the chrome mode.