aspera-cli 4.11.0 → 4.12.0

data/README.md

@@ -1,11 +1,13 @@
 # Command Line Interface for IBM Aspera products
 <!-- markdownlint-disable MD033 MD003 MD053 -->
-
+<!-- cSpell:ignore devkit zcvf zxvf noded secondfile filesize sedemo eudemo webmail csum eascp loglevel cronfile magick keepalive inotify eastus bluemix trev sshfp struct genkey passout ibmaspera unpermitted -->
+<!-- cSpell:ignoreRegExp /-P[a-z]+/g -->
+<!-- cSpell:ignoreRegExp /my[a-z]+/g -->
 [comment1]: # (Do not edit this README.md, edit docs/README.erb.md, for details, read docs/README.md)
 
 ##
 
-Version : 4.11.0
+Version : 4.12.0
 
 Laurent/2016-2023
 
@@ -64,10 +66,20 @@ For scripting and ad'hoc command line operations, `ascli` is perfect.
 
 ## Notations, Shell, Examples
 
-In examples, command line operations are shown using a shell such: `bash` or `zsh`.
+Command line operations examples are shown using a shell such: `bash` or `zsh`.
 
 Command line parameters in examples beginning with `my_`, like `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)**.
+
+> **Note:** The transfer agent is a client for the remote Transfer Server (HSTS).
+The transfer agent 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`
+
 ## Quick Start
 
 This section guides you from installation, first use and advanced use.
@@ -81,7 +93,7 @@ ascli --version
 ```
 
 ```bash
-4.11.0
+4.12.0
 ```
 
 ### First use
@@ -92,6 +104,8 @@ 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:
 
+<!-- spellchecker: disable -->
+
 ```bash
 ascli config initdemo
 ```
@@ -111,6 +125,8 @@ ascli server browse /
 :............:...........:......:........:...........................:.......................:
 ```
 
+<!-- spellchecker: enable -->
+
 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)
@@ -119,7 +135,7 @@ If you want to use `ascli` with another server, and in order to make further cal
 - download a file
 
 ```bash
-ascli config preset update myserver --url=ssh://demo.asperasoft.com:33001 --username=asperaweb --password=_pass_here_
+ascli config preset update myserver --url=ssh://demo.asperasoft.com:33001 --username=asperaweb --password=my_password_here
 ```
 
 ```output
@@ -142,15 +158,10 @@ ascli server browse /aspera-test-dir-large
 :............:...........:......:..............:...........................:............................:
 :   zmode    :   zuid    : zgid :     size     :           mtime           :            name            :
 :............:...........:......:..............:...........................:............................:
-: -rw-rw-rw- : asperaweb : fasp : 10133504     : 2018-05-04 14:16:24 +0200 : ctl_female_2.fastq.partial :
 : -rw-r--r-- : asperaweb : fasp : 209715200    : 2014-04-10 19:49:27 +0200 : 200MB                      :
 : -rw-r--r-- : asperaweb : fasp : 524288000    : 2014-04-10 19:44:15 +0200 : 500MB                      :
 : -rw-r--r-- : asperaweb : fasp : 5368709120   : 2014-04-10 19:45:52 +0200 : 5GB                        :
 : -rw-r--r-- : asperaweb : fasp : 500000000000 : 2017-06-14 20:09:57 +0200 : 500GB                      :
-: -rw-rw-rw- : asperaweb : fasp : 13606912     : 2018-05-04 14:20:21 +0200 : ctl_male_2.fastq.partial   :
-: -rw-rw-rw- : asperaweb : fasp : 76           : 2018-05-04 14:13:18 +0200 : ctl_female_2.fastq.haspx   :
-: -rw-rw-rw- : asperaweb : fasp : 647348       : 2018-05-04 14:26:39 +0200 : ctl_female_2.gz            :
-: -rw-rw-rw- : asperaweb : fasp : 74           : 2018-05-04 14:16:00 +0200 : ctl_male_2.fastq.haspx     :
 : -rw-r--r-- : asperaweb : fasp : 1048576000   : 2014-04-10 19:49:23 +0200 : 1GB                        :
 : -rw-r--r-- : asperaweb : fasp : 104857600    : 2014-04-10 19:49:29 +0200 : 100MB                      :
 : -rw-r--r-- : asperaweb : fasp : 10737418240  : 2014-04-10 19:49:04 +0200 : 10GB                       :
@@ -242,7 +253,7 @@ ascli -v
 ```
 
 ```text
-4.11.0
+4.12.0
 ```
 
 In order to keep persistency of configuration on the host,
@@ -290,7 +301,7 @@ A convenience sample script is also provided: download the script [`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 behaviour:
+Some environment variables can be set for this script to adapt its behavior:
 
 | env var      | description                        | default                  | example                  |
 |--------------|------------------------------------|--------------------------|--------------------------|
@@ -652,7 +663,7 @@ Using `ascli` with plugin `server` for command line gives advantages over `ascp`
 - 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 (`EX_ascp_args`).
+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`).
 
 ### <a id="parsing"></a>Command line parsing, Special Characters
 
@@ -702,13 +713,13 @@ 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 depoends on the underlying syntax: shell , JSON, etc...
+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.
 
 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.
 
 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 protext the special character ` ` (space) with a backslash. <!-- markdownlint-disable-line -->
+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
@@ -798,9 +809,9 @@ ascli conf echo @ruby:"{'title'=>%q{Test \" ' & \\\\}}" --format=json
 {"title":"Test \" ' & \\"}
 ```
 
-#### Reading special characters interractively
+#### Reading special characters interactively
 
-If `ascli` is used interractively (a user typing on terminal), it is easy to require the user to type values:
+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
@@ -956,7 +967,7 @@ The style of output can be set using the `format` parameter, supporting:
 
 Table output can be filtered using the `select` parameter. Example:
 
-```javascript
+```bash
 ascli aoc admin res user list --fields=name,email,ats_admin --query=@json:'{"sort":"name"}' --select=@json:'{"ats_admin":true}'
 ```
 
@@ -1009,7 +1020,9 @@ The extended value syntax is:
 <0 or more decoders><0 or 1 reader><nothing or some text value>
 ```
 
-The difference between reader and decoder is order and ordinality. Both act like a function of value on right hand side. Decoders are at the beginning of the value, followed by a single optional reader, followed by the optional value.
+The difference between reader and decoder is order and cardinality.
+Both act like a function of value on right hand side.
+Decoders are at the beginning of the value, followed by a single optional reader, followed by the optional value.
 
 The following "readers" are supported (returns value in []):
 
@@ -1019,13 +1032,13 @@ The following "readers" are supported (returns value in []):
 - @path:PATH   : [String] performs path expansion (prefix `~/` is replaced with the users home folder), e.g. `--config-file=@path:~/sample_config.yml`
 - @env:ENVVAR  : [String] read from a named env var, e.g.--password=@env:MYPASSVAR
 - @stdin:      : [String] read from stdin (no value on right)
-- @preset:NAME : [Hash] get whole option preset value by name. Subvalues can also be used using `.` as separator. e.g. `foo.bar` is `conf[foo][bar]`
+- @preset:NAME : [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]`
 
 In addition it is possible to decode a value, using one or multiple decoders :
 
 - @base64: [String] decode a base64 encoded string
 - @json: [any] decode JSON values (convenient to provide complex structures)
-- @zlib: [String] uncompress data
+- @zlib: [String] un-compress data
 - @ruby: [any] execute ruby code
 - @csvt: [Array] decode a titled CSV value
 - @lines: [Array] split a string in multiple lines and return an array
@@ -1040,10 +1053,10 @@ Example: read the content of the specified file, then, base64 decode, then unzip
 ascli config echo @zlib:@base64:@file:myfile.dat
 ```
 
-Example: create a value as a hash, with one key and the value is read from a file:
+Example: Create a value as a hash, with one key and the value is read from a file:
 
 ```bash
-ascli config echo @ruby:'{"token_verification_key"=>File.read("pubkey.txt")}'
+ascli config echo @ruby:'{"token_verification_key"=>File.read("mykey.txt")}'
 ```
 
 Example: read a csv file and create a list of hash for bulk provisioning:
@@ -1073,7 +1086,7 @@ ascli config echo @csvt:@file:test.csv
 
 Example: create a hash and include values from preset named "config" of config file in this hash
 
-```javascript
+```bash
 ascli config echo @incps:@json:'{"hello":true,"incps":["config"]}'
 ```
 
@@ -1123,7 +1136,7 @@ ascli config folder
 C:\Users\Kenji\.aspera\ascli
 ```
 
-When OAuth is used (AoC, Faspex4 apiv4, Faspex5) `ascli` keeps a cache of generated bearer tokens in `[config folder]/persist_store` by default.
+When OAuth is used (AoC, Faspex4 api v4, Faspex5) `ascli` keeps a cache of generated bearer tokens in `[config folder]/persist_store` by default.
 Option `cache_tokens` (**yes**/no) allows to control if Oauth tokens are cached on file system, or generated for each request.
 The command `config flush_tokens` deletes all existing tokens.
 Tokens are kept on disk for a maximum of 30 minutes (`TOKEN_CACHE_EXPIRY_SEC`) and garbage collected after that.
@@ -1157,7 +1170,7 @@ ascli config preset set|delete|show|initialize|update <option preset>
 The command `update` allows the easy creation of [option preset](#lprt) by simply providing the options in their command line format, e.g. :
 
 ```bash
-ascli config preset update demo_server --url=ssh://demo.asperasoft.com:33001 --username=asperaweb --password=_pass_here_ --ts=@json:'{"precalculate_job_size":true}'
+ascli config preset update demo_server --url=ssh://demo.asperasoft.com:33001 --username=asperaweb --password=my_password_here --ts=@json:'{"precalculate_job_size":true}'
 ```
 
 - This creates a [option preset](#lprt) `demo_server` with all provided options.
@@ -1165,13 +1178,13 @@ ascli config preset update demo_server --url=ssh://demo.asperasoft.com:33001 --u
 The command `set` allows setting individual options in a [option preset](#lprt).
 
 ```bash
-ascli config preset set demo_server password _pass_here_
+ascli config preset set demo_server password my_password_here
 ```
 
 The command `initialize`, like `update` allows to set several parameters at once, but it deletes an existing configuration instead of updating it, and expects a [*Structured Value*](#native).
 
-```javascript
-ascli config preset initialize demo_server @json:'{"url":"ssh://demo.asperasoft.com:33001","username":"asperaweb","password":"_pass_here_","ts":{"precalculate_job_size":true}}'
+```bash
+ascli config preset initialize demo_server @json:'{"url":"ssh://demo.asperasoft.com:33001","username":"asperaweb","password":"my_pass_here","ts":{"precalculate_job_size":true}}'
 ```
 
 A full terminal based overview of the configuration can be displayed using:
@@ -1225,7 +1238,7 @@ ascli config preset set default _plugin_name_ _default_preset_for_plugin_
 ascli config preset get default _plugin_name_
 ```
 
-```javascript
+```json
 "_default_preset_for_plugin_"
 ```
 
@@ -1295,7 +1308,7 @@ cli_default:
 demo_server:
   url: ssh://demo.asperasoft.com:33001
   username: asperaweb
-  password: _pass_here_
+  password: my_password_here
 ```
 
 We can see here:
@@ -1370,13 +1383,13 @@ ascli config preset unset cli_default interactive
 Example: Define options using command line:
 
 ```bash
-ascli -N --url=_url_here_ --password=_pass_here_ --username=_name_here_ node --show-config
+ascli -N --url=_url_here_ --password=my_password_here --username=_name_here_ node --show-config
 ```
 
 Example: Define options using a hash:
 
-```javascript
-ascli -N --preset=@json:'{"url":"_url_here_","password":"_pass_here_","username":"_name_here_"}' node --show-config
+```bash
+ascli -N --preset=@json:'{"url":"_url_here_","password":"my_password_here","username":"_name_here_"}' node --show-config
 ```
 
 #### Shares Examples
@@ -1386,7 +1399,7 @@ only username/password and url are required (either on command line, or from con
 Those can usually be provided on the command line:
 
 ```bash
-ascli shares repo browse / --url=https://10.25.0.6 --username=john --password=_pass_here_
+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:
@@ -1396,19 +1409,19 @@ This can also be provisioned in a config file:
 ```bash
 ascli config preset set shares06 url https://10.25.0.6
 ascli config preset set shares06 username john
-ascli config preset set shares06 password _pass_here_
+ascli config preset set shares06 password my_password_here
 ```
 
 This can also be done with one single command:
 
-```javascript
-ascli config preset init shares06 @json:'{"url":"https://10.25.0.6","username":"john","password":"_pass_here_"}'
+```bash
+ascli config preset init shares06 @json:'{"url":"https://10.25.0.6","username":"john","password":"my_password_here"}'
 ```
 
 or
 
 ```bash
-ascli config preset update shares06 --url=https://10.25.0.6 --username=john --password=_pass_here_
+ascli config preset update shares06 --url=https://10.25.0.6 --username=john --password=my_password_here
 ```
 
 - Define this [option preset](#lprt) as the default [option preset](#lprt) for the specified plugin (`shares`)
@@ -1452,13 +1465,13 @@ export ASCLI_VAULT_PASSWORD
 read -s ASCLI_VAULT_PASSWORD
 ```
 
-#### Vault: System keychain
+#### Vault: System key chain
 
 > **Note:** **macOS only**
 
-It is possible to manage secrets in macOS keychain (only read supported currently).
+It is possible to manage secrets in macOS key chain (only read supported currently).
 
-```json
+```bash
 --vault=@json:'{"type":"system","name":"ascli"}'
 ```
 
@@ -1466,7 +1479,7 @@ It is possible to manage secrets in macOS keychain (only read supported currentl
 
 It is possible to store and use secrets encrypted in a file.
 
-```json
+```bash
 --vault=@json:'{"type":"file","name":"vault.bin"}'
 ```
 
@@ -1484,7 +1497,7 @@ Then secrets can be manipulated using commands:
 - `delete`
 
 ```bash
-ascli conf vault create mylabel @json:'{"password":"__value_here__","description":"for this account"}'
+ascli conf vault create mylabel @json:'{"password":"my_password_here","description":"for this account"}'
 ```
 
 #### <a id="config_finder"></a>Configuration Finder
@@ -1506,7 +1519,7 @@ For a more secure storage one can do:
 
 ```bash
 `ascli` conf preset update myconf --url=... --username=... --password=@val:@vault:myconf.password
-`ascli` conf vault create myconf @json:'{"password":"__value_here__"}'
+`ascli` conf vault create myconf @json:'{"password":"my_password_here"}'
 ```
 
 > **Note:** use `@val:` in front of `@vault:` so that the extended value is not evaluated.
@@ -1529,9 +1542,9 @@ Typically, in `$HOME/.ssh` or `$HOME/.aspera/ascli`:
 PRIVKEYFILE=~/.aspera/ascli/my_private_key
 ```
 
-Several methods can be used to generate a key pair:
+Several methods can be used to generate a key pair.
 
-- `ascli`
+#### `ascli` for key generation
 
 The generated key is of type RSA, by default: 4096 bit.
 For convenience, the public key is also extracted with extension `.pub`.
@@ -1541,7 +1554,7 @@ The key is not passphrase protected.
 ascli config genkey ${PRIVKEYFILE} 4096
 ```
 
-- `ssh-keygen`
+#### `ssh-keygen`
 
 Both private and public keys are generated, option `-N` is for passphrase.
 
@@ -1549,24 +1562,27 @@ Both private and public keys are generated, option `-N` is for passphrase.
 ssh-keygen -t rsa -b 4096 -m PEM -N '' -f ${PRIVKEYFILE}
 ```
 
-- `openssl`
+#### `openssl`
 
 To generate a private key pair with a passphrase the following can be used on any system:
-
+<!-- spellchecker: disable -->
 ```bash
 openssl genrsa -passout pass:_passphrase_here_ -out ${PRIVKEYFILE}.protected 4096
 openssl rsa -pubout -in ${PRIVKEYFILE} -out ${PRIVKEYFILE}.pub
 ```
+<!-- spellchecker: enable -->
 
 `openssl` is sometimes compiled to support option `-nodes` (no DES, i.e. no passphrase, e.g. on macOS).
 In that case, add option `-nodes` instead of `-passout pass:_passphrase_here_` to generate a key without passphrase.
 
 If option `-nodes` is not available, the passphrase can be removed using this method:
 
+<!-- spellchecker: disable -->
 ```bash
 openssl rsa -passin pass:_passphrase_here_ -in ${PRIVKEYFILE}.protected -out ${PRIVKEYFILE}
 rm -f ${PRIVKEYFILE}.protected
 ```
+<!-- spellchecker: enable -->
 
 To change (or add) the passphrase for a key do:
 
@@ -1610,9 +1626,9 @@ ascli conf plugin list
 
 #### <a id="createownplugin"></a>Create your own plugin
 
-By default plugins are looked-up in folders specifed by (multi-value) option `plugin_folder`:
+By default plugins are looked-up in folders specified by (multi-value) option `plugin_folder`:
 
-```javascript
+```bash
 ascli --show-config --select=@json:'{"key":"plugin_folder"}'
 ```
 
@@ -1661,7 +1677,7 @@ Available loggers: `stdout`, `stderr`, `syslog`.
 
 Available levels: `debug`, `info`, `warn`, `error`.
 
-> **Note:** When using the `direct` agent (`ascp`), additional transfer logs can be activated using `ascp` option `EX_ascp_args`, see [`direct`](#agt_direct).
+> **Note:** When using the `direct` agent (`ascp`), additional transfer logs can be activated using `ascp` options and `ascp_args`, see [`direct`](#agt_direct).
 
 Examples:
 
@@ -1707,7 +1723,7 @@ Like any other option, those can be set either on command line, or in config fil
 
 Example:
 
-```javascript
+```bash
 ascli aoc admin res package list --http-options=@json:'{"read_timeout":10.0}'
 ```
 
@@ -1739,7 +1755,7 @@ Refer to the following sections.
 There are two possibilities to define an HTTP proxy to be used when Ruby HTTP is used.
 
 The `http_proxy` environment variable (**lower case**, preferred) can be set to the URL of the proxy, e.g. `http://myproxy.org.net:3128`.
-Refer to [Ruby findproxy](https://rubyapi.org/3.0/o/uri/generic#method-i-find_proxy).
+Refer to [Ruby find proxy](https://rubyapi.org/3.0/o/uri/generic#method-i-find_proxy).
 
 > **Note:** Ruby expects a URL and `myproxy.org.net:3128` alone is **not** accepted.
 
@@ -1794,8 +1810,7 @@ ascli --proxy-credentials=@list::__username_here__:__password_here__ ...
 
 ### Proxy for Legacy Aspera HTTP/S Fallback
 
-To specify a proxy for legacy HTTP fallback, set the [*transfer-spec*](#transferspec) parameter: `EX_http_proxy_url` (only supported with the `direct` agent).
-(It is also possible to use `EX_ascp_args` and native options in `direct`)
+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
 
@@ -1803,7 +1818,8 @@ To specify a FASP proxy (forward), set the [*transfer-spec*](#transferspec) para
 
 ### <a id="client"></a>FASP configuration
 
-The `config` plugin also allows specification for the use of a local FASP client. It provides the following commands for `ascp` subcommand:
+The `config` plugin also allows specification for the use of a local FASP **client**.
+It provides the following commands for `ascp` subcommand:
 
 - `show` : shows the path of `ascp` used
 - `use` : list,download connect client versions available on internet
@@ -1941,12 +1957,12 @@ Time: 00:00:02 =========================================================== 100%
 Downloaded: IBMAsperaConnectInstaller-3.11.2.63.dmg
 ```
 
-### <a id="agents"></a>Transfer Agents
+### <a id="agents"></a>Transfer Clients: Agents
 
 Some of the actions on Aspera Applications lead to file transfers (upload and download) using the FASP protocol (`ascp`).
 
 When a transfer needs to be started, a [*transfer-spec*](#transferspec) has been internally prepared.
-This [*transfer-spec*](#transferspec) will be executed by a transfer client, here called "Transfer Agent".
+This [*transfer-spec*](#transferspec) will be executed by a transfer client, here called **Transfer Agent**.
 
 There are currently 3 agents:
 
@@ -1975,6 +1991,7 @@ The `transfer_info` option accepts the following optional parameters to control
 | 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 |
@@ -2000,33 +2017,33 @@ ascli config ascp errors
 
 Examples:
 
-```javascript
+```bash
 ascli ... --transfer-info=@json:'{"wss":true,"resume":{"iter_max":20}}'
 ascli ... --transfer-info=@json:'{"spawn_delay_sec":2.5,"multi_incr_udp":false}'
 ```
 
 > **Note:** The `direct` agent supports additional `transfer_spec` parameters starting with `EX_` (extended).
-In particular the field, `EX_ascp_args` which is a list of additional command line options to `ascp`.
+But it is preferred to use the option `transfer_info` with parameter `ascp_args`.
 
 This can be useful to activate logging using option `-L` of `ascp`.
-For example the option `--ts=@json:'{"EX_ascp_args":["-DDL-"]}'` will activate debug level 2 for `ascp` (`DD`), and display those logs on the terminal (`-`).
+For example the option `--transfer-info=@json:'{"ascp_args":["-DDL-"]}'` will activate debug level 2 for `ascp` (`DD`), and display those logs on the terminal (`-`).
 This is useful if the transfer fails.
-To store `ascp` logs in file `aspera-scp-transfer.log` in a folder, use `--ts=@json:'{"EX_ascp_args":["-L","/path/to/folder"]}'`.
+To store `ascp` logs in file `aspera-scp-transfer.log` in a folder, use `--transfer-info=@json:'{"ascp_args":["-L","/path/to/folder"]}'`.
 
-> **Note:** Implementation note: when transfer agent [`direct`](#agt_direct) is used, the list of files to transfer is provided to `ascp` using either `--file-list` or `--file-pair-list` and a file list (or pair) file generated in a temporary folder. (unless `--file-list` or `--file-pair-list` is provided in option `ts` in `EX_ascp_args`).
+> **Note:** When transfer agent [`direct`](#agt_direct) is used, the list of files to transfer is provided to `ascp` using either `--file-list` or `--file-pair-list` and a file list (or pair) file generated in a temporary folder. (unless `--file-list` or `--file-pair-list` is provided using `transfer_info` parameter `ascp_args`).
 
 In addition to standard methods described in section [File List](#file_list), it is possible to specify the list of file using those additional methods:
 
 - Using the pseudo [*transfer-spec*](#transferspec) parameter `EX_file_list`
 
-```javascript
---sources=@ts --ts=@json:'{"EX_file_list":"filelist.txt"}'
+```bash
+--sources=@ts --ts=@json:'{"EX_file_list":"file_list.txt"}'
 ```
 
-- Using the pseudo [*transfer-spec*](#transferspec) parameter `EX_ascp_args`
+- Using option `transfer_info` parameter `ascp_args`
 
-```javascript
---sources=@ts --ts=@json:'{"EX_ascp_args":["--file-list","myfilelist"]}'
+```bash
+--sources=@ts --transfer-info=@json:'{"ascp_args":["--file-list","myfilelist"]}'
 ```
 
 > **Note:** File lists is shown here, there are also similar options for file pair lists.
@@ -2035,17 +2052,6 @@ In addition to standard methods described in section [File List](#file_list), it
 >
 > **Note:** Those methods have limitations: they apply **only** to the [`direct`](#agt_direct) transfer agent (i.e. local `ascp`) and not for Aspera on Cloud.
 
-In addition to special transfer spec parameter `EX_ascp_args`, it is possible to provide the same `ascp` options using option `ascp_opts` of `ascli`.
-This option expects an `Array`, which can be conveniently provided with extended syntax `@list:`
-
-```bash
-ascli server download /aspera-test-dir-large/200MB --ascp-opts=@list:' -l 10m -k 3'
-```
-
-> **Note:** Using `@list:`, the use of quotes and leading character "space" here is important: The `@list:` expects a single string which must not be parsed by the shell (so protected with quotes) and the leading space is the separator character.
->
-> **Note:** The option `ascp_opts` are appended to `EX_ascp_args` if present.
-
 #### <a id="agt_connect"></a>IBM Aspera Connect Client GUI
 
 By specifying option: `--transfer=connect`, `ascli` will start transfers using the locally installed Aspera Connect Client. There are no option for `transfer_info`.
@@ -2064,8 +2070,8 @@ Parameters provided in option `transfer_info` are:
 | root_id | string | password or secret</br>Mandatory only for bearer token |
 
 Like any other option, `transfer_info` can get its value from a pre-configured [option preset](#lprt) :
-`--transfer-info=@preset:<psetname>` or be specified using the extended value syntax :
-`--transfer-info=@json:'{"url":"https://...","username":"theuser","password":"_pass_here_"}'`
+`--transfer-info=@preset:_name_here_` or be specified using the extended value syntax :
+`--transfer-info=@json:'{"url":"https://...","username":"_user_here_","password":"my_password_here"}'`
 
 If `transfer_info` is not specified and a default node has been configured (name in `node` for section `default`) then this node is used by default.
 
@@ -2077,15 +2083,15 @@ If it possible to send using a HTTP gateway, in case FASP is not allowed.
 
 Parameters provided in option `transfer_info` are:
 
-| Name | Type | Description |
-|------|------|-------------|
-| url | string | URL of the HTTP GW</br>Mandatory |
-| upload_bar_refresh_sec | float | Refresh rate for upload progress bar |
-| upload_chunksize | int | Size in bytes of chunks for upload |
+| Name                   | Type   | Description                           |
+|------------------------|--------|---------------------------------------|
+| url                    | string | URL of the HTTP GW</br>Mandatory      |
+| upload_bar_refresh_sec | float  | Refresh rate for upload progress bar  |
+| upload_chunk_size      | int    | Size in bytes of chunks for upload    |
 
 Example:
 
-```javascript
+```bash
 ascli faspex package recv --id=323 --transfer=httpgw --transfer-info=@json:'{"url":"https://asperagw.example.com:9443/aspera/http-gwy/v1"}'
 ```
 
@@ -2093,7 +2099,7 @@ ascli faspex package recv --id=323 --transfer=httpgw --transfer-info=@json:'{"ur
 
 #### <a id="agt_trsdk"></a>Transfer SDK
 
-Another possibility is to use the Transfer SDK daemon (asperatransferd).
+Another possibility is to use the Transfer SDK daemon (`asperatransferd`).
 
 By default it will listen on local port `55002` on `127.0.0.1`.
 
@@ -2105,11 +2111,12 @@ gem install grpc
 ```
 
 On Windows the compilation may fail for various reasons (3.1.1):
-
+<!-- spellchecker: disable -->
 - `cannot find -lx64-ucrt-ruby310`
    &rarr; copy the file `[Ruby main dir]\lib\libx64-ucrt-ruby310.dll.a` to `[Ruby main dir]\lib\libx64-ucrt-ruby310.a` (remove the dll extension)
 - `conflicting types for 'gettimeofday'`
   &rarr; edit the file `[Ruby main dir]/include/ruby-[version]/ruby/win32.h` and change the signature of `gettimeofday` to `gettimeofday(struct timeval *, void *)` ,i.e. change `struct timezone` to `void`
+<!-- spellchecker: enable -->
 
 ### <a id="transferspec"></a>Transfer Specification
 
@@ -2126,7 +2133,9 @@ is described in a [*transfer-spec*](#transferspec) (Transfer Specification), suc
 
 If needed, it is possible to modify or add any of the supported [*transfer-spec*](#transferspec) parameter using the `ts` option. The `ts` option accepts a [Structured Value](#native) containing one or several [*transfer-spec*](#transferspec) parameters. Multiple `ts` options on command line are cumulative.
 
-It is possible to specify `ascp` options when the `transfer` option is set to [`direct`](#agt_direct) using the special [*transfer-spec*](#transferspec) parameter: `EX_ascp_args`. Example: `--ts=@json:'{"EX_ascp_args":["-l","100m"]}'`. This is especially useful for `ascp` command line parameters not supported yet in the transfer spec.
+It is possible to specify `ascp` options when the `transfer` option is set to [`direct`](#agt_direct) using `transfer_info` option parameter: `ascp_args`.
+Example: `--transfer-info=@json:'{"ascp_args":["-l","100m"]}'`.
+This is especially useful for `ascp` command line parameters not supported in the transfer spec.
 
 The use of a [*transfer-spec*](#transferspec) instead of `ascp` parameters has the advantage of:
 
@@ -2148,7 +2157,7 @@ References:
 
 Parameters can be displayed with commands:
 
-```javascript
+```bash
 ascli config ascp spec
 ascli config ascp spec --select=@json:'{"d":"Y"}' --fields=-d,n,c
 ```
@@ -2246,8 +2255,8 @@ Fields with EX_ prefix are extensions to transfer agent [`direct`](#agt_direct).
 | title | string | &nbsp; | Y | Y | Title of the transfer |
 | token | string | Y | Y | Y | Authorization token: Bearer, Basic or ATM (Also arg -W)<br/>(env:ASPERA_SCP_TOKEN) |
 | use_ascp4 | bool | Y | Y | &nbsp; | specify version of protocol |
-| wss_enabled | bool | Y | Y | Y | &nbsp; |
-| wss_port | int | Y | Y | Y | TCP port used for websocket service feed. |
+| wss_enabled | bool | Y | Y | Y | Server has Web Socket service enabled |
+| wss_port | int | Y | Y | Y | TCP port used for websocket service feed |
 
 #### Destination folder for transfers
 
@@ -2312,7 +2321,7 @@ So, by default, the list of files to transfer will be simply specified on the co
 
   - Using JSON array
 
-    ```javascript
+    ```bash
     --sources=@json:'["file1","file2"]'
     ```
 
@@ -2333,7 +2342,7 @@ Examples:
 
   - Using transfer spec
 
-  ```javascript
+  ```bash
   --sources=@ts --ts=@json:'{"paths":[{"source":"file1"},{"source":"file2"}]}'
   ```
 
@@ -2360,7 +2369,7 @@ Multi session, i.e. starting a transfer of a file set using multiple sessions (o
 
 - when agent=node :
 
-```javascript
+```bash
 --ts=@json:'{"multi_session":10,"multi_session_threshold":1}'
 ```
 
@@ -2368,7 +2377,7 @@ Multi-session is directly supported by the node daemon.
 
 - when agent=direct :
 
-```javascript
+```bash
 --ts=@json:'{"multi_session":5,"multi_session_threshold":1,"resume_policy":"none"}'
 ```
 
@@ -2380,7 +2389,7 @@ When multi-session is used, one separate UDP port is used per session (refer to
 
 #### Content protection
 
-Also known as Client-side encryption at reast (CSEAR), content protection allows a client to send files to a server
+Also known as Client-side encryption at rest (CSEAR), content protection allows a client to send files to a server
 which will store them encrypted (upload), and decrypt files as they are being downloaded from a server, both
 using a passphrase, only known by users sharing files. Files stay encrypted on server side.
 
@@ -2391,39 +2400,33 @@ activating CSEAR consists in using transfer spec parameters:
 
 Example: parameter to download a faspex package and decrypt on the fly
 
-```javascript
---ts=@json:'{"content_protection":"decrypt","content_protection_password":"_pass_here_"}'
-```
-
-> **Note:** Up to version `ascli` 4.6.0, the following parameters should be used for agent `direct`:
-
-```javascript
---ts=@json:'{"EX_ascp_args":["--file-crypt=decrypt"],"EX_at_rest_password":"_secret_here_"}'
+```bash
+--ts=@json:'{"content_protection":"decrypt","content_protection_password":"my_password_here"}'
 ```
 
 #### Transfer Spec Examples
 
 - Change target rate
 
-```javascript
+```bash
 --ts=@json:'{"target_rate_kbps":500000}'
 ```
 
 - Override the FASP SSH port to a specific TCP port:
 
-```javascript
+```bash
 --ts=@json:'{"ssh_port":33002}'
 ```
 
 - Force http fallback mode:
 
-```javascript
+```bash
 --ts=@json:'{"http_fallback":"force"}'
 ```
 
 - Activate progress when not activated by default on server
 
-```javascript
+```bash
 --ts=@json:'{"precalculate_job_size":true}'
 ```
 
@@ -2536,7 +2539,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 backround), 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://`.
 
@@ -2571,7 +2574,7 @@ The sequence parameter is applied as follows:
 
 - If `seq` is `sequential` then each file size is:
 
-  - `size + ((fileindex - 1) * inc)`
+  - `size + ((file_index - 1) * inc)`
   - Where first file is index 1
   - So file1 is `size` bytes, file2 is `size + inc` bytes, file3 is `size + inc * 2` bytes, etc.
   - As with `random`, `inc` will be adjusted if `size + (count * inc)` is not less then 8*2<sup>60</sup>.
@@ -2605,7 +2608,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.11.0)
+        ascli -- a command line tool for Aspera Applications (v4.12.0)
 
 SYNOPSIS
         ascli COMMANDS [OPTIONS] [ARGS]
@@ -2653,7 +2656,7 @@ OPTIONS: global
     -w, --warnings                   check for language warnings
         --ui=ENUM                    method to start browser: text, [graphical]
         --log-level=ENUM             Log level: debug, info, [warn], error, fatal, unknown
-        --logger=ENUM                log method: [stderr], stdout, syslog
+        --logger=ENUM                logging method: [stderr], stdout, syslog
         --lock-port=VALUE            prevent dual execution of a command, e.g. in cron
         --http-options=VALUE         options for http socket (extended value)
         --insecure=ENUM              do not validate HTTPS certificate: no, [yes]
@@ -2693,9 +2696,8 @@ OPTIONS:
         --version-check-days=VALUE   Period in days to check new version (zero to disable)
         --plugin-folder=VALUE        Folder where to find additional plugins
         --ts=VALUE                   Override transfer spec values (Hash, e.g. use @json: prefix), current={"create_dir"=>true}
-        --to-folder=VALUE            Destination folder for transfered files
-        --sources=VALUE              How list of transfered files is provided (@args,@ts,Array)
-        --ascp-opts=VALUE            Options for ascp in its native format
+        --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-info=VALUE        Parameters for transfer agent
@@ -2708,6 +2710,7 @@ OPTIONS:
         --url=VALUE                  URL of application, e.g. https://org.asperafiles.com
         --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
@@ -2766,7 +2769,7 @@ OPTIONS:
 
 
 COMMAND: faspex5
-SUBCOMMANDS: admin bearer_token health package user version
+SUBCOMMANDS: admin bearer_token gateway health package postprocessing shared_folders user version
 OPTIONS:
         --url=VALUE                  URL of application, e.g. https://org.asperafiles.com
         --username=VALUE             username to log in
@@ -2777,6 +2780,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           RSA private key passphrase
+        --shared-folder=VALUE        Shared folder source for package files
 
 
 COMMAND: cos
@@ -2785,7 +2789,7 @@ OPTIONS:
         --bucket=VALUE               Bucket name
         --endpoint=VALUE             Storage endpoint url
         --apikey=VALUE               Storage API key
-        --crn=VALUE                  Ressource instance id
+        --crn=VALUE                  Resource instance id
         --service-credentials=VALUE  IBM Cloud service credentials (Hash)
         --region=VALUE               Storage region
         --identity=VALUE             Authentication url (https://iam.cloud.ibm.com/identity)
@@ -2819,7 +2823,7 @@ OPTIONS:
         --skip-folders=VALUE         list of folder to skip
         --case=VALUE                 basename of output for for test
         --scan-path=VALUE            subpath in folder id to start scan in (default=/)
-        --scan-id=VALUE              forder id in storage to start scan in, default is access key main folder id
+        --scan-id=VALUE              folder id in storage to start scan in, default is access key main folder id
         --mimemagic=ENUM             use Mime type detection of gem mimemagic: [no], yes
         --overwrite=ENUM             when to overwrite result file: always, never, [mtime]
         --file-access=ENUM           how to read and write files in repository: [local], remote
@@ -2855,8 +2859,8 @@ OPTIONS:
         --password=VALUE             user's password
         --auth=ENUM                  OAuth type of authentication: web, jwt
         --operation=ENUM             client operation for transfers: push, pull
-        --client-id=VALUE            OAuth API client identifier in application
-        --client-secret=VALUE        OAuth API client passcode
+        --client-id=VALUE            OAuth API client identifier
+        --client-secret=VALUE        OAuth API client secret
         --redirect-uri=VALUE         OAuth API client redirect URI
         --private-key=VALUE          OAuth JWT RSA private key PEM value (prefix file path with @file:)
         --scope=VALUE                OAuth scope for AoC API calls
@@ -3000,13 +3004,15 @@ If you did not use the wizard, you can also manually create a [option preset](#l
 
 Lets create an [option preset](#lprt) called: `my_aoc_org` using `ask` interactive input (client info from previous step):
 
+<!-- spellchecker: disable -->
 ```bash
 ascli config preset ask my_aoc_org url client_id client_secret
 option: url> https://myorg.ibmaspera.com/
-option: client_id> my_BJbQiFw
-option: client_secret> yFS1mu-crbKuQhGFtfhYuoRW...
+option: client_id> my_client_id_here
+option: client_secret> my_client_secret_here
 updated: my_aoc_org
 ```
+<!-- spellchecker: enable -->
 
 (This can also be done in one line using the command `config preset update my_aoc_org --url=...`)
 
@@ -3052,7 +3058,7 @@ ascli aoc admin res client list
 :............:...............:
 ```
 
-```javascript
+```bash
 ascli aoc admin res client modify my_BJbQiFw @json:'{"jwt_grant_enabled":true,"explicit_authorization_required":false}'
 ```
 
@@ -3187,19 +3193,19 @@ Examples:
 
 - List users with `laurent` in name:
 
-```javascript
+```bash
 ascli aoc admin res user list --query=--query=@json:'{"q":"laurent"}'
 ```
 
 - List users who logged-in before a date:
 
-```javascript
+```bash
 ascli aoc admin res user list --query=@json:'{"q":"last_login_at:<2018-05-28"}'
 ```
 
 - List external users and sort in reverse alphabetical order using name:
 
-```javascript
+```bash
 ascli aoc admin res user list --query=@json:'{"member_of_any_workspace":false,"sort":"-name"}'
 ```
 
@@ -3270,7 +3276,7 @@ The secret is provided using the `secret` option.
 For example in a command like:
 
 ```bash
-ascli aoc admin res node --id=123 --secret="secret1" v3 info
+ascli aoc admin res node --id=123 --secret="my_secret_here" v3 info
 ```
 
 It is also possible to store secrets in the [secret vault](#vault) and then automatically find the related secret using the [config finder](#config_finder).
@@ -3305,7 +3311,7 @@ The environment provided contains the following additional variable:
 
 Example:
 
-```javascript
+```bash
 ascli aoc admin analytics transfers --once-only=yes --lock-port=12345 \
 --query=@json:'{"status":"completed","direction":"receive"}' \
 --notif-to=active --notif-template=@file:mytemplate.erb
@@ -3330,7 +3336,7 @@ Refer to section "Examples" of [ATS](#ats) and substitute command `ats` with `ao
 
 #### Example: Bulk creation of users
 
-```javascript
+```bash
 ascli aoc admin res user create --bulk=yes @json:'[{"email":"dummyuser1@example.com"},{"email":"dummyuser2@example.com"}]'
 ```
 
@@ -3345,7 +3351,9 @@ ascli aoc admin res user create --bulk=yes @json:'[{"email":"dummyuser1@example.
 
 #### Example: Find with filter and delete
 
-```javascript
+<!-- spellchecker: disable -->
+
+```bash
 ascli aoc admin res user list --query='@json:{"q":"dummyuser"}' --fields=id,email
 ```
 
@@ -3366,7 +3374,7 @@ thelist=$(ascli aoc admin res user list --query='@json:{"q":"dummyuser"}' --fiel
 echo $thelist
 ```
 
-```javascript
+```json
 ["113501","354061"]
 ```
 
@@ -3383,6 +3391,8 @@ ascli aoc admin res user --bulk=yes --id=@json:"$thelist" delete
 :.......:.........:
 ```
 
+<!-- spellchecker: enable -->
+
 #### Example: <a id="deactuser"></a>Find deactivated users since more than 2 years
 
 ```ruby
@@ -3423,11 +3433,11 @@ ascli aoc admin res node --secret=_secret_ v3 transfer list --value=@json:'[["q"
 
 Examples of query (TODO: cleanup):
 
-```javascript
+```json
 {"q":"type(file_upload OR file_delete OR file_download OR file_rename OR folder_create OR folder_delete OR folder_share OR folder_share_via_public_link)","sort":"-date"}
 ```
 
-```javascript
+```json
 {"tag":"aspera.files.package_id=LA8OU3p8w"}
 ```
 
@@ -3439,7 +3449,7 @@ ascli aoc admin res node --secret=_secret_ v3 events
 
 #### Example: Display members of a workspace
 
-```javascript
+```bash
 ascli aoc admin res workspace_membership list --fields=member_type,manager,member.email --query=@json:'{"embed":"member","inherited":false,"workspace_id":11363,"sort":"name"}'
 ```
 
@@ -3458,7 +3468,7 @@ ascli aoc admin res workspace_membership list --fields=member_type,manager,membe
 
 Other query parameters:
 
-```javascript
+```json
 {"workspace_membership_through":true,"include_indirect":true}
 ```
 
@@ -3504,7 +3514,7 @@ ascli aoc admin res workspace_membership create --bulk=yes @json:@file:ws2_membe
 
 #### Example: Get users who did not log since a date
 
-```javascript
+```bash
 ascli aoc admin res user list --fields=email --query=@json:'{"q":"last_login_at:<2018-05-28"}'
 ```
 
@@ -3519,7 +3529,7 @@ ascli aoc admin res user list --fields=email --query=@json:'{"q":"last_login_at:
 
 #### Example: List "Limited" users
 
-```javascript
+```bash
 ascli aoc admin res user list --fields=email --select=@json:'{"member_of_any_workspace":false}'
 ```
 
@@ -3599,13 +3609,15 @@ Then, create two shared folders located in two regions, in your files home, in a
 
 Then, transfer between those:
 
-```javascript
+```bash
 ascli -Paoc_show aoc files transfer --from-folder='IBM Cloud SJ' --to-folder='AWS Singapore' 100GB.file --ts=@json:'{"target_rate_kbps":"1000000","multi_session":10,"multi_session_threshold":1}'
 ```
 
 #### Example: create registration key to register a node
 
-```javascript
+<!-- spellchecker: disable -->
+
+```bash
 ascli aoc admin res client create @json:'{"data":{"name":"laurentnode","client_subject_scopes":["alee","aejd"],"client_subject_enabled":true}}' --fields=token --format=csv
 ```
 
@@ -3630,6 +3642,8 @@ ascli aoc admin res client list --fields=id --format=csv|ascli aoc admin res cli
 +-----+---------+
 ```
 
+<!-- spellchecker: enable -->
+
 #### Example: Create a Node
 
 AoC nodes as actually composed with two related entities:
@@ -3648,7 +3662,7 @@ So, for example, the creation of a node using ATS in IBM Cloud looks like (see o
 
   The creation options are the ones of ATS API, refer to the [section on ATS](#ats_params) for more details and examples.
 
-  ```javascript
+  ```bash
   ascli aoc admin ats access_key create --cloud=softlayer --region=eu-de --params=@json:'{"storage":{"type":"ibm-s3","bucket":"mybucket","credentials":{"access_key_id":"mykey","secret_access_key":"mysecret"},"path":"/"}}'
   ```
 
@@ -3666,8 +3680,8 @@ So, for example, the creation of a node using ATS in IBM Cloud looks like (see o
 
   Then use the returned address for the `url` key to actually create the AoC Node entity:
 
-  ```javascript
-  ascli aoc admin res node create @json:'{"name":"myname","access_key":"*accesskeyid*","ats_access_key":true,"ats_storage_type":"ibm-s3","url":"https://ats-sl-fra-all.aspera.io"}'
+  ```bash
+  ascli aoc admin res node create @json:'{"name":"myname","access_key":"myaccesskeyid","ats_access_key":true,"ats_storage_type":"ibm-s3","url":"https://ats-sl-fra-all.aspera.io"}'
   ```
 
 Creation of a node with a self-managed node is similar, but the command `aoc admin ats access_key create` is replaced with `node access_key create` on the private node itself.
@@ -3717,46 +3731,54 @@ Notes:
 
 #### Example: Send a package with one file to two users, using their email
 
-```javascript
-ascli aoc package send --value=@json:'{"name":"my title","note":"my note","recipients":["laurent.martin.aspera@fr.ibm.com","other@example.com"]}' my_file.dat
+```bash
+ascli aoc packages send --value=@json:'{"name":"my title","note":"my note","recipients":["laurent.martin.aspera@fr.ibm.com","other@example.com"]}' my_file.dat
 ```
 
 #### Example: Send a package to a shared inbox with metadata
 
-```javascript
-ascli aoc package send --workspace=eudemo --value=@json:'{"name":"my pack title","recipients":["Shared Inbox With Meta"],"metadata":{"Project Id":"123","Type":"Opt2","CheckThose":["Check1","Check2"],"Optional Date":"2021-01-13T15:02:00.000Z"}}' ~/Documents/Samples/200KB.1
+```bash
+ascli aoc packages send --workspace=eudemo --value=@json:'{"name":"my pack title","recipients":["Shared Inbox With Meta"],"metadata":{"Project Id":"123","Type":"Opt2","CheckThose":["Check1","Check2"],"Optional Date":"2021-01-13T15:02:00.000Z"}}' ~/Documents/Samples/200KB.1
 ```
 
 It is also possible to use identifiers and API parameters:
 
-```javascript
-ascli aoc package send --workspace=eudemo --value=@json:'{"name":"my pack title","recipients":[{"type":"dropbox","id":"12345"}],"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"]}]}' ~/Documents/Samples/200KB.1
+```bash
+ascli aoc packages send --workspace=eudemo --value=@json:'{"name":"my pack title","recipients":[{"type":"dropbox","id":"12345"}],"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"]}]}' ~/Documents/Samples/200KB.1
 ```
 
 #### Example: List packages in a given shared inbox
 
 When user packages are listed, the following query is used:
 
-```javascript
+```json
 {"archived":false,"exclude_dropbox_packages":true,"has_content":true,"received":true}
 ```
 
-To list packages in a shared inbox, the query has to be specified with withe the shared inbox by name or its identifier. Additionnal parameters can be specified, as supported by the API (to find out available filters, consult the API definition, or use the web interface in developer mode). The current workspace is added unless specified in the query.
+To list packages in a shared inbox, the query has to be specified with withe the shared inbox by name or its identifier.
+Additional parameters can be specified, as supported by the API (to find out available filters, consult the API definition, or use the web interface in developer mode).
+The current workspace is added unless specified in the query.
 
 Using shared inbox name:
 
-```javascript
+```bash
 ascli aoc packages list --query=@json:'{"dropbox_name":"My Shared Inbox","archived":false,"received":true,"has_content":true,"exclude_dropbox_packages":false,"include_draft":false,"sort":"-received_at"}'
 ```
 
 Using shared inbox identifier: first retrieve the id of the shared inbox, and then list packages with the appropriate filter.
 
 ```bash
-shbxid=$(ascli aoc packages shared_inboxes show name 'My Shared Inbox' --format=csv --display=data --fields=id --transpose-single=no)
+shared_box_id=$(ascli aoc packages shared_inboxes show name 'My Shared Inbox' --format=csv --display=data --fields=id --transpose-single=no)
+```
+
+```bash
+ascli aoc packages list --query=@json:'{"dropbox_id":"'$shared_box_id'","archived":false,"received":true,"has_content":true,"exclude_dropbox_packages":false,"include_draft":false,"sort":"-received_at"}'
 ```
 
-```javascript
-ascli aoc packages list --query=@json:'{"dropbox_id":"'$shbxid'","archived":false,"received":true,"has_content":true,"exclude_dropbox_packages":false,"include_draft":false,"sort":"-received_at"}'
+#### Example: Receive all packages from a given shared inbox
+
+```bash
+ascli aoc packages recv ALL --workspace=_workspace_ --once-only=yes --lock-port=12345 --query=@json:'{"dropbox_name":"_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}'
 ```
 
 #### Example: Send a package with files from the Files app
@@ -3781,7 +3803,7 @@ ascli aoc files browse /src_folder
 Let's send a package with the file `10M.dat` from subfolder /src_folder in a package:
 
 ```bash
-ascli aoc files node_info /src_folder --format=json --display=data | ascli aoc package send --value=@json:'{"name":"test","recipients":["laurent.martin.aspera@fr.ibm.com"]}' 10M.dat --transfer=node --transfer-info=@json:@stdin:
+ascli aoc files node_info /src_folder --format=json --display=data | ascli aoc packages send --value=@json:'{"name":"test","recipients":["laurent.martin.aspera@fr.ibm.com"]}' 10M.dat --transfer=node --transfer-info=@json:@stdin:
 ```
 
 #### <a id="aoccargo"></a>Receive new packages only (Cargo)
@@ -3917,19 +3939,19 @@ f["type"].eql?("file") and (DateTime.now-DateTime.parse(f["modified_time"]))<100
 - Find files older than 1 year on a given node and store in file list
 
 ```bash
-ascli aoc admin res node --name='my node name' --secret='_secret_here_' v4 find / --fields=path --value='exec:f["type"].eql?("file") and (DateTime.now-DateTime.parse(f["modified_time"]))<100' --format=csv > my_file_list.txt
+ascli aoc admin res node --name='my node name' --secret='my_secret_here' v4 find / --fields=path --value='exec:f["type"].eql?("file") and (DateTime.now-DateTime.parse(f["modified_time"]))<100' --format=csv > my_file_list.txt
 ```
 
 - Delete the files, one by one
 
 ```bash
-cat my_file_list.txt|while read path;do echo ascli aoc admin res node --name='my node name' --secret='_secret_here_' v4 delete "$path" ;done
+cat my_file_list.txt|while read path;do echo ascli aoc admin res node --name='my node name' --secret='my_secret_here' v4 delete "$path" ;done
 ```
 
 - Delete the files in bulk
 
 ```bash
-cat my_file_list.txt | ascli aoc admin res node --name='my node name' --secret='_secret_here_' v3 delete @lines:@stdin:
+cat my_file_list.txt | ascli aoc admin res node --name='my node name' --secret='my_secret_here' v3 delete @lines:@stdin:
 ```
 
 ### AoC sample commands
@@ -3937,10 +3959,10 @@ cat my_file_list.txt | ascli aoc admin res node --name='my node name' --secret='
 ```bash
 aoc admin analytics transfers --query=@json:'{"status":"completed","direction":"receive"}' --notif-to=my_recipient_email --notif-template=@ruby:'%Q{From: <%=from_name%> <<%=from_email%>>\nTo: <<%=to%>>\nSubject: <%=ev["files_completed"]%> files received\n\n<%=ev.to_yaml%>}'
 aoc admin ats access_key create --cloud=aws --region=my_aws_bucket_region --params=@json:'{"id":"ak_aws","name":"my test key AWS","storage":{"type":"aws_s3","bucket":"my_aws_bucket_name","credentials":{"access_key_id":"my_aws_bucket_key","secret_access_key":"my_aws_bucket_secret"},"path":"/"}}'
-aoc admin ats access_key create --cloud=softlayer --region=my_icos_bucket_region --params=@json:'{"id":"ak1ibmcloud","secret":"somesecret","name":"my test key","storage":{"type":"ibm-s3","bucket":"my_icos_bucket_name","credentials":{"access_key_id":"my_icos_bucket_key","secret_access_key":"my_icos_bucket_secret"},"path":"/"}}'
+aoc admin ats access_key create --cloud=softlayer --region=my_icos_bucket_region --params=@json:'{"id":"ak1ibmcloud","secret":"my_secret_here","name":"my test key","storage":{"type":"ibm-s3","bucket":"my_icos_bucket_name","credentials":{"access_key_id":"my_icos_bucket_key","secret_access_key":"my_icos_bucket_secret"},"path":"/"}}'
 aoc admin ats access_key delete ak1ibmcloud
 aoc admin ats access_key list --fields=name,id
-aoc admin ats access_key node ak1ibmcloud --secret=somesecret browse /
+aoc admin ats access_key node ak1ibmcloud --secret=my_secret_here browse /
 aoc admin ats cluster clouds
 aoc admin ats cluster list
 aoc admin ats cluster show --cloud=aws --region=eu-west-1
@@ -4007,6 +4029,7 @@ aoc files upload --to-folder=/ testfile.bin --link=my_aoc_publink_folder
 aoc files upload --to-folder=/testsrc testfile.bin
 aoc files upload Test.pdf --transfer=node --transfer-info=@json:@stdin:
 aoc files v3 info
+aoc gateway --value=https://localhost:12345/aspera/faspex & jobs -p
 aoc org --link=my_aoc_publink_recv_from_aocuser
 aoc organization
 aoc packages browse "my_package_id" /contents
@@ -4014,6 +4037,7 @@ aoc packages list
 aoc packages list --query=@json:'{"dropbox_name":"my_aoc_shbx_name","sort":"-received_at","archived":false,"received":true,"has_content":true,"exclude_dropbox_packages":false}'
 aoc packages recv "my_package_id" --to-folder=.
 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_aoc_shbx_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 send --value=@json:'{"name":"Important files delivery","recipients":["my_email_external_user"]}' --new-user-option=@json:'{"package_contact":true}' testfile.bin
 aoc packages send --value=@json:'{"name":"Important files delivery","recipients":["my_email_internal_user"],"note":"my note"}' testfile.bin
 aoc packages send --value=@json:'{"name":"Important files delivery"}' testfile.bin --link=my_aoc_publink_send_aoc_user --password=my_aoc_publink_send_use_pass
@@ -4041,10 +4065,12 @@ ATS is usable either :
 ### IBM Cloud ATS : creation of api key
 
 This section is about using ATS with an IBM cloud subscription.
-If you are using ATS as part of AoC, then authentication is thropugh AoC, not IBM Cloud.
+If you are using ATS as part of AoC, then authentication is through AoC, not IBM Cloud.
 
 First get your IBM Cloud APIkey. For instance, it can be created using the IBM Cloud web interface, or using command line:
 
+<!-- spellchecker: disable -->
+
 ```bash
 ibmcloud iam api-key-create mykeyname -d 'my sample key'
 ```
@@ -4058,7 +4084,7 @@ Please preserve the API key! It cannot be retrieved after it's created.
 Name          mykeyname
 Description   my sample key
 Created At    2019-09-30T12:17+0000
-API Key       my_secret_api_key_here_8f8d9fdakjhfsashjk678
+API Key       my_secret_api_key_here
 Locked        false
 UUID          ApiKey-05b8fadf-e7fe-4bc4-93a9-6fd348c5ab1f
 ```
@@ -4068,10 +4094,14 @@ References:
 - [https://console.bluemix.net/docs/iam/userid_keys.html#userapikey](https://console.bluemix.net/docs/iam/userid_keys.html#userapikey)
 - [https://ibm.ibmaspera.com/helpcenter/transfer-service](https://ibm.ibmaspera.com/helpcenter/transfer-service)
 
+<!-- spellchecker: enable -->
+
 Then, to register the key by default for the ats plugin, create a preset. Execute:
 
+<!-- spellchecker: disable -->
+
 ```bash
-ascli config preset update my_ibm_ats --ibm-api-key=my_secret_api_key_here_8f8d9fdakjhfsashjk678
+ascli config preset update my_ibm_ats --ibm-api-key=my_secret_api_key_here
 ```
 
 ```bash
@@ -4108,36 +4138,39 @@ ascli ats api_key create
 ascli config preset update my_ibm_ats --ats-key=ats_XXXXXXXXXXXXXXXXXXXXXXXX --ats-secret=YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
 ```
 
+<!-- spellchecker: enable -->
+
 ### <a id="ats_params"></a>ATS Access key creation parameters
 
-When creating an ATS access key, the option `params` must contain an extended value with the creation parameters. Those asre directly the parameters expected by the [ATS API](https://developer.ibm.com/apis/catalog?search=%22Aspera%20ATS%20API%22).
+When creating an ATS access key, the option `params` must contain an extended value with the creation parameters.
+Those are directly the parameters expected by the [ATS API](https://developer.ibm.com/apis/catalog?search=%22Aspera%20ATS%20API%22).
 
 ### Misc. Examples
 
 Example: create access key on IBM Cloud (softlayer):
 
-```javascript
-ascli ats access_key create --cloud=softlayer --region=ams --params=@json:'{"storage":{"type":"softlayer_swift","container":"_container_name_","credentials":{"api_key":"_secret_here_","username":"_name_:_usr_name_"},"path":"/"},"id":"_optional_id_","name":"_optional_name_"}'
+```bash
+ascli ats access_key create --cloud=softlayer --region=ams --params=@json:'{"storage":{"type":"softlayer_swift","container":"_container_name_","credentials":{"api_key":"my_secret_here","username":"_name_:_usr_name_"},"path":"/"},"id":"_optional_id_","name":"_optional_name_"}'
 ```
 
 Example: create access key on AWS:
 
-```javascript
-ascli ats access_key create --cloud=aws --region=eu-west-1 --params=@json:'{"id":"testkey3","name":"laurent key AWS","storage":{"type":"aws_s3","bucket":"my-bucket","credentials":{"access_key_id":"AKIA_MY_API_KEY","secret_access_key":"_secret_here_"},"path":"/laurent"}}'
+```bash
+ascli ats access_key create --cloud=aws --region=eu-west-1 --params=@json:'{"id":"myaccesskey","name":"laurent key AWS","storage":{"type":"aws_s3","bucket":"my-bucket","credentials":{"access_key_id":"_access_key_id_here_","secret_access_key":"my_secret_here"},"path":"/laurent"}}'
 ```
 
 Example: create access key on Azure SAS:
 
-```javascript
-ascli ats access_key create --cloud=azure --region=eastus --params=@json:'{"id":"testkeyazure","name":"laurent key azure","storage":{"type":"azure_sas","credentials":{"shared_access_signature":"https://containername.blob.core.windows.net/blobname?sr=c&..."},"path":"/"}}'
+```bash
+ascli ats access_key create --cloud=azure --region=eastus --params=@json:'{"id":"myaccesskey","name":"laurent key azure","storage":{"type":"azure_sas","credentials":{"shared_access_signature":"https://containername.blob.core.windows.net/blobname?sr=c&..."},"path":"/"}}'
 ```
 
 (Note that the blob name is mandatory after server address and before parameters. and that parameter sr=c is mandatory.)
 
 Example: create access key on Azure:
 
-```javascript
-ascli ats access_key create --cloud=azure --region=eastus --params=@json:'{"id":"testkeyazure","name":"laurent key azure","storage":{"type":"azure","credentials":{"account":"myaccount","key":"myaccesskey","storage_endpoint":"myblob"},"path":"/"}}'
+```bash
+ascli ats access_key create --cloud=azure --region=eastus --params=@json:'{"id":"myaccesskey","name":"laurent key azure","storage":{"type":"azure","credentials":{"account":"myaccount","key":"myaccesskey","storage_endpoint":"myblob"},"path":"/"}}'
 ```
 
 delete all my access keys:
@@ -4151,14 +4184,14 @@ The parameters provided to ATS for access key creation are the ones of [ATS API]
 ### ATS sample commands
 
 ```bash
-ats access_key cluster ak2ibmcloud --secret=somesecret
+ats access_key cluster ak2ibmcloud --secret=my_secret_here
 ats access_key create --cloud=aws --region=my_aws_bucket_region --params=@json:'{"id":"ak_aws","name":"my test key AWS","storage":{"type":"aws_s3","bucket":"my_aws_bucket_name","credentials":{"access_key_id":"my_aws_bucket_key","secret_access_key":"my_aws_bucket_secret"},"path":"/"}}'
-ats access_key create --cloud=softlayer --region=my_icos_bucket_region --params=@json:'{"id":"ak2ibmcloud","secret":"somesecret","name":"my test key","storage":{"type":"ibm-s3","bucket":"my_icos_bucket_name","credentials":{"access_key_id":"my_icos_bucket_key","secret_access_key":"my_icos_bucket_secret"},"path":"/"}}'
+ats access_key create --cloud=softlayer --region=my_icos_bucket_region --params=@json:'{"id":"ak2ibmcloud","secret":"my_secret_here","name":"my test key","storage":{"type":"ibm-s3","bucket":"my_icos_bucket_name","credentials":{"access_key_id":"my_icos_bucket_key","secret_access_key":"my_icos_bucket_secret"},"path":"/"}}'
 ats access_key delete ak2ibmcloud
 ats access_key delete ak_aws
 ats access_key entitlement ak2ibmcloud
 ats access_key list --fields=name,id
-ats access_key node ak2ibmcloud browse / --secret=somesecret
+ats access_key node ak2ibmcloud browse / --secret=my_secret_here
 ats access_key show ak2ibmcloud
 ats api_key create
 ats api_key instances
@@ -4209,8 +4242,8 @@ server upload --sources=@ts --ts=@json:'{"EX_file_list":"'"filelist.txt"'"}' --t
 server upload --sources=@ts --ts=@json:'{"EX_file_pair_list":"'"filepairlist.txt"'"}'
 server upload --sources=@ts --ts=@json:'{"paths":[{"source":"testfile.bin","destination":"NEW_SERVER_FOLDER/othername"}]}'
 server upload --src-type=pair --sources=@json:'["testfile.bin","NEW_SERVER_FOLDER/othername"]'
-server upload --src-type=pair testfile.bin NEW_SERVER_FOLDER/othername --notif-to=my_recipient_email --ascp-opts=@list:' -l 10m'
-server upload --src-type=pair testfile.bin folder_1/with_options --ts=@json:'{"cipher":"aes-192-gcm","content_protection":"encrypt","content_protection_password":"_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 --src-type=pair testfile.bin NEW_SERVER_FOLDER/othername --notif-to=my_recipient_email --transfer-info=@json:'{"ascp_args":["-l","10m"]}'
+server upload --src-type=pair testfile.bin folder_1/with_options --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=folder_1/target_hot --lock-port=12345 --ts=@json:'{"EX_ascp_args":["--remove-after-transfer","--remove-empty-directories","--exclude-newer-than=-8","--src-base","source_hot"]}' source_hot
 server upload testfile.bin --to-folder=NEW_SERVER_FOLDER --ts=@json:'{"multi_session":3,"multi_session_threshold":1,"resume_policy":"none","target_rate_kbps":1500}' --transfer-info=@json:'{"spawn_delay_sec":2.5,"multi_incr_udp":false}' --progress=multi
 ```
@@ -4228,7 +4261,7 @@ If no SSH password or key is provided and a transfer token is provided in transf
 Example:
 
 ```bash
-ascli server --url=ssh://_server_address_:33001 ... --ts=@json:'{"token":"Basic abc123"}'
+ascli server --url=ssh://_server_address_:33001 ... --ts=@json:'{"token":"Basic _token_here_"}'
 ```
 
 > **Note:** If you need to use the Aspera public keys, then specify an empty token: `--ts=@json:'{"token":""}'` : Aspera public SSH keys will be used, but the protocol will ignore the empty token.
@@ -4245,9 +4278,16 @@ ascli server --ssh-keys=@json:'["~/.ssh/id_rsa"]'
 ```
 
 For file operation command (browse, delete), the ruby SSH client library `Net::SSH` is used and provides several options settable using option `ssh_options`.
-For a list of SSH client options, refer to the ruby documentation of [Net::SSH](http://net-ssh.github.io/net-ssh/Net/SSH.html).
 
-By default the SSH library expect that a local ssh-agent is running.
+For a list of SSH client options, refer to the ruby documentation of [Net::SSH](http://net-ssh.github.io/net-ssh/Net/SSH.html#method-c-start).
+
+Some of the 50 available SSH options:
+
+- `verbose`
+- `use_agent`
+- `passphrase`
+
+By default the SSH library will check if a local `ssh-agent` is running.
 
 On Linux, if you get an error message such as:
 
@@ -4261,25 +4301,26 @@ or on Windows:
 ERROR -- net.ssh.authentication.agent: could not connect to ssh-agent: pageant process not running
 ```
 
-This means that you don't have such an SSH agent running, then:
+This means that your environment suggessts to use an agent but you don't have such an SSH agent running, then:
 
 - Check env var: `SSH_AGENT_SOCK`
+- Check your file: `$HOME/.ssh/config`
 - Check if the SSH key is protected with a passphrase (then, use the `passphrase` SSH option)
-- [check the manual](https://net-ssh.github.io/ssh/v1/chapter-2.html#s2)
+- [Check the Ruby SSH manual](https://www.rubydoc.info/github/net-ssh/net-ssh/Net%2FSSH.start)
 - To disable the use of `ssh-agent`, use the option `ssh_options` like this:
 
 ```bash
-ascli server --ssh-options=@ruby:'{use_agent: false}' ...
+ascli server --ssh-options=@json:'{"use_agent": false}' ...
 ```
 
-This can also be set as default using a global preset.
+> **Note:** This can also be set using a preset.
 
 ### Other session channels for `server`
 
-URL schemes `local` and `https` are also supported, mainly for testing purpose.
+URL schemes `local` and `https` are also supported (mainly for testing purpose).
 (`--url=local:` , `--url=https://...`)
 
-- `local` will execute `ascmd` locally, instead of using a SSH cnnection.
+- `local` will execute `ascmd` locally, instead of using an SSH connection.
 - `https` will use Web Socket Session: This requires the use of a transfer token. For example a `Basic` token can be used.
 
 As, most of the time, SSH is used, if an `http` scheme is provided without token, the plugin will fallback to SSH and port 33001.
@@ -4314,7 +4355,7 @@ For transfers, it is possible to control how transfer is authorized using option
 - `hybrid` : same as `aspera`, but token is replaced with basic token like `basic`
 - `basic` : transfer spec is created like this:
 
-```javascript
+```json
 {
   "remote_host": "<address of node url>",
   "remote_user": "xfer",
@@ -4344,8 +4385,8 @@ It is possible to start a FASPStream session using the node API:
 
 Use the "node stream create" command, then arguments are provided as a [*transfer-spec*](#transferspec).
 
-```javascript
-ascli node stream create --ts=@json:'{"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":"_pass_here_"}' --preset=stream
+```bash
+ascli node stream create --ts=@json:'{"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"}' --preset=stream
 ```
 
 ### Watchfolder
@@ -4357,17 +4398,21 @@ Refer to [Aspera documentation](https://download.asperasoft.com/download/docs/en
 - Start watchd and watchfolderd services running as a system user having access to files
 - configure a watchfolder to define automated transfers
 
-```javascript
+<!-- spellchecker: disable -->
+
+```bash
 ascli node service create @json:'{"id":"mywatchd","type":"WATCHD","run_as":{"user":"user1"}}'
 ascli node service create @json:'{"id":"mywatchfolderd","type":"WATCHFOLDERD","run_as":{"user":"user1"}}'
 ascli node watch_folder create @json:'{"id":"mywfolder","source_dir":"/watch1","target_dir":"/","transport":{"host":"10.25.0.4","user":"user1","pass":"mypassword"}}'
 ```
 
+<!-- spellchecker: enable -->
+
 ### Out of Transfer File Validation
 
 Follow the Aspera Transfer Server configuration to activate this feature.
 
-```javascript
+```bash
 ascli node central file list --validator=ascli --data=@json:'{"file_transfer_filter":{"max_result":1}}'
 ```
 
@@ -4379,7 +4424,7 @@ ascli node central file list --validator=ascli --data=@json:'{"file_transfer_fil
 :..............:..............:............:......................................:
 ```
 
-```javascript
+```bash
 ascli node central file update --validator=ascli --data=@json:'{"files":[{"session_uuid": "1a74444c-...","file_id": "084fb181-...","status": "completed"}]}'
 ```
 
@@ -4389,23 +4434,23 @@ updated
 
 ### Example: SHOD to ATS
 
-Scenario: Access to a "Shares on Demand" (SHOD) server on AWS is provided by a partner.
+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: awsshod.
-Create another configuration for the Azure ATS instance: in section "node", named azureats.
+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 execute the following command:
 
 ```bash
-ascli node download /share/sourcefile --to-folder=/destinationfolder --preset=awsshod --transfer=node --transfer-info=@preset:azureats
+ascli node download /share/sourcefile --to-folder=/destination_folder --preset=aws_shod --transfer=node --transfer-info=@preset:azure_ats
 ```
 
 This will get transfer information from the SHOD instance and tell the Azure ATS instance to download files.
 
 ### Create access key
 
-```javascript
-ascli node access_key create --value=@json:'{"id":"eudemo-sedemo","secret":"mystrongsecret","storage":{"type":"local","path":"/data/asperafiles"}}'
+```bash
+ascli node access_key create --value=@json:'{"id":"myaccesskey","secret":"my_secret_here","storage":{"type":"local","path":"/data/mydir"}}'
 ```
 
 ### Node sample commands
@@ -4464,7 +4509,7 @@ node sync state my_syncid
 node sync stop my_syncid
 node sync summary my_syncid
 node transfer list --value=@json:'{"active_only":true}'
-node upload --to-folder="folder_1" --sources=@ts --ts=@json:'{"paths":[{"source":"/aspera-test-dir-small/10MB.1"}],"precalculate_job_size":true}' --transfer=node --transfer-info=@json:'{"url":"my_node_url","username":"my_node_user","password":"my_node_pass"}'
+node upload --to-folder="folder_1" --sources=@ts --ts=@json:'{"paths":[{"source":"/aspera-test-dir-small/10MB.1"}],"precalculate_job_size":true}' --transfer=node --transfer-info=@json:'{"url":"my_node_url","username":"my_node_user","password":"my_node_pass_here"}'
 node upload --username=my_aoc_ak_name --password=my_aoc_ak_secret testfile.bin --token-type=basic
 node upload testfile.bin --to-folder=folder_1 --ts=@json:'{"target_rate_cap_kbps":10000}'
 node upload testfile.bin --to-folder=folder_1 --ts=@json:'{"target_rate_cap_kbps":10000}' --token-type=hybrid
@@ -4482,7 +4527,7 @@ IBM Aspera's newer self-managed application.
 
 ### Faspex 5 JWT authentication
 
-This is the **recomended** method to use.
+This is the **recommended** method to use.
 
 For `jwt`, create an API client in Faspex with JWT support:
 
@@ -4498,7 +4543,7 @@ Then use these options:
 ```text
 --auth=jwt
 --client-id=_client_id_here_
---client-secret=_secret_here_
+--client-secret=my_secret_here
 --username=_username_here_
 --private-key=@file:.../path/to/key.pem
 ```
@@ -4520,7 +4565,7 @@ Then use options:
 ```text
 --auth=web
 --client-id=_client_id_here_
---client-secret=_secret_here_
+--client-secret=my_secret_here
 --redirect-uri=https://127.0.0.1:8888
 ```
 
@@ -4539,10 +4584,19 @@ Use this token as password and use `--auth=boot`.
 ascli conf id f5boot update --url=https://localhost/aspera/faspex --auth=boot --password=_token_here_
 ```
 
+### Faspex 5 packages
+
+The `value` option provided to command `faspex5 package send` is the same as for the Faspex 5 API: `POST /packages`.
+
+In addition, `ascli` adds some convenience: the field `recipients` is normally an Array of Hash, each with field `name` and optionally `recipient_type`, but it is also possible to provide an Array of String, with simply a recipient name.
+Then `ascli` will lookup existing contacts, and if a single match is found will use it, and set the `name` and `recipient_type` accordingly.
+
+> **Note:** The lookup is case insensitive and on partial matches.
+
 ### Faspex 5 sample commands
 
 Most commands are directly REST API calls.
-Parameters to commandsa are carried through option `value`, as extended value.
+Parameters to commands are carried through option `value`, as extended value.
 Usually using JSON format with prefix `@json:`.
 
 > **Note:** The API is listed in [Faspex 5 API Reference](https://developer.ibm.com/apis/catalog?search="faspex+5") under **IBM Aspera Faspex API**.
@@ -4559,40 +4613,114 @@ faspex5 admin res saml_configs list
 faspex5 admin res shared_inboxes list
 faspex5 admin res workgroups list
 faspex5 bearer_token
+faspex5 gateway --value=https://localhost:12345/aspera/faspex &\
 faspex5 health
 faspex5 package list --value=@json:'{"mailbox":"inbox","state":["released"]}'
 faspex5 package receive "my_package_id" --to-folder=.  --ts=@json:'{"content_protection_password":"abc123_yo"}'
-faspex5 package send --value=@json:'{"title":"test title","recipients":[{"name":"my_f5_user"}]}' testfile.bin --ts=@json:'{"content_protection_password":"_content_prot_here_"}'
+faspex5 package send --value=@json:'{"title":"test title","recipients":["my_shinbox"],"metadata":{"Options":"Opt1","TextInput":"example text"}}' testfile.bin
+faspex5 package send --value=@json:'{"title":"test title","recipients":[{"name":"my_f5_user"}]}' testfile.bin --ts=@json:'{"content_protection_password":"my_passphrase_here"}'
 faspex5 package show "my_package_id"
+faspex5 postprocessing --value=@json:'{"url":"https://localhost:8443/domain","processing":{"script_folder":"tests"},"certificate":{"key":"../local/k","cert":"../local/c","chain":"../local/ch"}}' &\
 faspex5 user profile modify @json:'{"preference":{"connect_disabled":false}}'
 faspex5 user profile show
 ```
 
 Other examples:
 
+- Send a package with metadata
+
+The interface is the one of the API (Refer to API documentation, or look at request in browser):
+
+```bash
+ascli faspex5 package send --value=@json:'{"title":"test title","recipients":["ascli shared inbox"],"metadata":{"Confidential":"Yes","Drop menu":"Option 1"}}' 'faux:///test1?k1'
+```
+
+Basically, add the field `metadata`, with one key per metadata and the value is directly the metadata value.
+
 - List all shared inboxes
 
-```javascript
+```bash
 ascli faspex5 admin res shared list --value=@json:'{"all":true}' --fields=id,name
 ```
 
 - Create Metadata profile
 
-```javascript
+```bash
 ascli faspex5 admin res metadata_profiles create --value=@json:'{"name":"the profile","default":false,"title":{"max_length":200,"illegal_chars":[]},"note":{"max_length":400,"illegal_chars":[],"enabled":false},"fields":[{"ordering":0,"name":"field1","type":"text_area","require":true,"illegal_chars":[],"max_length":100},{"ordering":1,"name":"fff2","type":"option_list","require":false,"choices":["opt1","opt2"]}]}'
 ```
 
 - Create a Shared inbox with specific metadata profile
 
-```javascript
+```bash
 ascli faspex5 admin res shared create --value=@json:'{"name":"the shared inbox","metadata_profile_id":1}'
 ```
 
+- List content in Shared folder and send package from remote source
+
+```bash
+ascli faspex5 shared_folders list
+```
+
+```bash
+ascli faspex5 shared_folders br 3 /folder
+```
+
+```bash
+ascli faspex5 package send --value=@json:'{"title":"hello","recipients":[{"name":"_recipient_here_"}]}' --shared-folder=3 /folder/file
+```
+
+### Faspex 4-style postprocessing script with Faspex 5
+
+`ascli` provides command `postprocessing` in plugin `faspex5` to emulate Faspex 4 postprocessing.
+It implements Faspex 5 web hooks, and calls a local script with the same environment as Faspex 4.
+
+It is invoked like this:
+
+```bash
+ascli faspex5 postprocessing --value=@json:'{"url":"http://localhost:8080/processing"}'
+```
+
+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                    | behaviour 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      |
+
+Parameter `url` defines:
+
+- if http or https is used
+- the local port
+- the "domain", i.e. main path of url
+
+When a request is received the following happens:
+
+- the processor get the path of the url called
+- it removes the "domain
+- it pre-prends 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`
+
+Then, the postprocessing script executed will be `script1.sh`.
+
+Environment variables at set to the values provided by the web hook which are the same as Faspex 4 postprocessing.
+
 ## <a id="faspex"></a>Plugin: `faspex`: IBM Aspera Faspex v4
 
 Notes:
 
-- The command "v4" requires the use of APIv4, refer to the Faspex Admin manual on how to activate.
+- The command `v4` requires the use of APIv4, refer to the Faspex Admin manual on how to activate.
 - For full details on Faspex API, refer to: [Reference on Developer Site](https://developer.ibm.com/apis/catalog/?search=faspex)
 
 ### Listing Packages
@@ -4628,7 +4756,7 @@ If no parameter `max` or `pmax` is provided, then all packages will be listed in
 
 #### Example: list packages in dropbox
 
-```javascript
+```bash
 ascli faspex package list --box=inbox --recipient='*my_dropbox' --query=@json:'{"max":20,"pmax":2,"count":20}'
 ```
 
@@ -4650,8 +4778,8 @@ ascli faspex package recv --link=faspe://...
 If the package is in a specific **dropbox**/**workgroup**, add option `recipient` for both the `list` and `recv` commands.
 
 ```bash
-ascli faspex package list --recipient='*thedropboxname'
-ascli faspex package recv 125 --recipient='*thedropboxname'
+ascli faspex package list --recipient='*dropbox_name'
+ascli faspex package recv 125 --recipient='*dropbox_name'
 ```
 
 if `id` is set to `ALL`, then all packages are downloaded, and if option `once_only`is used, then a persistency file is created to keep track of already downloaded packages.
@@ -4663,7 +4791,7 @@ The contents of `delivery_info` is directly the contents of the `send` v3 [API o
 
 Example:
 
-```javascript
+```bash
 ascli faspex package send --delivery-info=@json:'{"title":"my title","recipients":["laurent.martin.aspera@fr.ibm.com"]}' --url=https://faspex.corp.com/aspera/faspex --username=foo --password=bar /tmp/file1 /home/bar/file2
 ```
 
@@ -4681,7 +4809,7 @@ Like for any transfer, a notification can be sent by email using parameters: `no
 
 Example:
 
-```javascript
+```bash
 ascli faspex package send --delivery-info=@json:'{"title":"test pkg 1","recipients":["aspera.user1@gmail.com"]}' ~/Documents/Samples/200KB.1 --notif-to=aspera.user1@gmail.com --notif-template=@ruby:'%Q{From: <%=from_name%> <<%=from_email%>>\nTo: <<%=to%>>\nSubject: Package sent: <%=ts["tags"]["aspera"]["faspex"]["metadata"]["_pkg_name"]%> files received\n\nTo user: <%=ts["tags"]["aspera"]["faspex"]["recipients"].first["email"]%>}'
 ```
 
@@ -4691,7 +4819,7 @@ In this example the notification template is directly provided on command line.
 
 Example:
 
-```javascript
+```bash
 ascli faspex v4 dropbox create --value=@json:'{"dropbox":{"e_wg_name":"test1","e_wg_desc":"test1"}}'
 ascli faspex v4 dropbox list
 ascli faspex v4 dropbox delete --id=36
@@ -4711,17 +4839,17 @@ my_faspex_conf:
   username: admin
   password: MyUserPassword
   storage:
-    testlaurent:
+    my_storage:
       node: "@preset:my_faspex_node"
-      path: /myfiles
+      path: /mydir
 my_faspex_node:
   url: https://10.25.0.3:9092
   username: node_faspex
   password: MyNodePassword
 ```
 
-In this example, a faspex storage named "testlaurent" exists in Faspex, and is located
-under the docroot in "/myfiles" (this must be the same as configured in Faspex).
+In this example, a faspex storage named `my_storage` exists in Faspex, and is located
+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.
@@ -4778,14 +4906,17 @@ Aspera Shares supports the "node API" for the file transfer part. (Shares 1 and
 ### Shares 1 sample commands
 
 ```bash
-shares admin share list
+shares admin group list
+shares admin node list
 shares admin share list --fields=-status,status_message
-shares admin share user_permissions 1
-shares admin user app_authorizations 1
-shares admin user ldap_import --value=the_name
+shares admin share user_permissions 1 list
+shares admin user add --type=ldap --value=the_name
+shares admin user app_authorizations 1 modify --value=@json:'{"app_login":true}'
+shares admin user app_authorizations 1 show
+shares admin user import --type=saml --value=@json:'{"id":"the_id","name_id":"the_name"}'
 shares admin user list
-shares admin user saml_import --value=@json:'{"id":"the_id","name_id":"the_name"}'
-shares admin user share_permissions 1
+shares admin user share_permissions 1 list
+shares admin user share_permissions 1 show 1
 shares health
 shares repository browse /
 shares repository delete my_shares_upload/testfile.bin
@@ -4873,29 +5004,33 @@ or using the IBM Cloud CLI:
 
 ```bash
 ibmcloud resource service-keys
-ibmcloud resource service-key aoclaurent --output JSON|jq '.[0].credentials'>$HOME/service_creds.json
+ibmcloud resource service-key _service_key_name_here_ --output JSON|jq '.[0].credentials'>$HOME/service_creds.json
 ```
 
 (if you don't have `jq` installed, extract the structure as follows)
 
 It consists in the following structure:
 
-```javascript
+<!-- spellchecker: disable -->
+
+```json
 {
-  "apikey": "_api_key_here_",
+  "apikey": "my_api_key_here",
   "cos_hmac_keys": {
-    "access_key_id": "_access_key_here_",
-    "secret_access_key": "_secret_here_"
+    "access_key_id": "my_access_key_here",
+    "secret_access_key": "my_secret_here"
   },
   "endpoints": "https://control.cloud-object-storage.cloud.ibm.com/v2/endpoints",
-  "iam_apikey_description": "my description _here_ ...",
-  "iam_apikey_name": "my key name _here_",
+  "iam_apikey_description": "my_description_here",
+  "iam_apikey_name": "my_key_name_here",
   "iam_role_crn": "crn:v1:bluemix:public:iam::::serviceRole:Writer",
   "iam_serviceid_crn": "crn:v1:bluemix:public:iam-identity::a/xxxxxxx.....",
   "resource_instance_id": "crn:v1:bluemix:public:cloud-object-storage:global:a/xxxxxxx....."
 }
 ```
 
+<!-- spellchecker: enable -->
+
 The field `resource_instance_id` is for option `crn`
 
 The field `apikey` is for option `apikey`
@@ -4950,7 +5085,7 @@ In this case, some of the `sync` parameters are fill from parameters of the rela
 > **Note:** All `sync` commands require an `async` enabled license and availability of the `async` executable (and `asyncadmin`).
 >
 > **Note:** Two JSON syntax are supported for option `sync_info`.
-> The first is same sync payload as specified on the `async` option `--conf` or in the latest node API, this is the prefered syntax and allows a single session definition.
+> The first is same sync payload as specified on the `async` option `--conf` or in the latest node API, this is the preferred syntax and allows a single session definition.
 > The second (legacy) is specific to `ascli` and allows definition of multiple sync sessions in a single command, although usually only one sync session is defined.
 
 Documentation on Async node API can be found on [IBM Developer Portal](https://developer.ibm.com/apis/catalog?search=%22aspera%20sync%20api%22).
@@ -5059,6 +5194,7 @@ dnf install unoconv
 
 - Amazon Linux
 
+<!-- spellchecker: disable -->
 ```bash
 amazon-linux-extras enable libreoffice
 yum clean metadata
@@ -5067,6 +5203,7 @@ wget https://raw.githubusercontent.com/unoconv/unoconv/master/unoconv
 mv unoconv /usr/bin
 chmod a+x /usr/bin/unoconv
 ```
+<!-- spellchecker: enable -->
 
 ### Configuration
 
@@ -5079,9 +5216,9 @@ The `xfer` user has a special protected shell: `aspshell`, so changing identity
 ```bash
 su -s /bin/bash - xfer
 
-ascli config preset update previewconf --url=https://localhost:9092 --username=my_access_key --password=my_secret --skip-types=office --lock-port=12346
+ascli config preset update mypreviewconf --url=https://localhost:9092 --username=my_access_key --password=my_secret --skip-types=office --lock-port=12346
 
-ascli config preset set default preview previewconf
+ascli config preset set default preview mypreviewconf
 ```
 
 Here we assume that Office file generation is disabled, else remove this option.
@@ -5126,6 +5263,7 @@ Lets first setup a script that will be used in the scheduler and set up the envi
 
 Example of startup script `cron_ascli`, which sets the Ruby environment and adds some timeout protection:
 
+<!-- spellchecker: disable -->
 ```bash
  #!/bin/bash
  # set a timeout protection, just in case
@@ -5134,6 +5272,7 @@ case "$*" in *trev*) tmout=10m ;; *) tmout=30m ;; esac
 rvm use 2.6 --quiet
 exec timeout ${tmout} ascli "${@}"
 ```
+<!-- spellchecker: enable -->
 
 Here the cronjob is created for user `xfer`.
 
@@ -5302,19 +5441,19 @@ The `smtp` option is a hash table (extended value) with the following fields:
 ```bash
 ascli config preset set smtp_google server smtp.google.com
 ascli config preset set smtp_google username john@gmail.com
-ascli config preset set smtp_google password _pass_here_
+ascli config preset set smtp_google password my_password_here
 ```
 
 or
 
-```javascript
-ascli config preset init smtp_google @json:'{"server":"smtp.google.com","username":"john@gmail.com","password":"_pass_here_"}'
+```bash
+ascli config preset init smtp_google @json:'{"server":"smtp.google.com","username":"john@gmail.com","password":"my_password_here"}'
 ```
 
 or
 
 ```bash
-ascli config preset update smtp_google --server=smtp.google.com --username=john@gmail.com --password=_pass_here_
+ascli config preset update smtp_google --server=smtp.google.com --username=john@gmail.com --password=my_password_here
 ```
 
 Set this configuration as global default, for instance:
@@ -5382,7 +5521,7 @@ It aims at simplifying the startup of a FASP session from a programmatic stand p
 - common to Aspera Connect API (browser javascript startTransfer)
 - easy to generate by using any third party language specific JSON library
 
-Hopefully, IBM integrates this diectly in `ascp`, and this tool is made redundant.
+Hopefully, IBM integrates this directly in `ascp`, and this tool is made redundant.
 
 This makes it easy to integrate with any language provided that one can spawn a sub process, write to its STDIN, read from STDOUT, generate and parse JSON.
 
@@ -5416,7 +5555,7 @@ There are special "extended" [*transfer-spec*](#transferspec) parameters support
 Create a file `session.json` with:
 
 ```json
-{"remote_host":"demo.asperasoft.com","remote_user":"asperaweb","ssh_port":33001,"remote_password":"_pass_here_","direction":"receive","destination_root":"./test.dir","paths":[{"source":"/aspera-test-dir-tiny/200KB.1"}],"resume_level":"none"}
+{"remote_host":"demo.asperasoft.com","remote_user":"asperaweb","ssh_port":33001,"remote_password":"my_password_here","direction":"receive","destination_root":"./test.dir","paths":[{"source":"/aspera-test-dir-tiny/200KB.1"}],"resume_level":"none"}
 ````
 
 Then start the session:
@@ -5431,9 +5570,9 @@ asession < session.json
 
 This is particularly useful for a persistent session ( with the [*transfer-spec*](#transferspec) parameter: `"keepalive":true` )
 
-```javascript
+```json
 asession
-{"remote_host":"demo.asperasoft.com","ssh_port":33001,"remote_user":"asperaweb","remote_password":"_pass_here_","direction":"receive","destination_root":".","keepalive":true,"resume_level":"none"}
+{"remote_host":"demo.asperasoft.com","ssh_port":33001,"remote_user":"asperaweb","remote_password":"my_password_here","direction":"receive","destination_root":".","keepalive":true,"resume_level":"none"}
 {"type":"START","source":"/aspera-test-dir-tiny/200KB.2"}
 {"type":"DONE"}
 ```
@@ -5498,16 +5637,16 @@ The general idea is to rely on :
 
 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` 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 that:
-
-- `ascli` takes transfer parameters exclusively as a [*transfer-spec*](#transferspec), with `--ts` parameter.
-- most, but not all, native `ascp` arguments are available as standard [*transfer-spec*](#transferspec) parameters
-- native `ascp` arguments can be provided with the [*transfer-spec*](#transferspec) parameter: `EX_ascp_args` (array), only for the [`direct`](#agt_direct) transfer agent (not others, like connect or node)
+> **Note:** `ascli` takes transfer parameters exclusively as a [*transfer-spec*](#transferspec), with `--ts` parameter.
+>
+> **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 option `transfer_info` parameter `ascp_args`.
 
 #### server side and configuration
 
@@ -5530,7 +5669,7 @@ ascli server upload source_hot --to-folder=/Upload/target_hot --lock-port=12345
 
 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 cooloff period).
+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
@@ -5585,7 +5724,7 @@ OK - [transfer:ok]
 ```
 
 ```bash
-ascli server health asctlstatus --cmd_prefix='sudo ' --format=nagios
+ascli server health asctl status --cmd_prefix='sudo ' --format=nagios
 ```
 
 ```output
@@ -5631,11 +5770,14 @@ 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). Once, Serban (founder) provided a shell script able to create a Faspex Package using Faspex REST API. Since all products relate to file transfers using FASP (`ascp`), I thought it would be interesting to have a unified CLI for transfers using FASP. Also, because there was already the `ascp` tool, I thought of an extended tool : `eascp.pl` which was accepting all `ascp` options for transfer but was also able to transfer to Faspex and Shares (destination was a kind of URI for the applications).
+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).
+Once, Serban (founder) provided a shell script able to create a Faspex Package using Faspex REST API.
+Since all products relate to file transfers using FASP (`ascp`), I thought it would be interesting to have a unified CLI for transfers using FASP.
+Also, because there was already the `ascp` tool, I thought of an extended tool : `eascp.pl` which was accepting all `ascp` options for transfer but was also able to transfer to Faspex and Shares (destination was a kind of URI for the applications).
 
 There were a few pitfalls:
 
-- The tool was written in the aging `perl` language while most Aspera application products (but the Transfer Server) are written in `ruby`.
+- The tool was written in the aging `perl` language while most Aspera web application products (but the Transfer Server) are written in `ruby`.
 - The tool was only for transfers, but not able to call other products APIs
 
 So, it evolved into `ascli`:
@@ -5645,6 +5787,9 @@ So, it evolved into `ascli`:
 - 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.
+It had the advantage of being relatively easy to installed, as a single executable (well, still using `ascp`), but it was too limited IMHO, and lacked a lot of the features of this CLI.
+
 ## Common problems
 
 ### Error: "Remote host is not who we expected"
@@ -5653,7 +5798,7 @@ Cause: `ascp` >= 4.x checks fingerprint of highest server host key, including EC
 
 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):
 
-```javascript
+```bash
 --ts=@json:'{"sshfp":null}'
 ```
 
@@ -5665,7 +5810,7 @@ References: ES-1944 in release notes of 4.1 and to [HSTS admin manual section "C
 
 Some Ruby gems dependencies require compilation of native parts (C).
 This also requires Ruby header files.
-If Ruby was installed as a Linux Packages, then also install ruby dev elopment package:
+If Ruby was installed as a Linux Packages, then also install ruby development package:
 `ruby-dev` ir `ruby-devel`, depending on distribution.
 
 ### ED255519 key not supported