aspera-cli 4.15.0 → 4.16.0

data/README.md

@@ -10,9 +10,9 @@
 
 ## Introduction
 
-Version : 4.15.0
+Version : 4.16.0
 
-Laurent/2016-2023
+Laurent/2016-2024
 
 This gem provides the `ascli` CLI (Command Line Interface) to IBM Aspera software.
 
@@ -44,16 +44,16 @@ Refer to [BUGS.md](BUGS.md) and [CONTRIBUTING.md](CONTRIBUTING.md).
 - Execute commands remotely on Aspera products
 - Transfer to/from Aspera products
 
-So it is designed for:
+It is designed for:
 
 - Interactive operations on a text terminal (typically, VT100 compatible), e.g. for maintenance
 - Scripting, e.g. batch operations in (shell) scripts (e.g. cron job)
 
 `ascli` can be seen as a command line tool integrating:
 
-- A configuration file (config.yaml)
-- Advanced command line options
-- cURL (for REST calls)
+- A configuration file (`config.yaml`)
+- Advanced command line options ([Extended Value](#extended))
+- `curl` (for REST calls)
 - Aspera transfer (`ascp`)
 
 If the need is to perform operations programmatically in languages such as: C, Go, Python, nodejs, ... then it is better to directly use [Aspera APIs](https://ibm.biz/aspera_api)
@@ -62,22 +62,23 @@ If the need is to perform operations programmatically in languages such as: C, G
 - Transfer SDK : with gRPC interface and language stubs (C, C++, Python, .NET/C#, java, Ruby, etc...)
 
 Using APIs (application REST API and transfer SDK) will prove to be easier to develop and maintain.
+Code examples here: <https://github.com/laurent-martin/aspera-api-examples>
 
 For scripting and ad'hoc command line operations, `ascli` is perfect.
 
 ### Notations, Shell, Examples
 
-Command line operations examples are shown using a shell such: `bash` or `zsh`.
+Command line operations examples are shown using a shell such as: `bash` or `zsh`.
 
-Command line parameters in examples beginning with `my_`, like `my_param_value` are user-provided value and not fixed value commands.
+Command line parameters in examples beginning with `my_`, e.g. `my_param_value`, are user-provided value and not fixed value commands.
 
 `ascli` is an API **Client** toward the remote Aspera application **Server** (Faspex, HSTS, etc...)
 
 Some commands will start an Aspera-based transfer (e.g. `upload`).
-The transfer is not directly implemented in `ascli`, rather `ascli` uses an external Aspera Client called **[Transfer Agents](#agents)**.
+The transfer is not directly implemented in `ascli`, rather `ascli` uses one of the external Aspera Transfer Clients called **[Transfer Agents](#agents)**.
 
-> **Note:** The transfer agent is a client for the remote Transfer Server (HSTS).
-The transfer agent may be local or remote...
+> **Note:** A **[Transfer Agents](#agents)** is a client for the remote Transfer Server (HSTS).
+The **[Transfer Agents](#agents)** may be local or remote...
 For example a remote Aspera Server may be used as a transfer agent (using node API).
 i.e. using option `--transfer=node`
 
@@ -85,23 +86,20 @@ i.e. using option `--transfer=node`
 
 This section guides you from installation, first use and advanced use.
 
-First, follow the section: [Installation](#installation) (Ruby, Gem, FASP) to start using `ascli`.
+First, follow section: [Installation](#installation) (Ruby, Gem, FASP) to start using `ascli`.
 
 Once the gem is installed, `ascli` shall be accessible:
 
-```bash
-ascli --version
-```
-
-```bash
-4.15.0
+```console
+$ ascli --version
+4.16.0
 ```
 
 ### First use
 
 Once installation is completed, you can proceed to the first use with a demo server:
 
-If you want to test with Aspera on Cloud, jump to section: [Wizard](#aocwizard)
+If you want to test with Aspera on Cloud, jump to section: [Wizard](#aocwizard).
 
 To test with Aspera demo transfer server, setup the environment and then test:
 
@@ -124,19 +122,21 @@ ascli server browse /
 +------------+--------+-----------+-------+---------------------------+-----------------------+
 ```
 
-If you want to use `ascli` with another server, and in order to make further calls more convenient, it is advised to define a [option preset](#lprt) for the server's authentication options. The following example will:
+If you want to use `ascli` with another server, and in order to make further calls more convenient, it is advised to define a [option preset](#lprt) for the server's authentication options.
+The following example will:
 
-- create a [option preset](#lprt)
-- define it as default for `server` plugin
-- list files in a folder
-- download a file
+- Create a [option preset](#lprt)
+- Define it as default for the `server` plugin
+- List files in a folder
+- Download a file
 
 ```bash
 ascli config preset update myserver --url=ssh://demo.asperasoft.com:33001 --username=asperaweb --password=my_password_here
 ```
 
 ```output
-updated: myserver
+Updated: myserver
+Saving config file.
 ```
 
 ```bash
@@ -144,7 +144,8 @@ ascli config preset set default server myserver
 ```
 
 ```output
-updated: default &rarr; server to myserver
+Updated: default: server <- myserver
+Saving config file.
 ```
 
 ```bash
@@ -182,7 +183,7 @@ Then, follow the section relative to the product you want to interact with ( Asp
 
 ## <a id="installation"></a>Installation
 
-It is possible to install **either** directly on the host operating system (Linux, macOS, Windows) or as a container (`docker`).
+It is possible to install **either** directly on the host operating system (Linux, macOS, Windows) or as a [container](#container) (`docker`, `podman`, `singularity`).
 
 The direct installation is recommended and consists in installing:
 
@@ -196,215 +197,16 @@ Ruby version: >= 2.6.
 
 The following sections provide information on the various installation methods.
 
-An internet connection is required for the installation. If you don't have internet for the installation, refer to section [Installation without internet access](#offline_install).
-
-### Container
-
-The container image is: [`martinlaurent/ascli`](https://hub.docker.com/r/martinlaurent/ascli).
-The container contains: Ruby, `ascli` and the Aspera Transfer SDK.
-To use the container, ensure that you have `podman` (or `docker`) installed.
-
-```bash
-podman --version
-```
-
-#### Container: Quick start
-
-**Wanna start quickly ?** With an interactive shell ? Execute this:
-
-```bash
-podman run --tty --interactive --entrypoint bash martinlaurent/ascli:latest
-```
-
-Then, execute individual `ascli` commands such as:
-
-```bash
-ascli conf init
-ascli conf preset overview
-ascli conf ascp info
-ascli server ls /
-```
-
-That is simple, but there are limitations:
-
-- Everything happens in the container
-- Any generated file in the container will be lost on container (shell) exit. Including configuration files and downloaded files.
-- No possibility to upload files located on the host system
-
-#### Container: Details
-
-The container image is built from this [Dockerfile](Dockerfile.tmpl.erb): the entry point is `ascli` and the default command is `help`.
-
-If you want to run the image with a shell, execute with option: `--entrypoint bash`, and give argument `-l` (`bash` login option to override the `help` default argument)
-
-The container can also be executed for individual commands like this: (add `ascli` commands and options at the end of the command line, e.g. `-v` to display the version)
-
-```bash
-podman run --rm --tty --interactive martinlaurent/ascli:latest
-```
-
-For more convenience, you may define a shell alias:
-
-```bash
-alias ascli='podman run --rm --tty --interactive martinlaurent/ascli:latest'
-```
-
-Then, you can execute the container like a local command:
-
-```bash
-ascli -v
-```
-
-```text
-4.15.0
-```
-
-In order to keep persistency of configuration on the host,
-you should specify your user's config folder as a volume for the container.
-To enable write access, a possibility is to run as `root` in the container (and set the default configuration folder to `/home/cliuser/.aspera/ascli`).
-Add options:
-
-```bash
---user root --env ASCLI_HOME=/home/cliuser/.aspera/ascli --volume $HOME/.aspera/ascli:/home/cliuser/.aspera/ascli
-```
-
-> **Note:** if you are using a `podman machine`, e.g. on macOS , make sure that the folder is also shared between the VM and the host, so that sharing is: container &rarr; VM &rarr; Host: `podman machine init ... --volume="/Users:/Users"`
-
-As shown in the quick start, if you prefer to keep a running container with a shell and `ascli` available,
-you can change the entry point, add option:
-
-```bash
---entrypoint bash
-```
-
-You may also probably want that files downloaded in the container are directed to the host.
-In this case you need also to specify the shared transfer folder as a volume:
-
-```bash
---volume $HOME/xferdir:/xferfiles
-```
-
-> **Note:** ascli is run inside the container, so transfers are also executed inside the container and do not have access to host storage by default.
-
-And if you want all the above, simply use all the options:
-
-```bash
-alias asclish="podman run --rm --tty --interactive --user root --env ASCLI_HOME=/home/cliuser/.aspera/ascli --volume $HOME/.aspera/ascli:/home/cliuser/.aspera/ascli --volume $HOME/xferdir:/xferfiles --entrypoint bash martinlaurent/ascli:latest"
-```
-
-```bash
-export xferdir=$HOME/xferdir
-mkdir -p $xferdir
-chmod -R 777 $xferdir
-mkdir -p $HOME/.aspera/ascli
-asclish
-```
-
-#### Container: Sample start script
-
-A convenience sample script is also provided: download the script [`dascli`](../examples/dascli) from [the GIT repo](https://raw.githubusercontent.com/IBM/aspera-cli/main/examples/dascli) :
-
-> **Note:** If you have installed `ascli`, the script `dascli` can also be found: `cp $(ascli conf gem path)/../examples/dascli ascli`
-
-Some environment variables can be set for this script to adapt its behavior:
-
-| env var        | description                        | default                  | example                  |
-|----------------|------------------------------------|--------------------------|--------------------------|
-| `ASCLI_HOME` | configuration folder (persistency) | `$HOME/.aspera/ascli` | `$HOME/.ascli_config` |
-| `docker_args`  | additional options to `podman`     | &lt;empty&gt;            | `--volume /Users:/Users` |
-| `image`        | container image name               | `martinlaurent/ascli`    |                          |
-| `version`      | container image version            | latest                   | `4.8.0.pre`              |
-
-The wrapping script maps the folder `$ASCLI_HOME` on host to `/home/cliuser/.aspera/ascli` in the container.
-(value expected in the container).
-This allows having persistent configuration on the host.
-
-To add local storage as a volume, you can use the env var `docker_args`:
-
-Example of use:
-
-```bash
-curl -o ascli https://raw.githubusercontent.com/IBM/aspera-cli/main/examples/dascli
-chmod a+x ascli
-export xferdir=$HOME/xferdir
-mkdir -p $xferdir
-chmod -R 777 $xferdir
-export docker_args="--volume $xferdir:/xferfiles"
-
-./ascli conf init
-
-echo 'Local file to transfer' > $xferdir/samplefile.txt
-./ascli server upload /xferfiles/samplefile.txt --to-folder=/Upload
-```
-
-> **Note:** The local file (`samplefile.txt`) is specified relative to storage view from container (`/xferfiles`) mapped to the host folder `$HOME/xferdir`
->
-> **Note:** Do not use too many volumes, as the legacy `aufs` limits the number. (anyway, prefer to use `overlay2`)
-
-#### Container: Offline installation
-
-- First create the image archive:
-
-```bash
-podman pull martinlaurent/ascli
-podman save martinlaurent/ascli|gzip>ascli_image_latest.tar.gz
-```
-
-- Then, on air-gapped system:
-
-```bash
-podman load -i ascli_image_latest.tar.gz
-```
-
-#### Container: `aspera.conf`
-
-`ascp`'s configuration file `aspera.conf` is located in the container at: `/aspera_sdk/aspera.conf` (see Dockerfile).
-As the container is immutable, it is not recommended to modify this file.
-If one wants to change the content, it is possible to tell `ascp` to use another file using `ascp` option `-f`, e.g. by locating it on the host folder `$HOME/.aspera/ascli` mapped to the container folder `/home/cliuser/.aspera/ascli`:
-
-```bash
-echo '<CONF/>' > $HOME/.aspera/ascli/aspera.conf
-```
+An internet connection is required for the installation.
+If you don't have internet for the installation, refer to section [Installation without internet access](#offline_install).
 
-Then, tell `ascp` to use that other configuration file:
-
-```bash
---transfer-info=@json:'{"ascp_args":["-f","/home/cliuser/.aspera/ascli/aspera.conf"]}'
-```
-
-#### Container: Singularity
-
-Singularity is another type of use of container.
-
-On Linux install:
-
-```bash
-dnf install singularity-ce
-```
-
-Build an image like this:
-
-```bash
-singularity build ascli.sif docker://martinlaurent/ascli
-```
-
-Then, start `ascli` like this:
-
-```bash
-singularity run ascli.sif
-```
-
-Or get a shell with access to `ascli` like this:
-
-```bash
-singularity shell ascli.sif
-```
+A package with pre-installed Ruby, gem and ascp may also be provided.
 
 ### <a id="ruby"></a>Ruby
 
-Use this method to install on the native host.
+Use this method to install on the native host (e.g. your Windows, macOS or Linux system).
 
-A Ruby interpreter is required to run `ascli` or to use the gem and tool.
+A Ruby interpreter is required to run `ascli`.
 
 Required Ruby version: >= 2.6.
 
@@ -412,24 +214,20 @@ Required Ruby version: >= 2.6.
 
 **Ruby can be installed using any method** : rpm, yum, dnf, rvm, brew, Windows installer, ... .
 
-In priority, refer to the official Ruby documentation:
+**In priority**, refer to the official Ruby documentation:
 
 - [Download Ruby](https://www.ruby-lang.org/en/downloads/)
 - [Installation Guide](https://www.ruby-lang.org/en/documentation/installation/)
 
-Else, refer to the following sections for a proposed method for specific operating systems.
-
-The recommended installation method is `rvm` for Unix-like systems (Linux, AIX, macOS, Windows with cygwin, etc...).
-If the generic install is not suitable (e.g. Windows, no cygwin), you can use one of OS-specific install method.
-If you have a simpler better way to install Ruby : use it !
+For convenience, you may refer to the following sections for a proposed method for specific operating systems.
 
-#### Generic: RVM: Single user installation (not root)
+#### Unix-like: RVM: Single user installation (not root)
 
-Use this method which provides more flexibility.
+Install `rvm`.
+Follow [https://rvm.io/](https://rvm.io/).
 
-Install `rvm`: follow [https://rvm.io/](https://rvm.io/) :
-
-Execute the shell/curl command. As regular user, it install in the user's home: `~/.rvm` .
+Execute the shell/curl command.
+As regular user, it installs in the user's home: `~/.rvm` .
 
 ```bash
 \curl -sSL https://get.rvm.io | bash -s stable
@@ -437,7 +235,7 @@ Execute the shell/curl command. As regular user, it install in the user's home:
 
 Follow on-screen instructions to install keys, and then re-execute the command.
 
-If you keep the same terminal (not needed if re-login):
+Upon RVM installation, open a new terminal or initialize with:
 
 ```bash
 source ~/.rvm/scripts/rvm
@@ -457,19 +255,16 @@ rvm install 3.2.2
 
 Ruby is now installed for the user, go to [Gem installation](#the_gem).
 
-#### Generic: RVM: Global installation (as root)
-
-Follow the same method as single user install, but execute as "root".
-
-As root, it installs by default in /usr/local/rvm for all users and creates `/etc/profile.d/rvm.sh`.
-One can install in another location with :
+Alternatively RVM can be installed system-wide, for this execute as `root`.
+It then installs by default in `/usr/local/rvm` for all users and creates `/etc/profile.d/rvm.sh`.
+One can install in another location with:
 
 ```bash
 curl -sSL https://get.rvm.io | bash -s -- --path /usr/local
 ```
 
 As root, make sure this will not collide with other application using Ruby (e.g. Faspex).
-If so, one can rename the login script:
+If so, one can rename the environment script so that it is not loaded by default:
 
 ```bash
 mv /etc/profile.d/rvm.sh /etc/profile.d/rvm.sh.ok
@@ -493,13 +288,13 @@ Manual installation:
 - Download the latest Ruby installer **"with devkit"**. (`Msys2` is needed to install some native extensions, such as `grpc`)
 - Execute the installer which installs by default in: `C:\RubyVV-x64` (VV is the version number)
 - At the end of the installation procedure, the `Msys2` installer is automatically executed, select option 3 (`Msys2` and mingw)
-- then install the aspera-cli gem and Aspera SDK (see next sections)
+- Then install the aspera-cli gem and Aspera SDK (see next sections)
 
 Automated installation, with internet access:
 
-The ruby installer supports silent installation, to see the options, execute it with `/help`, or refer to the [Ruby Installer FAQ](https://github.com/oneclick/rubyinstaller2/wiki/FAQ)
+The Ruby installer supports silent installation, to see the options, execute it with `/help`, or refer to the [Ruby Installer FAQ](https://github.com/oneclick/rubyinstaller2/wiki/FAQ)
 
-Download the ruby installer executable from <https://rubyinstaller.org/downloads/> and then install:
+Download the Ruby installer executable from <https://rubyinstaller.org/downloads/> and then install:
 
 ```bat
 rubyinstaller-devkit-3.2.2-1-x64.exe /silent /currentuser /noicons /dir=C:\aspera-cli
@@ -507,9 +302,15 @@ rubyinstaller-devkit-3.2.2-1-x64.exe /silent /currentuser /noicons /dir=C:\asper
 
 Installation without network:
 
-It is essentially the same procedure, but instead of retrieving files from internet, one copies the files from a machine with internet access, and then install from those archives:
+It is essentially the same procedure, but instead of retrieving files from internet, copy the files from a machine with internet access, and then install from those archives:
+
+- Download the `exe` Ruby installer from <https://rubyinstaller.org/downloads/>
+
+  ```bash
+  v=$(curl -s https://rubyinstaller.org/downloads/|sed -nEe 's|.*(https://.*/releases/download/.*exe).*|\1|p'|head -n 1)
+  curl -o ${v##*/} $v
+  ```
 
-- Download the `exe` ruby installer from <https://rubyinstaller.org/downloads/>
 - Create an archive with necessary gems: <https://help.rubygems.org/kb/rubygems/installing-gems-with-no-network>
 
   ```bat
@@ -537,25 +338,20 @@ rubyinstaller-devkit-3.2.2-1-x64.exe /silent /currentuser /noicons /dir=C:\asper
 gem install --force --local *.gem
 ```
 
-- install the SDK
+- Install the SDK
 
 ```bash
-ascli conf ascp install --sdk-url=file:///sdk.zip
+ascli config ascp install --sdk-url=file:///sdk.zip
 ```
 
 > **Note:** An example of installation script is provided: [docs/install.bat](docs/install.bat)
 
-#### macOS: Pre-installed or `brew`
-
-macOS 10.13+ (High Sierra) comes with a recent Ruby.
-So you can use it directly.
-You will need to install aspera-cli using `sudo` :
+#### macOS: `brew`
 
-```bash
-sudo gem install aspera-cli
-```
+**macOS** come with Ruby.
+Nevertheless, [Apple has deprecated it](https://developer.apple.com/documentation/macos-release-notes/macos-catalina-10_15-release-notes), and it will be removed in the future, so better not to rely on it.
 
-Alternatively, if you use [Homebrew](https://brew.sh/) already you can install Ruby with it:
+The recommended way is to either user `RVM` or use [Homebrew](https://brew.sh/).
 
 ```bash
 brew install ruby
@@ -567,13 +363,13 @@ If your Linux distribution provides a standard Ruby package, you can use it prov
 
 **Example:** RHEL 8+, Rocky Linux 8+, Centos 8 Stream: with extensions to compile native gems
 
-- Check available ruby versions:
+- Check available Ruby versions:
 
   ```bash
   dnf module list ruby
   ```
 
-- If ruby was already installed with an older version, remove it:
+- If Ruby was already installed with an older version, remove it:
 
   ```bash
   dnf module -y reset ruby
@@ -602,7 +398,7 @@ yum install -y ruby ruby-devel rubygems ruby-json
 apt install -y ruby ruby-dev rubygems ruby-json
 ```
 
-One can cleanup the whole yum-installed Ruby environment like this to uninstall:
+One can remove all installed gems, for example to start fresh:
 
 ```bash
 gem uninstall -axI $(ls $(gem env gemdir)/gems/|sed -e 's/-[^-]*$//'|sort -u)
@@ -610,7 +406,7 @@ gem uninstall -axI $(ls $(gem env gemdir)/gems/|sed -e 's/-[^-]*$//'|sort -u)
 
 #### Other Unixes (AIX)
 
-Ruby is sometimes made available as installable package through third party providers.
+Ruby is sometimes made available as an installable package through third party providers.
 For example for AIX, one can look at:
 
 <https://www.ibm.com/support/pages/aix-toolbox-open-source-software-downloads-alpha#R>
@@ -618,7 +414,7 @@ For example for AIX, one can look at:
 If your Unix does not provide a pre-built Ruby, you can get it using one of those
 [methods](https://www.ruby-lang.org/en/documentation/installation/).
 
-For instance to build from source, and install in `/opt/ruby` :
+For instance to build from source and install in `/opt/ruby` :
 
 ```bash
 wget https://cache.ruby-lang.org/pub/ruby/2.7/ruby-2.7.2.tar.gz
@@ -644,9 +440,25 @@ If you already have a Java JVM on your system (`java`), it is possible to use `j
 
 > **Note:** Using `jruby`, the startup time is longer than the native Ruby, but transfer speed is not impacted (executed by `ascp` binary).
 
+#### Optional gems
+
+Some additional gems can be installed to provide additional features:
+
+- `rmagick` : to generate thumbnails of images
+- `grpc` : to use the transfer SDK (gRPC)
+- `mimemagic` : to detect MIME type of files for `preview` command
+
+Install like this:
+
+```bash
+gem install rmagick grpc mimemagic
+```
+
+> **Note:** Those are not installed as part of dependencies because they involve compilation of native code.
+
 ### <a id="the_gem"></a>`aspera-cli` gem
 
-Once you have Ruby and rights to install gems: Install the gem and its dependencies:
+Once you have Ruby and rights to install gems, install the `aspera-cli` gem and its dependencies:
 
 ```bash
 gem install aspera-cli
@@ -658,27 +470,27 @@ To upgrade to the latest version:
 gem update aspera-cli
 ```
 
-`ascli` checks every week if a new version is available and notify the user in a WARN log.
+During its execution, `ascli` checks every week if a new version is available and notifies the user in a WARN log.
 To de-activate this feature, globally set the option `version_check_days` to `0`, or specify a different period in days.
 
 To check if a new version is available (independently of `version_check_days`):
 
 ```bash
-ascli conf check_update
+ascli config check_update
 ```
 
 ### <a id="fasp_prot"></a>FASP Protocol
 
-Most file transfers will be done using the FASP protocol, using `ascp`.
+Most file transfers will be executed using the **FASP** protocol, using `ascp`.
 Only two additional files are required to perform an Aspera Transfer, which are part of Aspera SDK:
 
 - `ascp`
-- aspera-license (in same folder, or ../etc)
+- `aspera-license` (in same folder, or ../etc)
 
 This can be installed either be installing an Aspera transfer software, or using an embedded command:
 
 ```bash
-ascli conf ascp install
+ascli config ascp install
 ```
 
 If a local SDK installation is preferred instead of fetching from internet: one can specify the location of the SDK file:
@@ -688,7 +500,7 @@ curl -Lso sdk.zip https://ibm.biz/aspera_sdk
 ```
 
 ```bash
-ascli conf ascp install --sdk-url=file:///sdk.zip
+ascli config ascp install --sdk-url=file:///sdk.zip
 ```
 
 The format is: `file:///<path>`, where `<path>` can be either a relative path (not starting with `/`), or an absolute path.
@@ -700,37 +512,39 @@ If the embedded method is not used, the following packages are also suitable:
 - IBM Aspera High Speed Transfer Server (Licensed)
 - IBM Aspera High Speed Transfer EndPoint (Licensed)
 
-For instance, Aspera Connect Client can be installed
-by visiting the page: [https://www.ibm.com/aspera/connect/](https://www.ibm.com/aspera/connect/).
+For instance, Aspera Connect Client can be installed by visiting the page:
+[https://www.ibm.com/aspera/connect/](https://www.ibm.com/aspera/connect/).
 
-`ascli` will detect most of Aspera transfer products in standard locations and use the first one found.
+`ascli` will detect most of Aspera transfer products in standard locations and use the first one found by default.
 Refer to section [FASP](#client) for details on how to select a client or set path to the FASP protocol.
 
 Several methods are provided to start a transfer.
-Use of a local client ([`direct`](#agt_direct) transfer agent) is one of them, but other methods are available. Refer to section: [Transfer Agents](#agents)
+Use of a local client ([`direct`](#agt_direct) transfer agent) is one of them, but other methods are available.
+Refer to section: [Transfer Agents](#agents)
 
 ### <a id="offline_install"></a>Installation in air gapped environment
 
-> **Note:** no pre-packaged version is provided.
+> **Note:** No pre-packaged version is provided yet.
 
 A method to build one is provided here:
 
 The procedure:
 
 - Follow the non-root installation procedure with RVM, including gem
+
 - Archive (zip, tar) the main RVM folder (includes ascli):
 
 ```bash
 cd $HOME && tar zcvf rvm-ascli.tgz .rvm
 ```
 
-- Get the Aspera SDK.
+- Show the Aspera SDK URL
 
 ```bash
-ascli conf --show-config --fields=sdk_url
+ascli --show-config --fields=sdk_url
 ```
 
-- Download the SDK archive from that URL.
+- Download the SDK archive from that URL
 
 ```bash
 curl -Lso sdk.zip https://ibm.biz/aspera_sdk
@@ -747,7 +561,7 @@ tar zxvf rvm-ascli.tgz
 
 source ~/.rvm/scripts/rvm
 
-ascli conf ascp install --sdk-url=file:///sdk.zip
+ascli config ascp install --sdk-url=file:///sdk.zip
 ```
 
 - Add those lines to shell init (`.profile`)
@@ -756,9 +570,218 @@ ascli conf ascp install --sdk-url=file:///sdk.zip
 source ~/.rvm/scripts/rvm
 ```
 
+> **Note:** Alternatively, to download all necessary gems in folder `my_gems`, execute:
+
+```bash
+gem install aspera-cli -N -i my_gems
+```
+
+### Container
+
+The container image is: [`martinlaurent/ascli`](https://hub.docker.com/r/martinlaurent/ascli).
+The container contains: Ruby, `ascli` and the Aspera Transfer SDK.
+To use the container, ensure that you have `podman` (or `docker`) installed.
+
+```bash
+podman --version
+```
+
+#### Container: Quick start
+
+**Wanna start quickly ?** With an interactive shell ?
+Execute this:
+
+```bash
+podman run --rm --tty --interactive --entrypoint bash martinlaurent/ascli:latest
+```
+
+> **Note:** This command changes the entrypoint to an interactive shell instead of direct execution of `ascli`.
+
+Then, execute individual `ascli` commands such as:
+
+```bash
+ascli config init
+ascli config preset overview
+ascli config ascp info
+ascli server ls /
+```
+
+That is simple, but there are limitations:
+
+- Everything happens in the container
+- Any generated file in the container will be lost on container (shell) exit. Including configuration files and downloaded files.
+- No possibility to upload files located on the host system
+
+#### Container: Details
+
+The container image is built from this [Dockerfile](Dockerfile.tmpl.erb).
+The entry point is `ascli` and the default command is `help`.
+
+The container can be executed for individual commands like this: (add `ascli` commands and options at the end of the command line, e.g. `-v` to display the version)
+
+```bash
+podman run --rm --tty --interactive martinlaurent/ascli:latest
+```
+
+For more convenience, you may define a shell alias:
+
+```bash
+alias ascli='podman run --rm --tty --interactive martinlaurent/ascli:latest'
+```
+
+Then, you can execute the container like a local command:
+
+```bash
+ascli -v
+```
+
+```text
+4.16.0
+```
+
+In order to keep persistency of configuration on the host, you should specify your user's configuration folder as a volume for the container.
+To enable write access, a possibility is to run as `root` in the container (and set the default configuration folder to `/home/cliuser/.aspera/ascli`).
+Add options:
+
+```bash
+--user root --env ASCLI_HOME=/home/cliuser/.aspera/ascli --volume $HOME/.aspera/ascli:/home/cliuser/.aspera/ascli
+```
+
+> **Note:** If you are using a `podman machine`, e.g. on macOS , make sure that the folder is also shared between the VM and the host, so that sharing is: container &rarr; VM &rarr; Host: `podman machine init ... --volume="/Users:/Users"`
+
+As shown in the quick start, if you prefer to keep a running container with a shell and `ascli` available,
+you can change the entry point, add option:
+
+```bash
+--entrypoint bash
+```
+
+You may also probably want that files downloaded in the container are directed to the host.
+In this case you need also to specify the shared transfer folder as a volume:
+
+```bash
+--volume $HOME/xferdir:/xferfiles
+```
+
+> **Note:** ascli is run inside the container, so transfers are also executed inside the container and do not have access to host storage by default.
+
+And if you want all the above, simply use all the options:
+
+```bash
+alias asclish="podman run --rm --tty --interactive --user root --env ASCLI_HOME=/home/cliuser/.aspera/ascli --volume $HOME/.aspera/ascli:/home/cliuser/.aspera/ascli --volume $HOME/xferdir:/xferfiles --entrypoint bash martinlaurent/ascli:latest"
+```
+
+```bash
+export xferdir=$HOME/xferdir
+mkdir -p $xferdir
+chmod -R 777 $xferdir
+mkdir -p $HOME/.aspera/ascli
+asclish
+```
+
+#### Container: Sample start script
+
+A convenience sample script is also provided: download the script [`dascli`](../examples/dascli) from [the GIT repo](https://raw.githubusercontent.com/IBM/aspera-cli/main/examples/dascli) :
+
+> **Note:** If you have installed `ascli`, the script `dascli` can also be found: `cp $(ascli config gem path)/../examples/dascli ascli`
+
+Some environment variables can be set for this script to adapt its behavior:
+
+| env var        | Description                        | Default                  | Example                  |
+|----------------|------------------------------------|--------------------------|--------------------------|
+| `ASCLI_HOME` | Configuration folder (persistency) | `$HOME/.aspera/ascli` | `$HOME/.ascli_config` |
+| `docker_args`  | Additional options to `podman`     | &lt;empty&gt;            | `--volume /Users:/Users` |
+| `image`        | Container image name               | `martinlaurent/ascli`    |                          |
+| `version`      | Container image version            | Latest                   | `4.8.0.pre`              |
+
+The wrapping script maps the folder `$ASCLI_HOME` on host to `/home/cliuser/.aspera/ascli` in the container.
+(value expected in the container).
+This allows having persistent configuration on the host.
+
+To add local storage as a volume, you can use the env var `docker_args`:
+
+Example of use:
+
+```bash
+curl -o ascli https://raw.githubusercontent.com/IBM/aspera-cli/main/examples/dascli
+chmod a+x ascli
+export xferdir=$HOME/xferdir
+mkdir -p $xferdir
+chmod -R 777 $xferdir
+export docker_args="--volume $xferdir:/xferfiles"
+
+./ascli config init
+
+echo 'Local file to transfer' > $xferdir/samplefile.txt
+./ascli server upload /xferfiles/samplefile.txt --to-folder=/Upload
+```
+
+> **Note:** The local file (`samplefile.txt`) is specified relative to storage view from container (`/xferfiles`) mapped to the host folder `$HOME/xferdir`
+>
+> **Note:** Do not use too many volumes, as the legacy `aufs` limits the number. (anyway, prefer to use `overlay2`)
+
+#### Container: Offline installation
+
+- First create the image archive:
+
+```bash
+podman pull martinlaurent/ascli
+podman save martinlaurent/ascli|gzip>ascli_image_latest.tar.gz
+```
+
+- Then, on air-gapped system:
+
+```bash
+podman load -i ascli_image_latest.tar.gz
+```
+
+#### Container: `aspera.conf`
+
+`ascp`'s configuration file `aspera.conf` is located in the container at: `/aspera_sdk/aspera.conf` (see Dockerfile).
+As the container is immutable, it is not recommended to modify this file.
+If one wants to change the content, it is possible to tell `ascp` to use another file using `ascp` option `-f`, e.g. by locating it on the host folder `$HOME/.aspera/ascli` mapped to the container folder `/home/cliuser/.aspera/ascli`:
+
+```bash
+echo '<CONF/>' > $HOME/.aspera/ascli/aspera.conf
+```
+
+Then, tell `ascp` to use that other configuration file:
+
+```bash
+--transfer-info=@json:'{"ascp_args":["-f","/home/cliuser/.aspera/ascli/aspera.conf"]}'
+```
+
+#### Container: Singularity
+
+Singularity is another type of use of container.
+
+On Linux install:
+
+```bash
+dnf install singularity-ce
+```
+
+Build an image like this:
+
+```bash
+singularity build ascli.sif docker://martinlaurent/ascli
+```
+
+Then, start `ascli` like this:
+
+```bash
+singularity run ascli.sif
+```
+
+Or get a shell with access to `ascli` like this:
+
+```bash
+singularity shell ascli.sif
+```
+
 ## <a id="cli"></a>Command Line Interface: `ascli`
 
-The `aspera-cli` Gem provides a command line interface (CLI) which interacts with Aspera Products (mostly using REST APIs):
+The `aspera-cli` gem provides a command line interface (CLI) which interacts with Aspera Products (mostly using REST APIs):
 
 - IBM Aspera High Speed Transfer Server (FASP and Node)
 - IBM Aspera on Cloud (including ATS)
@@ -766,21 +789,21 @@ The `aspera-cli` Gem provides a command line interface (CLI) which interacts wit
 - IBM Aspera Shares
 - IBM Aspera Console
 - IBM Aspera Orchestrator
-- and more...
+- And more...
 
 `ascli` provides the following features:
 
-- Supports most Aspera server products (on-premise and SaaS)
-- Any command line options (products URL, credentials or any option) can be provided on command line, in configuration file, in env var, in files
+- Supports commands to Aspera server products (on-premise and SaaS)
+- Any command line **options** (products URL, credentials or any option) can be provided on command line, in configuration file, in env var, in files, ...
 - Supports Commands, Option values and Parameters shortcuts
 - FASP [Transfer Agents](#agents) can be: local `ascp`, or Connect Client, or any transfer node
 - Transfer parameters can be altered by modification of [*transfer-spec*](#transferspec), this includes requiring multi-session
 - Allows transfers from products to products, essentially at node level (using the node transfer agent)
 - Supports FaspStream creation (using Node API)
-- Supports "Watchfolder" creation (using Node API)
+- Supports **Watchfolder** creation (using Node API)
 - Additional command plugins can be written by the user
 - Supports download of faspex and Aspera on Cloud "external" links
-- Supports "legacy" ssh based FASP transfers and remote commands (`ascmd`)
+- Supports **Legacy** SSH based FASP transfers and remote commands (`ascmd`)
 
 Basic usage is displayed by executing:
 
@@ -790,7 +813,7 @@ ascli -h
 
 Refer to sections: [Usage](#usage).
 
-Not all `ascli` features are fully documented here, the user may explore commands on the command line.
+> **Note:** `ascli` features are not fully documented here, the user may explore commands on the command line.
 
 ### `ascp` command line
 
@@ -798,17 +821,17 @@ If you want to use `ascp` directly as a command line, refer to IBM Aspera docume
 
 Using `ascli` with plugin `server` for command line gives advantages over `ascp`:
 
-- automatic resume on error
-- configuration file
-- choice of transfer agents
-- integrated support of multi-session
+- Automatic resume on error
+- Configuration file
+- Choice of transfer agents
+- Integrated support of multi-session
 
-Moreover all `ascp` options are supported either through transfer spec parameters and with the possibility to provide `ascp` arguments directly when the `direct` agent is used (`ascp_args`).
+Moreover all `ascp` options are supported either through transfer spec parameters (listed with `conf ascp spec`) and with the possibility to provide `ascp` arguments directly when the `direct` agent is used (`ascp_args` in `transfer_info`).
 
 ### <a id="parsing"></a>Command line parsing, Special Characters
 
 `ascli` is typically executed in a shell, either interactively or in a script.
-`ascli` receives its arguments from this shell (through Operating System).
+`ascli` receives its arguments from this shell (through the Operating System).
 
 #### Shell parsing for Unix-like systems: Linux, macOS, AIX
 
@@ -819,7 +842,7 @@ In this environment the shell parses the command line, possibly replacing variab
 See [bash shell operation](https://www.gnu.org/software/bash/manual/bash.html#Shell-Operation).
 The shell builds the list of arguments and then `fork`/`exec` Ruby with that list.
 Ruby receives a list parameters from shell and gives it to `ascli`.
-So special character handling (quotes, spaces, env vars, ...) is handled by the shell for any command executed.
+Special character handling (quotes, spaces, env vars, ...) is handled by the shell for any command executed.
 
 #### Shell parsing for Windows
 
@@ -834,22 +857,22 @@ One can also run `ascli` with option `--log-level=debug` to display the command
 
 The following examples give the same result on Windows:
 
-- single quote protects the double quote
+- Single quote protects the double quote
 
   ```cmd
-   conf echo @json:'{"url":"https://..."}'
+  ascli config echo @json:'{"url":"https://..."}'
   ```
 
-- triple double quotes are replaced with a single double quote
+- Triple double quotes are replaced with a single double quote
 
   ```cmd
-   conf echo @json:{"""url""":"""https://..."""}
+  ascli config echo @json:{"""url""":"""https://..."""}
   ```
 
-- double quote is escaped with backslash within double quotes
+- Double quote is escaped with backslash within double quotes
 
   ```cmd
-   conf echo @json:"{\"url\":\"https://...\"}"
+  ascli config echo @json:"{\"url\":\"https://...\"}"
   ```
 
 More details: on Windows, `cmd.exe` is typically used to start .
@@ -858,7 +881,8 @@ Basically it handles I/O redirection (`<>|`), shell variables (`%`), multiple co
 Eventually, all those special characters are removed from the command line unless escaped with `^` or `"`.
 `"` are kept and given to the program.
 
-Then, Windows `CreateProcess` is called with just the whole command line as a single string, unlike Unix-like systems where the command line is split into arguments by the shell.
+Then, the shell calls Windows' `CreateProcess` with just the whole command line as a single string.
+Unlike Unix-like systems where the command line is split into arguments by the shell.
 
 It's up to the program to split arguments:
 
@@ -869,26 +893,29 @@ It's up to the program to split arguments:
 Ruby vaguely follows the Microsoft C/C++ parameter parsing rules.
 (See `w32_cmdvector` in Ruby source [`win32.c`](https://github.com/ruby/ruby/blob/master/win32/win32.c#L1766)) : <!--cspell:disable-line-->
 
-- space characters: split arguments (space, tab, newline)
-- backslash: `\` escape single special character
-- globing characters: `*?[]{}` for file globing
-- double quotes: `"`
-- single quotes: `'`
+- Space characters: split arguments (space, tab, newline)
+- Backslash: `\` escape single special character
+- Globing characters: `*?[]{}` for file globing
+- Double quotes: `"`
+- Single quotes: `'`
 
 #### Extended Values (JSON, Ruby, ...)
 
-Some of the `ascli` parameters are expected to be [Extended Values](#extended), i.e. not a simple `String`, but a complex structure (`Hash`, `Array`).
+Some of the `ascli` parameters are expected to be [Extended Values](#extended), i.e. not a simple `String`, but a composite structure (`Hash`, `Array`).
 Typically, the `@json:` modifier is used, it expects a [JSON](https://www.json.org/) string.
 JSON itself has some special syntax: for example `"` is used to enclose a `String`.
 
 #### Testing Extended Values
 
-In case of doubt of argument values after parsing, one can test using command `config echo`. `config echo` takes exactly **one** argument which can use the [Extended Value](#extended) syntax. Unprocessed command line arguments are shown in the error message.
+In case of doubt of argument values after parsing, one can test using command `config echo`.
+`config echo` takes exactly **one** argument which can use the [Extended Value](#extended) syntax.
+Unprocessed command line arguments are shown in the error message.
 
-Example: The shell parses three arguments (as `String`: `1`, `2` and `3`), so the additional two arguments are not processed by the `echo` command.
+Example:
+The shell parses three arguments (as `String`: `1`, `2` and `3`), so the additional two arguments are not processed by the `echo` command.
 
 ```bash
-ascli conf echo 1 2 3
+ascli config echo 1 2 3
 ```
 
 ```ruby
@@ -900,9 +927,10 @@ ERROR: Argument: unprocessed values: ["2", "3"]
 
 > **Note:** It gets its value after shell command line parsing and `ascli` extended value parsing.
 
-In the following examples (using a POSIX shell, such as `bash`), several sample commands are provided when equivalent.
-For all example, most of special character handling is not specific to `ascli`: It depends on the underlying syntax: shell , JSON, etc...
-Depending on the case, a different `format` is used to display the actual value.
+In the following examples (using a POSIX shell, such as `bash`), several equivalent sample commands are provided.
+For all example, most of special character handling is not specific to `ascli`:
+It depends on the underlying syntax: shell , JSON, etc...
+Depending on the case, a different `format` option is used to display the actual value.
 
 For example, in the simple string `Hello World`, the space character is special for the shell, so it must be escaped so that a single value is represented.
 
@@ -910,9 +938,9 @@ Double quotes are processed by the shell to create a single string argument.
 For **POSIX shells**, single quotes can also be used in this case, or protect the special character ` ` (space) with a backslash. <!-- markdownlint-disable-line -->
 
 ```bash
-ascli conf echo "Hello World" --format=text
-ascli conf echo 'Hello World' --format=text
-ascli conf echo Hello\ World --format=text
+ascli config echo "Hello World" --format=text
+ascli config echo 'Hello World' --format=text
+ascli config echo Hello\ World --format=text
 ```
 
 ```output
@@ -922,14 +950,14 @@ Hello World
 #### Using a shell variable, parsed by shell, in an extended value
 
 To be evaluated by shell, the shell variable must not be in single quotes.
-Even if the variable contains spaces it makes only one argument to `ascli` because word parsing is made before variable expansion by shell.
+Even if the variable contains spaces it results only in one argument for `ascli` because word parsing is made before variable expansion by shell.
 
-> **Note:** we use a shell variable here: the variable is not necessarily an environment variable (`export`).
+> **Note:** We use a shell variable here: the variable is not necessarily an environment variable (`export`).
 
 ```bash
 MYVAR="Hello World"
-ascli conf echo @json:'{"title":"'$MYVAR'"}' --format=json
-ascli conf echo @json:{\"title\":\"$MYVAR\"} --format=json
+ascli config echo @json:'{"title":"'$MYVAR'"}' --format=json
+ascli config echo @json:{\"title\":\"$MYVAR\"} --format=json
 ```
 
 ```json
@@ -942,8 +970,8 @@ Double quote is a shell special character.
 Like any shell special character, it can be protected either by preceding with a backslash or by enclosing in a single quote.
 
 ```bash
-ascli conf echo \"
-ascli conf echo '"'
+ascli config echo \"
+ascli config echo '"'
 ```
 
 ```output
@@ -953,9 +981,9 @@ ascli conf echo '"'
 Double quote in JSON is a little tricky because `"` is special both for the shell and JSON. Both shell and JSON syntax allow to protect `"`, but only the shell allows protection using single quote.
 
 ```bash
-ascli conf echo @json:'"\""' --format=text
-ascli conf echo @json:\"\\\"\" --format=text
-ascli conf echo @ruby:\'\"\' --format=text
+ascli config echo @json:'"\""' --format=text
+ascli config echo @json:\"\\\"\" --format=text
+ascli config echo @ruby:\'\"\' --format=text
 ```
 
 ```output
@@ -988,9 +1016,9 @@ Both `"` and `\` are special characters for JSON and Ruby and can be protected w
 - Then, since the value will be evaluated by shell, any shell special characters must be protected, either using preceding `\` for each character to protect, or by enclosing in single quote:
 
 ```bash
-ascli conf echo @json:{\"title\":\"Test\ \\\"\ \'\ \&\ \\\\\"} --format=json
-ascli conf echo @json:'{"title":"Test \" '\'' & \\"}' --format=json
-ascli conf echo @ruby:"{'title'=>%q{Test \" ' & \\\\}}" --format=json
+ascli config echo @json:{\"title\":\"Test\ \\\"\ \'\ \&\ \\\\\"} --format=json
+ascli config echo @json:'{"title":"Test \" '\'' & \\"}' --format=json
+ascli config echo @ruby:"{'title'=>%q{Test \" ' & \\\\}}" --format=json
 ```
 
 ```json
@@ -1002,7 +1030,7 @@ ascli conf echo @ruby:"{'title'=>%q{Test \" ' & \\\\}}" --format=json
 If `ascli` is used interactively (a user typing on terminal), it is easy to require the user to type values:
 
 ```bash
-ascli conf echo @ruby:"{'title'=>gets.chomp}" --format=json
+ascli config echo @ruby:"{'title'=>gets.chomp}" --format=json
 ```
 
 `gets` is Ruby's method of terminal input (terminated by `\n`), and `chomp` removes the trailing `\n`.
@@ -1012,13 +1040,13 @@ ascli conf echo @ruby:"{'title'=>gets.chomp}" --format=json
 If you need to provide a list of command line argument from lines that are in a file, on Linux you can use the `xargs` command:
 
 ```bash
-xargs -a lines.txt -d \\n ascli conf echo
+xargs -a lines.txt -d \\n ascli config echo
 ```
 
 This is equivalent to execution of:
 
 ```bash
-ascli conf echo [line1] [line2] [line3] ...
+ascli config echo [line1] [line2] [line3] ...
 ```
 
 If there are spaces in the lines, those are not taken as separator, as we provide option `-d \\n` to `xargs`.
@@ -1037,8 +1065,8 @@ Using those values will not require any escaping of characters since values do n
 If the value is to be assigned directly to an option of ascli, then you can directly use the content of the file or env var using the `@file:` or `@env:` readers:
 
 ```bash
-ascli conf echo @file:title.txt --format=text
-ascli conf echo @env:MYTITLE --format=text
+ascli config echo @file:title.txt --format=text
+ascli config echo @env:MYTITLE --format=text
 ```
 
 ```output
@@ -1048,8 +1076,8 @@ Test " ' & \
 If the value to be used is in a more complex structure, then the `@ruby:` modifier can be used: it allows any Ruby code in expression, including reading from file or env var. In those cases, there is no character to protect because values are not parsed by the shell, or JSON or even Ruby.
 
 ```bash
-ascli conf echo @ruby:"{'title'=>File.read('title.txt')}" --format=json
-ascli conf echo @ruby:"{'title'=>ENV['MYTITLE']}" --format=json
+ascli config echo @ruby:"{'title'=>File.read('title.txt')}" --format=json
+ascli config echo @ruby:"{'title'=>ENV['MYTITLE']}" --format=json
 ```
 
 ```json
@@ -1061,11 +1089,11 @@ ascli conf echo @ruby:"{'title'=>ENV['MYTITLE']}" --format=json
 Command line arguments are the units of command line typically separated by spaces (the `argv` of C).
 The tokenization of the command line is typically done by the shell, refer to the previous section [Command Line Parsing](#parsing).
 
-`ascli` considers three types of command line arguments:
+`ascli` handles three types of command line arguments:
 
 - Commands
-- Options
 - Positional Arguments
+- Options
 
 For example:
 
@@ -1073,29 +1101,30 @@ For example:
 ascli command subcommand --option-name=VAL1 VAL2
 ```
 
-- executes **command**: `command subcommand`
-- with one **option**: `option_name` and its **value**: `VAL1`
-- the command has one additional **positional argument**: `VAL2`
+- Executes **command**: `command subcommand`
+- With one **option**: `option_name` and its **value**: `VAL1`
+- The command has one additional **positional argument**: `VAL2`
 
 If the value of a command, option or argument is constrained by a fixed list of values, then it is possible to use a few of the first letters of the value, provided that it uniquely identifies the value.
-For example `ascli conf pre ov` is the same as `ascli config preset overview`.
+For example `ascli config pre ov` is the same as `ascli config preset overview`.
 
 The value of options and arguments is evaluated with the [Extended Value Syntax](#extended).
 
 #### Commands
 
 Commands are typically entity types or verbs to act on those entities.
+Its value is a `String` that must belong to a fixed list of values in a given context.
 
 Example:
 
 ```bash
-ascli conf ascp info
+ascli config ascp info
 ```
 
 - `ascli` is the executable executed by the shell
-- `conf` is the first level command, and is also the name f the plugin to be used
-- `ascp` is the second level command, and is also the name of the component (singleton)
-- `info` is the third level command, and is also the action to be performed
+- `conf` is the first level command: name of the plugin to be used
+- `ascp` is the second level command: name of the component (singleton)
+- `info` is the third level command: action to be performed
 
 Typically, commands are located at the **beginning** of the command line.
 Order is significant.
@@ -1104,20 +1133,37 @@ If wrong, or no command is provided when expected, an error message is displayed
 
 Some sub-commands appear after entity selection, e.g. `ascli aoc admin res node do 8669 browse /`: `browse` is a sub-command of `node`.
 
+#### Positional Arguments
+
+Positional Arguments are typically mandatory values for a command, such as entity creation data.
+
+It could also be designed as an option, but since it is mandatory and typically creation parameters need not be set in a configuration file, then it is better to use a positional argument, and not define specific options.
+
+The advantages of using a positional argument instead of an option for the same are that the command line is shorter(no option name, just the position) and the value is clearly mandatory.
+
+The disadvantage is that it is not possible to define a default value in a configuration file or environment variable like for options.
+Nevertheless, [Extended Values](#extended) syntax is supported, so it is possible to retrieve a value from the configuration file or environment variable (using `@preset:`).
+
+If a Positional Arguments begins with `-`, then either use the `@val:` syntax (see [Extended Values](#extended)), or use the `--` separator (see below).
+
+A few positional arguments are optional, they are located at the end of the command line.
+
 #### Options
 
 All options, e.g. `--log-level=debug`, are command line arguments that:
 
-- start with `--`
-- have a name, in lowercase, using `-` as word separator in name  (e.g. `--log-level=debug`)
-- have a value, separated from name with a `=`
-- can be used by prefix, provided that it is unique. E.g. `--log-l=debug` is the same as `--log-level=debug` (avoid)
+- Start with `--`
+- Have a name, in lowercase, using `-` as word separator in name  (e.g. `--log-level=debug`)
+- Have a value, separated from name with a `=`
+- Can be used by prefix (avoid), provided that it is unique. E.g. `--log-l=debug` is the same as `--log-level=debug`
 
 Exceptions:
 
-- some options accept a short form, e.g. `-Ptoto` is equivalent to `--preset=toto`, refer to the manual or `-h`.
-- some options (flags) don't take a value, e.g. `-N`
-- the special option `--` stops option processing and is ignored, following command line arguments are taken as arguments, including the ones starting with a `-`. Example:
+- Some options accept a short form, e.g. `-Ptoto` is equivalent to `--preset=toto`, refer to the manual or `-h`.
+- Some options (flags) don't take a value, e.g. `-N`
+- The special option `--` stops option processing and is ignored, following command line arguments are taken as arguments, including the ones starting with a `-`.
+
+Example:
 
 ```bash
 ascli config echo -- --sample
@@ -1129,14 +1175,12 @@ ascli config echo -- --sample
 
 > **Note:** Here, `--sample` is taken as an argument, and not as an option, due to `--`.
 
-Options may have an (hardcoded) default value.
-
-Options can be placed anywhere on command line and evaluated in order.
+Options may have a (hardcoded) default value.
 
-Options are typically:
+Options can be placed anywhere on command line and are evaluated in order.
 
-- optional : to change the default behavior
-- mandatory : so they can be placed in a config file, for example: connection information
+Options are typically optional: to change the default behavior.
+But some are mandatory, so they can be placed in a configuration file, for example: connection information.
 
 The value for **any** options can come from the following locations (in this order, last value evaluated overrides previous value):
 
@@ -1146,27 +1190,14 @@ The value for **any** options can come from the following locations (in this ord
 
 Environment variable starting with prefix: ASCLI_ are taken as option values, e.g. `ASCLI_OPTION_NAME` is for `--option-name`.
 
-Options values can be displayed for a given command by providing the `--show-config` option: `ascli node --show-config`
-
-Parameters are typically designed as options if:
-
-- it is a mandatory parameters that would benefit from being set in a config file or environment variable
-- it is optional
+Option `show_config` dry runs the configuration, and then returns currently set values for options.
+`ascli --show-config` outputs global options only, and `ascli [plugin] --show-config` outputs global and plugin default options.
+In addition, option `--show-config` can be added at the end of any full command line, this displays the options that would be used for the command.
 
-#### Positional Arguments
-
-Positional Arguments are typically mandatory values for a command, such as entity creation data.
+A parameter is typically designed as option if:
 
-It could also be designed as an option, but since it is mandatory and typically creation parameters need not be set in a configuration file, then it is better to use a positional argument, and not define specific options.
-
-The advantages of using a positional argument instead of an option for the same are that the command line is shorter(no option name, just the position) and the value is clearly mandatory.
-
-The disadvantage is that it is not possible to define a default value in a config file or environment variable like for options.
-Nevertheless, [Extended Values](#extended) syntax is supported, so it is possible to retrieve a value from the config file or environment variable.
-
-If a Positional Arguments begins with `-`, then either use the `@val:` syntax (see [Extended Values](#extended)), or use the `--` separator (see above).
-
-Very few positional arguments are optional, they are located at the end of the command line.
+- It is optional, or
+- It is a mandatory parameter that would benefit from being set persistently (i.e. in a configuration file or environment variable, e.g. URL and credentials).
 
 ### Interactive Input
 
@@ -1186,6 +1217,8 @@ The behavior can be controlled with:
 Command execution will result in output (terminal, stdout/stderr).
 The information displayed depends on the action.
 
+To redirect results to a file, use option `output`.
+
 #### Types of output data
 
 Depending on action, the output will contain:
@@ -1202,10 +1235,10 @@ Depending on action, the output will contain:
 By default, result of type single_object and object_list are displayed using format `table`.
 The table style can be customized with parameter: `table_style` (horizontal, vertical and intersection characters) and is `:.:` by default.
 
-In a table format, when displaying "objects" (single, or list), by default, sub object are
+In a table format, when displaying **Objects** (single, or list), by default, sub object are
 flattened (option `flat_hash`). So, object `{"user":{"id":1,"name":"toto"}}` will have attributes: `user.id` and `user.name`.
 Setting `flat_hash` to `false` will only display one field: `user` and value is the sub `Hash`.
-When in flatten mode, it is possible to filter fields by "dotted" field name.
+When in flatten mode, it is possible to filter fields by compound field name using dot as separator.
 
 Object lists are displayed one per line, with attributes as columns. Single objects are transposed: one attribute per line.
 If transposition of single object is not desired, use option: `transpose_single` set to `no`.
@@ -1220,17 +1253,6 @@ The style of output can be set using the `format` parameter, supporting:
 - `yaml` : YAML
 - `csv` : Comma Separated Values
 
-#### Entity identifier
-
-When a command is executed on a single entity, the entity is identified by a unique identifier that follows the command: e.g. `ascli aoc admin res user show 1234` where `1234` is the user's identifier.
-
-> **Note:** The legacy option `id` is deprecated: `--id=1234` as it does not provide the possibility to have sub-entities.
-
-Only some commands provide the following capability:
-If the entity can also be uniquely identified by a name, then the name can be used instead of the identifier, using the **percent selector**: `ascli aoc admin res user show %name:john` where `john` is the user name.
-
-Syntax: `%<field>:<value>`
-
 #### Verbosity of output
 
 Output messages are categorized in 3 types:
@@ -1260,9 +1282,9 @@ Elements of the list can be:
 
 - `DEF` : default display of columns (that's the default, when not set)
 - `ALL` : all columns available
-- -property : remove property from the current list
-- property : add property to the current list
-- a ruby `RegEx` : using `@ruby:'/.../'`
+- `-`**property** : remove property from the current list
+- **property** : add property to the current list
+- A Ruby `RegEx` : using `@ruby:'/.../'`
 
 Examples:
 
@@ -1300,6 +1322,20 @@ In above example, the same result is obtained with option:
 --select=@ruby:'->(i){i["ats_admin"]}'
 ```
 
+#### Percent selector
+
+The percent selector allows identification of an entity by another unique identifier other than the native identifier.
+
+When a command is executed on a single entity, the entity is identified by a unique identifier that follows the command:
+e.g. `ascli aoc admin res user show 1234` where `1234` is the user's identifier.
+
+Some commands provide the following capability:
+If the entity can also be uniquely identified by a name, then the name can be used instead of the identifier, using the **percent selector**: `ascli aoc admin res user show %name:john` where `john` is the user name.
+
+Syntax: `%<field>:<value>`
+
+> **Note:** The legacy option `id` is deprecated: `--id=1234` (options have a single value and thus do not provide the possibility to identify sub-entities)
+
 ### <a id="extended"></a>Extended Value Syntax
 
 Most options and arguments are specified by a simple string (e.g. username or url).
@@ -1318,27 +1354,30 @@ Decoders act like a function with its parameter on right hand side and are recog
 
 The following decoders are supported:
 
-| decoder | parameter | returns | description |
-|---------|-----------|---------|-------------|
-| base64  | String    | String  | decode a base64 encoded string
-| `csvt`  | String    | Array   | decode a titled CSV value
-| `env`   | String    | String  | read from a named env var name, e.g. `--password=@env:MYPASSVAR`
-| `file`  | String    | String  | read value from specified file (prefix `~/` is replaced with the users home folder), e.g. `--key=@file:~/.ssh/mykey`
-| `json`  | String    | Any     | decode JSON values (convenient to provide complex structures)
-| `lines` | String    | Array   | split a string in multiple lines and return an array
-| `list`  | String    | Array   | split a string in multiple items taking first character as separator and return an array
-| `none`  | None      | Nil     | A null value
-| `path`  | String    | String  | performs path expansion on specified path (prefix `~/` is replaced with the users home folder), e.g. `--config-file=@path:~/sample_config.yml`
-| preset  | String    | Hash    | get whole option preset value by name. Sub-values can also be used using `.` as separator. e.g. `foo.bar` is `conf[foo][bar]`
-| extend  | String    | String  | evaluates embedded extended value syntax in string
-| `re`    | String    | Regexp  | Ruby Regular Expression (short for `@ruby:/.../`)
-| `ruby`  | String    | Any     | execute specified Ruby code
-| secret  | None      | String  | Ask password interactively (hides input)
-| `stdin` | None      | String  | read from stdin (no value on right)
-| `uri`   | String    | String  | read value from specified URL, e.g. `--fpac=@uri:http://serv/f.pac`
-| `val`   | String    | String  | prevent decoders on the right to be decoded. e.g. `--key=@val:@file:foo` sets the option `key` to value `@file:foo`.
-| `yaml`  | String    | Any     | decode YAML
-| `zlib`  | String    | String  | un-compress data
+| Decoder  | Parameter| Returns | Description |
+|----------|----------|---------|-------------|
+| `base64` | String   | String  | Decode a base64 encoded string |
+| `csvt`   | String   | Array   | Decode a titled CSV value |
+| `env`    | String   | String  | Read from a named env var name, e.g. `--password=@env:MYPASSVAR` |
+| `file`   | String   | String  | Read value from specified file (prefix `~/` is replaced with the users home folder), e.g. `--key=@file:~/.ssh/mykey` |
+| `json`   | String   | Any     | Decode JSON values (convenient to provide complex structures) |
+| `lines`  | String   | Array   | Split a string in multiple lines and return an array |
+| `list`   | String   | Array   | Split a string in multiple items taking first character as separator and return an array |
+| `none`   | None     | Nil     | A null value |
+| `path`   | String   | String  | Performs path expansion on specified path (prefix `~/` is replaced with the users home folder), e.g. `--config-file=@path:~/sample_config.yml` |
+| `preset` | String   | Hash    | Get whole option preset value by name. Sub-values can also be used using `.` as separator. e.g. `foo.bar` is `conf[foo][bar]` |
+| `extend` | String   | String  | Evaluates embedded extended value syntax in string |
+| `re`     | String   | Regexp  | Ruby Regular Expression (short for `@ruby:/.../`) |
+| `ruby`   | String   | Any     | Execute specified Ruby code |
+| `secret` | None     | String  | Ask password interactively (hides input) |
+| `stdin`  | None     | String  | Read from stdin (no value on right) |
+| `uri`    | String   | String  | Read value from specified URL, e.g. `--fpac=@uri:http://serv/f.pac` |
+| `val`    | String   | String  | Prevent decoders on the right to be decoded. e.g. `--key=@val:@file:foo` sets the option `key` to value `@file:foo`. |
+| `yaml`   | String   | Any     | Decode YAML |
+| `zlib`   | String   | String  | Un-compress zlib data |
+
+> **Note:** A few commands support a value of type `Proc` (lambda expression).
+For example, the **Extended Value** `@ruby:'->(i){i["attr"]}'` is a lambda expression that returns the value of attribute `attr` of the `Hash` `i`.
 
 To display the result of an extended value, use the `config echo` command.
 
@@ -1406,7 +1445,7 @@ ascli config echo @json:@extend:'{"hello":true,"version":"@preset:config.version
 Example: Create a `Hash` from YAML provided as **heredoc**:
 
 ```bash
-ascli conf echo @yaml:@stdin: --format=json<<EOF
+ascli config echo @yaml:@stdin: --format=json<<EOF
 key1: value1
 key2:
 - item1
@@ -1528,7 +1567,7 @@ If necessary, the configuration file can opened in a text editor with:
 ascli config open
 ```
 
-> **Note:** this starts the editor specified by env var `EDITOR` if defined.
+> **Note:** This starts the editor specified by env var `EDITOR` if defined.
 
 Older format for commands are still supported:
 
@@ -1568,35 +1607,35 @@ ascli config preset get default _plugin_name_
 
 Plugin `config` provides general commands for `ascli`:
 
-- Option preset, config file operations
-- wizard
-- vault
+- Option preset, configuration file operations
+- `wizard`
+- `vault`
 - `ascp`
 
 The default preset for `config` is read for any plugin invocation, this allows setting global options, such as `--log-level` or `--interactive`.
 When `ascli` starts, it looks for the `default` Option preset and checks the value for `config`.
 If set, it loads the options independently of the plugin used.
 
-> **Note:** If no global default is set by the user, `ascli` will use `global_common_defaults` when setting global parameters (e.g. `conf ascp use`)
+> **Note:** If no global default is set by the user, `ascli` will use `global_common_defaults` when setting global parameters (e.g. `config ascp use`)
 >
 > **Note:** If you don't know the name of the global preset, you can use `GLOBAL` to refer to it.
 
 Show current default (global) Option preset (`config` plugin):
 
 ```console
-$ ascli conf preset get default config
+$ ascli config preset get default config
 global_common_defaults
 ```
 
 ```bash
-ascli conf preset set GLOBAL version_check_days 0
+ascli config preset set GLOBAL version_check_days 0
 ```
 
 If the default global Option preset is not set, and you want to use a different name:
 
 ```bash
-ascli conf preset set my_common_defaults version_check_days 0
-ascli conf preset set default config my_common_defaults
+ascli config preset set GLOBAL version_check_days 0
+ascli config preset set default config my_common_defaults
 ```
 
 #### Config sample commands
@@ -1619,6 +1658,7 @@ config ascp use /usr/bin/ascp
 config check_update
 config coffee
 config coffee --ui=text
+config coffee --ui=text --query=@json:'{"text":"true"}'
 config detect https://faspex4.example.com/path
 config detect https://faspex5.example.com/path
 config detect https://node.example.com/path
@@ -1626,6 +1666,7 @@ config detect https://shares.example.com/path shares
 config detect my_org aoc
 config doc
 config doc transfer-parameters
+config echo -- --special-string
 config echo @base64:SGVsbG8gV29ybGQK
 config echo @csvt:@stdin:
 config echo @env:USER
@@ -1661,6 +1702,7 @@ config preset show conf_name
 config preset unset conf_name param
 config preset update conf_name --p1=v1 --p2=v2
 config proxy_check --fpac=@file:examples/proxy.pac https://eudemo.asperademo.com --proxy-credentials=@list:,user,pass
+config pubkey @file:my_key
 config vault create my_label @json:'{"password":"my_password_here","description":"my secret"}'
 config vault delete my_label
 config vault list
@@ -1671,8 +1713,8 @@ config wizard https://faspex5.example.com/path faspex5 --key-path=my_private_key
 config wizard https://node.example.com/path node --username=test --password=test
 config wizard https://orch.example.com/path orchestrator --username=test --password=test
 config wizard https://shares.example.com/path shares --username=test --password=test
-config wizard my_org aoc --key-path= --username=my_user_email
-config wizard my_org aoc --key-path= --username=my_user_email --use-generic-client=yes
+config wizard my_org aoc --key-path=my_private_key --username=my_user_email
+config wizard my_org aoc --key-path=my_private_key --username=my_user_email --use-generic-client=yes
 ```
 
 #### Format of file
@@ -1696,9 +1738,9 @@ demo_server:
 We can see here:
 
 - The configuration was created with `ascli` version 0.3.7
-- the default [option preset](#lprt) to load for `server` plugin is : `demo_server`
-- the [option preset](#lprt) `demo_server` defines some parameters: the URL and credentials
-- the default [option preset](#lprt) to load in any case is : `cli_default`
+- The default [option preset](#lprt) to load for `server` plugin is : `demo_server`
+- The [option preset](#lprt) `demo_server` defines some parameters: the URL and credentials
+- The default [option preset](#lprt) to load in any case is : `cli_default`
 
 Two [option presets](#lprt) are reserved:
 
@@ -1710,7 +1752,7 @@ The user may create as many [option presets](#lprt) as needed. For instance, a p
 
 Values in the configuration also follow the [Extended Value Syntax](#extended).
 
-> **Note:** if the user wants to use the [Extended Value Syntax](#extended) inside the configuration file, using the `config preset update` command, the user shall use the `@val:` prefix. Example:
+> **Note:** If the user wants to use the [Extended Value Syntax](#extended) inside the configuration file, using the `config preset update` command, the user shall use the `@val:` prefix. Example:
 
 ```bash
 ascli config preset set my_aoc_org private_key @val:@file:"$HOME/.aspera/ascli/my_private_key"
@@ -1719,10 +1761,8 @@ ascli config preset set my_aoc_org private_key @val:@file:"$HOME/.aspera/ascli/m
 This creates the [option preset](#lprt):
 
 ```yaml
-...
 my_aoc_org:
-  private_key: @file:"/Users/laurent/.aspera/ascli/my_private_key"
-...
+  private_key: "@file:/Users/laurent/.aspera/ascli/my_private_key"
 ```
 
 So, the key file will be read only at execution time, but not be embedded in the configuration file.
@@ -1734,7 +1774,7 @@ Some options are global, some options are available only for some plugins. (the
 Options are loaded using this algorithm:
 
 - If option `--no-default` (or `-N`) is specified, then no default value is loaded for the plugin
-- else it looks for the name of the plugin as key in section `default`, the value is the name of the default [option preset](#lprt) for it, and loads it.
+- Else it looks for the name of the plugin as key in section `default`, the value is the name of the default [option preset](#lprt) for it, and loads it.
 - If option `--preset=<name or extended value hash>` is specified (or `-Pxxxx`), this reads the [option preset](#lprt) specified from the configuration file, or if the value is a `Hash`, it uses it as options values.
 - Environment variables are evaluated
 - Command line options are evaluated
@@ -1743,8 +1783,9 @@ Parameters are evaluated in the order of command line.
 
 To avoid loading the default [option preset](#lprt) for a plugin, use: `-N`
 
-On command line, words in parameter names are separated by a dash, in configuration file, separator
-is an underscore. E.g. --xxx-yyy  on command line gives xxx_yyy in configuration file.
+On command line, words in parameter names are separated by a dash (`-`).
+In configuration file, separator is an underscore.
+E.g. `--xxx-yyy` on command line gives `xxx_yyy` in configuration file.
 
 The main plugin name is `config`, so it is possible to define a default [option preset](#lprt) for the main plugin with:
 
@@ -1789,14 +1830,14 @@ ascli config wizard
 #### Example of configuration for a plugin
 
 For Faspex, Shares, Node (including ATS, Aspera Transfer Service), Console,
-only username/password and url are required (either on command line, or from config file).
+only username/password and url are required (either on command line, or from configuration file).
 Those can usually be provided on the command line:
 
 ```bash
 ascli shares repo browse / --url=https://10.25.0.6 --username=john --password=my_password_here
 ```
 
-This can also be provisioned in a config file:
+This can also be provisioned in a configuration file:
 
 - Build [option preset](#lprt)
 
@@ -1838,25 +1879,46 @@ ascli shares repo browse /
 
 ### <a id="vault"></a>Secret Vault
 
-Password and secrets are command options.
+Secrets (e.g. passwords) are usually command options.
 They can be provided on command line, env vars, files etc.
-A more secure option is to retrieve values from a secret vault.
+
+For security reasons, those secrets shall not be exposed in clear, either:
+
+- On terminal during input
+- In logs
+- In command output
+
+Instead, they shall be hidden or encrypted.
+
+Terminal output secret removal is controlled by option `show_secrets` (default: `no`).
+Log secret removal is controlled by option `log_secrets` (default: `no`).
+Mandatory command line options can be requested interactively (e.g. password) using option `interactive`.
+Or it is possible to use extended value `@secret:[name]` to ask for a secret interactively.
+It is also possible to enter an option as an environment variable, e.g. `ASCLI_PASSWORD` for option `password` and read the env var  like this:
+
+```bash
+read -s ASCLI_PASSWORD
+export ASCLI_PASSWORD
+```
+
+Another possibility is to retrieve values from a secret vault.
 
 The vault is used with options `vault` and `vault_password`.
 
-`vault` defines the vault to be used and shall be a `Hash`, example:
+`vault` shall be a `Hash` describing the vault:
 
 ```json
 {"type":"system","name":"ascli"}
 ```
 
 `vault_password` specifies the password for the vault.
-Although it can be specified on command line, for security reason you can hide the value.
+
+Although it can be specified on command line, for security reason you should avoid exposing the secret.
 For example it can be securely specified on command line like this:
 
 ```bash
-export ASCLI_VAULT_PASSWORD
 read -s ASCLI_VAULT_PASSWORD
+export ASCLI_VAULT_PASSWORD
 ```
 
 #### Vault: System key chain
@@ -1871,13 +1933,13 @@ It is possible to manage secrets in macOS key chain (only read supported current
 
 #### Vault: Encrypted file
 
-It is possible to store and use secrets encrypted in a file.
+It is possible to store and use secrets encrypted in a file using option `vault` set to:
 
-```bash
---vault=@json:'{"type":"file","name":"vault.bin"}'
+```json
+{"type":"file","name":"vault.bin"}
 ```
 
-`name` is the file path, absolute or relative to the config folder `ASCLI_HOME`.
+`name` is the file path, absolute or relative to the configuration folder `ASCLI_HOME`.
 
 #### Vault: Operations
 
@@ -1891,12 +1953,12 @@ Then secrets can be manipulated using commands:
 - `delete`
 
 ```bash
-ascli conf vault create mylabel @json:'{"password":"my_password_here","description":"for this account"}'
+ascli config vault create mylabel @json:'{"password":"my_password_here","description":"for this account"}'
 ```
 
 #### <a id="config_finder"></a>Configuration Finder
 
-When a secret is needed by a sub command, the command can search for existing configurations in the config file.
+When a secret is needed by a sub command, the command can search for existing configurations in the configuration file.
 
 The lookup is done by comparing the service URL and username (or access key).
 
@@ -1906,20 +1968,20 @@ A passwords can be saved in clear in a [option preset](#lprt) together with othe
 Example:
 
 ```bash
-ascli conf preset update myconf --url=... --username=... --password=...
+ascli config preset update myconf --url=... --username=... --password=...
 ```
 
 For a more secure storage one can do:
 
 ```bash
-ascli conf preset update myconf --url=... --username=... --password=@val:@vault:myconf.password
+ascli config preset update myconf --url=... --username=... --password=@val:@vault:myconf.password
 ```
 
 ```bash
-ascli conf vault create myconf @json:'{"password":"my_password_here"}'
+ascli config vault create myconf @json:'{"password":"my_password_here"}'
 ```
 
-> **Note:** use `@val:` in front of `@vault:` so that the extended value is not evaluated.
+> **Note:** Use `@val:` in front of `@vault:` so that the extended value is not evaluated.
 
 ### <a id="private_key"></a>Private Key
 
@@ -1955,10 +2017,16 @@ ascli config genkey ${PRIVKEYFILE} 4096
 
 > **Note:** `ascli` uses the `openssl` library.
 
+To display the public key of a private key:
+
+```bash
+ascli config pubkey @file:${PRIVKEYFILE}
+```
+
 To display the version of **openssl** used in `ascli`:
 
 ```bash
-ascli config echo @ruby:OpenSSL::OPENSSL_VERSION
+ascli config echo @ruby:OpenSSL::OPENSSL_VERSION --format=text
 ```
 
 #### `ssh-keygen`
@@ -2014,8 +2082,8 @@ Ruby's default values can be overridden using env vars: `SSL_CERT_FILE` and `SSL
 > **Note:** One can display those values like this:
 
 ```bash
-ascli conf echo @ruby:OpenSSL::X509::DEFAULT_CERT_DIR --format=text
-ascli conf echo @ruby:OpenSSL::X509::DEFAULT_CERT_FILE --format=text
+ascli config echo @ruby:OpenSSL::X509::DEFAULT_CERT_DIR --format=text
+ascli config echo @ruby:OpenSSL::X509::DEFAULT_CERT_FILE --format=text
 ```
 
 `ascp` also needs to validate certificates when using **WSS**.
@@ -2023,13 +2091,13 @@ ascli conf echo @ruby:OpenSSL::X509::DEFAULT_CERT_FILE --format=text
 > **Note:** `ascli` overrides the default hardcoded location used by `ascp` for WSS (e.g. on macOS: `/Library/Aspera/ssl`) and uses the same locations as specified in `cert_stores` (using `-i` switch of `ascp`). Hardcoded locations can be found using:
 
 ```bash
-strings $(ascli conf ascp info --fields=ascp)|grep -w OPENSSLDIR
+ascli config ascp info --fields=openssldir
 ```
 
 or
 
 ```bash
-ascli conf ascp info --fields=openssldir
+strings $(ascli config ascp info --fields=ascp)|grep -w OPENSSLDIR
 ```
 
 To update trusted root certificates for `ascli`:
@@ -2039,29 +2107,29 @@ Typically done by updating the system's root certificate store.
 An up-to-date version of the certificate bundle can be retrieved with:
 
 ```bash
-ascli conf echo @uri:https://curl.haxx.se/ca/cacert.pem --format=text
+ascli config echo @uri:https://curl.haxx.se/ca/cacert.pem --format=text
 ```
 
 To download that certificate store:
 
 ```bash
-ascli conf echo @uri:https://curl.haxx.se/ca/cacert.pem --format=text > /tmp/cacert.pem
+ascli config echo @uri:https://curl.haxx.se/ca/cacert.pem --format=text > /tmp/cacert.pem
 ```
 
-Then, use this store by setting the  option `` or env var export SSL_CERT_FILE
+Then, use this store by setting the  option `cert_stores` or env var `SSL_CERT_FILE`.
 
-To trust a certificate (e.g. self-signed), provided that the `CN` is correct, save the certificate to a file:
+To trust a specific certificate (e.g. self-signed), **provided that the `CN` is correct**, save the certificate to a file:
 
 ```bash
-ascli conf remote_certificate https://localhost:9092 > myserver.pem
+ascli config remote_certificate https://localhost:9092 > myserver.pem
 ```
 
-> **Note:** the saved certificate shows the CN as first line.
+> **Note:** The saved certificate shows the CN as first line.
 
 Then, use this file as certificate store (e.g. here, Node API):
 
 ```bash
-ascli conf echo @uri:https://localhost:9092/ping --cert-stores=myserver.pem
+ascli config echo @uri:https://localhost:9092/ping --cert-stores=myserver.pem
 ```
 
 ### Image and video thumbnails
@@ -2072,18 +2140,18 @@ It's also available when using the `show` command of `preview` plugin.
 
 The following options can be specified in the option `query`:
 
-| option     | description |
+| Option     | Description |
 |------------|-------------|
-| text       | display text instead of image (Bool) |
-| double     | display double text resolution (half characters) (Bool) |
+| text       | Display text instead of image (Bool) |
+| double     | Display double text resolution (half characters) (Bool) |
 | font_ratio | Font height/width ratio in terminal (Float) |
 
 ### <a id="graphical"></a>Graphical Interactions: Browser and Text Editor
 
 Some actions may require the use of a graphical tool:
 
-- a browser for Aspera on Cloud authentication (web auth method)
-- a text editor for configuration file edition
+- A browser for Aspera on Cloud authentication (web auth method)
+- A text editor for configuration file edition
 
 By default `ascli` assumes that a graphical environment is available on Windows, and on other systems, rely on the presence of the `DISPLAY` environment variable.
 It is also possible to force the graphical mode with option --ui :
@@ -2110,16 +2178,16 @@ Available levels: `debug`, `info`, `warn`, `error`.
 
 Examples:
 
-- display debugging log on `stdout`:
+- Display debugging log on `stdout`:
 
 ```bash
-ascli conf pre over --log-level=debug --logger=stdout
+ascli config pre over --log-level=debug --logger=stdout
 ```
 
-- log errors to `syslog`:
+- Log errors to `syslog`:
 
 ```bash
-ascli conf pre over --log-level=error --logger=syslog
+ascli config pre over --log-level=error --logger=syslog
 ```
 
 When `ascli` is used interactively in a shell, the shell itself will usually log executed commands in the history file.
@@ -2135,14 +2203,18 @@ It will display the exact content of HTTP requests and responses.
 
 ### <a id="http_options"></a>HTTP socket parameters
 
-To ignore SSL certificate for any address/port, use option: `insecure`, i.e. `--insecure=yes`.
-To ignore SSL certificate for specific address/port, use option `ignore_certificate`, set to an `Array` of URL for which certificate will be ignored (only the address and port are matched), e.g. `--ignore-certificate=@list:,https://127.0.0.1:9092`
+To ignore SSL certificate for **any** address/port, use option: `insecure`, i.e. `--insecure=yes`.
+To ignore SSL certificate for a list of specific address/port, use option `ignore_certificate`, set to an `Array` of URL for which certificate will be ignored (only the address and port are matched), e.g. `--ignore-certificate=@list:,https://127.0.0.1:9092`
 
 > **Note:** Ignoring certificate also applies to `ascp`'s wss.
 
+Ignoring a certificate is not recommended, it is better to add the certificate to the trusted store.
+So, a warning is displayed when a certificate is ignored.
+To disable the warning, use option `silent_insecure` set to `no`.
+
 HTTP connection parameters (not `ascp` wss) can be adjusted using option `http_options`:
 
-| parameter            | default |
+| Parameter            | Default |
 |----------------------|---------|
 | `read_timeout`       | 60      |
 | `write_timeout`      | 60      |
@@ -2153,7 +2225,7 @@ Values are in set **seconds** and can be of type either integer or float.
 Default values are the ones of Ruby:
 For a full list, refer to the Ruby library: [`Net::HTTP`](https://ruby-doc.org/stdlib/libdoc/net/http/rdoc/Net/HTTP.html).
 
-Like any other option, those can be set either on command line, or in config file, either in a global preset or server-specific one.
+Like any other option, those can be set either on command line, or in configuration file, either in a global preset or server-specific one.
 
 Example:
 
@@ -2165,13 +2237,15 @@ ascli aoc admin res package list --http-options=@json:'{"read_timeout":10.0}'
 
 There are several types of network connections, each of them use a different mechanism to define a (forward) **proxy**:
 
-- Ruby HTTP: REST and HTTP Gateway client
-- Legacy Aspera HTTP/S Fallback and `ascp` wss
-- Aspera FASP
+- REST calls (APIs) and HTTP Gateway
+- `ascp` WSS and Legacy Aspera HTTP/S Fallback
+- `ascp` SSH and UDP (Aspera FASP)
 
 Refer to the following sections.
 
-### Proxy for REST and HTTP Gateway
+#### Proxy for REST and HTTP Gateway
+
+REST API calls and transfers based on HTTP Gateway both use Ruby `Net::HTTP` gem.
 
 There are two possibilities to define an HTTP proxy to be used when Ruby HTTP is used.
 
@@ -2185,7 +2259,7 @@ Refer to [Ruby find proxy](https://rubyapi.org/3.0/o/uri/generic#method-i-find_p
 export http_proxy=http://proxy.example.com:3128
 ```
 
-The `fpac` option (function for proxy auto config) can be set to a [Proxy Auto Configuration (PAC)](https://en.wikipedia.org/wiki/Proxy_auto-config) javascript value.
+Alternatively, the `fpac` option (function for proxy auto config) can be set to a [Proxy Auto Configuration (PAC)](https://en.wikipedia.org/wiki/Proxy_auto-config) javascript value.
 To read the script from a URL (`http:`, `https:` and `file:`), use prefix: `@uri:`.
 A minimal script can be specified to define the use of a local proxy:
 
@@ -2197,7 +2271,7 @@ The result of a PAC file can be tested with command: `config proxy_check`.
 Example, using command line option:
 
 ```bash
-ascli conf proxy_check --fpac='function FindProxyForURL(url, host) {return "PROXY proxy.example.com:3128;DIRECT";}' http://example.com
+ascli config proxy_check --fpac='function FindProxyForURL(url, host) {return "PROXY proxy.example.com:3128;DIRECT";}' http://example.com
 ```
 
 ```text
@@ -2230,11 +2304,11 @@ ascli --proxy-credentials=@json:'["__username_here__","__password_here__"]' ...
 ascli --proxy-credentials=@list::__username_here__:__password_here__ ...
 ```
 
-### Proxy for Legacy Aspera HTTP/S Fallback
+#### Proxy for Legacy Aspera HTTP/S Fallback
 
 Only supported with the `direct` agent: To specify a proxy for legacy HTTP fallback, use `ascp` native option `-x` and `ascp_args`: `--transfer-info=@json:'{"ascp_args":["-x","url_here"]}'`. Alternatively, set the [*transfer-spec*](#transferspec) parameter: `EX_http_proxy_url`.
 
-### FASP proxy (forward) for transfers
+#### FASP proxy (forward) for transfers
 
 To specify a FASP proxy (forward), set the [*transfer-spec*](#transferspec) parameter: `proxy` (only supported with the `direct` agent).
 
@@ -2244,9 +2318,9 @@ The `config` plugin also allows specification for the use of a local FASP **clie
 It provides the following commands for `ascp` subcommand:
 
 - `show` : shows the path of `ascp` used
-- `use` : list,download connect client versions available on internet
+- `use` : specify the ascp path to use
 - `products` : list Aspera transfer products available locally
-- `connect` : list,download connect client versions available on internet
+- `connect` : list and download connect client versions available on internet
 
 #### Show path of currently used `ascp`
 
@@ -2272,7 +2346,7 @@ ascli config ascp info
 
 #### Selection of `ascp` location for [`direct`](#agt_direct) agent
 
-By default, `ascli` uses any found local product with `ascp`, including SDK.
+By default, `ascli` uses any found local product with `ascp`, including Transfer SDK.
 
 To temporarily use an alternate `ascp` path use option `ascp_path` (`--ascp-path=`)
 
@@ -2327,7 +2401,7 @@ ascli config ascp products list
 
 If no `ascp` is selected, this is equivalent to using option: `--use-product=FIRST`.
 
-Using the option use_product finds the `ascp` binary of the selected product.
+Using the option `use_product` finds the `ascp` binary of the selected product.
 
 To permanently use the `ascp` of a product:
 
@@ -2395,7 +2469,7 @@ There are currently 3 agents, set with option `transfer`:
 - [`trsdk`](#agt_trsdk) : use of Aspera Transfer SDK
 
 > **Note:** All transfer operations are seen from the point of view of the agent.
-For example, a node agent executing an "upload", or "package send" operation
+For example, a node agent executing an **upload**, or **package send** operation
 will effectively push files to the related server from the agent node.
 
 `ascli` standardizes on the use of a [*transfer-spec*](#transferspec) instead of **native** `ascp` options to provide parameters for a transfer session, as a common method for those three Transfer Agents.
@@ -2405,25 +2479,24 @@ Specific options for agents are provided with option `transfer_info`, cumulative
 #### <a id="agt_direct"></a>Direct
 
 The `direct` agent directly executes a local `ascp`.
-This is the default agent for `ascli`.
-This is equivalent to option `--transfer=direct`.
+This is the default agent for `ascli` (option `--transfer=direct`).
 `ascli` will search locally installed Aspera products, including SDK, and use `ascp` from that component.
 Refer to section [FASP](#client).
 
 The `transfer_info` option accepts the following optional parameters to control multi-session, Web Socket Session and Resume policy:
 
-| Name                 | Type  | Description |
-|----------------------|-------|-------------|
-| `wss`                | Bool  | Web Socket Session<br/>Enable use of web socket session in case it is available<br/>Default: true |
-| `ascp_args`          | Array | Array of strings with native `ascp` arguments<br/>Use this instead of deprecated `EX_ascp_args`.<br/>Default: [] |
-| `spawn_timeout_sec`  | Float | Multi session<br/>Verification time that `ascp` is running<br/>Default: 3 |
-| `spawn_delay_sec`    | Float | Multi session<br/>Delay between startup of sessions<br/>Default: 2 |
-| `multi_incr_udp`     | Bool  | Multi Session<br/>Increment UDP port on multi-session<br/>If true, each session will have a different UDP port starting at `fasp_port` (or default 33001)<br/>Else, each session will use `fasp_port` (or `ascp` default)<br/>Default: true |
-| `resume`             | Hash  | Resume<br/>parameters<br/>See below |
-| `resume.iter_max`    | int   | Resume<br/>Max number of retry on error<br/>Default: 7 |
+| Name                   | Type  | Description |
+|------------------------|-------|-------------|
+| `wss`                  | Bool  | Web Socket Session<br/>Enable use of web socket session in case it is available<br/>Default: true |
+| `ascp_args`            | Array | Array of strings with native `ascp` arguments<br/>Use this instead of deprecated `EX_ascp_args`.<br/>Default: [] |
+| `spawn_timeout_sec`    | Float | Multi session<br/>Verification time that `ascp` is running<br/>Default: 3 |
+| `spawn_delay_sec`      | Float | Multi session<br/>Delay between startup of sessions<br/>Default: 2 |
+| `multi_incr_udp`       | Bool  | Multi Session<br/>Increment UDP port on multi-session<br/>If true, each session will have a different UDP port starting at `fasp_port` (or default 33001)<br/>Else, each session will use `fasp_port` (or `ascp` default)<br/>Default: true |
+| `resume`               | Hash  | Resume<br/>parameters<br/>See below |
+| `resume.iter_max`      | int   | Resume<br/>Max number of retry on error<br/>Default: 7 |
 | `resume.sleep_initial` | int   | Resume<br/>First Sleep before retry<br/>Default: 2 |
 | `resume.sleep_factor`  | int   | Resume<br/>Multiplier of sleep period between attempts<br/>Default: 2 |
-| `resume.sleep_max`   | int   | Resume<br/>Default: 60 |
+| `resume.sleep_max`     | int   | Resume<br/>Default: 60 |
 
 In case of transfer interruption, the agent will **resume** a transfer up to `iter_max` time.
 Sleep between iterations is:
@@ -2493,7 +2566,7 @@ asconfigurator -x 'set_node_data;transfer_in_bandwidth_aggregate_trunk_id,1'
 asconfigurator -x 'set_node_data;transfer_out_bandwidth_aggregate_trunk_id,2'
 ```
 
-But this command is not available on clients, so edit the file `aspera.conf`, you can find the location with: `ascli conf ascp info --fields=aspera_conf` and modify the sections `default` and `trunks` like this for a global 100 Mbps virtual link:
+But this command is not available on clients, so edit the file `aspera.conf`, you can find the location with: `ascli config ascp info --fields=aspera_conf` and modify the sections `default` and `trunks` like this for a global 100 Mbps virtual link:
 
 ```xml
 <?xml version='1.0' encoding='UTF-8'?>
@@ -2555,9 +2628,9 @@ Parameters provided in option `transfer_info` are:
 | Name     | Type   | Description |
 |----------|--------|-------------|
 | url      | string | URL of the node API</br>Mandatory |
-| username | string | node api user or access key</br>Mandatory |
-| password | string | password, secret or bearer token</br>Mandatory |
-| root_id  | string | password or secret</br>Mandatory only for bearer token |
+| username | string | Node api user or access key</br>Mandatory |
+| password | string | Password, secret or bearer token</br>Mandatory |
+| root_id  | string | Root file id</br>Mandatory only for bearer token |
 
 Like any other option, `transfer_info` can get its value from a pre-configured [option preset](#lprt) :
 
@@ -2585,9 +2658,9 @@ Parameters provided in option `transfer_info` are:
 | Name                   | Type   | Description                           |
 |------------------------|--------|---------------------------------------|
 | url                    | string | URL of the HTTP GW</br>Mandatory      |
-| upload_chunk_size      | int    | Size in bytes of chunks for upload<br/>Default: 64000    |
-| api_version            | string | v1 or v2, for force use of version<br/>Default: v2       |
-| synchronous            | bool   | wait for each message acknowledgment<br/>Default: false  |
+| upload_chunk_size      | int    | Size in bytes of chunks for upload<br/>Default: `64000`    |
+| api_version            | string | Force use of version (`v1`, `v2`)<br/>Default: `v2`       |
+| synchronous            | bool   | Wait for each message acknowledgment<br/>Default: `false`  |
 
 Example:
 
@@ -2606,11 +2679,11 @@ Options for `transfer_info` are:
 
 | Name     | Type   | Description |
 |----------|--------|-------------|
-| url      | string | IP address and port listened by the daemon</br>Mandatory<br/>Default: grpc://127.0.0.1:0 |
-| external | bool   | Use external daemon, do not start<br/>Default: false |
-| keep     | bool   | Keep the daemon running after exiting `ascli`<br/>Default: false |
+| `url`      | string | IP address and port listened by the daemon</br>Mandatory<br/>Default: `:0` |
+| `external` | bool   | Use external daemon, do not start<br/>Default: `false` |
+| `keep`     | bool   | Keep the daemon running after exiting `ascli`<br/>Default: `false` |
 
-> **Note:** if port zero is specified in the URL, then the daemon will listen on a random available port.
+> **Note:** If port zero is specified in the URL, then the daemon will listen on a random available port. If no address is specified, then `127.0.0.1` is used.
 
 The gem `grpc` was removed from dependencies, as it requires compilation of a native part.
 So, to use the Transfer SDK you should install this gem:
@@ -2638,11 +2711,11 @@ On Windows the compilation may fail for various reasons (3.1.1):
 Some commands lead to file transfer (upload/download).
 All parameters necessary for this transfer are described in a [*transfer-spec*](#transferspec) (Transfer Specification), such as:
 
-- server address
-- transfer user name
-- credentials
-- file list
-- etc...
+- Server address
+- Transfer user name
+- Credentials
+- File list
+- Etc...
 
 `ascli` builds the [*transfer-spec*](#transferspec) internally as a `Hash`.
 It is not necessary to provide additional parameters on the command line for this transfer.
@@ -2660,13 +2733,13 @@ This is especially useful for `ascp` command line parameters not supported in th
 
 The use of a [*transfer-spec*](#transferspec) instead of `ascp` parameters has the advantage of:
 
-- common to all [Transfer Agent](#agents)
-- not dependent on command line limitations (special characters...)
+- Common to all [Transfer Agent](#agents)
+- Not dependent on command line limitations (special characters...)
 
 ### <a id="transferparams"></a>Transfer Parameters
 
 All standard [*transfer-spec*](#transferspec) parameters can be specified.
-[*transfer-spec*](#transferspec) can also be saved/overridden in the config file.
+[*transfer-spec*](#transferspec) can also be saved/overridden in the configuration file.
 
 References:
 
@@ -2830,9 +2903,9 @@ So, by default, the list of files to transfer will be simply specified on the co
   ascli server upload --sources=@args --src-type=list ~/mysample.file secondfile
   ```
 
-- an [Extended Value](#extended) with type **Array of String**
+- An [Extended Value](#extended) with type **Array of String**
 
-  > **Note:** extended values can be tested with the command `conf echo`
+  > **Note:** extended values can be tested with the command `config echo`
 
   Examples:
 
@@ -2903,10 +2976,10 @@ The transfer destination is normally expected to designate a destination folder.
 
 But there is one exception: The destination specifies the new item name when the following are met:
 
-- there is a single source item (file or folder)
-- transfer spec `create_dir` is not set to `true` (`ascp` option `-d` not provided)
-- destination is not an existing folder
-- the `dirname` of destination is an existing folder
+- There is a single source item (file or folder)
+- Transfer spec `create_dir` is not set to `true` (`ascp` option `-d` not provided)
+- Destination is not an existing folder
+- The `dirname` of destination is an existing folder
 
 For this reason it is recommended to set `create_dir` to `true` for consistent behavior between single and multiple items transfer, this is the default in `ascli`.
 
@@ -3054,7 +3127,7 @@ For example, on Linux it is convenient to create a wrapping script, e.g. `cron_a
 
 ```bash
 #!/bin/bash
-# load the ruby environment
+# load the Ruby environment
 . /etc/profile.d/rvm.sh
 rvm use 2.6 --quiet
 # set a timeout protection, just in case ascli is frozen 
@@ -3072,7 +3145,7 @@ crontab<<EOF
 EOF
 ```
 
-> **Note:** The logging options are kept here in the cron file instead of conf file to allow execution on command line with output on command line.
+> **Note:** Logging options are kept here in the cron file instead of configuration file to allow execution on command line with output on command line.
 
 ### <a id="locking"></a>Locking for exclusive execution
 
@@ -3119,7 +3192,7 @@ Several **PVCL** adapters are available, one is embedded in `ascp`, the others a
 The list of supported **PVCL** adapters can be retrieved with command:
 
 ```bash
-ascli conf ascp info --fields=@re:'^pvcl'
+ascli config ascp info --fields=@re:'^pvcl'
 ```
 
 ```output
@@ -3135,7 +3208,7 @@ stdio-tar v1
 Here we can see the adapters: `process`, `shares`, `noded`, `faux`, `file`, `stdio`, `stdio-tar`.
 
 Those adapters can be used wherever a file path is used in `ascp` including configuration.
-They act as a pseudo "drive".
+They act as a **pseudo drive**.
 
 The simplified format is:
 
@@ -3166,7 +3239,7 @@ where:
 - `filename` is the name that will be assigned to the file on the destination
 - `filesize` is the number of bytes that will be sent (in decimal).
 
-> **Note:** characters `?` and `&` are shell special characters (wildcard and background), so `faux` file specification on command line should be protected (using quotes or `\`). If not, the shell may give error: `no matches found` or equivalent.
+> **Note:** Characters `?` and `&` are shell special characters (wildcard and background), so `faux` file specification on command line should be protected (using quotes or `\`). If not, the shell may give error: `no matches found` or equivalent.
 
 For all sizes, a suffix can be added (case insensitive) to the size: k,m,g,t,p,e (values are power of 2, e.g. 1M is 2<sup>20</sup>, i.e. 1 mebibyte, not megabyte). The maximum allowed value is 8*2<sup>60</sup>. Very large `faux` file sizes (petabyte range and above) will likely fail due to lack of destination storage unless destination is `faux://`.
 
@@ -3179,12 +3252,12 @@ faux:///dirname?<arg1>=<val1>&...
 where:
 
 - `dirname` is the folder name and can contain `/` to specify a subfolder.
-- supported arguments are:
+- Supported arguments are:
 
 | Name   | Type | Description |
 |--------|------|-------------|
-|count   |int   |mandatory|Number of files<br/>Mandatory|
-|file    |string|Basename for files<br>Default: "file"|
+|count   |int   |Number of files<br/>Mandatory|
+|file    |string|Basename for files<br>Default: `file`|
 |size    |int   |Size of first file.<br>Default: 0|
 |inc     |int   |Increment applied to determine next file size<br>Default: 0|
 |seq     |enum  |Sequence in determining next file size<br/>Values: random, sequential<br/>Default: sequential|
@@ -3233,7 +3306,7 @@ ascli server upload "faux:///mydir?file=testfile&count=1m&size=0&inc=2&seq=seque
 ```text
 ascli -h
 NAME
-        ascli -- a command line tool for Aspera Applications (v4.15.0)
+        ascli -- a command line tool for Aspera Applications (v4.16.0)
 
 SYNOPSIS
         ascli COMMANDS [OPTIONS] [ARGS]
@@ -3265,6 +3338,7 @@ OPTIONS: global
         --interactive=ENUM           Use interactive input of missing params: [no], yes
         --ask-options=ENUM           Ask even optional options: [no], yes
         --format=ENUM                Output format: text, nagios, ruby, json, jsonpp, yaml, [table], csv
+        --output=VALUE               Destination for results (String)
         --display=ENUM               Output only some information: [info], data, error
         --fields=VALUE               Comma separated list of: fields, or ALL, or DEF (String, Array, Regexp, Proc)
         --select=VALUE               Select only some items in lists: column, value (Hash, Proc)
@@ -3287,7 +3361,7 @@ OPTIONS: global
         --pid-file=VALUE             Write process identifier to file, delete on exit (String)
 
 COMMAND: config
-SUBCOMMANDS: ascp check_update coffee detect documentation echo email_test file flush_tokens folder gem genkey initdemo open plugins preset proxy_check remote_certificate smtp_settings throw vault wizard
+SUBCOMMANDS: ascp check_update coffee detect documentation echo email_test file flush_tokens folder gem genkey initdemo open plugins preset proxy_check pubkey remote_certificate smtp_settings throw vault wizard
 OPTIONS:
         --home=VALUE                 Home folder for tool (String)
         --config-file=VALUE          Path to YAML file with preset configuration
@@ -3317,7 +3391,8 @@ OPTIONS:
         --notify-to=VALUE            Email recipient for notification of transfers
         --notify-template=VALUE      Email ERB template for notification of transfers
         --insecure=ENUM              Do not validate any HTTPS certificate: [no], yes
-        --ignore-certificate=VALUE   List of HTTPS url where to no validate certificate (Array)
+        --ignore-certificate=VALUE   Do not validate HTTPS certificate for these URLs (Array)
+        --silent-insecure=ENUM       Issue a warning if certificate is ignored: no, [yes]
         --cert-stores=VALUE          List of folder with trusted certificates (Array, String)
         --http-options=VALUE         Options for HTTP/S socket (Hash)
         --cache-tokens=ENUM          Save and reuse Oauth tokens: no, [yes]
@@ -3327,7 +3402,7 @@ OPTIONS:
         --to-folder=VALUE            Destination folder for transferred files
         --sources=VALUE              How list of transferred files is provided (@args,@ts,Array)
         --src-type=ENUM              Type of file list: [list], pair
-        --transfer=ENUM              Type of transfer agent: [direct], node, connect, httpgw, trsdk
+        --transfer=ENUM              Type of transfer agent: trsdk, [direct], httpgw, connect, node, alpha
         --transfer-info=VALUE        Parameters for transfer agent (Hash)
 
 
@@ -3337,11 +3412,10 @@ OPTIONS:
         --url=VALUE                  URL of application, e.g. https://faspex.example.com/aspera/faspex
         --username=VALUE             Username to log in
         --password=VALUE             User's password
-        --type=ENUM                  Type of user/group for operations: [any], local, ldap, saml
 
 
 COMMAND: node
-SUBCOMMANDS: access_keys api_details asperabrowser async basic_token bearer_token browse central delete download events health http_node_download info license mkdir mkfile mklink rename search service slash space ssync stream sync transfer upload watch_folder
+SUBCOMMANDS: access_keys api_details asperabrowser async basic_token bearer_token browse central delete download events health http_node_download info license mkdir mkfile mklink rename search service simulator slash space ssync stream sync transfer upload watch_folder
 OPTIONS:
         --url=VALUE                  URL of application, e.g. https://faspex.example.com/aspera/faspex
         --username=VALUE             Username to log in
@@ -3406,7 +3480,7 @@ OPTIONS:
         --auth=ENUM                  OAuth type of authentication: boot, web, [jwt]
         --private-key=VALUE          OAuth JWT RSA private key PEM value (prefix file path with @file:)
         --passphrase=VALUE           OAuth JWT RSA private key passphrase
-        --box=VALUE                  Package inbox, either shared inbox name or one of ["inbox", "inbox_history", "inbox_all", "inbox_all_history", "outbox", "outbox_history", "pending", "pending_history", "all"] or ALL
+        --box=VALUE                  Package inbox, either shared inbox name or one of: inbox, inbox_history, inbox_all, inbox_all_history, outbox, outbox_history, pending, pending_history, all or ALL
         --shared-folder=VALUE        Send package with files from shared folder
         --group-type=ENUM            Type of shared box: [shared_inboxes], workgroups
 
@@ -3515,7 +3589,7 @@ OPTIONS:
 
 ```
 
-> **Note:** commands and parameter values can be written in short form.
+> **Note:** Commands and parameter values can be written in short form.
 
 ### Bulk creation and deletion of resources
 
@@ -3528,12 +3602,12 @@ This option is available only for some of the resources: if you need it: try and
 `ascli` uses a plugin mechanism.
 The first level command (just after `ascli` on the command line) is the name of the concerned plugin which will execute the command.
 Each plugin usually represents commands sent to a specific application.
-For instance, the plugin `faspex` allows operations on the application "Aspera Faspex".
+For instance, the plugin `faspex` allows operations on **Aspera Faspex**.
 
 Available plugins can be found using command:
 
 ```bash
-ascli conf plugin list
+ascli config plugin list
 ```
 
 ```output
@@ -3561,7 +3635,7 @@ ascli --show-config --select=@json:'{"key":"plugin_folder"}'
 You can create the skeleton of a new plugin like this:
 
 ```bash
-ascli conf plugin create foo .
+ascli config plugin create foo .
 ```
 
 ```output
@@ -3590,7 +3664,7 @@ Here is a sample invocation :
 
 ```text
 ascli config wizard
-option: url> https://myorg.ibmaspera.com
+option: url> https://_your_instance_.ibmaspera.com
 Detected: Aspera on Cloud
 Preparing preset: aoc_myorg
 Please provide path to your private RSA key, or empty to generate one:
@@ -3602,21 +3676,25 @@ option: username> john@example.com
 Updating profile with new key
 creating new config preset: aoc_myorg
 Setting config preset as default for aspera
-saving config file
+saving configuration file
 Done.
 You can test with:
 ascli aoc user profile show
 ```
 
-Optionally, it is possible to create a new organization-specific "integration", i.e. client application identification.
+> **Note:** In above example, replace `https://_your_instance_.ibmaspera.com` with your actual AoC URL.
+
+Optionally, it is possible to create a new organization-specific integration, i.e. client application identification.
 For this, specify the option: `--use-generic-client=no`.
 
 If you already know the application, and want to limit the detection to it, provide url and plugin name:
 
 ```bash
-ascli config wizard myorg aoc
+ascli config wizard _your_instance_ aoc
 ```
 
+> **Note:** In above example, replace `_your_instance_` with the first part of your actual AoC URL: `https://_your_instance_.ibmaspera.com`.
+
 ### <a id="aocmanual"></a>Configuration: Using manual setup
 
 > **Note:** If you used the wizard (recommended): skip this section.
@@ -3635,7 +3713,7 @@ For a **quick start**, follow the mandatory and sufficient section: [API Client
 
 For a more convenient, browser-less, experience follow the [JWT](#jwt) section (auth=jwt) in addition to Client Registration.
 
-In Oauth, a "Bearer" token is generated to authenticate REST calls.
+In Oauth, a **Bearer** token is generated to authenticate REST calls.
 Bearer tokens are valid for a period of time defined (by the AoC app, configurable by admin) at its creation.
 `ascli` saves generated tokens in its configuration folder, tries to re-use them or regenerates them when they have expired.
 
@@ -3649,34 +3727,37 @@ Else you can use a specific OAuth API client_id, the first step is to declare `a
 
 Let's start by a registration with web based authentication (auth=web):
 
-- Open a web browser, log to your instance: e.g. `https://myorg.ibmaspera.com/`
+- Open a web browser, log to your instance: e.g. `https://_your_instance_.ibmaspera.com/`
+  (use your actual AoC instance URL)
 - Go to Apps &rarr; Admin &rarr; Organization &rarr; Integrations
-- Click "Create New"
-  - Client Name: `ascli`
-  - Redirect URIs: `http://localhost:12345`
-  - Origins: `localhost`
-  - uncheck "Prompt users to allow client to access"
+- Click **Create New**
+  - **Client Name**: `ascli`
+  - **Redirect URIs**: `http://localhost:12345`
+  - **Origins**: `localhost`
+  - uncheck **Prompt users to allow client to access**
   - leave the JWT part for now
-- Save
+- **Save**
 
-> **Note:** for web based authentication, `ascli` listens on a local port (e.g. specified by the redirect_uri, in this example: 12345), and the browser will provide the OAuth code there. For ``ascli`, HTTP is required, and 12345 is the default port.
+> **Note:** For web based authentication, `ascli` listens on a local port (e.g. specified by the redirect_uri, in this example: 12345), and the browser will provide the OAuth code there. For ``ascli`, HTTP is required, and 12345 is the default port.
 
-Once the client is registered, a "Client ID" and "Secret" are created, these values will be used in the next step.
+Once the client is registered, a **Client ID** and **Secret** are created, these values will be used in the next step.
 
 #### <a id="aocpreset"></a>[option preset](#lprt) for Aspera on Cloud
 
 If you did not use the wizard, you can also manually create a [option preset](#lprt) for `ascli` in its configuration file.
 
-Lets create an [option preset](#lprt) called: `my_aoc_org` using `ask` interactive input (client info from previous step):
+Lets create a [option preset](#lprt) called: `my_aoc_org` using `ask` for interactive input (client info from previous step):
 
 ```bash
 ascli config preset ask my_aoc_org url client_id client_secret
-option: url> https://myorg.ibmaspera.com/
+option: url> https://_your_instance_.ibmaspera.com/
 option: client_id> my_client_id_here
 option: client_secret> my_client_secret_here
 updated: my_aoc_org
 ```
 
+> **Note:** In above example, replace `https://_your_instance_.ibmaspera.com` with your actual AoC URL.
+
 (This can also be done in one line using the command `config preset update my_aoc_org --url=...`)
 
 Define this [option preset](#lprt) as default configuration for the `aspera` plugin:
@@ -3700,12 +3781,13 @@ If you are not using the built-in client_id and secret, JWT needs to be authoriz
 
 - Graphically
 
-  - Open a web browser, log to your instance: `https://myorg.ibmaspera.com/`
+  - Open a web browser, log to your instance: `https://_your_instance_.ibmaspera.com/`
+    (Use your actual AoC instance URL)
   - Go to Apps &rarr; Admin &rarr; Organization &rarr; Integrations
   - Click on the previously created application
-  - select tab : "JSON Web Token Auth"
-  - Modify options if necessary, for instance: activate both options in section "Settings"
-  - Click "Save"
+  - select tab : **JSON Web Token Auth**
+  - Modify options if necessary, for instance: activate both options in section **Settings**
+  - **Save**
 
 - Using command line
 
@@ -3737,11 +3819,12 @@ The public key must be assigned to your user. This can be done in two manners:
 
 Open the previously generated public key located here: `$HOME/.aspera/ascli/my_private_key.pub`
 
-- Open a web browser, log to your instance: `https://myorg.ibmaspera.com/`
+- Open a web browser, log to your instance: `https://_your_instance_.ibmaspera.com/`
+  (Use your actual AoC instance URL)
 - Click on the user's icon (top right)
-- Select "Account Settings"
-- Paste the **Public Key** in the "Public Key" section
-- Click on "Submit"
+- Select **Account Settings**
+- Paste the Public Key PEM value in the **Public Key** section
+- Click on **Submit**
 
 ##### Using command line
 
@@ -3766,15 +3849,15 @@ ascli aoc user profile modify @ruby:'{"public_key"=>File.read(File.expand_path("
 modified
 ```
 
-> **Note:** the `aspera user info show` command can be used to verify modifications.
+> **Note:** The `aspera user info show` command can be used to verify modifications.
 
 #### [option preset](#lprt) modification for JWT
 
 To activate default use of JWT authentication for `ascli` using the [option preset](#lprt), do the following:
 
-- change auth method to JWT
-- provide location of private key
-- provide username to login as (OAuth "subject")
+- Change auth method to JWT
+- Provide location of private key
+- Provide username to login as (OAuth **subject**)
 
 Execute:
 
@@ -3782,7 +3865,10 @@ Execute:
 ascli config preset update my_aoc_org --auth=jwt --private-key=@val:@file:~/.aspera/ascli/my_private_key --username=someuser@example.com
 ```
 
-> **Note:** the private key argument represents the actual PEM string. In order to read the content from a file, use the `@file:` prefix. But if the @file: argument is used as is, it will read the file and set in the config file. So to keep the "@file" tag in the configuration file, the `@val:` prefix is added.
+> **Note:** The private key argument represents the actual PEM string.
+In order to read the content from a file, use the `@file:` prefix.
+But if the @file: argument is used as is, it will read the file and set in the configuration file.
+So, to keep the `@file:` tag in the configuration file, the `@val:` prefix is added.
 
 After this last step, commands do not require web login anymore.
 
@@ -3837,7 +3923,7 @@ ascli aoc admin res node v4 1234 --secret=_ak_secret_here_ bearer_token_node /
 
 The `admin` command allows several administrative tasks (and require admin privilege).
 
-It allows actions (create, update, delete) on "resources": users, group, nodes, workspace, etc... with the `admin resource` command.
+It allows actions (create, update, delete) on **resources**: users, group, nodes, workspace, etc... with the `admin resource` command.
 
 #### Listing resources
 
@@ -3898,9 +3984,9 @@ Resources are identified by a unique `id`, as well as a unique `name` (case inse
 To execute an action on a specific resource, select it using one of those methods:
 
 - **recommended**: give id directly on command line **after the action**: `aoc admin res node show 123`
-- give name on command line **after the action**: `aoc admin res node show name abc`
-- provide option `id` : `aoc admin res node show 123`
-- provide option `name` : `aoc admin res node show --name=abc`
+- Give name on command line **after the action**: `aoc admin res node show name abc`
+- Provide option `id` : `aoc admin res node show 123`
+- Provide option `name` : `aoc admin res node show --name=abc`
 
 #### <a id="res_create"></a>Creating a resource
 
@@ -3971,7 +4057,7 @@ It can also support filters and send notification using option `notify_to`. a te
 
 `mytemplate.erb`:
 
-```bash
+```yaml
 From: <%=from_name%> <<%=from_email%>>
 To: <<%=ev['user_email']%>>
 Subject: <%=ev['files_completed']%> files received
@@ -3985,7 +4071,7 @@ Thank you.
 
 The environment provided contains the following additional variable:
 
-- ev : all details on the transfer event
+- `ev` : all details on the transfer event
 
 Example:
 
@@ -4008,7 +4094,7 @@ The option `default_ports` ([yes]/no) allows ascli to retrieve the server ports
 
 #### Using ATS
 
-Refer to section "Examples" of [ATS](#ats) and substitute command `ats` with `aoc admin ats`.
+Refer to section **Examples** of [ATS](#ats) and substitute command `ats` with `aoc admin ats`.
 
 #### Files with type `link`
 
@@ -4107,7 +4193,7 @@ ascli aoc user workspaces list
 +------+----------------------------+
 ```
 
-#### Example: Create a sub access key in a "node"
+#### Example: Create a sub access key in a `node`
 
 Creation of a sub-access key is like creation of access key with the following difference: authentication to node API is made with accesskey (master access key) and only the path parameter is provided: it is relative to the storage root of the master key. (id and secret are optional)
 
@@ -4217,7 +4303,7 @@ ascli aoc admin res user list --fields=email --query=@json:'{"q":"last_login_at:
 +-------------------------------+
 ```
 
-#### Example: List "Limited" users
+#### Example: List **Limited** users
 
 ```bash
 ascli aoc admin res user list --fields=email --select=@json:'{"member_of_any_workspace":false}'
@@ -4268,7 +4354,7 @@ In this example, a user has access to a workspace where two shared folders are l
 First, setup the environment (skip if already done)
 
 ```bash
-ascli conf wizard --url=https://sedemo.ibmaspera.com --username=someuser@example.com
+ascli config wizard --url=https://sedemo.ibmaspera.com --username=someuser@example.com
 ```
 
 ```output
@@ -4287,13 +4373,13 @@ Once updated or validated, press enter.
 
 creating new config preset: aoc_sedemo
 Setting config preset as default for aspera
-saving config file
+saving configuration file
 Done.
 You can test with:
 ascli aoc user profile show
 ```
 
-This creates the option preset "aoc_&lt;org name&gt;" to allow seamless command line access and sets it as default for aspera on cloud.
+This creates the option preset `aoc_[org name]` to allow seamless command line access and sets it as default for aspera on cloud.
 
 Then, create two shared folders located in two regions, in your files home, in a workspace.
 
@@ -4335,12 +4421,12 @@ ascli aoc admin res client list --fields=id --format=csv|ascli aoc admin res cli
 AoC nodes as actually composed with two related entities:
 
 - An access key created on the Transfer Server (HSTS/ATS)
-- a `node` resource in the AoC application.
+- A `node` resource in the AoC application.
 
 The web UI allows creation of both entities in one shot.
 For more flexibility, `ascli` allows this in two separate steps.
 
-> **Note:** When selecting "Use existing access key" in the web UI, this actually skips access key creation (first step).
+> **Note:** When selecting **Use existing access key** in the web UI, this actually skips access key creation (first step).
 
 So, for example, the creation of a node using ATS in IBM Cloud looks like (see other example in this manual):
 
@@ -4379,10 +4465,10 @@ Refer to section [File list](#file_list)
 
 > **Note:** A special case is when the source files are located on **Aspera on Cloud** (i.e. using access keys and the `file id` API).
 
-Source files are located on "Aspera on cloud", when :
+Source files are located on **Aspera on cloud**, when :
 
-- the server is Aspera on Cloud, and executing a download or recv
-- the agent is Aspera on Cloud, and executing an upload or send
+- The server is Aspera on Cloud, and executing a download or recv
+- The agent is Aspera on Cloud, and executing an upload or send
 
 In this case:
 
@@ -4538,7 +4624,7 @@ For creation, parameters are the same as for node API [permissions](https://deve
 `ascli` expects the same payload for creation, but it will automatically populate required tags if needed.
 
 Also, the pseudo key `with` is available: it will lookup the name in the contacts and fill the proper type and id.
-The pseudo parameter `link_name` allows changing default "shared as" name.
+The pseudo parameter `link_name` allows changing default **shared as** name.
 
 - List permissions on a shared folder as user
 
@@ -4579,7 +4665,7 @@ Procedure to send a file from org1 to org2:
 - Check that access works and locate the source file e.g. `mysourcefile`, e.g. using command `files browse`
 - Get access to Organization 2 and create a [option preset](#lprt): e.g. `org2`
 - Check that access works and locate the destination folder `mydestfolder`
-- execute the following:
+- Execute the following:
 
 ```bash
 ascli -Porg1 aoc files node_info /mydestfolder --format=json --display=data | ascli -Porg2 aoc files upload mysourcefile --transfer=node --transfer-info=@json:@stdin:
@@ -4612,7 +4698,9 @@ For instructions, refer to section `find` for plugin `node`.
 ### AoC sample commands
 
 ```bash
+aoc admin analytics transfers nodes
 aoc admin analytics transfers organization --query=@json:'{"status":"completed","direction":"receive"}' --notify-to=my_email_external --notify-template=@ruby:'%Q{From: <%=from_name%> <<%=from_email%>>\nTo: <<%=to%>>\nSubject: <%=ev["files_completed"]%> files received\n\n<%=ev.to_yaml%>}'
+aoc admin analytics transfers users --once_only=yes
 aoc admin ats access_key create --cloud=aws --region=my_bucket_region --params=@json:'{"id":"ak_aws","name":"my test key AWS","storage":{"type":"aws_s3","bucket":"my_bucket_name","credentials":{"access_key_id":"my_bucket_key","secret_access_key":"my_bucket_secret"},"path":"/"}}'
 aoc admin ats access_key create --cloud=softlayer --region=my_bucket_region --params=@json:'{"id":"ak1ibmcloud","secret":"my_secret_here","name":"my test key","storage":{"type":"ibm-s3","bucket":"my_bucket_name","credentials":{"access_key_id":"my_bucket_key","secret_access_key":"my_bucket_secret"},"path":"/"}}'
 aoc admin ats access_key delete ak1ibmcloud
@@ -4691,25 +4779,29 @@ aoc files upload --to-folder=/ test_file.bin --url=my_public_link_folder_no_pass
 aoc files upload --to-folder=/testsrc test_file.bin
 aoc files upload --workspace=my_other_workspace --to-folder=my_other_folder test_file.bin --transfer=node --transfer-info=@json:@stdin:
 aoc files v3 info
-aoc gateway --pid-file=server_pid https://localhost:12345/aspera/faspex
+aoc gateway --pid-file=pid_aocfxgw https://localhost:12345/aspera/faspex &
 aoc org --url=my_public_link_recv_from_aoc_user
 aoc organization
 aoc packages browse package_id3 /contents
 aoc packages list
 aoc packages list --query=@json:'{"dropbox_name":"my_shared_inbox_name","sort":"-received_at","archived":false,"received":true,"has_content":true,"exclude_dropbox_packages":false}'
-aoc packages recv ALL --to-folder=. --once-only=yes --lock-port=12345
-aoc packages recv ALL --to-folder=. --once-only=yes --lock-port=12345 --query=@json:'{"dropbox_name":"my_shared_inbox_name","archived":false,"received":true,"has_content":true,"exclude_dropbox_packages":false,"include_draft":false}' --ts=@json:'{"resume_policy":"sparse_csum","target_rate_kbps":50000}'
-aoc packages recv package_id3 --to-folder=.
-aoc packages send --workspace=my_workspace_shared_inbox @json:'{"name":"Important files delivery","recipients":["my_shared_inbox_name"],"metadata":[{"input_type":"single-text","name":"Project Id","values":["123"]},{"input_type":"single-dropdown","name":"Type","values":["Opt2"]},{"input_type":"multiple-checkbox","name":"CheckThose","values":["Check1","Check2"]},{"input_type":"date","name":"Optional Date","values":["2021-01-13T15:02:00.000Z"]}]}' test_file.bin
-aoc packages send --workspace=my_workspace_shared_inbox @json:'{"name":"Important files delivery","recipients":["my_shared_inbox_name"],"metadata":{"Project Id":"456","Type":"Opt2","CheckThose":["Check1","Check2"],"Optional Date":"2021-01-13T15:02:00.000Z"}}' test_file.bin
-aoc packages send --workspace=my_workspace_shared_inbox @json:'{"name":"Important files delivery","recipients":["my_shared_inbox_name"]}' test_file.bin
-aoc packages send @json:'{"name":"Important files delivery","recipients":["my_email_external"]}' --new-user-option=@json:'{"package_contact":true}' test_file.bin
-aoc packages send @json:'{"name":"Important files delivery","recipients":["my_email_internal"],"note":"my note"}' test_file.bin
-aoc packages send @json:'{"name":"Important files delivery"}' test_file.bin --url=my_public_link_send_aoc_user --password=my_public_link_send_use_pass
-aoc packages send @json:'{"name":"Important files delivery"}' test_file.bin --url=my_public_link_send_shared_inbox
+aoc packages receive ALL --once-only=yes --to-folder=. --lock-port=12345
+aoc packages receive ALL --once-only=yes --to-folder=. --lock-port=12345 --query=@json:'{"dropbox_name":"my_shared_inbox_name","archived":false,"received":true,"has_content":true,"exclude_dropbox_packages":false,"include_draft":false}' --ts=@json:'{"resume_policy":"sparse_csum","target_rate_kbps":50000}'
+aoc packages receive INIT --once-only=yes --query=@json:'{"dropbox_name":"my_shared_inbox_name"}'
+aoc packages receive package_id3 --to-folder=.
+aoc packages send --workspace=my_workspace_shared_inbox --validate-metadata=yes @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_shared_inbox_meta"],"metadata":[{"input_type":"single-text","name":"Project Id","values":["123"]},{"input_type":"single-dropdown","name":"Type","values":["Opt2"]},{"input_type":"multiple-checkbox","name":"CheckThose","values":["Check1","Check2"]},{"input_type":"date","name":"Optional Date","values":["2021-01-13T15:02:00.000Z"]}]}' test_file.bin
+aoc packages send --workspace=my_workspace_shared_inbox --validate-metadata=yes @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_shared_inbox_meta"],"metadata":{"Project Id":"456","Type":"Opt2","CheckThose":["Check1","Check2"],"Optional Date":"2021-01-13T15:02:00.000Z"}}' test_file.bin
+aoc packages send --workspace=my_workspace_shared_inbox --validate-metadata=yes @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_shared_inbox_meta"],"metadata":{"Type":"Opt2","CheckThose":["Check1","Check2"],"Optional Date":"2021-01-13T15:02:00.000Z"}}' test_file.bin
+aoc packages send --workspace=my_workspace_shared_inbox @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_shared_inbox_name"]}' test_file.bin
+aoc packages send @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_email_external"]}' --new-user-option=@json:'{"package_contact":true}' test_file.bin
+aoc packages send @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_email_internal"],"note":"my note"}' test_file.bin
+aoc packages send @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE"}' test_file.bin --url=my_public_link_send_aoc_user --password=my_public_link_send_use_pass
+aoc packages send @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE"}' test_file.bin --url=my_public_link_send_shared_inbox
 aoc packages shared_inboxes list
 aoc remind --username=my_user_email
 aoc servers
+aoc user pref modify @json:'{"default_language":"en-us"}'
+aoc user pref show
 aoc user profile modify @json:'{"name":"dummy change"}'
 aoc user profile show
 aoc user workspaces current
@@ -4720,9 +4812,9 @@ aoc user workspaces list
 
 ATS is usable either :
 
-- from an AoC subscription : ascli aoc admin ats : use AoC authentication
+- From an AoC subscription : ascli aoc admin ats : use AoC authentication
 
-- or from an IBM Cloud subscription : ascli ats : use IBM Cloud API key authentication
+- Or from an IBM Cloud subscription : ascli ats : use IBM Cloud API key authentication
 
 ### IBM Cloud ATS : Creation of api key
 
@@ -4872,6 +4964,7 @@ then commands `ascp` (for transfers) and `ascmd` (for file operations) are execu
 
 ```bash
 server browse /
+server browse / --password=@none: --ssh-options=@json:'{"number_of_password_prompts":0}' --ssh-keys=$aspera_key_path
 server browse my_inside_folder/test_file.bin
 server browse my_upload_folder/target_hot
 server cp my_inside_folder/test_file.bin my_upload_folder/200KB.2
@@ -4899,7 +4992,7 @@ server upload --sources=@ts --transfer-info=@json:'{"ascp_args":["--file-list","
 server upload --sources=@ts --transfer-info=@json:'{"ascp_args":["--file-pair-list","file_pair_list.txt"]}'
 server upload --sources=@ts --ts=@json:'{"paths":[{"source":"test_file.bin","destination":"my_inside_folder/other_name_4"}]}' --transfer=trsdk
 server upload --src-type=pair 'test_file.bin' my_inside_folder/other_name_2 --notify-to=my_email_external --transfer-info=@json:'{"ascp_args":["-l","100m"]}'
-server upload --src-type=pair --sources=@json:'["test_file.bin","my_inside_folder/other_name_3"]' --transfer-info=@json:'{"quiet":false}' --progress=no
+server upload --src-type=pair --sources=@json:'["test_file.bin","my_inside_folder/other_name_3"]' --transfer-info=@json:'{"quiet":false}' --ts=@json:'{"use_ascp4":true}' --progress=no
 server upload --src-type=pair test_file.bin my_upload_folder/other_name_5 --ts=@json:'{"cipher":"aes-192-gcm","content_protection":"encrypt","content_protection_password":"my_secret_here","cookie":"biscuit","create_dir":true,"delete_before_transfer":false,"delete_source":false,"exclude_newer_than":1,"exclude_older_than":10000,"fasp_port":33001,"http_fallback":false,"multi_session":0,"overwrite":"diff+older","precalculate_job_size":true,"preserve_access_time":true,"preserve_creation_time":true,"rate_policy":"fair","resume_policy":"sparse_csum","symlink_policy":"follow"}'
 server upload --to-folder=my_upload_folder/target_hot --lock-port=12345 --transfer-info=@json:'{"ascp_args":["--remove-after-transfer","--remove-empty-directories","--exclude-newer-than=-8","--src-base","source_hot"]}' source_hot
 ```
@@ -5014,9 +5107,9 @@ The authentication is `username` and `password` or `access_key` and `secret` thr
 
 It is possible to do **gen3/node user** operations:
 
-- browse
-- transfer (upload / download / sync)
-- delete
+- `browse`
+- Transfer (`upload` / `download` / `sync`)
+- `delete`
 - ...
 
 When using an access key, so called **gen4/access key** API is also supported through sub commands using `access_keys do self`.
@@ -5038,7 +5131,7 @@ It recursively scans storage to find files/folders matching a criteria and then
 `[filter_expr]` is either:
 
 - Optional (default) : all files and folder are selected
-- type `String` : the expression is similar to shell globing, refer to **Ruby** function: [`File.fnmatch`](https://ruby-doc.org/3.2.2/File.html#method-c-fnmatch)
+- Type `String` : the expression is similar to shell globing, refer to **Ruby** function: [`File.fnmatch`](https://ruby-doc.org/3.2.2/File.html#method-c-fnmatch)
 - Type `Proc` : the expression is a Ruby lambda that takes one argument: a `Hash` that contains the current folder entry to test. Refer to the following examples.
 
 Examples of expressions:
@@ -5093,13 +5186,13 @@ The following are examples of `ruby_lambda` to be provided in the following temp
   ->(f){f["name"].match?(/\.gif$/)}
   ```
 
-`ascli` commands can be piped in order to combine operations, such as "find and delete":
+`ascli` commands can be piped in order to combine operations, such as **find and delete**:
 
 ```bash
 ascli node access_keys do self find / @ruby:'->(f){f["type"].eql?("file") and (DateTime.now-DateTime.parse(f["modified_time"]))>365}' --fields=path --format=csv | ascli node --bulk=yes delete @lines:@stdin:
 ```
 
-> **Note:** the pipe `|` character on the last line.
+> **Note:** The pipe `|` character on the last line.
 
 ### Central
 
@@ -5114,7 +5207,7 @@ ascli node central file list
 
 By providing the `validator` option, offline transfer validation can be done.
 
-> **Note:** This API will probably be deprecated in the future.
+> **Note:** See later in this doc, refer to HSTS doc.
 
 ### Sync
 
@@ -5134,14 +5227,14 @@ Use the command `ascli node stream create --ts=@json:<value>`, with [*transfer-s
 {"direction":"send","source":"udp://233.3.3.4:3000?loopback=1&ttl=2","destination":"udp://233.3.3.3:3001/","remote_host":"localhost","remote_user":"stream","remote_password":"my_pass_here"}
 ```
 
-### "Watchfolder"
+### Watchfolder
 
 Refer to [Aspera documentation](https://download.asperasoft.com/download/docs/entsrv/3.7.4/es_admin_linux/webhelp/index.html#watchfolder_external/dita/json_conf.html) for watch folder creation.
 
 `ascli` supports remote operations through the node API. Operations are:
 
 - Start `watchd` and `watchfolderd` services running as a system user having access to files
-- configure a "watchfolder" to define automated transfers
+- Configure a **watchfolder** to define automated transfers
 
 ```bash
 ascli node service create @json:'{"id":"mywatchd","type":"WATCHD","run_as":{"user":"user1"}}'
@@ -5153,6 +5246,8 @@ ascli node watch_folder create @json:'{"id":"mywfolder","source_dir":"/watch1","
 
 Follow the Aspera Transfer Server configuration to activate this feature.
 
+The following command lists one file that requires validation, and assign it to the unique validator identifier provided:
+
 ```bash
 ascli node central file list --validator=ascli --data=@json:'{"file_transfer_filter":{"max_result":1}}'
 ```
@@ -5165,6 +5260,8 @@ ascli node central file list --validator=ascli --data=@json:'{"file_transfer_fil
 +--------------+--------------+------------+--------------------------------------+
 ```
 
+To update the status of the file, use the following command:
+
 ```bash
 ascli node central file update --validator=ascli --data=@json:'{"files":[{"session_uuid": "1a74444c-...","file_id": "084fb181-...","status": "completed"}]}'
 ```
@@ -5178,8 +5275,8 @@ updated
 Scenario: Access to a **Shares on Demand** (SHOD) server on AWS is provided by a partner.
 We need to transfer files from this third party SHOD instance into our Azure BLOB storage.
 Simply create an **Aspera Transfer Service** instance, which provides access to the node API.
-Then create a configuration for the **SHOD** instance in the configuration file: in section "shares", a configuration named: aws_shod.
-Create another configuration for the Azure ATS instance: in section "node", named azure_ats.
+Then create a configuration for the **SHOD** instance in the configuration file: in section **shares**, a configuration named: `aws_shod`.
+Create another configuration for the Azure ATS instance: in section **node**, named `azure_ats`.
 Then execute the following command:
 
 ```bash
@@ -5188,7 +5285,7 @@ ascli node download /share/sourcefile --to-folder=/destination_folder --preset=a
 
 This will get transfer information from the SHOD instance and tell the Azure ATS instance to download files.
 
-### node file information
+### Node file information
 
 When node api is used with an **Access key**, extra information can be retrieved, such as preview.
 
@@ -5213,7 +5310,7 @@ ascli aoc files thumbnail /preview_samples/Aspera.mpg
 
 > **Note:** To specify the file by its file id, use the selector syntax: `%id:_file_id_here_`
 >
-> **Note:** To force textual display of the preview on **iTerm**, prefix command with: `env -u TERM_PROGRAM -u LC_TERMINAL`
+> **Note:** To force textual display of the preview on **iTerm**, prefix command with: `env -u TERM_PROGRAM -u LC_TERMINAL` or use option: ``
 
 ### Create access key
 
@@ -5249,8 +5346,8 @@ A bearer token is authorized on the node by creating `permissions` on a **folder
 
 Bearer tokens can be generated using command `bearer_token`: it takes two arguments:
 
-- the private key used to sign the token
-- the token information, which is a `Hash` containing the following elements:
+- The private key used to sign the token
+- The token information, which is a `Hash` containing the following elements:
 
 | parameter                 | Default                     | type      | description                                              |
 | ------------------------  |-----------------------------|-----------|----------------------------------------------------------|
@@ -5270,7 +5367,7 @@ Bearer tokens can be generated using command `bearer_token`: it takes two argume
 
 #### Bearer token: Environment
 
-- If a self-managed Aspera node is used, then a "node user admin" must be created:
+- If a self-managed Aspera node is used, then a **node user admin** must be created:
   It has no `docroot` but has at least one file restriction (for testing, one can use `*` to accept creation of an access key with any storage root path).
   Refer to the Aspera HSTS documentation.
 
@@ -5289,7 +5386,7 @@ Let's assume that the access key was created, and a default configuration is set
 
   ```bash
   my_private_pem=./myorgkey.pem
-  ascli conf genkey $my_private_pem
+  ascli config genkey $my_private_pem
   ```
 
   > **Note:** This key is not used for authentication, it is used to sign bearer tokens.
@@ -5345,9 +5442,9 @@ Let's assume that the access key was created, and a default configuration is set
 
 Now, let's assume we are the user, the only information received are:
 
-- the url of the node API
-- a Bearer token
-- a file `id` for which we have access
+- The url of the node API
+- A Bearer token
+- A file `id` for which we have access
 
 Let's use it:
 
@@ -5481,7 +5578,7 @@ Setting config preset as default for faspex5
 Done.
 You can test with:
 ascli faspex5 user profile show
-Saving config file.
+Saving configuration file.
 ```
 
 > **Note:** Include the public key `BEGIN` and `END` lines when pasting in the user profile.
@@ -5532,9 +5629,9 @@ As usual, typically a user will create preset to avoid having to type these opti
 Example:
 
 ```bash
-ascli conf preset update myf5 --auth=jwt --client-id=_client_id_here_ --client-secret=my_secret_here --username=_username_here_ --private-key=@file:.../path/to/key.pem
+ascli config preset update myf5 --auth=jwt --client-id=_client_id_here_ --client-secret=my_secret_here --username=_username_here_ --private-key=@file:.../path/to/key.pem
 
-ascli conf preset set default faspx5 myf5
+ascli config preset set default faspx5 myf5
 
 ascli faspex5 user profile show
 ```
@@ -5570,7 +5667,7 @@ For `boot` method: (will be removed in future)
 Use this token as password and use `--auth=boot`.
 
 ```bash
-ascli conf preset update f5boot --url=https://localhost/aspera/faspex --auth=boot --password=_token_here_
+ascli config preset update f5boot --url=https://localhost/aspera/faspex --auth=boot --password=_token_here_
 ```
 
 ### Faspex 5 sample commands
@@ -5590,35 +5687,36 @@ faspex5 admin res node list
 faspex5 admin res oauth_clients list
 faspex5 admin res registrations list
 faspex5 admin res saml_configs list
-faspex5 admin res shared_inboxes invite %name:my_shared_inbox_name johnny@example.com
+faspex5 admin res shared_inboxes invite %name:my_shared_box_name johnny@example.com
 faspex5 admin res shared_inboxes list
-faspex5 admin res shared_inboxes members %name:my_shared_inbox_name create %name:john@example.com
-faspex5 admin res shared_inboxes members %name:my_shared_inbox_name delete %name:john@example.com
-faspex5 admin res shared_inboxes members %name:my_shared_inbox_name delete %name:johnny@example.com
-faspex5 admin res shared_inboxes members %name:my_shared_inbox_name list
+faspex5 admin res shared_inboxes list --query=@json:'{"all":true}'
+faspex5 admin res shared_inboxes members %name:my_shared_box_name create %name:john@example.com
+faspex5 admin res shared_inboxes members %name:my_shared_box_name delete %name:john@example.com
+faspex5 admin res shared_inboxes members %name:my_shared_box_name delete %name:johnny@example.com
+faspex5 admin res shared_inboxes members %name:my_shared_box_name list
 faspex5 admin res workgroups list
 faspex5 admin smtp show
 faspex5 admin smtp test my_email_external
 faspex5 bearer_token
-faspex5 gateway --pid-file=server_pid https://localhost:12345/aspera/faspex
+faspex5 gateway --pid-file=pid_f5_fxgw https://localhost:12346/aspera/faspex &
 faspex5 health
-faspex5 packages list --box=my_shared_inbox_name
+faspex5 packages list --box=my_shared_box_name
 faspex5 packages list --box=my_workgroup --group-type=workgroups
 faspex5 packages list --query=@json:'{"mailbox":"inbox","state":["released"]}'
-faspex5 packages receive --box=my_shared_inbox_name package_box_id1 --to-folder=.
+faspex5 packages receive --box=my_shared_box_name package_box_id1 --to-folder=.
 faspex5 packages receive --box=my_workgroup --group-type=workgroups workgroup_package_id1 --to-folder=.
 faspex5 packages receive ALL --once-only=yes --to-folder=.
 faspex5 packages receive INIT --once-only=yes
 faspex5 packages receive f5_p31 --to-folder=. --ts=@json:'{"content_protection_password":"my_secret_here"}'
 faspex5 packages send --shared-folder=%name:my_shared_folder_name @json:'{"title":"test title","recipients":["my_email_internal"]}' my_shared_folder_file
-faspex5 packages send @json:'{"title":"test title","recipients":["my_shared_inbox_name"],"metadata":{"Options":"Opt1","TextInput":"example text"}}' test_file.bin
+faspex5 packages send @json:'{"title":"test title","recipients":["my_shared_box_name"],"metadata":{"Options":"Opt1","TextInput":"example text"}}' test_file.bin
 faspex5 packages send @json:'{"title":"test title","recipients":["my_workgroup"]}' test_file.bin
 faspex5 packages send @json:'{"title":"test title","recipients":[{"name":"my_username"}]my_meta}' test_file.bin --ts=@json:'{"content_protection_password":"my_passphrase_here"}'
-faspex5 packages show --box=my_shared_inbox_name package_box_id1
+faspex5 packages show --box=my_shared_box_name package_box_id1
 faspex5 packages show --box=my_workgroup --group-type=workgroups workgroup_package_id1
 faspex5 packages show f5_p31
 faspex5 packages status f5_p31
-faspex5 postprocessing --pid-file=server_pid @json:'{"url":"https://localhost:8443/domain","processing":{"script_folder":"tests"}}'
+faspex5 postprocessing --pid-file=pid_f5_postproc @json:'{"url":"https://localhost:8443/domain","processing":{"script_folder":""}}' &
 faspex5 shared browse %name:my_src
 faspex5 shared list
 faspex5 shared_folders browse %name:my_shared_folder_name
@@ -5633,25 +5731,28 @@ By default, package operations (send, receive, list) are done on the user's inbo
 
 To select another inbox, use option `box` with one of the following values:
 
-- inbox
-- inbox_history
-- inbox_all
-- inbox_all_history
-- outbox
-- outbox_history
-- pending
-- pending_history
-- all
-- ALL (only admin)
-- name of a shared inbox or workgroup
+- `inbox`
+- `inbox_history`
+- `inbox_all`
+- `inbox_all_history`
+- `outbox`
+- `outbox_history`
+- `pending`
+- `pending_history`
+- `all`
+- `ALL` (**admin only**, all inboxes of all users)
+- **name of a shared inbox or workgroup**
 
-> **Note:** specify if the box is a shared inbox or a workgroup using option `group_type` with either `shared_inboxes` or `workgroups`
+> **Note:** In case the name of the `box` is specific, use option `group_type` with either `shared_inboxes` or `workgroups` to be more specific.
 
 ### Faspex 5: Send a package
 
-The `Hash` creation parameter provided to command `faspex5 packages send` corresponds to the Faspex 5 API: `POST /packages`.
+The `Hash` creation parameter provided to command `faspex5 packages send [extended value: Hash with package info ] [files...]` corresponds to the Faspex 5 API: `POST /packages`.
+
+The interface is the one of the API (Refer to Faspex5 API documentation, or look at request in browser).
 
 Required fields are `title` and `recipients`.
+
 Example using `@json:` format:
 
 ```json
@@ -5660,15 +5761,16 @@ Example using `@json:` format:
 
 `recipient_type` is one of (Refer to API):
 
-- user
-- workgroup
-- external_user
-- distribution_list
-- shared_inbox
+- `user`
+- `workgroup`
+- `external_user`
+- `distribution_list`
+- `shared_inbox`
 
-`ascli` adds some convenience: The API expects the field `recipients` to be an `Array` of `Hash`, each with field `name` and optionally `recipient_type`.
-It is also possible to provide an `Array` of `String`, with simply a recipient name.
-Then `ascli` will lookup existing contacts among all possible types, use it if a single match is found, and set the `name` and `recipient_type` accordingly.
+`ascli` adds some convenience:
+The API expects the field `recipients` to be an `Array` of `Hash`, each with field `name` and optionally `recipient_type`.
+`ascli` also accepts an `Array` of `String`, with simply a recipient name.
+Then, `ascli` will lookup existing contacts among all possible types, use it if a single match is found, and set the `name` and `recipient_type` accordingly.
 Else an exception is sent.
 
 > **Note:** The lookup is case insensitive and on partial matches.
@@ -5677,39 +5779,74 @@ Else an exception is sent.
 {"title":"some title","recipients":["user@example.com"]}
 ```
 
-If the lookup needs to be only on certain types, you can specify the field: `recipient_types` with either a single value or an Array of values (from the list above). e.g. :
+If the lookup needs to be only on certain types, you can specify the field: `recipient_types` with either a single value or an `Array` of values (from the list above). e.g. :
 
 ```json
 {"title":"test title","recipient_types":"user","recipients":["user1@example.com","user2@example.com"]}
 ```
 
-### Faspex 5:  Send a package with metadata
+### Faspex 5: Send a package with metadata
 
-The interface is the one of the API (Refer to API documentation, or look at request in browser):
+It's the same as sending a package, but with an extra field `metadata` in the package info.
 
-```bash
-ascli faspex5 packages send @json:'{"title":"test title","recipients":["my shared inbox"],"metadata":{"Confidential":"Yes","Drop menu":"Option 1"}}' 'faux:///test1?k1'
+```json
+{"title":"test title","recipients":["my shared inbox"],"metadata":{"Confidential":"Yes","Drop menu":"Option 1"}}
 ```
 
 Basically, add the field `metadata`, with one key per metadata and the value is directly the metadata value.
+(Refer to API documentation for more details).
+
+### Faspex 5: List packages
+
+Option `box` can be used to list packages from a specific box (see **Inbox selection** above).
+
+Option `query` can be used to filter the list of packages, based on native API parameters, directly sent to [Faspex 5 API `GET /packages`](https://developer.ibm.com/apis/catalog/aspera--ibm-aspera-faspex-5-0-api/api/API--aspera--ibm-aspera-faspex-api#getAllPackages).
+
+| parameter | Type    | description |
+|-----------|---------|-------------|
+| `offset`  | Native  | Managed by `ascli`: Offset of first package. Default: 0 |
+| `limit`   | Native  | Managed by `ascli`: # of packages per API call. Default: 100 |
+| `q`       | Native  | General search string (case insensitive, matches if value is contained in several fields) |
+| ...       | Native  | Other native parameters are supported (Refer to API documentation) |
+| `max`     | Special | Maximum number of items to retrieve (stop pages when the maximum is passed) |
+| `pmax`    | Special | Maximum number of pages to request (stop pages when the maximum is passed) |
+
+A positional parameter in last position, of type `Proc`, can be used to filter the list of packages.
+This advantage of this method is that the expression can be any test, even complex, as it is Ruby code.
+But the disadvantage is that the filtering is done in `ascli` and not in Faspex 5, so it is less efficient.
+
+Examples:
+
+- List only available packages: (filtering is done in Faspex)
+
+  ```bash
+  ascli faspex5 packages list --query=@json:'{"status":"completed"}'
+  ```
+
+- Similar, using filtering in `ascli`:
+
+  ```bash
+  ascli faspex5 packages list @ruby:'->(p){p["state"].eql?("released")}'
+  ```
 
 ### Faspex 5: Receive a package
 
-The (numeric) identifier of the package t receive is given as argument to command `faspex5 packages receive`.
+To receive one, or several packages at once, use command `faspex5 packages receive`.
+Provide either a single package id, or an extended value `Array` of package ids, e.g. `@list:,1,2,3` as argument.
 
-> **Note:** option `box` applies.
+The same options as for `faspex5 packages list` can be used to select the box and filter the packages to download.
+I.e. options `box` and `query`, as well as last positional parameter `Proc` (filter).
 
-### Faspex 5: List packages
+Option `--once-only=yes` can be used, for "cargo-like" behavior.
+Special package id `INIT` initializes the persistency of already received packages when option `--once-only=yes` is used.
 
-The following parameters in option `query` are supported:
+Special package id `ALL` selects all packages (of the selected box).
+In this case, typically, only `completed` packages should be downloaded, so use option `--query=@json:'{"status":"completed"}'`.
 
-- `q` : a filter on name (case insensitive, matches if value is contained in name)
-- `max` : maximum number of items to retrieve (stop pages when the maximum is passed)
-- `pmax` : maximum number of pages to request (stop pages when the maximum is passed)
-- `offset` : native api parameter, in general do not use (added by `ascli`)
-- `limit` : native api parameter, number of items par api call, in general do not use (added by `ascli`)
+If a package is password protected, then the content protection password is asked interactively.
+To keep the content encrypted, use option: `--ts=@json:'{"content_protection":null}'`, or provide the password instead of `null`.
 
-Admin only: If the value `ALL` is provided to option `box`, then all packages are selected.
+> **Tip:** If you use option `query` and/or positional `filter`, you can use the `list` command for a dry run.
 
 ### Faspex 5: List all shared inboxes and work groups
 
@@ -5784,7 +5921,7 @@ ascli faspex5 packages send @json:'{"title":"hello","recipients":[{"name":"_reci
 To receive all packages, only once, through persistency of already received packages:
 
 ```bash
-ascli faspex5 packages receive ALL --once-only=yes
+ascli faspex5 packages receive ALL --once-only=yes --query=@json:'{"status":"completed"}'
 ```
 
 To initialize, and skip all current package so that next time `ALL` is used, only newer packages are downloaded:
@@ -5808,33 +5945,34 @@ The following parameters are supported:
 
 | parameter                  | type    | default                | description                                         |
 |----------------------------|---------|------------------------|-----------------------------------------------------|
-| url                        | string  | <http://localhost:8080>  | Defines the base url on which requests are listened |
-| certificate                | hash    | nil                    | used to define certificate if https is used         |
-| certificate.key            | string  | nil                    | path to private key file                            |
-| certificate.cert           | string  | nil                    | path to certificate                                 |
-| certificate.chain          | string  | nil                    | path to intermediary certificates                   |
-| processing                 | hash    | nil                    | behavior of post processing                        |
-| processing.script_folder   | string  | .                      | prefix added to script path                         |
-| processing.fail_on_error   | bool    | false                  | if true and process exit with non zero, then fail   |
-| processing.timeout_seconds | integer | 60                     | processing script is killed if takes more time      |
+<!-- markdownlint-disable-next-line -->
+| url                        | string  | http://localhost:8080  | Base url on which requests are listened             |
+| certificate                | hash    | nil                    | Certificate information (if HTTPS)                  |
+| certificate.key            | string  | nil                    | Path to private key file                            |
+| certificate.cert           | string  | nil                    | Path to certificate                                 |
+| certificate.chain          | string  | nil                    | Path to intermediary certificates                   |
+| processing                 | hash    | nil                    | Behavior of post processing                         |
+| processing.script_folder   | string  | .                      | Prefix added to script path                         |
+| processing.fail_on_error   | bool    | false                  | Fail if true and process exit with non zero         |
+| processing.timeout_seconds | integer | 60                     | Max. execution time before script is killed         |
 
 Parameter `url` defines:
 
-- if http or https is used
-- the local port
-- the "domain", i.e. main path of url
+- If `http` or `https` is used
+- The local port number
+- The **base path**, i.e. the path under which requests are received.
 
 When a request is received the following happens:
 
-- the processor get the path of the url called
-- it removes the "domain
-- it prepends it with the value of `script_folder`
-- it executes the script
-- upon success, a success code is returned
+- The processor get the path of the url called
+- It removes the **base path**
+- It prepends it with the value of `script_folder`
+- It executes the script
+- Upon success, a success code is returned
 
 In Faspex 5, configure like this:
 
-`Webhook endpoint URI` : `http://localhost:8080/processing/script1.sh`
+**Webhook endpoint URI** : `http://localhost:8080/processing/script1.sh`
 
 Then, the postprocessing script executed will be `script1.sh`.
 
@@ -5859,8 +5997,8 @@ By default it looks in box `inbox`, but the following boxes are also supported:
 
 A user can receive a package because the recipient is:
 
-- the user himself (default)
-- the user is member of a dropbox/workgroup: filter using option `recipient` set with value `*<name of dropbox/workgroup>`
+- The user himself (default)
+- The user is member of a dropbox/workgroup: filter using option `recipient` set with value `*<name of dropbox/workgroup>`
 
 #### Option `query`
 
@@ -5874,7 +6012,7 @@ As inboxes may be large, it is possible to use the following query parameters:
 
 (SQL query is `LIMIT <startIndex>, <count>`)
 
-The API is listed in [Faspex 4 API Reference](https://developer.ibm.com/apis/catalog/?search=faspex) under "Services (API v.3)".
+The API is listed in [Faspex 4 API Reference](https://developer.ibm.com/apis/catalog/?search=faspex) under **Services (API v.3)**.
 
 If no parameter `max` or `pmax` is provided, then all packages will be listed in the inbox, which result in paged API calls (using parameter: `count` and `page`).
 By default `count` is `0` (`10`), it can be increased to issue less HTTP calls.
@@ -5891,9 +6029,9 @@ List a maximum of 20 items grouped by pages of 20, with maximum 2 pages in recei
 
 The command is `package recv`, possible methods are:
 
-- provide a package id with option `id`
-- provide a public link with option `link`
-- provide a `faspe:` URI with option `link`
+- Provide a package id with option `id`
+- Provide a public link with option `link`
+- Provide a `faspe:` URI with option `link`
 
 ```bash
 ascli faspex package recv 12345
@@ -5951,7 +6089,7 @@ ascli faspex package send --delivery-info=@json:'{"title":"test pkg 1","recipien
 
 In this example the notification template is directly provided on command line. Package information placed in the message are directly taken from the tags in transfer spec. The template can be placed in a file using modifier: `@file:`
 
-### Operation on "dropboxes"
+### Operation on dropboxes
 
 Example:
 
@@ -5963,9 +6101,8 @@ ascli faspex v4 dropbox delete 36
 
 ### Remote sources
 
-Faspex lacks an API to list the contents of a remote source (available in web UI). To workaround this,
-the node API is used, for this it is required to add a section ":storage" that links
-a storage name to a node config and sub path.
+Faspex lacks an API to list the contents of a remote source (available in web UI).
+To workaround this, the node API is used, for this it is required to set option: `storage` that links a storage name to a node configuration and sub path.
 
 Example:
 
@@ -5988,7 +6125,7 @@ In this example, a faspex storage named `my_storage` exists in Faspex, and is lo
 under the docroot in `/mydir` (this must be the same as configured in Faspex).
 The node configuration name is `my_faspex_node` here.
 
-> **Note:** the v4 API provides an API for nodes and shares.
+> **Note:** The v4 API provides an API for nodes and shares.
 
 ### Automated package download (cargo)
 
@@ -6007,23 +6144,23 @@ faspex dropbox list --recipient="*my_dbx"
 faspex health
 faspex login_methods
 faspex me
-faspex package list --box=sent --fields=package_id --format=csv --display=data --query=@json:'{"max":1}'
-faspex package list --fields=package_id --format=csv --display=data --query=@json:'{"max":1}'
+faspex package list --box=sent --query=@json:'{"max":1}' --fields=package_id --display=data --format=csv --output=f4_prs2
+faspex package list --query=@json:'{"max":1}' --fields=package_id --display=data --format=csv --output=f4_prs1
 faspex package list --query=@json:'{"max":5}'
-faspex package list --recipient="*my_dbx" --format=csv --fields=package_id --query=@json:'{"max":1}'
-faspex package list --recipient="*my_wkg" --format=csv --fields=package_id --query=@json:'{"max":1}'
-faspex package recv --to-folder=. --link=https://app.example.com/recv_from_user_path
-faspex package recv ALL --to-folder=. --once-only=yes --query=@json:'{"max":10}'
-faspex package recv f4_db_id1 --recipient="*my_dbx" --to-folder=.
-faspex package recv f4_db_id2 --recipient="*my_wkg" --to-folder=.
-faspex package recv f4_pri1 --to-folder=.
-faspex package recv f4_prs2 --to-folder=. --box=sent
-faspex package send --delivery-info=@json:'{"title":"Important files delivery","recipients":["*my_dbx"]}' test_file.bin
-faspex package send --delivery-info=@json:'{"title":"Important files delivery","recipients":["*my_wkg"]}' test_file.bin
-faspex package send --delivery-info=@json:'{"title":"Important files delivery","recipients":["my_email_internal","my_username"]}' test_file.bin
-faspex package send --delivery-info=@json:'{"title":"TIMESTAMP package remote","recipients":["my_email_internal"]}' --remote_source=%name:my_src sample_source.txt
-faspex package send --link=https://app.example.com/send_to_dropbox_path --delivery-info=@json:'{"title":"Important files delivery"}' test_file.bin
-faspex package send --link=https://app.example.com/send_to_user_path --delivery-info=@json:'{"title":"Important files delivery"}' test_file.bin
+faspex package list --recipient="*my_dbx" --format=csv --fields=package_id --query=@json:'{"max":1}' --output=f4_db_id1
+faspex package list --recipient="*my_wkg" --format=csv --fields=package_id --query=@json:'{"max":1}' --output=f4_db_id2
+faspex package receive --to-folder=. --link=https://app.example.com/recv_from_user_path
+faspex package receive ALL --once-only=yes --to-folder=. --query=@json:'{"max":10}'
+faspex package receive f4_db_id1 --recipient="*my_dbx" --to-folder=.
+faspex package receive f4_db_id2 --recipient="*my_wkg" --to-folder=.
+faspex package receive f4_pri1 --to-folder=.
+faspex package receive f4_prs2 --to-folder=. --box=sent
+faspex package send --delivery-info=@json:'{"title":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["*my_dbx"]}' test_file.bin
+faspex package send --delivery-info=@json:'{"title":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["*my_wkg"]}' test_file.bin
+faspex package send --delivery-info=@json:'{"title":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_email_internal","my_username"]}' test_file.bin
+faspex package send --delivery-info=@json:'{"title":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_email_internal"]}' --remote_source=%name:my_src sample_source.txt
+faspex package send --link=https://app.example.com/send_to_dropbox_path --delivery-info=@json:'{"title":"$(notdir test) PACKAGE_TITLE_BASE"}' test_file.bin
+faspex package send --link=https://app.example.com/send_to_user_path --delivery-info=@json:'{"title":"$(notdir test) PACKAGE_TITLE_BASE"}' test_file.bin
 faspex source info %name:my_src --storage=@preset:faspex4_storage
 faspex source list
 faspex source node %name:my_src br / --storage=@preset:faspex4_storage
@@ -6035,25 +6172,41 @@ faspex v4 wmembership list
 faspex v4 workgroup list
 ```
 
-## <a id="shares"></a>Plugin: `shares`: IBM Aspera Shares v1
+## <a id="shares"></a>Plugin: `shares`: IBM Aspera Shares v1
+
+Aspera Shares supports the **node API** for the file transfer part.
+
+Supported commands are listed in Share's API documentation:
+
+<https://developer.ibm.com/apis/catalog/aspera--aspera-shares-api/Introduction>
+
+Example:
+
+```bash
+ascli shares admin share create @json:'{"node_id":1,"name":"test1","directory":"test1","create_directory":true}'
+
+share_id=$(ascli shares admin share list --select=@json:'{"name":"test1"}' --fields=id)
+
+user_id=$(ascli shares admin user list --select=@json:'{"username":"entity1"}' --fields=id)
 
-Aspera Shares supports the "node API" for the file transfer part.
+ascli shares admin share user_permissions $share_id create @json:'{"user_id":'$user_id',"browse_permission":true, "download_permission":true, "mkdir_permission":true,"delete_permission":true,"rename_permission":true,"content_availability_permission":true,"manage_permission":true}'
+```
 
 ### Shares 1 sample commands
 
 ```bash
-shares admin group list
+shares admin group all list
 shares admin node list
 shares admin share list --fields=DEF,-status,status_message
 shares admin share user_permissions 1 list
-shares admin user add --type=ldap the_name
-shares admin user app_authorizations 1 modify @json:'{"app_login":true}'
-shares admin user app_authorizations 1 show
-shares admin user import --type=saml @json:'{"id":"the_id","name_id":"the_name"}'
-shares admin user list
-shares admin user list --type=local
-shares admin user share_permissions 1 list
-shares admin user share_permissions 1 show 1
+shares admin user all app_authorizations 1 modify @json:'{"app_login":true}'
+shares admin user all app_authorizations 1 show
+shares admin user all list
+shares admin user all share_permissions 1 list
+shares admin user all share_permissions 1 show 1
+shares admin user ldap add the_name
+shares admin user local list
+shares admin user saml import @json:'{"id":"the_id","name_id":"the_name"}'
 shares files browse /
 shares files delete my_share1/test_file.bin
 shares files download --to-folder=. my_share1/test_file.bin
@@ -6116,8 +6269,8 @@ If you have those parameters already, then following options shall be provided:
 For example, let us create a default configuration:
 
 ```bash
-ascli conf preset update mycos --bucket=mybucket --endpoint=https://s3.us-east.cloud-object-storage.appdomain.cloud --apikey=abcdefgh --crn=crn:v1:bluemix:public:iam-identity::a/xxxxxxx
-ascli conf preset set default cos mycos
+ascli config preset update mycos --bucket=mybucket --endpoint=https://s3.us-east.cloud-object-storage.appdomain.cloud --apikey=abcdefgh --crn=crn:v1:bluemix:public:iam-identity::a/xxxxxxx
+ascli config preset set default cos mycos
 ```
 
 Then, jump to the transfer example.
@@ -6180,8 +6333,8 @@ The required options for this method are:
 For example, let us create a default configuration:
 
 ```bash
-ascli conf preset update mycos --bucket=laurent --service-credentials=@val:@json:@file:~/service_creds.json --region=us-south
-ascli conf preset set default cos mycos
+ascli config preset update mycos --bucket=laurent --service-credentials=@val:@json:@file:~/service_creds.json --region=us-south
+ascli config preset set default cos mycos
 ```
 
 ### Operations, transfers
@@ -6195,50 +6348,19 @@ ascli cos node info
 ascli cos node upload 'faux:///sample1G?1g'
 ```
 
-> **Note:** we generate a dummy file `sample1G` of size 2GB using the `faux` PVCL (man `ascp` and section above), but you can of course send a real file by specifying a real file instead.
+> **Note:** We generate a dummy file `sample1G` of size 2GB using the `faux` PVCL (man `ascp` and section above), but you can of course send a real file by specifying a real file instead.
 
 ### COS sample commands
 
 ```bash
 cos --bucket=my_bucket_name --endpoint=my_bucket_endpoint --apikey=my_bucket_apikey --crn=my_resource_instance_id node info
-cos --bucket=my_bucket_name --region=my_bucket_region --service-credentials=@json:@file:service_creds.json node info
+cos --bucket=my_bucket_name --region=my_bucket_region --service-credentials=@json:@file:my_cos_svc_cred node info
 cos node access_key show self
 cos node download test_file.bin --to-folder=.
 cos node info --log-level=trace2
 cos node upload test_file.bin
 ```
 
-## <a id="async"></a>IBM Aspera Sync
-
-An interface for the `async` utility is provided in the following plugins:
-
-- server sync
-- node sync
-- aoc files sync (uses node)
-- shares files sync (uses node)
-
-The main advantage over the `async` command line when using `server` is the possibility to use a configuration file, using standard options of `ascli`.
-
-In this case, some of the `sync` parameters are filled by the related plugin using transfer spec parameters (e.g. including token).
-
-> **Note:** All `sync` commands require an `async` enabled license and availability of the `async` executable (and `asyncadmin`).
-
-Two JSON syntax are supported for option `sync_info`.
-
-### async JSON: API format
-
-It is the same payload as specified on the option `--conf` of `async` or in node API `/asyncs`.
-This is the preferred syntax and allows a single session definition.
-But there is no progress output nor error messages.
-
-Documentation on Async node API can be found on [IBM Developer Portal](https://developer.ibm.com/apis/catalog?search=%22aspera%20sync%20api%22).
-
-### async JSON: Options mapping
-
-`ascli` defines a JSON equivalent to regular `async`options.
-It is based on a JSON representation of `async` command line options.
-It allows definition of multiple sync sessions in a single command, although usually only one sync session is defined.
-
 ## <a id="preview"></a>Plugin: `preview`: Preview generator for AoC
 
 The `preview` generates thumbnails (office, images, video) and video previews on storage for use primarily in the Aspera on Cloud application.
@@ -6249,6 +6371,8 @@ Several parameters can be used to tune several aspects:
 - Methods for generation of video preview
 - Parameters for video handling
 
+See also <https://github.com/IBM/aspera-on-cloud-file-previews>
+
 ### Aspera Server configuration
 
 Specify the previews folder as shown in:
@@ -6264,7 +6388,7 @@ asconfigurator -x "server;preview_dir,previews"
 asnodeadmin --reload
 ```
 
-> **Note:** the configuration `preview_dir` is **relative** to the storage root, no need leading or trailing `/`. In general just set the value to `previews`
+> **Note:** The configuration `preview_dir` is **relative** to the storage root, no need leading or trailing `/`. In general just set the value to `previews`
 
 If another folder is configured on the HSTS, then specify it to `ascli` using the option `previews_folder`.
 
@@ -6283,16 +6407,16 @@ asconfigurator -x "server; max_request_file_create_size_kb,16384"
 
 If you use a value different than 16777216, then specify it using option `max_size`.
 
-> **Note:** the HSTS parameter (`max_request_file_create_size_kb`) is in **kiloBytes** while the generator parameter is in **Bytes** (factor of 1024).
+> **Note:** The HSTS parameter (`max_request_file_create_size_kb`) is in **kiloBytes** while the generator parameter is in **Bytes** (factor of 1024).
 
 ### <a id="prev_ext"></a>External tools: Linux
 
 `ascli` requires the following external tools available in the `PATH`:
 
-- ImageMagick : `convert` `composite`
-- "OptiPNG" : `optipng`
-- "FFmpeg" : `ffmpeg` `ffprobe`
-- "Libreoffice" : `libreoffice`
+- **ImageMagick** : `convert` `composite`
+- **OptiPNG** : `optipng`
+- **FFmpeg** : `ffmpeg` `ffprobe`
+- **Libreoffice** : `libreoffice`
 
 Here shown on Redhat/CentOS.
 
@@ -6421,7 +6545,7 @@ case "$*" in *trev*) tmout=10m ;; *) tmout=30m ;; esac
 
 - `trevents` : only recently uploaded files will be tested (transfer events)
 - `events` : only recently uploaded files will be tested (file events: not working)
-- `scan` : recursively scan all files under the access key&apos;s "storage root"
+- `scan` : recursively scan all files under the access key&apos;s **storage root**
 - `test` : test using a local file
 
 Once candidate are selected, once candidates are selected,
@@ -6460,11 +6584,11 @@ Use option `skip_format` to skip generation of a format.
 
 The preview generator supports rendering of those file categories:
 
-- image
-- pdf
-- plaintext
-- office
-- video
+- `image`
+- `pdf`
+- `plaintext`
+- `office`
+- `video`
 
 To avoid generation for some categories, specify a list using option `skip_types`.
 
@@ -6487,7 +6611,7 @@ In this case the `preview` command will first analyze the file content using `mi
 
 If the `mimemagic` gem complains about missing mime info file:
 
-- any OS:
+- Any OS:
 
   - Examine the error message
   - Download the file: [`freedesktop.org.xml.in`](https://gitlab.freedesktop.org/xdg/shared-mime-info/-/raw/master/data/freedesktop.org.xml.in)
@@ -6511,7 +6635,7 @@ If the `mimemagic` gem complains about missing mime info file:
 dnf install shared-mime-info
 ```
 
-- macOS:
+- **macOS**:
 
 ```bash
 brew install shared-mime-info
@@ -6542,9 +6666,153 @@ preview show --base=test my_mpg mp4 --video-conversion=reencode
 preview show --base=test my_pdf
 preview test --base=test my_dcm
 preview test --base=test my_mxf mp4 --video-conversion=blend --query=@json:'{"text":true,"double":true}'
+preview test --mimemagic=yes --base=test my_dcm
 preview trevents --once-only=yes --skip-types=office --log-level=info
 ```
 
+## <a id="async"></a>IBM Aspera Sync
+
+An interface for the `async` utility is provided in the following plugins:
+
+- `server sync`
+- `node sync`
+- `aoc files sync` (uses node)
+- `shares files sync` (uses node)
+
+The main advantage over the `async` command line when using `server` is the possibility to use a configuration file, using standard options of `ascli`.
+
+In this case, some of the `sync` parameters are filled by the related plugin using transfer spec parameters (e.g. including token).
+
+> **Note:** All `sync` commands require an `async` enabled license and availability of the `async` executable (and `asyncadmin`).
+
+Two JSON syntax are supported for option `sync_info`.
+
+### `async` JSON: API format
+
+It is the same payload as specified on the option `--conf` of `async` or in node API `/asyncs`.
+This is the preferred syntax and allows a single session definition.
+But there is no progress output nor error messages.
+
+Documentation on Async node API can be found on [IBM Developer Portal](https://developer.ibm.com/apis/catalog?search=%22aspera%20sync%20api%22).
+
+### `async` JSON: Options mapping
+
+`ascli` defines a JSON equivalent to regular `async`options.
+It is based on a JSON representation of `async` command line options.
+It allows definition of multiple sync sessions in a single command, although usually only one sync session is defined.
+
+## Hot folder
+
+### Requirements
+
+`ascli` maybe used as a simple hot folder engine.
+A hot folder being defined as a tool that:
+
+- Locally (or remotely) detects new files in a top folder
+- Send detected files to a remote (respectively, local) repository
+- Only sends new files, do not re-send already sent files
+- Optionally: sends only files that are not still **growing**
+- Optionally: after transfer of files, deletes or moves to an archive
+
+In addition: the detection should be made **continuously** or on specific time/date.
+
+### Setup procedure
+
+The general idea is to rely on :
+
+- Existing `ascp` features for detection and transfer
+- Take advantage of `ascli` configuration capabilities and server side knowledge
+- The OS scheduler for reliability and continuous operation
+
+#### `ascp` features
+
+Interesting `ascp` features are found in its arguments: (see `ascp` manual):
+
+- `ascp` already takes care of sending only **new** files: option `-k 1,2,3` (`resume_policy`)
+- `ascp` has some options to remove or move files after transfer: `--remove-after-transfer`, `--move-after-transfer`, `--remove-empty-directories` (`remove_after_transfer`, `move_after_transfer`, `remove_empty_directories`)
+- `ascp` has an option to send only files not modified since the last X seconds: `--exclude-newer-than`, `--exclude-older-than` (`exclude_newer_than`,`exclude_older_than`)
+- `--src-base` (`src_base`) if top level folder name shall not be created on destination
+
+> **Note:** `ascli` takes transfer parameters exclusively as a [*transfer-spec*](#transferspec), with `ts` option.
+>
+> **Note:** Most, but not all, native `ascp` arguments are available as standard [*transfer-spec*](#transferspec) parameters.
+>
+> **Note:** Only for the [`direct`](#agt_direct) transfer agent (not others, like connect or node), native `ascp` arguments can be provided with parameter `ascp_args` of option `transfer_info` .
+
+#### Server side and configuration
+
+Virtually any transfer on a **repository** on a regular basis might emulate a hot folder.
+
+> **Note:** File detection is not based on events (`inotify`, etc...), but on a simple folder scan on source side.
+>
+> **Note:** Parameters may be saved in a [option preset](#lprt) and used with `-P`.
+
+#### Scheduling
+
+Once `ascli` parameters are defined, run the command using the OS native scheduler, e.g. every minutes, or 5 minutes, etc...
+Refer to section [Scheduler](#scheduler). (on use of option `lock_port`)
+
+### Example: Upload hot folder
+
+```bash
+ascli server upload source_hot --to-folder=/Upload/target_hot --lock-port=12345 --ts=@json:'{"remove_after_transfer":true,"remove_empty_directories":true,"exclude_newer_than:-8,"src_base":"source_hot"}'
+```
+
+The local folder (here, relative path: `source_hot`) is sent (upload) to an aspera server.
+Source files are deleted after transfer.
+Growing files will be sent only once they don't grow anymore (based on an 8-second cool-off period).
+If a transfer takes more than the execution period, then the subsequent execution is skipped (`lock_port`) preventing multiple concurrent runs.
+
+### Example: Unidirectional synchronization (upload) to server
+
+```bash
+ascli server upload source_sync --to-folder=/Upload/target_sync --lock-port=12345 --ts=@json:'{"resume_policy":"sparse_csum","exclude_newer_than":-8,"src_base":"source_sync"}'
+```
+
+This can also be used with other folder-based applications: Aspera on Cloud, Shares, Node.
+
+### Example: Unidirectional synchronization (download) from Aspera on Cloud Files
+
+```bash
+ascli aoc files download . --to-folder=. --lock-port=12345 --progress-bar=no --display=data --ts=@json:'{"resume_policy":"sparse_csum","target_rate_kbps":50000,"exclude_newer_than":-8,"delete_before_transfer":true}'
+```
+
+> **Note:** Option `delete_before_transfer` will delete files locally, if they are not present on remote side.
+>
+> **Note:** Options `progress` and `display` limit output for headless operation (e.g. cron job)
+
+## Health check and Nagios
+
+Most plugin provide a `health` command that will check the health status of the application. Example:
+
+```bash
+ascli console health
+```
+
+```output
++--------+-------------+------------+
+| status | component   | message    |
++--------+-------------+------------+
+| ok     | console api | accessible |
++--------+-------------+------------+
+```
+
+Typically, the health check uses the REST API of the application with the following exception: the `server` plugin allows checking health by:
+
+- Issuing a transfer to the server
+- Checking web app status with `asctl all:status`
+- Checking daemons process status
+
+`ascli` can be called by Nagios to check the health status of an Aspera server. The output can be made compatible to Nagios with option `--format=nagios` :
+
+```bash
+ascli server health transfer --to-folder=/Upload --format=nagios --progress-bar=no
+```
+
+```output
+OK - [transfer:ok]
+```
+
 ## SMTP for email notifications
 
 `ascli` can send email, for that setup SMTP configuration. This is done with option `smtp`.
@@ -6555,14 +6823,14 @@ The `smtp` option is a `Hash` (extended value) with the following fields:
 | field        | default             | example                    | description                      |
 |--------------|---------------------|----------------------------|----------------------------------|
 | `server`     | -                   | smtp.gmail.com             | SMTP server address              |
-| `tls`        | true                | true                       | enable STARTTLS (port 587)       |
-| `ssl`        | false               | false                      | enable TLS (port 465)            |
-| `port`       | 587 or 465 or 25    | 587                        | port for service                 |
-| `domain`     | domain of server    | gmail.com                  | email domain of user             |
-| `username`   | -                   | john@example.com           | user to authenticate on SMTP server, leave empty for open auth. |
-| `password`   | -                   | my_password_here           | password for above username      |
-| `from_email` | username if defined | johnny@example.com         | address used if receiver replies |
-| `from_name`  | same as email       | John Wayne                 | display name of sender           |
+| `tls`        | true                | true                       | Enable STARTTLS (port 587)       |
+| `ssl`        | false               | false                      | Enable TLS (port 465)            |
+| `port`       | 587 or 465 or 25    | 587                        | Port for service                 |
+| `domain`     | domain of server    | gmail.com                  | Email domain of user             |
+| `username`   | -                   | john@example.com           | User to authenticate on SMTP server, leave empty for open auth. |
+| `password`   | -                   | my_password_here           | Password for above username      |
+| `from_email` | username if defined | johnny@example.com         | Address used if receiver replies |
+| `from_name`  | same as email       | John Wayne                 | Display name of sender           |
 <!-- markdownlint-enable MD034 -->
 
 ### Example of configuration
@@ -6625,10 +6893,10 @@ A default e-mail template is used, but it can be overridden with option `notify_
 
 The environment provided contains the following additional variables:
 
-- subject
-- body
-- global_transfer_status
-- ts
+- `subject`
+- `body`
+- `global_transfer_status`
+- `ts`
 
 Example of template:
 
@@ -6646,9 +6914,9 @@ This gem comes with a second executable tool providing a simplified standardized
 
 It aims at simplifying the startup of a FASP session from a programmatic stand point as formatting a [*transfer-spec*](#transferspec) is:
 
-- common to Aspera Node API (HTTP POST /ops/transfer)
-- common to Aspera Connect API (browser javascript startTransfer)
-- easy to generate by using any third party language specific JSON library
+- Common to Aspera Node API (HTTP POST /ops/transfer)
+- Common to Aspera Connect API (browser javascript startTransfer)
+- Easy to generate by using any third party language specific JSON library
 
 Hopefully, IBM integrates this directly in `ascp`, and this tool is made redundant.
 
@@ -6662,22 +6930,22 @@ If no argument is provided, it assumes a value of: `@json:@stdin:`, i.e. a JSON
 
 During execution, it generates all low level events, one per line, in JSON format on stdout.
 
-There are special "extended" [*transfer-spec*](#transferspec) parameters supported by `asession`:
+There are special **extended** [*transfer-spec*](#transferspec) parameters supported by `asession`:
 
 - `EX_loglevel` to change log level of `ascli`
 - `EX_file_list_folder` to set the folder used to store (exclusively, because of garbage collection) generated file lists. By default it is `[system tmp folder]/[username]_asession_filelists`
 
-> **Note:** In addition, many "EX_" [*transfer-spec*](#transferspec) parameters are supported for the [`direct`](#agt_direct) transfer agent (used by `asession`), refer to section [*transfer-spec*](#transferspec).
+> **Note:** In addition, many (deprecated) `EX_` [*transfer-spec*](#transferspec) parameters are supported for the [`direct`](#agt_direct) transfer agent (used by `asession`), refer to section [*transfer-spec*](#transferspec).
 
 ### Comparison of interfaces
 
-| feature/tool | `asession` | `ascp` | FaspManager | Transfer SDK |
-|--------------|----------|--------|-------------|--------------|
-| language integration | any | any | C/C++<br/>C#/.net<br/>Go<br/>Python<br/>java<br/> | many |
-| required additional components to `ascp` | Ruby<br/>Aspera | - | library<br/>(headers) | daemon |
-| startup | JSON on stdin<br/>(standard APIs:<br/>JSON.generate<br/>Process.spawn) | command line arguments | API | daemon |
-| events | JSON on stdout | none by default<br/>or need to open management port<br/>and proprietary text syntax | callback | callback |
-| platforms | any with Ruby and `ascp` | any with `ascp` (and SDK if compiled) | any with `ascp` | any with `ascp` and transfer daemon |
+| feature/tool          | Transfer SDK | FaspManager                      | `ascp` | `asession` |
+|-----------------------|--------------|---------------------------------|--------|------------|
+| language integration  | Many         | C/C++<br/>C#/.net<br/>Go<br/>Python<br/>java<br/> | Any    | Any        |
+| required additional components to `ascp` | Daemon       | Library<br/>(+headers) | - | Ruby<br/>Aspera gem |
+| startup               | Daemon       | API | Command line arguments | JSON on stdin<br/>(standard APIs:<br/>JSON.generate<br/>Process.spawn) |
+| events                | Poll     | Callback | Possibility to open management port<br/>and proprietary text syntax | JSON on stdout |
+| platforms             | Any with `ascp` and transfer daemon | Any with `ascp` (and SDK if compiled) | Any with `ascp` | Any with Ruby and `ascp` |
 
 ### Simple session
 
@@ -6695,7 +6963,7 @@ asession < session.json
 
 ### Asynchronous commands and Persistent session
 
-`asession` also supports asynchronous commands (on the management port). Instead of the traditional text protocol as described in `ascp` manual, the format for commands is: one single line per command, formatted in JSON, where parameters shall be "snake" style, for example: `LongParameter` -&gt; `long_parameter`
+`asession` also supports asynchronous commands (on the management port). Instead of the traditional text protocol as described in `ascp` manual, the format for commands is: one single line per command, formatted in JSON, where parameters shall be **snake** style, for example: `LongParameter` -&gt; `long_parameter`
 
 This is particularly useful for a persistent session ( with the [*transfer-spec*](#transferspec) parameter: `"keepalive":true` )
 
@@ -6739,126 +7007,6 @@ EXAMPLES
 
 ```
 
-## Hot folder
-
-### Requirements
-
-`ascli` maybe used as a simple hot folder engine.
-A hot folder being defined as a tool that:
-
-- locally (or remotely) detects new files in a top folder
-- send detected files to a remote (respectively, local) repository
-- only sends new files, do not re-send already sent files
-- optionally: sends only files that are not still "growing"
-- optionally: after transfer of files, deletes or moves to an archive
-
-In addition: the detection should be made "continuously" or on specific time/date.
-
-### Setup procedure
-
-The general idea is to rely on :
-
-- existing `ascp` features for detection and transfer
-- take advantage of `ascli` configuration capabilities and server side knowledge
-- the OS scheduler for reliability and continuous operation
-
-#### `ascp` features
-
-Interesting `ascp` features are found in its arguments: (see `ascp` manual):
-
-- `ascp` already takes care of sending only **new** files: option `-k 1,2,3` (`resume_policy`)
-- `ascp` has some options to remove or move files after transfer: `--remove-after-transfer`, `--move-after-transfer`, `--remove-empty-directories` (`remove_after_transfer`, `move_after_transfer`, `remove_empty_directories`)
-- `ascp` has an option to send only files not modified since the last X seconds: `--exclude-newer-than`, `--exclude-older-than` (`exclude_newer_than`,`exclude_older_than`)
-- `--src-base` (`src_base`) if top level folder name shall not be created on destination
-
-> **Note:** `ascli` takes transfer parameters exclusively as a [*transfer-spec*](#transferspec), with `ts` option.
->
-> **Note:** Most, but not all, native `ascp` arguments are available as standard [*transfer-spec*](#transferspec) parameters.
->
-> **Note:** Only for the [`direct`](#agt_direct) transfer agent (not others, like connect or node), native `ascp` arguments can be provided with parameter `ascp_args` of option `transfer_info` .
-
-#### server side and configuration
-
-Virtually any transfer on a "repository" on a regular basis might emulate a hot folder.
-
-> **Note:** file detection is not based on events (`inotify`, etc...), but on a simple folder scan on source side.
->
-> **Note:** parameters may be saved in a [option preset](#lprt) and used with `-P`.
-
-#### Scheduling
-
-Once `ascli` parameters are defined, run the command using the OS native scheduler, e.g. every minutes, or 5 minutes, etc...
-Refer to section [Scheduler](#scheduler). (on use of option `lock_port`)
-
-### Example: Upload hot folder
-
-```bash
-ascli server upload source_hot --to-folder=/Upload/target_hot --lock-port=12345 --ts=@json:'{"remove_after_transfer":true,"remove_empty_directories":true,"exclude_newer_than:-8,"src_base":"source_hot"}'
-```
-
-The local folder (here, relative path: `source_hot`) is sent (upload) to an aspera server.
-Source files are deleted after transfer.
-Growing files will be sent only once they don't grow anymore (based on an 8-second cool-off period).
-If a transfer takes more than the execution period, then the subsequent execution is skipped (`lock_port`) preventing multiple concurrent runs.
-
-### Example: Unidirectional synchronization (upload) to server
-
-```bash
-ascli server upload source_sync --to-folder=/Upload/target_sync --lock-port=12345 --ts=@json:'{"resume_policy":"sparse_csum","exclude_newer_than":-8,"src_base":"source_sync"}'
-```
-
-This can also be used with other folder-based applications: Aspera on Cloud, Shares, Node:
-
-### Example: Unidirectional synchronization (download) from Aspera on Cloud Files
-
-```bash
-ascli aoc files download . --to-folder=. --lock-port=12345 --progress-bar=no --display=data --ts=@json:'{"resume_policy":"sparse_csum","target_rate_kbps":50000,"exclude_newer_than":-8,"delete_before_transfer":true}'
-```
-
-> **Note:** option `delete_before_transfer` will delete files locally, if they are not present on remote side.
->
-> **Note:** options `progress` and `display` limit output for headless operation (e.g. cron job)
-
-## Health check and Nagios
-
-Most plugin provide a `health` command that will check the health status of the application. Example:
-
-```bash
-ascli console health
-```
-
-```output
-+--------+-------------+------------+
-| status | component   | message    |
-+--------+-------------+------------+
-| ok     | console api | accessible |
-+--------+-------------+------------+
-```
-
-Typically, the health check uses the REST API of the application with the following exception: the `server` plugin allows checking health by:
-
-- issuing a transfer to the server
-- checking web app status with `asctl all:status`
-- checking daemons process status
-
-`ascli` can be called by Nagios to check the health status of an Aspera server. The output can be made compatible to Nagios with option `--format=nagios` :
-
-```bash
-ascli server health transfer --to-folder=/Upload --format=nagios --progress-bar=no
-```
-
-```output
-OK - [transfer:ok]
-```
-
-```bash
-ascli server health asctl status --cmd_prefix='sudo ' --format=nagios
-```
-
-```output
-OK - [NP:running, MySQL:running, Mongrels:running, Background:running, DS:running, DB:running, Email:running, Apache:running]
-```
-
 ## Ruby Module: `Aspera`
 
 Main components:
@@ -6869,10 +7017,6 @@ Main components:
 
 Working examples can be found in repo: <https://github.com/laurent-martin/aspera-api-examples> in Ruby examples.
 
-## Changes (Release notes)
-
-See [CHANGELOG.md](CHANGELOG.md)
-
 ## History
 
 When I joined Aspera, there was only one CLI: `ascp`, which is the implementation of the FASP protocol, but there was no CLI to access the various existing products (Server, Faspex, Shares).
@@ -6887,9 +7031,9 @@ There were a few pitfalls:
 
 So, it evolved into `ascli`:
 
-- portable: works on platforms supporting `ruby` (and `ascp`)
-- easy to install with the `gem` utility
-- supports transfers with multiple [Transfer Agents](#agents), that&apos;s why transfer parameters moved from `ascp` command line to [*transfer-spec*](#transferspec) (more reliable , more standard)
+- Portable: works on platforms supporting `ruby` (and `ascp`)
+- Easy to install with the `gem` utility
+- Supports transfers with multiple [Transfer Agents](#agents), that&apos;s why transfer parameters moved from `ascp` command line to [*transfer-spec*](#transferspec) (more reliable , more standard)
 - `ruby` is consistent with other Aspera products
 
 Over the time, a supported command line tool `aspera` was developed in C++, it was later on deprecated.
@@ -6898,17 +7042,20 @@ It had the advantage of being relatively easy to installed, as a single executab
 Enjoy a coffee on me:
 
 ```bash
-ascli conf coffee
-ascli conf coffee --ui=text
+ascli config coffee --ui=text
+ascli config coffee --ui=text --query=@json:'{"text":"true"}'
+ascli config coffee
 ```
 
 ## Common problems
 
+`ascli` detects common problems and provides hints to solve them.
+
 ### Error: "Remote host is not who we expected"
 
 Cause: `ascp` >= 4.x checks fingerprint of highest server host key, including ECDSA. `ascp` < 4.0 (3.9.6 and earlier) support only to RSA level (and ignore ECDSA presented by server). `aspera.conf` supports a single fingerprint.
 
-Workaround on client side: To ignore the certificate (SSH fingerprint) add option on client side (this option can also be added permanently to the config file):
+Workaround on client side: To ignore the certificate (SSH fingerprint) add option on client side (this option can also be added permanently to the configuration file):
 
 ```bash
 --ts=@json:'{"sshfp":null}'
@@ -6927,9 +7074,10 @@ If Ruby was installed as a Linux Packages, then also install Ruby development pa
 
 ### ED255519 key not supported
 
-ED25519 keys are deactivated since version 0.9.24 so this type of key will just be ignored.
+ED25519 keys are deactivated since `ascli` version 0.9.24 as it requires additional gems that require native compilation and thus caused problems.
+This type of key will just be ignored.
 
-Without this deactivation, if such key was present the following error was generated:
+Without this deactivation, if such key was present in user's `.ssh` folder then the following error was generated:
 
 ```output
 OpenSSH keys only supported if ED25519 is available
@@ -6937,3 +7085,5 @@ OpenSSH keys only supported if ED25519 is available
 
 Which meant that you do not have Ruby support for ED25519 SSH keys.
 You may either install the suggested Gems, or remove your ed25519 key from your `.ssh` folder to solve the issue.
+
+To re-activate, set env var `ASCLI_ENABLE_ED25519` to `true`.