aspera-cli 4.24.0 → 4.24.1

data/README.md

@@ -2,19 +2,21 @@
 <!--
 DO NOT EDIT: THIS FILE IS GENERATED, edit docs/README.erb.md, for details, read docs/README.md
 PANDOC_META_BEGIN
-subtitle: "ascli 4.24.0"
+subtitle: "ascli 4.24.1"
 author: "Laurent MARTIN"
 PANDOC_META_END
 -->
 <!-- markdownlint-disable MD033 -->
 
+<!-- NOTE CAUTION WARNING IMPORTANT TIP INFO -->
+
 [![Gem Version](https://badge.fury.io/rb/aspera-cli.svg)](https://badge.fury.io/rb/aspera-cli)
 [![unit tests](https://github.com/IBM/aspera-cli/actions/workflows/test.yml/badge.svg?branch=main)](https://github.com/IBM/aspera-cli/actions)
 [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/5861/badge)](https://bestpractices.coreinfrastructure.org/projects/5861)
 
 ## Introduction
 
-![Hootput the Owl](../docs/ascli-impersonation-small.png)
+![Hootput the Owl](docs/ascli-impersonation-small.png)
 
 Hootput lives in the terminal, watching over every command with wide, unblinking eyes.
 Known for concise output and sharp insight, this owl thrives where others get lost in the dark.
@@ -39,7 +41,7 @@ Need to debug? I’ll show you what’s going on under the hood.
 
 Think of me as Aspera’s command-line sidekick: quick, reliable, and a little no-nonsense. You bring the files; I’ll bring the horsepower."
 
-Version : 4.24.0
+Version : 4.24.1
 
 Laurent/2016-2025
 
@@ -126,12 +128,12 @@ First, follow section: [Installation](#installation) (Ruby, Gem, FASP) to start
 
 Once the gem is installed, `ascli` shall be accessible:
 
-```bash
+```shell
 ascli --version
 ```
 
 ```text
-4.24.0
+4.24.1
 ```
 
 > [!NOTE]
@@ -145,11 +147,11 @@ If you want to test with Aspera on Cloud, jump to section: [Wizard](#configurati
 
 To test with Aspera demo transfer server, set up the environment and then test:
 
-```bash
+```shell
 ascli config initdemo
 ```
 
-```bash
+```shell
 ascli server browse /
 ```
 
@@ -172,7 +174,7 @@ The following example will:
 - List files in a folder
 - Download a file
 
-```bash
+```shell
 ascli config preset update myserver --url=ssh://demo.asperasoft.com:33001 --username=asperaweb --password=my_password_here
 ```
 
@@ -181,7 +183,7 @@ Updated: myserver
 Saving config file.
 ```
 
-```bash
+```shell
 ascli config preset set default server myserver
 ```
 
@@ -190,7 +192,7 @@ Updated: default: server <- myserver
 Saving config file.
 ```
 
-```bash
+```shell
 ascli server browse /aspera-test-dir-large
 ```
 
@@ -207,7 +209,7 @@ ascli server browse /aspera-test-dir-large
 ╰────────────┴──────┴───────────┴─────────────┴───────────────────────────┴───────╯
 ```
 
-```bash
+```shell
 ascli server download /aspera-test-dir-large/200MB
 ```
 
@@ -255,7 +257,7 @@ It is planned to provide `ascli` as a single platform-dependent executable.
 >
 > On Linux, check the minimum required GLIBC on this site: [repology.org](https://repology.org/project/glibc/versions), or check your GLIBC version with `ldd`:
 
-```bash
+```shell
 ldd --version | head -n1
 ```
 
@@ -265,7 +267,7 @@ ldd (GNU libc) 2.34
 
 Check an executable's (e.g. `/bin/bash`, `ascli`, `ascp`) minimum required GLIBC version:
 
-```bash
+```shell
 objdump -p /bin/bash | sed -n 's/^.*GLIBC_//p' | sort -V | tail -n1
 ```
 
@@ -315,7 +317,7 @@ The Ruby installer supports silent installation, to see the options, execute it
 
 Download the Ruby installer executable from <https://rubyinstaller.org/downloads/> and then install:
 
-```bat
+```batchfile
 rubyinstaller-devkit-3.2.2-1-x64.exe /silent /currentuser /noicons /dir=C:\aspera-cli
 ```
 
@@ -328,7 +330,7 @@ Do not use it.
 
 The recommended way is to use [Homebrew](https://brew.sh/).
 
-```bash
+```shell
 brew install ruby
 ```
 
@@ -336,7 +338,7 @@ This installs a recent Ruby suitable for `ascli`.
 
 To add PATH to Ruby on Apple Silicon, add this in your shell configuration file (e.g. `~/.bash_profile` or `~/.zshrc`):
 
-```bash
+```shell
 use_ruby(){
     local version=$1
     case $version in list) for r in $(brew list -1 | grep '^ruby'); do
@@ -367,48 +369,48 @@ If your Linux distribution provides a standard Ruby package, you can use it prov
 
 - Check available Ruby versions:
 
-  ```bash
+  ```shell
   dnf module list ruby
   ```
 
 - If Ruby was already installed with an older version, remove it:
 
-  ```bash
+  ```shell
   dnf module -y reset ruby
   ```
 
 - Install packages needed to build native gems:
   
-  ```bash
+  ```shell
   dnf install -y make automake gcc gcc-c++ kernel-devel
   ```
 
 - Enable the Ruby version you want:
 
-  ```bash
+  ```shell
   dnf module -y enable ruby:3.1
   dnf install -y ruby-devel
   ```
 
 **Example:** Ubuntu
 
-```bash
+```shell
 apt-get install -y ruby-full
 ```
 
 **Other examples:**
 
-```bash
+```shell
 yum install -y ruby ruby-devel rubygems ruby-json
 ```
 
-```bash
+```shell
 apt install -y ruby ruby-dev rubygems ruby-json
 ```
 
 One can remove all installed gems, for example to start fresh:
 
-```bash
+```shell
 gem uninstall -axI $(ls $(gem env gemdir)/gems/|sed -e 's/-[^-]*$//'|sort -u)
 ```
 
@@ -420,7 +422,7 @@ Follow [https://rvm.io/](https://rvm.io/).
 Execute the shell/curl command.
 As regular user, it installs in the user's home: `~/.rvm`.
 
-```bash
+```shell
 \curl -sSL https://get.rvm.io | bash -s stable
 ```
 
@@ -428,19 +430,19 @@ Follow on-screen instructions to install keys, and then re-execute the command.
 
 Upon RVM installation, open a new terminal or initialize with:
 
-```bash
+```shell
 source ~/.rvm/scripts/rvm
 ```
 
 It is advised to get one of the pre-compiled Ruby version, you can list with:
 
-```bash
+```shell
 rvm list --remote
 ```
 
 Install the chosen pre-compiled Ruby version:
 
-```bash
+```shell
 rvm install 3.2.2
 ```
 
@@ -450,30 +452,30 @@ Alternatively RVM can be installed system-wide, for this execute as `root`.
 It then installs by default in `/usr/local/rvm` for all users and creates `/etc/profile.d/rvm.sh`.
 One can install in another location with:
 
-```bash
+```shell
 curl -sSL https://get.rvm.io | bash -s -- --path /usr/local
 ```
 
 As root, make sure this will not collide with other application using Ruby (e.g. Faspex).
 If so, one can rename the environment script so that it is not loaded by default:
 
-```bash
+```shell
 mv /etc/profile.d/rvm.sh /etc/profile.d/rvm.sh.ok
 ```
 
 To activate Ruby (and ascli) later, source it:
 
-```bash
+```shell
 source /etc/profile.d/rvm.sh.ok
 ```
 
-```bash
+```shell
 rvm version
 ```
 
 On macOS, one way to force use of OpenSSL 3.0 is:
 
-```bash
+```shell
 RUBY_CONFIGURE_OPTS="--with-openssl-dir=$(brew --prefix openssl@3.0)" rvm install 3.4.0
 ```
 
@@ -481,19 +483,19 @@ RUBY_CONFIGURE_OPTS="--with-openssl-dir=$(brew --prefix openssl@3.0)" rvm instal
 
 If you don't have root access, you can install Ruby in your home directory using `rbenv` see [`rbenv-installer`](https://github.com/rbenv/rbenv-installer#rbenv-installer):
 
-```bash
+```shell
 curl -fsSL https://github.com/rbenv/rbenv-installer/raw/HEAD/bin/rbenv-installer | bash
 ```
 
 Then open a new terminal, or `source` the shell initialization script:
 
-```bash
+```shell
 source ~/.bashrc
 ```
 
 Then install Ruby:
 
-```bash
+```shell
 rbenv install 3.2.2
 ```
 
@@ -508,7 +510,7 @@ If your Unix does not provide a pre-built Ruby, you can get it using one of thos
 
 For instance to build from source and install in `/opt/ruby` :
 
-```bash
+```shell
 wget https://cache.ruby-lang.org/pub/ruby/2.7/ruby-2.7.2.tar.gz
 
 gzip -d ruby-2.7.2.tar.gz
@@ -548,14 +550,14 @@ Choose the latest version from:
 
 Example: start `ascli` with JRuby and reduce startup time:
 
-```bash
+```shell
 export JRUBY_OPTS=--dev
 ascli -v
 ```
 
 or
 
-```bash
+```shell
 JRUBY_OPTS=--dev ascli -v
 ```
 
@@ -579,7 +581,7 @@ See [Gemfile](Gemfile):
 
 Install like this:
 
-```bash
+```shell
 gem install grpc -v '~> 1.71'
 gem install mimemagic -v '~> 0.4'
 gem install rmagick -v '~> 6.1'
@@ -594,13 +596,13 @@ gem install sequel -v '~> 5.96'
 
 Once you have Ruby and rights to install gems, install the `aspera-cli` gem and its dependencies:
 
-```bash
+```shell
 gem install aspera-cli
 ```
 
 To upgrade to the latest version:
 
-```bash
+```shell
 gem update aspera-cli
 ```
 
@@ -609,7 +611,7 @@ To deactivate this feature, globally set the option `version_check_days` to `0`,
 
 To check if a new version is available (independently of `version_check_days`):
 
-```bash
+```shell
 ascli config check_update
 ```
 
@@ -622,13 +624,13 @@ For [secure installation](https://guides.rubygems.org/security/#using-gems), one
 
 Import the verification certificate:
 
-```bash
+```shell
 gem cert --add <(curl -Ls https://raw.githubusercontent.com/IBM/aspera-cli/main/certs/aspera-cli-public-cert.pem)
 ```
 
 The user installs the gem with `HighSecurity` or `MediumSecurity`: this will succeed only of the gem is trusted:
 
-```bash
+```shell
 gem install -P MediumSecurity aspera-cli
 ```
 
@@ -647,13 +649,13 @@ This can be installed either be installing an Aspera transfer software or using
 The easiest option to install `ascp` is through the use of the IBM Aspera Transfer Daemon (`transferd`).
 Install using `ascli` for the current platform with:
 
-```bash
+```shell
 ascli config transferd install
 ```
 
 or
 
-```bash
+```shell
 ascli config ascp install
 ```
 
@@ -679,25 +681,25 @@ Available Transfer Daemon versions available from `locations_url` can be listed
 
 To install a specific version, e.g. 1.1.3:
 
-```bash
+```shell
 ascli config ascp install 1.1.3
 ```
 
 To get the download URL for a specific platform and version:
 
-```bash
+```shell
 ascli config transferd list --select=@json:'{"platform":"osx-arm64","version":"1.1.3"}' --fields=url
 ```
 
 To download it, pipe to `config download`:
 
-```bash
+```shell
 ascli config transferd list --select=@json:'{"platform":"osx-arm64","version":"1.1.3"}' --fields=url | ascli config download @stdin:
 ```
 
 If installation from a local file preferred (air-gapped installation) instead of fetching from internet: one can specify the location of the SDK file with option `sdk_url`:
 
-```bash
+```shell
 ascli config ascp install --sdk-url=file:///macos-arm64-1.1.3-c6c7a2a.zip
 ```
 
@@ -733,7 +735,7 @@ Refer to section: [Transfer Agents](#transfer-clients-agents)
 
 The sample script: [windows/build_package.sh](windows/build_package.sh) can be used to download all necessary gems and dependencies in a `tar.gz`.
 
-```bash
+```shell
 ./build_package.sh aspera-cli 4.18.0
 ```
 
@@ -751,7 +753,7 @@ The procedure:
 
 - Archive (zip, tar) the main RVM folder (includes ascli):
 
-```bash
+```shell
 cd $HOME && tar zcvf rvm-ascli.tgz .rvm
 ```
 
@@ -761,7 +763,7 @@ cd $HOME && tar zcvf rvm-ascli.tgz .rvm
 
 - On target system
 
-```bash
+```shell
 cd $HOME
 
 tar zxvf rvm-ascli.tgz
@@ -773,7 +775,7 @@ ascli config ascp install --sdk-url=file:///[SDK archive file path]
 
 - Add those lines to shell environment (`.profile`)
 
-```bash
+```shell
 source ~/.rvm/scripts/rvm
 ```
 
@@ -785,7 +787,7 @@ It is essentially the same procedure as installation for Windows with internet,
 
 - Download the Ruby installer from <https://rubyinstaller.org/downloads/>
 
-  ```bash
+  ```shell
   v=$(curl -s https://rubyinstaller.org/downloads/ | sed -nEe 's|.*(https://.*/releases/download/.*exe).*|\1|p' | head -n 1)
   curl -o ${v##*/} $v
   ```
@@ -801,19 +803,19 @@ Then, on the target system:
 - Unzip the archive
 - Execute the installer:
 
-```bat
+```batchfile
 rubyinstaller-devkit-3.2.2-1-x64.exe /silent /currentuser /noicons /dir=C:\aspera-cli
 ```
 
 - Install the gems: Extract the gem archive and then:
 
-```bat
+```batchfile
 gem install --force --local *.gem
 ```
 
 - Install the Aspera Transfer Daemon SDK
 
-```bash
+```shell
 ascli config ascp install --sdk-url=file:///sdk.zip
 ```
 
@@ -826,7 +828,7 @@ The container image is: [`docker.io/martinlaurent/ascli`](https://hub.docker.com
 The container contains: Ruby, `ascli` and the Aspera Transfer Daemon.
 To use the container, ensure that you have `podman` (or `docker`) installed.
 
-```bash
+```shell
 podman --version
 ```
 
@@ -836,7 +838,7 @@ podman --version
 
 Execute this:
 
-```bash
+```shell
 podman run --rm --tty --interactive --entrypoint bash docker.io/martinlaurent/ascli:latest
 ```
 
@@ -845,7 +847,7 @@ podman run --rm --tty --interactive --entrypoint bash docker.io/martinlaurent/as
 
 Then, execute individual `ascli` commands such as:
 
-```bash
+```shell
 ascli config init
 ascli config preset overview
 ascli config ascp info
@@ -866,31 +868,31 @@ The entry point is `ascli` and the default command is `help`.
 
 The container can be executed for individual commands like this: (add `ascli` commands and options at the end of the command line, e.g. `-v` to display the version)
 
-```bash
+```shell
 podman run --rm --tty --interactive docker.io/martinlaurent/ascli:latest
 ```
 
 For more convenience, you may define a shell alias:
 
-```bash
+```shell
 alias ascli='podman run --rm --tty --interactive docker.io/martinlaurent/ascli:latest'
 ```
 
 Then, you can execute the container like a local command:
 
-```bash
+```shell
 ascli -v
 ```
 
 ```text
-4.24.0
+4.24.1
 ```
 
 In order to keep persistency of configuration on the host, you should specify your user's configuration folder as a volume for the container.
 To enable write access, a possibility is to run as `root` in the container (and set the default configuration folder to `/home/cliuser/.aspera/ascli`).
 Add options:
 
-```bash
+```shell
 --user root --env ASCLI_HOME=/home/cliuser/.aspera/ascli --volume $HOME/.aspera/ascli:/home/cliuser/.aspera/ascli
 ```
 
@@ -902,14 +904,14 @@ Add options:
 As shown in the quick start, if you prefer to keep a running container with a shell and `ascli` available,
 you can change the entry point, add option:
 
-```bash
+```shell
 --entrypoint bash
 ```
 
 You may also probably want that files downloaded in the container are directed to the host.
 In this case you need also to specify the shared transfer folder as a volume:
 
-```bash
+```shell
 --volume $HOME/xferdir:/xferfiles
 ```
 
@@ -918,11 +920,11 @@ In this case you need also to specify the shared transfer folder as a volume:
 
 And if you want all the above, simply use all the options:
 
-```bash
+```shell
 alias asclish="podman run --rm --tty --interactive --user root --env ASCLI_HOME=/home/cliuser/.aspera/ascli --volume $HOME/.aspera/ascli:/home/cliuser/.aspera/ascli --volume $HOME/xferdir:/xferfiles --entrypoint bash docker.io/martinlaurent/ascli:latest"
 ```
 
-```bash
+```shell
 export xferdir=$HOME/xferdir
 mkdir -p $xferdir
 chmod -R 777 $xferdir
@@ -956,7 +958,7 @@ To add local storage as a volume, you can use the env var `docker_args`:
 
 Example of use:
 
-```bash
+```shell
 curl -o ascli https://raw.githubusercontent.com/IBM/aspera-cli/main/container/dascli
 chmod a+x ascli
 export xferdir=$HOME/xferdir
@@ -981,14 +983,14 @@ echo 'Local file to transfer' > $xferdir/samplefile.txt
 
 - First create the image archive:
 
-```bash
+```shell
 podman pull docker.io/martinlaurent/ascli
 podman save docker.io/martinlaurent/ascli|gzip>ascli_image_latest.tar.gz
 ```
 
 - Then, on air-gapped system:
 
-```bash
+```shell
 podman load -i ascli_image_latest.tar.gz
 ```
 
@@ -998,13 +1000,13 @@ podman load -i ascli_image_latest.tar.gz
 As the container is immutable, it is not recommended modifying this file.
 If one wants to change the content, it is possible to tell `ascp` to use another file using `ascp` option `-f`, e.g. by locating it on the host folder `$HOME/.aspera/ascli` mapped to the container folder `/home/cliuser/.aspera/ascli`:
 
-```bash
+```shell
 echo '<CONF/>' > $HOME/.aspera/ascli/aspera.conf
 ```
 
 Then, tell `ascp` to use that other configuration file:
 
-```bash
+```shell
 --transfer-info=@json:'{"ascp_args":["-f","/home/cliuser/.aspera/ascli/aspera.conf"]}'
 ```
 
@@ -1014,25 +1016,25 @@ Singularity is another type of use of container.
 
 On Linux install:
 
-```bash
+```shell
 dnf install singularity-ce
 ```
 
 Build an image like this:
 
-```bash
+```shell
 singularity build ascli.sif docker://docker.io/martinlaurent/ascli
 ```
 
 Then, start `ascli` like this:
 
-```bash
+```shell
 singularity run ascli.sif
 ```
 
 Or get a shell with access to `ascli` like this:
 
-```bash
+```shell
 singularity shell ascli.sif
 ```
 
@@ -1042,13 +1044,13 @@ singularity shell ascli.sif
 
 To display the version of **OpenSSL** used in `ascli`:
 
-```bash
+```shell
 ascli config echo @ruby:OpenSSL::OPENSSL_VERSION --format=text
 ```
 
 It is possible to specify to use another SSL library or version by executing:
 
-```bash
+```shell
 gem install openssl -- --with-openssl-dir=[openssl library folder]
 ```
 
@@ -1056,7 +1058,7 @@ Where `[openssl library folder]` is the path to the folder containing the `lib`
 
 For example, on macOS, to use the `openssl@3` library installed with `brew`:
 
-```bash
+```shell
 openssl version -e|sed -n 's|ENGINESDIR: "\(.*\)/lib[^/]*/.*|\1|p'
 ```
 
@@ -1066,7 +1068,7 @@ openssl version -e|sed -n 's|ENGINESDIR: "\(.*\)/lib[^/]*/.*|\1|p'
 
 Then install the `openssl` gem with:
 
-```bash
+```shell
 gem install openssl -- --with-openssl-dir=$(openssl version -e|sed -n 's|ENGINESDIR: "\(.*\)/lib[^/]*/.*|\1|p')
 ```
 
@@ -1076,7 +1078,7 @@ SSL certificates are validated using a certificate store, by default it is the o
 
 To display trusted certificate store locations:
 
-```bash
+```shell
 ascli --show-config --fields=cert_stores
 ```
 
@@ -1085,7 +1087,7 @@ Ruby's default values can be overridden using env vars: `SSL_CERT_FILE` and `SSL
 
 One can display those default values:
 
-```bash
+```shell
 ascli config echo @ruby:OpenSSL::X509::DEFAULT_CERT_DIR --format=text
 ascli config echo @ruby:OpenSSL::X509::DEFAULT_CERT_FILE --format=text
 ```
@@ -1095,7 +1097,7 @@ Check this repository on how to update the system's CA certificate bundle: [http
 
 For example on RHEL/Rocky Linux:
 
-```bash
+```shell
 dnf install -y ca-certificates
 update-ca-trust extract
 ```
@@ -1115,7 +1117,7 @@ When `cert_stores` is provided:
 
 For example, on Linux to force the use the system's certificate store:
 
-```bash
+```shell
 --cert-stores=$(openssl version -d|cut -f2 -d'"')/cert.pem
 ```
 
@@ -1124,7 +1126,7 @@ For example, on Linux to force the use the system's certificate store:
 By default,`ascp` uses a hard coded root location `OPENSSLDIR`.
 Original `ascp`'s hard coded locations can be found using:
 
-```bash
+```shell
 ascli config ascp info --fields=openssldir
 ```
 
@@ -1138,13 +1140,13 @@ Typically done by updating the system's root certificate store.
 
 An up-to-date version of the certificate bundle can also be retrieved with:
 
-```bash
+```shell
 ascli config echo @uri:https://curl.haxx.se/ca/cacert.pem --format=text
 ```
 
 To download that certificate store:
 
-```bash
+```shell
 ascli config echo @uri:https://curl.haxx.se/ca/cacert.pem --format=text --output=/tmp/cacert.pem
 ```
 
@@ -1152,7 +1154,7 @@ Then, use this store by setting the option `cert_stores` (or env var `SSL_CERT_F
 
 To trust a specific certificate (e.g. self-signed), **provided that the `CN` is correct**, save the certificate chain to a file:
 
-```bash
+```shell
 ascli config remote_certificate chain https://localhost:9092 --insecure=yes --output=myserver.pem
 ```
 
@@ -1161,7 +1163,7 @@ ascli config remote_certificate chain https://localhost:9092 --insecure=yes --ou
 
 Then, use this file as certificate store (e.g. here, Node API):
 
-```bash
+```shell
 ascli config echo @uri:https://localhost:9092/ping --cert-stores=myserver.pem
 ```
 
@@ -1195,7 +1197,7 @@ The `aspera-cli` gem provides a command line interface (CLI) which interacts wit
 
 Basic usage is displayed by executing:
 
-```bash
+```shell
 ascli -h
 ```
 
@@ -1252,7 +1254,7 @@ One can also run `ascli` with option `--log-level=debug` to display the command
 
 It is also possible to display arguments received by Ruby using this command:
 
-```bat
+```batchfile
 C:> ruby -e 'puts ARGV' "Hello World" 1 2
 ```
 
@@ -1289,19 +1291,19 @@ The following examples give the same result on Windows using `cmd.exe`:
 
 - Single quote protects the double quote
 
-  ```cmd
+  ```batchfile
   ascli config echo @json:'{"url":"https://..."}'
   ```
 
 - Triple double quotes are replaced with a single double quote
 
-  ```cmd
+  ```batchfile
   ascli config echo @json:{"""url""":"""https://..."""}
   ```
 
 - Double quote is escaped with backslash within double quotes
 
-  ```cmd
+  ```batchfile
   ascli config echo @json:"{\"url\":\"https://...\"}"
   ```
 
@@ -1355,7 +1357,7 @@ Unprocessed command line arguments are shown in the error message.
 Example:
 The shell parses three arguments (as `String`: `1`, `2` and `3`), so the additional two arguments are not processed by the `echo` command.
 
-```bash
+```shell
 ascli config echo 1 2 3
 ```
 
@@ -1379,7 +1381,7 @@ For example, in the simple string `Hello World`, the space character is special
 Double quotes are processed by the shell to create a single string argument.
 For **POSIX shells**, single quotes can also be used in this case, or protect the special character ` ` (space) with a backslash. <!-- markdownlint-disable-line -->
 
-```bash
+```shell
 ascli config echo "Hello World" --format=text
 ascli config echo 'Hello World' --format=text
 ascli config echo Hello\ World --format=text
@@ -1398,7 +1400,7 @@ Even if the variable contains spaces it results only in one argument for `ascli`
 > We use a simple shell variable in this example.
 > Note that it does not need to be exported as an environment variable.
 
-```bash
+```shell
 MYVAR="Hello World"
 ascli config echo @json:'{"title":"'$MYVAR'"}' --format=json
 ascli config echo @json:{\"title\":\"$MYVAR\"} --format=json
@@ -1413,7 +1415,7 @@ ascli config echo @json:{\"title\":\"$MYVAR\"} --format=json
 Double quote is a shell special character.
 Like any shell special character, it can be protected either by preceding with a backslash or by enclosing in a single quote.
 
-```bash
+```shell
 ascli config echo \"
 ascli config echo '"'
 ```
@@ -1425,7 +1427,7 @@ ascli config echo '"'
 Double quote in JSON is a little tricky because `"` is special both for the shell and JSON.
 Both shell and JSON syntax allow protecting `"`, but only the shell allows protection using single quote.
 
-```bash
+```shell
 ascli config echo @json:'"\""' --format=text
 ascli config echo @json:\"\\\"\" --format=text
 ascli config echo @ruby:\'\"\' --format=text
@@ -1461,7 +1463,7 @@ Both `"` and `\` are special characters for JSON and Ruby and can be protected w
   
 - Then, since the value will be evaluated by shell, any shell special characters must be protected, either using preceding `\` for each character to protect, or by enclosing in single quote:
 
-```bash
+```shell
 ascli config echo @json:{\"title\":\"Test\ \\\"\ \'\ \&\ \\\\\"} --format=json
 ascli config echo @json:'{"title":"Test \" '\'' & \\"}' --format=json
 ascli config echo @ruby:"{'title'=>%q{Test \" ' & \\\\}}" --format=json
@@ -1475,7 +1477,7 @@ ascli config echo @ruby:"{'title'=>%q{Test \" ' & \\\\}}" --format=json
 
 If `ascli` is used interactively (a user typing on terminal), it is easy to require the user to type values:
 
-```bash
+```shell
 ascli config echo @ruby:"{'title'=>gets.chomp}" --format=json
 ```
 
@@ -1485,13 +1487,13 @@ ascli config echo @ruby:"{'title'=>gets.chomp}" --format=json
 
 If you need to provide a list of command line argument from lines that are in a file, on Linux you can use the `xargs` command:
 
-```bash
+```shell
 xargs -a lines.txt -d \\n ascli config echo
 ```
 
 This is equivalent to execution of:
 
-```bash
+```shell
 ascli config echo [line1] [line2] [line3] ...
 ```
 
@@ -1501,7 +1503,7 @@ If there are spaces in the lines, those are not taken as separator, as we provid
 
 Using a text editor or shell: create a file `title.txt` (and env var) that contains exactly the text required: `Test " ' & \` :
 
-```bash
+```shell
 export MYTITLE='Test " '\'' & \'
 echo -n $MYTITLE > title.txt
 ```
@@ -1510,7 +1512,7 @@ Using those values will not require any escaping of characters since values do n
 
 If the value is to be assigned directly to an option of ascli, then you can directly use the content of the file or env var using the `@file:` or `@env:` readers:
 
-```bash
+```shell
 ascli config echo @file:title.txt --format=text
 ascli config echo @env:MYTITLE --format=text
 ```
@@ -1522,7 +1524,7 @@ Test " ' & \
 If the value to be used is in a more complex structure, then the `@ruby:` modifier can be used: it allows any Ruby code in expression, including reading from file or env var.
 In those cases, there is no character to protect because values are not parsed by the shell, or JSON or even Ruby.
 
-```bash
+```shell
 ascli config echo @ruby:"{'title'=>File.read('title.txt')}" --format=json
 ascli config echo @ruby:"{'title'=>ENV['MYTITLE']}" --format=json
 ```
@@ -1543,7 +1545,7 @@ The tokenization of the command line is typically done by the shell, refer to th
 
 For example:
 
-```bash
+```shell
 ascli command subcommand --option-name=VAL1 VAL2
 ```
 
@@ -1569,7 +1571,7 @@ Its value is a `String` that must belong to a fixed list of values in a given co
 
 Example:
 
-```bash
+```shell
 ascli config ascp info
 ```
 
@@ -1642,11 +1644,11 @@ Exceptions and Special Cases:
 
 Example:
 
-```bash
+```shell
 ascli config echo -- --sample
 ```
 
-```bash
+```shell
 "--sample"
 ```
 
@@ -1739,13 +1741,13 @@ For `format=csv`, options are described in gem [`csv`](https://ruby.github.io/cs
 
 For example, to display a table with thick Unicode borders:
 
-```bash
+```shell
 ascli config preset over --table-style=@ruby:'{border: :unicode_thick_edge}'
 ```
 
 For example, to display a CSV with headers and quotes:
 
-```bash
+```shell
 ascli config echo @json:'[{"name":"foo","id":1},{"name":"bar","id":8}]' --format=csv --table=@json:'{"headers":true,"force_quotes":true}'
 ```
 
@@ -1765,7 +1767,7 @@ In this case, it is possible to filter fields using the option `fields` using th
 
 Example: Result of command is a list of objects with a single object:
 
-```bash
+```shell
 ascli config echo @json:'{"A":"a","B":[{"name":"B1","value":"b1"},{"name":"B2","value":"b2"}],"C":[{"C1":"c1"},{"C2":"c2"}],"D":{"D1":"d1","D2":"d2"}}'
 ```
 
@@ -1783,7 +1785,7 @@ ascli config echo @json:'{"A":"a","B":[{"name":"B1","value":"b1"},{"name":"B2","
 ╰────────┴───────╯
 ```
 
-```bash
+```shell
 ascli config echo @json:'{"A":"a","B":[{"name":"B1","value":"b1"},{"name":"B2","value":"b2"}],"C":[{"C1":"c1"},{"C2":"c2"}],"D":{"D1":"d1","D2":"d2"}}' -
 -flat=no
 ```
@@ -1812,7 +1814,7 @@ Special values are highlighted as follows::
 
 Example:
 
-```bash
+```shell
 ascli config echo @json:'{"ni":null,"es":"","ea":[],"eh":{}}'
 ```
 
@@ -1854,7 +1856,7 @@ The display of result is as follows:
 
 This parameter can be set as a global default with:
 
-```bash
+```shell
 ascli config preset set GLOBAL multi_single single
 ```
 
@@ -1862,7 +1864,7 @@ Examples:
 
 Simulate a result by executing this command:
 
-```bash
+```shell
 ascli config echo @json:'<json value here>' --multi-single=<no|yes|single>
 ```
 
@@ -1978,7 +1980,7 @@ The `Proc` takes as argument a line (`Hash`) in the table and is a Ruby lambda e
 
 Example:
 
-```bash
+```shell
 ascli aoc admin user list --fields=name,email,ats_admin --query=@json:'{"sort":"name"}' --select=@json:'{"ats_admin":true}'
 ```
 
@@ -1996,7 +1998,7 @@ ascli aoc admin user list --fields=name,email,ats_admin --query=@json:'{"sort":"
 
 In above example, the same result is obtained with option:
 
-```bash
+```shell
 --select=@ruby:'->(i){i["ats_admin"]}'
 ```
 
@@ -2011,7 +2013,7 @@ Syntax: `%<field>:<value>`
 When a command is executed on a single entity, the entity is identified by a unique identifier that follows the command.
 For example, in the following command, `1234` is the user's identifier:
 
-```bash
+```shell
 ascli aoc admin user show 1234
 ```
 
@@ -2019,7 +2021,7 @@ Some commands provide the following capability:
 If the entity can also be uniquely identified by a name, then the name can be used instead of the identifier, using the **percent selector**.
 For example, if the name of the user is `john` and a field for this entity named `name` has a value `john`:
 
-```bash
+```shell
 ascli aoc admin user show %name:john
 ```
 
@@ -2033,7 +2035,7 @@ The **Extended Value** Syntax allows to specify such values and even read values
 
 The syntax is:
 
-```bash
+```shell
 <0 or more decoders><some text value or nothing>
 ```
 
@@ -2075,35 +2077,35 @@ It expects a `@` to close the embedded extended value syntax.
 
 Example: Create a `Hash` value with the convenient `@json:` decoder:
 
-```bash
+```shell
 ascli config echo @json:'{"key1":"value1","key2":"value2"}'
 ```
 
 Example: read the content of the specified file, then, base64 decode, then unzip:
 
-```bash
+```shell
 ascli config echo @zlib:@base64:@file:myfile.dat
 ```
 
 Example: Create a `Hash` value with one key and the value is read from a file:
 
-```bash
+```shell
 ascli config echo @ruby:'{"token_verification_key"=>File.read("mykey.txt")}'
 ```
 
 Example: read a CSV file and create an `Array` of `Hash` for bulk provisioning:
 
-```bash
+```shell
 cat test.csv
 ```
 
-```bash
+```shell
 name,email
 lolo,laurent@example.com
 toto,titi@tutu.tata
 ```
 
-```bash
+```shell
 ascli config echo @csvt:@file:test.csv
 ```
 
@@ -2118,7 +2120,7 @@ ascli config echo @csvt:@file:test.csv
 
 Example: create a `Hash` with values coming from a preset named `config`
 
-```bash
+```shell
 ascli config echo @json:@extend:'{"hello":true,"version":"@preset:config.version@"}'
 ```
 
@@ -2133,7 +2135,7 @@ ascli config echo @json:@extend:'{"hello":true,"version":"@preset:config.version
 
 Example: Create a `Hash` from YAML provided as shell **Here document**:
 
-```bash
+```shell
 ascli config echo @yaml:@stdin: --format=json<<EOF
 key1: value1
 key2:
@@ -2161,11 +2163,11 @@ EOF
 
 The configuration folder can be displayed using :
 
-```bash
+```shell
 ascli config folder
 ```
 
-```bash
+```shell
 /Users/kenji/.aspera/ascli
 ```
 
@@ -2176,7 +2178,7 @@ It can be overridden using option `home`.
 
 Example (Windows):
 
-```bat
+```batchfile
 set ASCLI_HOME=C:\Users\Kenji\.aspera\ascli
 
 ascli config folder
@@ -2232,13 +2234,13 @@ An [Option Preset](#option-preset) is a collection of options and their associat
 
 A named [Option Preset](#option-preset) can be modified directly using `ascli`, which will update the configuration file :
 
-```bash
+```shell
 ascli config preset set|delete|show|initialize|update <option preset>
 ```
 
 The command `update` allows the easy creation of [Option Preset](#option-preset) by simply providing the options in their command line format, e.g. :
 
-```bash
+```shell
 ascli config preset update demo_server --url=ssh://demo.asperasoft.com:33001 --username=asperaweb --password=my_password_here --ts=@json:'{"precalculate_job_size":true}'
 ```
 
@@ -2246,32 +2248,32 @@ ascli config preset update demo_server --url=ssh://demo.asperasoft.com:33001 --u
 
 The command `set` allows setting individual options in an [Option Preset](#option-preset).
 
-```bash
+```shell
 ascli config preset set demo_server password my_password_here
 ```
 
 The command `initialize`, like `update` allows to set several options at once, but it deletes an existing configuration instead of updating it, and expects a [`Hash` Extended Value](#extended-value-syntax).
 
-```bash
+```shell
 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:
 
-```bash
+```shell
 ascli config preset over
 ```
 
 A list of [Option Preset](#option-preset) can be displayed using:
 
-```bash
+```shell
 ascli config preset list
 ```
 
 A good practice is to not manually edit the configuration file and use modification commands instead.
 If necessary, the configuration file can be opened in a text editor with:
 
-```bash
+```shell
 ascli config open
 ```
 
@@ -2280,7 +2282,7 @@ ascli config open
 
 The former format for commands is still supported:
 
-```bash
+```shell
 ascli config preset set|delete|show|initialize|update <name>
 ascli config preset over
 ascli config preset list
@@ -2289,7 +2291,7 @@ ascli config preset list
 It is possible to load an [Option Preset](#option-preset) from within another [Option Preset](#option-preset) using the `preset` option.
 For example if `pcommon` is a preset with common options, and `pspecific` is a preset with specific options, then `pspecific` can load `pcommon` using:
 
-```bash
+```shell
 ascli config preset set pspecific preset pcommon
 ```
 
@@ -2311,11 +2313,11 @@ When a plugin is invoked, the preset associated with the name of the plugin is l
 
 Operations on this preset are done using regular `config` operations:
 
-```bash
+```shell
 ascli config preset set default _plugin_name_ _default_preset_for_plugin_
 ```
 
-```bash
+```shell
 ascli config preset get default _plugin_name_
 ```
 
@@ -2340,12 +2342,12 @@ If set, it loads the options independently of the plugin used.
 > [!NOTE]
 > If no global default is set by the user, `ascli` will use `global_common_defaults` when setting global options (e.g. `config ascp use`)
 
-> [!NOTE]
+> [!TIP]
 > If you don't know the name of the global preset, you can use `GLOBAL` to refer to it.
 
 Show current default (global) Option Preset (`config` plugin):
 
-```bash
+```shell
 ascli config preset get default config
 ```
 
@@ -2355,17 +2357,17 @@ global_common_defaults
 
 Set a global parameter:
 
-```bash
+```shell
 ascli config preset set GLOBAL version_check_days 0
 ```
 
 If the default global Option Preset is not set, and you want to use a different name:
 
-```bash
+```shell
 ascli config preset set GLOBAL version_check_days 0
 ```
 
-```bash
+```shell
 ascli config preset set default config my_common_defaults
 ```
 
@@ -2515,7 +2517,7 @@ Values in the configuration also follow the [Extended Value Syntax](#extended-va
 
 Example:
 
-```bash
+```shell
 ascli config preset set my_aoc_org private_key @val:@file:"$HOME/.aspera/ascli/my_private_key"
 ```
 
@@ -2551,29 +2553,29 @@ E.g. `--xxx-yyy` on command line gives `xxx_yyy` in configuration file.
 
 The main plugin name is `config`, so it is possible to define a default [Option Preset](#option-preset) for the main plugin with:
 
-```bash
+```shell
 ascli config preset set cli_default interactive no
 ```
 
-```bash
+```shell
 ascli config preset set default config cli_default
 ```
 
 An [Option Preset](#option-preset) value can be removed with `unset`:
 
-```bash
+```shell
 ascli config preset unset cli_default interactive
 ```
 
 Example: Define options using command line:
 
-```bash
+```shell
 ascli -N --url=_url_here_ --password=my_password_here --username=_name_here_ node --show-config
 ```
 
 Example: Define options using a `Hash`:
 
-```bash
+```shell
 ascli -N --preset=@json:'{"url":"_url_here_","password":"my_password_here","username":"_name_here_"}' node --show-config
 ```
 
@@ -2601,7 +2603,7 @@ They will be added to the [Option Preset](#option-preset) created by the wizard.
 
 The simplest invocation is:
 
-```bash
+```shell
 ascli config wizard
 ```
 
@@ -2611,7 +2613,7 @@ For Faspex, Shares, Node (including ATS, Aspera Transfer Service), Console,
 only username/password and URL are required (either on command line, or from configuration file).
 Those can be usually provided on the command line:
 
-```bash
+```shell
 ascli shares repo browse / --url=https://10.25.0.6 --username=john --password=my_password_here
 ```
 
@@ -2619,7 +2621,7 @@ This can also be provisioned in a configuration file:
 
 - Build [Option Preset](#option-preset)
 
-```bash
+```shell
 ascli config preset set shares06 url https://10.25.0.6
 ascli config preset set shares06 username john
 ascli config preset set shares06 password my_password_here
@@ -2627,31 +2629,31 @@ ascli config preset set shares06 password my_password_here
 
 This can also be done with one single command:
 
-```bash
+```shell
 ascli config preset init shares06 @json:'{"url":"https://10.25.0.6","username":"john","password":"my_password_here"}'
 ```
 
 or
 
-```bash
+```shell
 ascli config preset update shares06 --url=https://10.25.0.6 --username=john --password=my_password_here
 ```
 
 - Define this [Option Preset](#option-preset) as the default [Option Preset](#option-preset) for the specified plugin (`shares`)
 
-```bash
+```shell
 ascli config preset set default shares shares06
 ```
 
 - Display the content of configuration file in table format
 
-```bash
+```shell
 ascli config preset overview
 ```
 
 - Execute a command on the **Shares** application using default options
 
-```bash
+```shell
 ascli shares repo browse /
 ```
 
@@ -2674,7 +2676,7 @@ Mandatory command line options can be requested interactively (e.g. password) us
 It is possible to use extended value `@secret:[name]` to ask for a secret interactively.
 It is also possible to enter an option as an environment variable, e.g. `ASCLI_PASSWORD` for option `password` and read the env var like this:
 
-```bash
+```shell
 read -s ASCLI_PASSWORD
 export ASCLI_PASSWORD
 ```
@@ -2694,7 +2696,7 @@ The vault is used with options `vault` and `vault_password`.
 Although it can be specified on command line, for security reason you should avoid exposing the secret.
 For example, it can be securely specified on command line like this:
 
-```bash
+```shell
 read -s ASCLI_VAULT_PASSWORD
 export ASCLI_VAULT_PASSWORD
 ```
@@ -2705,7 +2707,7 @@ export ASCLI_VAULT_PASSWORD
 
 Quick start macOS:
 
-```bash
+```shell
 brew tap hashicorp/tap
 brew install hashicorp/tap/vault
 vault server -dev -dev-root-token-id=dev-only-token
@@ -2717,7 +2719,7 @@ vault server -dev -dev-root-token-id=dev-only-token
 | `url`     | `http://127.0.0.1:8200` | The URL of the vault  |
 | `token`   | `dev-only-token`        | The token for the vault, by default uses parameter `vault_password` |
 
-```bash
+```shell
 --vault=@json:'{"type":"vault","url":"http://127.0.0.1:8200"}' --vault_password=dev-only-token
 ```
 
@@ -2733,7 +2735,7 @@ It is possible to manage secrets in macOS keychain (only read supported currentl
 | `type`    | `system` | The type of the vault |
 | `name`    | ``ascli``  | The name of the keychain to use |
 
-```bash
+```shell
 --vault=@json:'{"type":"system","name":"ascli"}'
 ```
 
@@ -2761,7 +2763,7 @@ Then secrets can be manipulated using commands:
 - `list`
 - `delete`
 
-```bash
+```shell
 ascli config vault create @json:'{"label":"mylabel","password":"my_password_here","description":"for this account"}'
 ```
 
@@ -2776,17 +2778,17 @@ The lookup is done by comparing the service URL and username (or access key).
 A password can be saved in clear in an [Option Preset](#option-preset) together with other account information (URL, username, etc...).
 Example:
 
-```bash
+```shell
 ascli config preset update myconf --url=... --username=... --password=...
 ```
 
 For a more secure storage one can do:
 
-```bash
+```shell
 ascli config preset update myconf --url=... --username=... --password=@val:@vault:myconf.password
 ```
 
-```bash
+```shell
 ascli config vault create @json:'{"label":"myconf","password":"my_password_here"}'
 ```
 
@@ -2811,7 +2813,7 @@ Set it to the desired safe location of the private key.
 Typically, located in folder `$HOME/.ssh` or `$HOME/.aspera/ascli`.
 For example:
 
-```bash
+```shell
 KEY_PAIR_PATH=~/.aspera/ascli/my_private_key
 ```
 
@@ -2827,13 +2829,13 @@ The generated key is of type `RSA`, by default: **4096** bit.
 For convenience, the public key is also extracted with extension `.pub`.
 The key is not passphrase protected.
 
-```bash
+```shell
 ascli config genkey ${KEY_PAIR_PATH} 4096
 ```
 
 To display the public key of a private key:
 
-```bash
+```shell
 ascli config pubkey @file:${KEY_PAIR_PATH}
 ```
 
@@ -2841,7 +2843,7 @@ ascli config pubkey @file:${KEY_PAIR_PATH}
 
 Both private and public keys are generated, option `-N` is for passphrase.
 
-```bash
+```shell
 ssh-keygen -t rsa -b 4096 -m PEM -N '' -f ${KEY_PAIR_PATH}
 ```
 
@@ -2849,7 +2851,7 @@ ssh-keygen -t rsa -b 4096 -m PEM -N '' -f ${KEY_PAIR_PATH}
 
 To generate a key pair with a passphrase the following can be used on any system:
 
-```bash
+```shell
 openssl genrsa -passout pass:_passphrase_here_ -out ${KEY_PAIR_PATH} 4096
 openssl rsa -pubout -in ${KEY_PAIR_PATH} -out ${KEY_PAIR_PATH}.pub
 ```
@@ -2859,14 +2861,14 @@ In that case, add option `-nodes` instead of `-passout pass:_passphrase_here_` t
 
 If option `-nodes` is not available, the passphrase can be removed using this method:
 
-```bash
+```shell
 openssl rsa -passin pass:_passphrase_here_ -in ${KEY_PAIR_PATH} -out ${KEY_PAIR_PATH}.no_des
 mv ${KEY_PAIR_PATH}.no_des ${KEY_PAIR_PATH}
 ```
 
 To change (or add) the passphrase for a key do:
 
-```bash
+```shell
 openssl rsa -des3 -in ${KEY_PAIR_PATH} -out ${KEY_PAIR_PATH}.with_des
 mv ${KEY_PAIR_PATH}.with_des ${KEY_PAIR_PATH}
 ```
@@ -2918,15 +2920,15 @@ The following options can be specified in the option `image`:
 | double     | `Bool`    | Display double text resolution (half characters) |
 | font_ratio | `Float`   | Font height/width ratio in terminal |
 
-```bash
+```shell
 ascli config image https://eudemo.asperademo.com/wallpaper.jpg --ui=text --image=@json:'{"text":true}'
 ```
 
-```bash
+```shell
 curl -so - https://eudemo.asperademo.com/wallpaper.jpg | ascli config image @stdbin:
 ```
 
-```bash
+```shell
 echo -n https://eudemo.asperademo.com/wallpaper.jpg | ascli config image @uri:@stdin:
 ```
 
@@ -2981,13 +2983,13 @@ Examples:
 
 - Display debugging log on `stdout`:
 
-```bash
+```shell
 ascli config pre over --log-level=debug --logger=stdout
 ```
 
 - Log errors to `syslog`:
 
-```bash
+```shell
 ascli config pre over --log-level=error --logger=syslog
 ```
 
@@ -3041,7 +3043,7 @@ Like any other option, those can be set either on command line, or in configurat
 
 Example:
 
-```bash
+```shell
 ascli aoc admin package list --http-options=@json:'{"read_timeout":10.0}'
 ```
 
@@ -3085,13 +3087,13 @@ E.g. `http://myproxy.org.net:3128`.
 
 Credentials for proxy are optional but can also be specified:
 
-```bash
+```shell
 export http_proxy=http://my_user_here:my_pass_here@proxy.example.com:3128
 ```
 
 Option `http_proxy` does the same (set env var) but on command line:
 
-```bash
+```shell
 ascli --http-proxy=http://my_user_here:my_pass_here@host:port ...
 ```
 
@@ -3102,14 +3104,14 @@ Note that proxy credentials are not supported in PAC files.
 To read the script from a URL (`http:`, `https:` and `file:`), use prefix: `@uri:`.
 A minimal script can be specified to define the use of a local proxy:
 
-```bash
+```shell
 ascli --fpac='function FindProxyForURL(url, host){return "PROXY localhost:3128"}' ...
 ```
 
 The result of a PAC file can be tested with command: `config proxy_check`.
 Example, using command line option:
 
-```bash
+```shell
 ascli config proxy_check --fpac='function FindProxyForURL(url, host) {return "PROXY proxy.example.com:3128;DIRECT";}' http://example.com
 ```
 
@@ -3117,7 +3119,7 @@ ascli config proxy_check --fpac='function FindProxyForURL(url, host) {return "PR
 PROXY proxy.example.com:1234;DIRECT
 ```
 
-```bash
+```shell
 ascli config proxy_check --fpac=@file:./proxy.pac http://www.example.com
 ```
 
@@ -3125,7 +3127,7 @@ ascli config proxy_check --fpac=@file:./proxy.pac http://www.example.com
 PROXY proxy.example.com:8080
 ```
 
-```bash
+```shell
 ascli config proxy_check --fpac=@uri:http://server/proxy.pac http://www.example.com
 ```
 
@@ -3135,11 +3137,11 @@ PROXY proxy.example.com:8080
 
 If the proxy found with the PAC requires credentials, then use option `proxy_credentials` with username and password provided as an `Array`:
 
-```bash
+```shell
 ascli --proxy-credentials=@json:'["__username_here__","__password_here__"]' ...
 ```
 
-```bash
+```shell
 ascli --proxy-credentials=@list::__username_here__:__password_here__ ...
 ```
 
@@ -3153,13 +3155,13 @@ To specify a FASP proxy (forward), set the [**transfer-spec**](#transfer-specifi
 
 For example, for an Aspera forward proxy not encrypted (HTTP) without authentication running on port 9091, the option would be:
 
-```bash
+```shell
 --ts=@json:'{"proxy":"dnat://proxy.example.org:9091"}'
 ```
 
 Or, alternatively, (prefer transfer spec like above, generally):
 
-```bash
+```shell
 --transfer-info=@json:'{"ascp_args":["--proxy","dnat://proxy.example.org:9091"]}'
 ```
 
@@ -3188,7 +3190,7 @@ It provides the following commands for `ascp` sub-command:
 
 #### Show path of currently used `ascp`
 
-```bash
+```shell
 ascli config ascp show
 ```
 
@@ -3196,7 +3198,7 @@ ascli config ascp show
 /Users/laurent/.aspera/ascli/sdk/ascp
 ```
 
-```bash
+```shell
 ascli config ascp info
 ```
 
@@ -3219,7 +3221,7 @@ For a permanent change, the command `config ascp use` sets the same option for t
 
 Using a POSIX shell:
 
-```bash
+```shell
 ascli config ascp use @path:'~/Applications/Aspera CLI/bin/ascp'
 ```
 
@@ -3250,7 +3252,7 @@ this is equivalent to using option: `--use-product=FIRST`.
 
 Locally installed Aspera products can be listed with:
 
-```bash
+```shell
 ascli config ascp products list
 ```
 
@@ -3269,14 +3271,14 @@ Using the option `use_product` finds the `ascp` binary of the selected product.
 
 To permanently use the `ascp` of a product:
 
-```bash
+```shell
 ascli config ascp products use 'Aspera Connect'
 saved to default global preset /Users/laurent/Applications/Aspera Connect.app/Contents/Resources/ascp
 ```
 
 #### Installation of Connect Client on command line
 
-```bash
+```shell
 ascli config ascp connect list
 ```
 
@@ -3293,7 +3295,7 @@ ascli config ascp connect list
 +-----------------------------------------------+--------------------------------------+-----------+
 ```
 
-```bash
+```shell
 ascli config ascp connect version 'Aspera Connect for Mac Intel' list
 ```
 
@@ -3308,7 +3310,7 @@ ascli config ascp connect version 'Aspera Connect for Mac Intel' list
 +-------------------------------------------+--------------------------+-----------------------------------------------------------------------------------------+----------+---------------------+
 ```
 
-```bash
+```shell
 ascli config ascp connect version 'Aspera Connect for Mac Intel' download enclosure --to-folder=.
 ```
 
@@ -3374,7 +3376,7 @@ The `transfer_info` option accepts the following optional parameters to control
 In case of transfer interruption, the agent will **resume** a transfer up to `iter_max` time.
 Sleep between iterations is given by the following formula where `iter_index` is the current iteration index, starting at 0:
 
-```bash
+```shell
 max( sleep_max, sleep_initial * sleep_factor ^ iter_index )
 ```
 
@@ -3390,13 +3392,13 @@ To use `ascp`'s default, use option: `--transfer-info=@json:'{"trusted_certs":nu
 Some transfer errors are considered **retry-able** (e.g. timeout) and some other not (e.g. wrong password).
 The list of known protocol errors and retry level can be listed:
 
-```bash
+```shell
 ascli config ascp errors
 ```
 
 Examples:
 
-```bash
+```shell
 ascli ... --transfer-info=@json:'{"wss":true,"resume":{"iter_max":20}}'
 ascli ... --transfer-info=@json:'{"spawn_delay_sec":2.5,"multi_incr_udp":false}'
 ```
@@ -3404,7 +3406,7 @@ ascli ... --transfer-info=@json:'{"spawn_delay_sec":2.5,"multi_incr_udp":false}'
 This can be useful to activate logging using option `-L` of `ascp`.
 For example, to activate debug level 2 for `ascp` (`DD`), and display those logs on the terminal (`-`):
 
-```bash
+```shell
 --transfer-info=@json:'{"ascp_args":["-DDL-"]}'
 ```
 
@@ -3419,7 +3421,7 @@ In addition to standard methods described in section [File List](#list-of-files-
 
 - Using option `transfer_info` parameter `ascp_args`
 
-```bash
+```shell
 --sources=@ts --transfer-info=@json:'{"ascp_args":["--file-list","myfilelist"]}'
 ```
 
@@ -3438,7 +3440,7 @@ This agent supports a local configuration file: `aspera.conf` where Virtual link
 
 On a server (HSTS), the following commands can be used to set a global virtual link:
 
-```bash
+```shell
 asconfigurator -x 'set_trunk_data;id,1;trunk_name,in;trunk_capacity,45000;trunk_on,true'
 asconfigurator -x 'set_trunk_data;id,2;trunk_name,out;trunk_capacity,45000;trunk_on,true'
 asconfigurator -x 'set_node_data;transfer_in_bandwidth_aggregate_trunk_id,1'
@@ -3506,7 +3508,7 @@ For example, let's assume we want to replace illegal character: `|` with an unde
 
 1. First, locate the configuration file with:
 
-```bash
+```shell
 ascli conf ascp info --fields=aspera_conf
 ```
 
@@ -3585,13 +3587,13 @@ Parameters provided in option `transfer_info` are:
 
 Like any other option, `transfer_info` can get its value from a pre-configured [Option Preset](#option-preset) :
 
-```bash
+```shell
 --transfer-info=@preset:_name_here_
 ```
 
 or be specified using the extended value syntax :
 
-```bash
+```shell
 --transfer-info=@json:'{"url":"https://...","username":"_user_here_","password":"my_password_here"}'
 ```
 
@@ -3617,7 +3619,7 @@ Parameters provided in option `transfer_info` are:
 
 Example:
 
-```bash
+```shell
 ascli faspex package recv 323 --transfer=httpgw --transfer-info=@json:'{"url":"https://asperagw.example.com:9443/aspera/http-gwy"}'
 ```
 
@@ -3645,20 +3647,20 @@ Options for `transfer_info` are:
 
 For example, to use an external, already running `transferd`, use option:
 
-```bash
+```shell
 --transfer-info=@json:'{"url":":55002","start":false,"stop":false}'
 ```
 
 The gem `grpc` is not part of default dependencies, as it requires compilation of a native part.
 So, to use the Transfer Daemon you should install this gem:
 
-```bash
+```shell
 gem install grpc
 ```
 
 If the execution complains about incompatible libraries, then force recompilation of the native part:
 
-```bash
+```shell
 gem uninstall grpc
 
 gem install grpc --platform ruby
@@ -3700,7 +3702,7 @@ To remove a (deep) key from transfer spec, set the value to `null`.
 > [!NOTE]
 > Default transfer spec values can be displayed with command:
 
-```bash
+```shell
 ascli config ascp info --fields=ts --flat-hash=no
 ```
 
@@ -3726,20 +3728,20 @@ References:
 
 Parameters can be displayed with commands:
 
-```bash
+```shell
 ascli config ascp spec
 ascli config ascp spec --select=@json:'{"d":"Y"}' --fields=-d,n,c
 ```
 
 A JSON Schema can be generated with command:
 
-```bash
+```shell
 ascli config ascp schema --format=jsonpp
 ```
 
 An optional parameter can be specified to display the schema for a specific transfer agent:
 
-```bash
+```shell
 ascli config ascp schema transferd --format=jsonpp
 ```
 
@@ -3878,19 +3880,19 @@ Possible values for option `sources` are:
 So, by default, the list of files to transfer will be simply specified on the command line.
 Example:
 
-  ```bash
+  ```shell
   ascli server upload ~/first.file secondfile
   ```
 
   This is the same as (with default values):
 
-  ```bash
+  ```shell
   ascli server upload --sources=@args --src-type=list ~/mysample.file secondfile
   ```
 
 - An [Extended Value](#extended-value-syntax) with type **Array of String**
 
-> [!NOTE]
+> [!TIP]
 > Extended values can be tested with the command `config echo`
 
   Examples:
@@ -3899,7 +3901,7 @@ Example:
 
     Create the file list:
 
-    ```bash
+    ```shell
     echo ~/mysample.file > myfilelist.txt
     echo secondfile >> myfilelist.txt
     ```
@@ -3912,13 +3914,13 @@ Example:
 
 - Using JSON array
 
-    ```bash
+    ```shell
     --sources=@json:'["file1","file2"]'
     ```
 
 - Using STDIN, one path per line
 
-    ```bash
+    ```shell
     --sources=@lines:@stdin:
     ```
 
@@ -3933,7 +3935,7 @@ Examples:
 
   - Using transfer spec
 
-  ```bash
+  ```shell
   --sources=@ts --ts=@json:'{"paths":[{"source":"file1"},{"source":"file2"}]}'
   ```
 
@@ -3949,7 +3951,7 @@ Supported values for `src_type` are:
 
 Example: Source file `200KB.1` is renamed `sample1` on destination:
 
-```bash
+```shell
 ascli server upload --src-type=pair ~/Documents/Samples/200KB.1 /Upload/sample1
 ```
 
@@ -4020,7 +4022,7 @@ Multi session, i.e. starting a transfer of a file set using multiple sessions (o
 
 - `--transfer=node`
 
-```bash
+```shell
 --ts=@json:'{"multi_session":10,"multi_session_threshold":1}'
 ```
 
@@ -4028,7 +4030,7 @@ Multi-session is directly supported by the node daemon.
 
 - `--transfer=direct`
 
-```bash
+```shell
 --ts=@json:'{"multi_session":5,"multi_session_threshold":1,"resume_policy":"none"}'
 ```
 
@@ -4051,7 +4053,7 @@ Activating CSEAR consists in using transfer spec parameters:
 
 Example: parameter to download a Faspex package and decrypt on the fly
 
-```bash
+```shell
 --ts=@json:'{"content_protection":"decrypt","content_protection_password":"my_password_here"}'
 ```
 
@@ -4059,25 +4061,25 @@ Example: parameter to download a Faspex package and decrypt on the fly
 
 - Change target rate
 
-```bash
+```shell
 --ts=@json:'{"target_rate_kbps":500000}'
 ```
 
 - Override the FASP SSH port to a specific TCP port:
 
-```bash
+```shell
 --ts=@json:'{"ssh_port":33002}'
 ```
 
 - Force HTTP fallback mode:
 
-```bash
+```shell
 --ts=@json:'{"http_fallback":"force"}'
 ```
 
 - Activate progress when not activated by default on server
 
-```bash
+```shell
 --ts=@json:'{"precalculate_job_size":true}'
 ```
 
@@ -4112,7 +4114,7 @@ Linux also provides `anacron`, if tasks are hourly or daily.
 
 For example, on Linux it is convenient to create a wrapping script, e.g. `cron_ascli` that will set up the environment (e.g. Ruby) to properly start `ascli`:
 
-```bash
+```shell
 #!/bin/bash
 # load the Ruby environment
 . /etc/profile.d/rvm.sh
@@ -4125,7 +4127,7 @@ exec timeout ${tmout} ascli "${@}"
 
 Example of cronjob created for user `xfer`.
 
-```bash
+```shell
 crontab<<EOF
 0    * * * *  /home/xfer/cron_ascli preview scan --logger=syslog --display=error
 2-59 * * * *  /home/xfer/cron_ascli preview trev --logger=syslog --display=error
@@ -4147,7 +4149,7 @@ Let's give a base name for our service: `my_ascli_svc`
 
 The startup script can be simply the `ascli` command line, for example: `/usr/local/bin/start_my_ascli_svc.sh`:
 
-```bash
+```shell
 #!/bin/bash
 set -e
 echo "Starting my_ascli_svc at $(date)"
@@ -4157,7 +4159,7 @@ exec ascli .....
 
 And make this script executable:
 
-```bash
+```shell
 chmod a+x /usr/local/bin/start_my_ascli_svc.sh
 ```
 
@@ -4185,7 +4187,7 @@ WantedBy=multi-user.target
 
 Then enable and start with:
 
-```bash
+```shell
 sudo systemctl daemon-reload
 sudo systemctl enable --now my_ascli_svc.service
 systemctl status my_ascli_svc.service
@@ -4207,7 +4209,7 @@ Usually the OS native scheduler already provides some sort of protection against
 - The Windows scheduler does this by default
 - Linux `cron` can leverage the utility [`flock`](https://man.cx/flock%281%29) to do the same:
 
-```bash
+```shell
 /usr/bin/flock -w 0 /var/cron.lock ascli ...
 ```
 
@@ -4220,13 +4222,13 @@ Testing `ascli` locking:
 
 Run this same command in two separate terminals within less than 30 seconds:
 
-```bash
+```shell
 ascli config echo @ruby:'sleep(30)' --lock-port=12345
 ```
 
 The first instance will sleep 30 seconds, the second one will immediately exit like this:
 
-```bash
+```shell
 WARN -- : Another instance is already running (Address already in use - bind(2) for "127.0.0.1" port 12345).
 ```
 
@@ -4238,7 +4240,7 @@ Several **PVCL** adapters are available, one is embedded in `ascp`, the others a
 
 The list of supported **PVCL** adapters can be retrieved with command:
 
-```bash
+```shell
 ascli config ascp info --fields=@re:'^pvcl'
 ```
 
@@ -4259,7 +4261,7 @@ They act as a **pseudo drive**.
 
 The simplified format is:
 
-```bash
+```shell
 <adapter>:///<sub file path>?<arg1>=<val1>&...
 ```
 
@@ -4276,7 +4278,7 @@ To discard data at the destination, the destination argument is set to `faux://`
 
 To send uninitialized data in place of an actual source file, the source file is replaced with an argument of the form:
 
-```bash
+```shell
 faux:///filename?filesize
 ```
 
@@ -4295,7 +4297,7 @@ Very large `faux` file sizes (petabyte range and above) will likely fail due to
 
 To send uninitialized data in place of a source directory, the source argument is replaced with an argument of the form:
 
-```bash
+```shell
 faux:///dirname?<arg1>=<val1>&...
 ```
 
@@ -4336,25 +4338,25 @@ Examples:
 
 - Upload 20 gibibyte of random data to file `myfile` to directory /Upload
 
-```bash
+```shell
 ascli server upload faux:///myfile\?20g --to-folder=/Upload
 ```
 
 - Upload a file /tmp/sample but do not save results to disk (no docroot on destination)
 
-```bash
+```shell
 ascli server upload /tmp/sample --to-folder=faux://
 ```
 
 - Upload a faux directory `mydir` containing 1 million files, sequentially with sizes ranging from 0 to 2 Mebibyte - 2 bytes, with the base name of each file being `testfile` to /Upload
 
-```bash
+```shell
 ascli server upload "faux:///mydir?file=testfile&count=1m&size=0&inc=2&seq=sequential" --to-folder=/Upload
 ```
 
 - Upload a faux directory `mydir` containing 1000 files, of size 1 byte, with the base name of each file being `testfile` to /Upload
 
-```bash
+```shell
 ascli server upload "faux:///mydir?file=testfile&count=1000&size=1" --to-folder=/Upload
 ```
 
@@ -4363,7 +4365,7 @@ ascli server upload "faux:///mydir?file=testfile&count=1000&size=1" --to-folder=
 ```text
 ascli -h
 NAME
-        ascli -- a command line tool for Aspera Applications (v4.24.0)
+        ascli -- a command line tool for Aspera Applications (v4.24.1)
 
 SYNOPSIS
         ascli COMMANDS [OPTIONS] [ARGS]
@@ -4690,7 +4692,7 @@ For instance, the plugin `faspex` allows operations on **Aspera Faspex**.
 
 Available plugins can be found using command:
 
-```bash
+```shell
 ascli config plugin list
 ```
 
@@ -4712,13 +4714,13 @@ Aspera on Cloud and Faspex 5 rely on OAuth.
 
 By default, plugins are looked-up in folders specified by (multi-value) option `plugin_folder`:
 
-```bash
+```shell
 ascli --show-config --fields=plugin_folder
 ```
 
 You can create the skeleton of a new plugin like this:
 
-```bash
+```shell
 ascli config plugin create foo .
 ```
 
@@ -4726,7 +4728,7 @@ ascli config plugin create foo .
 Created ./foo.rb
 ```
 
-```bash
+```shell
 ascli --plugin-folder=. foo
 ```
 
@@ -4785,7 +4787,7 @@ For this, specify the option: `--use-generic-client=no`.
 
 If you already know the application, and want to limit the detection to it, provide URL and plugin name:
 
-```bash
+```shell
 ascli config wizard _your_instance_ aoc
 ```
 
@@ -4795,7 +4797,7 @@ ascli config wizard _your_instance_ aoc
 After successful completion of the wizard, a new configuration preset is created, and set as default for the `aoc` plugin.
 This can be verified with command:
 
-```bash
+```shell
 ascli config preset over
 ```
 
@@ -4857,7 +4859,7 @@ If you did not use the wizard, you can also manually create an [Option Preset](#
 
 Let's create an [Option Preset](#option-preset) called: `my_aoc_org` using `ask` for interactive input (client info from previous step):
 
-```bash
+```shell
 ascli config preset ask my_aoc_org url client_id client_secret
 option: url> https://_your_instance_.ibmaspera.com/
 option: client_id> my_client_id_here
@@ -4872,7 +4874,7 @@ updated: my_aoc_org
 
 Define this [Option Preset](#option-preset) as default configuration for the `aspera` plugin:
 
-```bash
+```shell
 ascli config preset set default aoc my_aoc_org
 ```
 
@@ -4904,7 +4906,7 @@ This can be done in two manners:
 
 - Using command line
 
-```bash
+```shell
 ascli aoc admin client list
 ```
 
@@ -4920,7 +4922,7 @@ Items: 4/4
 ╰────────────┴─────────────────────╯
 ```
 
-```bash
+```shell
 ascli aoc admin client modify my_BJbQiFw @json:'{"jwt_grant_enabled":true,"explicit_authorization_required":false}'
 ```
 
@@ -4946,7 +4948,7 @@ Open the previously generated public key located here: `$HOME/.aspera/ascli/my_p
 
 ##### Using command line
 
-```bash
+```shell
 ascli aoc admin user list
 ```
 
@@ -4968,7 +4970,7 @@ ascli aoc user profile modify @ruby:'{"public_key"=>File.read(File.expand_path("
 modified
 ```
 
-> [!NOTE]
+> [!TIP]
 > The `aspera user info show` command can be used to verify modifications.
 
 #### [Option Preset](#option-preset) modification for JWT
@@ -4981,7 +4983,7 @@ To activate default use of JWT authentication for `ascli` using the [Option Pres
 
 Execute:
 
-```bash
+```shell
 ascli config preset update my_aoc_org --auth=jwt --private-key=@val:@file:~/.aspera/ascli/my_private_key --username=someuser@example.com
 ```
 
@@ -5010,7 +5012,7 @@ In that case, it is possible to list those shared folder by using a value for op
 
 Once client has been registered and [Option Preset](#option-preset) created: `ascli` can be used:
 
-```bash
+```shell
 ascli aoc files br /
 ```
 
@@ -5026,17 +5028,17 @@ This can be useful when a command is not yet available.
 
 Example:
 
-```bash
+```shell
 curl -s -H "Authorization: $(ascli aoc bearer_token)" 'https://api.ibmaspera.com/api/v1/group_memberships?embed[]=dropbox&embed[]=workspace'|jq -r '.[]|(.workspace.name + " -> " + .dropbox.name)'
 ```
 
 It is also possible to get the bearer token for node, as user or as admin using:
 
-```bash
+```shell
 ascli aoc files bearer_token_node /
 ```
 
-```bash
+```shell
 ascli aoc admin node v4 1234 --secret=_ak_secret_here_ bearer_token_node /
 ```
 
@@ -5081,25 +5083,25 @@ Examples:
 
 - List users with `laurent` in name:
 
-```bash
+```shell
 ascli aoc admin user list --query=@json:'{"q":"laurent"}'
 ```
 
 - List users who logged-in before a date:
 
-```bash
+```shell
 ascli aoc admin user list --query=@json:'{"q":"last_login_at:<2018-05-28"}'
 ```
 
 - List external users and sort in reverse alphabetical order using name:
 
-```bash
+```shell
 ascli aoc admin user list --query=@json:'{"member_of_any_workspace":false,"sort":"-name"}'
 ```
 
 Refer to the AoC API for full list of query parameters, or use the browser in developer mode with the web UI.
 
-> [!NOTE]
+> [!TIP]
 > The option `select` can also be used to further refine selection, refer to [section earlier](#option-select).
 
 #### Selecting a resource
@@ -5117,7 +5119,7 @@ To execute an action on a specific resource, select it using one of those method
 
 New resources (users, groups, workspaces, etc...) can be created using a command like:
 
-```bash
+```shell
 ascli aoc admin create <resource type> @json:'{<...parameters...>}'
 ```
 
@@ -5126,7 +5128,7 @@ Sadly, not all.
 
 Nevertheless, it is possible to guess the structure of the creation value by simply dumping an existing resource, and use the same parameters for the creation.
 
-```bash
+```shell
 ascli aoc admin group show 12345 --format=json
 ```
 
@@ -5138,7 +5140,7 @@ Remove the parameters that are either obviously added by the system: `id`, `crea
 
 And then craft your command:
 
-```bash
+```shell
 ascli aoc admin group create @json:'{"wrong":"param"}'
 ```
 
@@ -5162,7 +5164,7 @@ In order to access some administrative actions on **nodes** (in fact, access key
 The secret is provided using the `secret` option.
 For example in a command like:
 
-```bash
+```shell
 ascli aoc admin node 123 --secret="my_secret_here" v3 info
 ```
 
@@ -5172,7 +5174,7 @@ It is also possible to store secrets in the [secret vault](#secret-vault) and th
 
 The activity app can be queried with:
 
-```bash
+```shell
 ascli aoc admin analytics transfers
 ```
 
@@ -5199,7 +5201,7 @@ The environment provided contains the following additional variable:
 
 Example:
 
-```bash
+```shell
 ascli aoc admin analytics transfers --once-only=yes --lock-port=12345 --query=@json:'{"status":"completed","direction":"receive"}' --notify-to=active --notify-template=@file:mytemplate.erb
 ```
 
@@ -5233,7 +5235,7 @@ To list the target folder content, add a `/` at the end of the path.
 
 Example:
 
-```bash
+```shell
 ascli aoc files br the_link
 ```
 
@@ -5246,7 +5248,7 @@ Current Workspace: Default (default)
 +------------+------+----------------+------+----------------------+--------------+
 ```
 
-```bash
+```shell
 ascli aoc files br the_link/
 ```
 
@@ -5261,7 +5263,7 @@ Current Workspace: Default (default)
 
 #### Example: Bulk creation of users
 
-```bash
+```shell
 ascli aoc admin user create --bulk=yes @json:'[{"email":"dummyuser1@example.com"},{"email":"dummyuser2@example.com"}]'
 ```
 
@@ -5276,7 +5278,7 @@ ascli aoc admin user create --bulk=yes @json:'[{"email":"dummyuser1@example.com"
 
 #### Example: Find with filter and delete
 
-```bash
+```shell
 ascli aoc admin user list --query='@json:{"q":"dummyuser"}' --fields=id,email
 ```
 
@@ -5289,7 +5291,7 @@ ascli aoc admin user list --query='@json:{"q":"dummyuser"}' --fields=id,email
 +-------+------------------------+
 ```
 
-```bash
+```shell
 ascli aoc admin user list --query='@json:{"q":"dummyuser"}' --fields=id --display=data --format=csv | ascli aoc admin user delete @lines:@stdin: --bulk=yes
 ```
 
@@ -5312,7 +5314,7 @@ To delete them use the same method as before
 
 #### Example: Display current user's workspaces
 
-```bash
+```shell
 ascli aoc user workspaces list
 ```
 
@@ -5330,13 +5332,13 @@ ascli aoc user workspaces list
 
 Creation of a sub-access key is like creation of access key with the following difference: authentication to Node API is made with access key (master access key) and only the path parameter is provided: it is relative to the storage root of the master key. (id and secret are optional)
 
-```bash
+```shell
 ascli aoc admin resource node --name=_node_name_ --secret=_secret_ v4 access_key create @json:'{"storage":{"path":"/folder1"}}'
 ```
 
 #### Example: Display transfer events (ops/transfer)
 
-```bash
+```shell
 ascli aoc admin node --secret=_secret_ v3 transfer list --query=@json:'[["q","*"],["count",5]]'
 ```
 
@@ -5352,13 +5354,13 @@ Examples of query:
 
 #### Example: Display node events (events)
 
-```bash
+```shell
 ascli aoc admin node --secret=_secret_ v3 events
 ```
 
 #### Example: Display members of a workspace
 
-```bash
+```shell
 ascli aoc admin workspace_membership list --fields=member_type,manager,member.email --query=@json:'{"embed":"member","inherited":false,"workspace_id":11363,"sort":"name"}'
 ```
 
@@ -5385,45 +5387,45 @@ Other query parameters:
 
 a- Get ID of first workspace
 
-```bash
+```shell
 WS1='First Workspace'
 WS1ID=$(ascli aoc admin workspace list --query=@json:'{"q":"'"$WS1"'"}' --select=@json:'{"name":"'"$WS1"'"}' --fields=id --format=csv)
 ```
 
 b- Get ID of second workspace
 
-```bash
+```shell
 WS2='Second Workspace'
 WS2ID=$(ascli aoc admin workspace list --query=@json:'{"q":"'"$WS2"'"}' --select=@json:'{"name":"'"$WS2"'"}' --fields=id --format=csv)
 ```
 
 c- Extract membership information
 
-```bash
+```shell
 ascli aoc admin workspace_membership list --fields=manager,member_id,member_type,workspace_id --query=@json:'{"workspace_id":'"$WS1ID"'}' --format=jsonpp --output=ws1_members.json
 ```
 
 d- Convert to creation data for second workspace:
 
-```bash
+```shell
 grep -Eve '(direct|effective_manager|_count|storage|"id")' ws1_members.json|sed '/workspace_id/ s/"'"$WS1ID"'"/"'"$WS2ID"'"/g' > ws2_members.json
 ```
 
 or, using `jq`:
 
-```bash
+```shell
 jq '[.[] | {member_type,member_id,workspace_id,manager,workspace_id:"'"$WS2ID"'"}]' ws1_members.json > ws2_members.json
 ```
 
 e- Add members to second workspace
 
-```bash
+```shell
 ascli aoc admin workspace_membership create --bulk=yes @json:@file:ws2_members.json
 ```
 
 #### Example: Get users who did not log since a date
 
-```bash
+```shell
 ascli aoc admin user list --fields=email --query=@json:'{"q":"last_login_at:<2018-05-28"}'
 ```
 
@@ -5438,7 +5440,7 @@ ascli aoc admin user list --fields=email --query=@json:'{"q":"last_login_at:<201
 
 #### Example: List **Limited** users
 
-```bash
+```shell
 ascli aoc admin user list --fields=email --select=@json:'{"member_of_any_workspace":false}'
 ```
 
@@ -5446,7 +5448,7 @@ ascli aoc admin user list --fields=email --select=@json:'{"member_of_any_workspa
 
 - Create the group and take note of `id`
 
-```bash
+```shell
 ascli aoc admin group create @json:'{"name":"group 1","description":"my super group"}'
 ```
 
@@ -5454,7 +5456,7 @@ Group: `11111`
 
 - Get the workspace ID
 
-```bash
+```shell
 ascli aoc admin workspace list --query=@json:'{"q":"myworkspace"}' --fields=id --format=csv --display=data
 ```
 
@@ -5462,13 +5464,13 @@ Workspace: 22222
 
 - Add group to workspace
 
-```bash
+```shell
 ascli aoc admin workspace_membership create @json:'{"workspace_id":22222,"member_type":"user","member_id":11111}'
 ```
 
 - Get a user's ID
 
-```bash
+```shell
 ascli aoc admin user list --query=@json:'{"q":"manu.macron@example.com"}' --fields=id --format=csv --display=data
 ```
 
@@ -5476,7 +5478,7 @@ User: 33333
 
 - Add user to group
 
-```bash
+```shell
 ascli aoc admin group_membership create @json:'{"group_id":11111,"member_type":"user","member_id":33333}'
 ```
 
@@ -5486,7 +5488,7 @@ In this example, a user has access to a workspace where two shared folders are l
 
 First, set up the environment (skip if already done)
 
-```bash
+```shell
 ascli config wizard --url=https://sedemo.ibmaspera.com --username=someuser@example.com
 ```
 
@@ -5518,7 +5520,7 @@ Then, create two shared folders located in two regions, in your files home, in a
 
 Then, transfer between those:
 
-```bash
+```shell
 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}'
 ```
 
@@ -5526,13 +5528,13 @@ ascli -Paoc_show aoc files transfer --from-folder='IBM Cloud SJ' --to-folder='AW
 
 The following command will create and display a secret token to register a self-managed Aspera Transfer Server:
 
-```bash
+```shell
 ascli aoc admin client_registration_token create @json:'{"data":{"name":"laurentnode","client_subject_scopes":["alee","aejd"],"client_subject_enabled":true}}' --fields=token --show-secrets=yes
 ```
 
 #### Example: Delete all registration keys
 
-```bash
+```shell
 ascli aoc admin client_registration_token list --fields=id --format=csv|ascli aoc admin client_registration_token delete @lines:@stdin: --bulk=yes
 ```
 
@@ -5566,7 +5568,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-access-key-creation-parameters) for more details and examples.
 
-  ```bash
+  ```shell
   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":"/"}}'
   ```
 
@@ -5580,13 +5582,13 @@ So, for example, the creation of a node using ATS in IBM Cloud looks like (see o
 
   First, Retrieve the ATS node address
 
-  ```bash
+  ```shell
   ascli aoc admin ats cluster show --cloud=softlayer --region=eu-de --fields=transfer_setup_url --format=csv
   ```
 
   Then use the returned address for the `url` key to actually create the AoC Node entity:
 
-  ```bash
+  ```shell
   ascli aoc admin 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"}'
   ```
 
@@ -5606,7 +5608,7 @@ The web-mail-like application.
 
 General syntax:
 
-```bash
+```shell
 ascli aoc packages send [package extended value] [other parameters such as options and file list]
 ```
 
@@ -5615,7 +5617,7 @@ Refer to the AoC package creation API, or display an existing package in JSON to
 
 List allowed shared inbox destinations with:
 
-```bash
+```shell
 ascli aoc packages shared_inboxes list
 ```
 
@@ -5633,19 +5635,19 @@ If a user recipient (email) is not already registered and the workspace allows e
 
 ##### Example: Send a package with one file to two users, using their email
 
-```bash
+```shell
 ascli aoc packages send @json:'{"name":"my title","note":"my note","recipients":["someuser@example.com","other@example.com"]}' my_file.dat
 ```
 
 ##### Example: Send a package to a shared inbox with metadata
 
-```bash
+```shell
 ascli aoc packages send --workspace="my ws" @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:
 
-```bash
+```shell
 ascli aoc packages send --workspace="my ws" @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
 ```
 
@@ -5653,7 +5655,7 @@ ascli aoc packages send --workspace="my ws" @json:'{"name":"my pack title","reci
 
 Find files in Files app:
 
-```bash
+```shell
 ascli aoc files browse /src_folder
 ```
 
@@ -5670,7 +5672,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
+```shell
 ascli aoc files node_info /src_folder --format=json --display=data | ascli aoc packages send @json:'{"name":"test","recipients":["someuser@example.com"]}' 10M.dat --transfer=node --transfer-info=@json:@stdin:
 ```
 
@@ -5678,7 +5680,7 @@ ascli aoc files node_info /src_folder --format=json --display=data | ascli aoc p
 
 The command to receive one or multiple packages is:
 
-```bash
+```shell
 ascli aoc packages recv <package id> [<file> ...]
 ```
 
@@ -5724,7 +5726,7 @@ Examples:
 
 ##### Example: Receive all packages from a given shared inbox
 
-```bash
+```shell
 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}'
 ```
 
@@ -5734,7 +5736,7 @@ To list packages that would be downloaded, without actually downloading them, re
 
 It is possible to automatically download new packages, like using Aspera Cargo:
 
-```bash
+```shell
 ascli aoc packages recv ALL --once-only=yes --lock-port=12345
 ```
 
@@ -5750,7 +5752,7 @@ Some `node` operations are available for a package, such as `browse` and `find`.
 
 To list the content of a package, use command `packages browse <package id> <folder>`:
 
-```bash
+```shell
 ascli aoc package browse my5CnbeWng /
 ```
 
@@ -5758,7 +5760,7 @@ Use command `find` to list recursively.
 
 For advanced users, it's also possible to pipe node information for the package and use node operations:
 
-```bash
+```shell
 ascli aoc package node_info <package ID here> / --format=json --show-secrets=yes --display=data | ascli node -N --preset=@json:@stdin: access_key do self browse /
 ```
 
@@ -5792,22 +5794,22 @@ Additional parameters can be specified, as supported by the API (to find out ava
 The current workspace is added unless specified in the query.
 
 > [!NOTE]
-> By default, `exclude_dropbox_packages` is set to `true` for user packages, and to false for shared inbox packages.
+> By default, `exclude_dropbox_packages` is set to `true` for user packages, and to `false` for shared inbox packages.
 > This can be overridden in the query.
 
 Using shared inbox name:
 
-```bash
+```shell
 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
+```shell
 shared_box_id=$(ascli aoc packages shared_inboxes show --name='My Shared Inbox' --format=csv --display=data --fields=id)
 ```
 
-```bash
+```shell
 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"}'
 ```
 
@@ -5823,7 +5825,7 @@ Files located here are either user's files, or shared folders.
 
 The general download command is:
 
-```bash
+```shell
 ascli aoc files download <source folder path> <source filename 1> ...
 ```
 
@@ -5831,7 +5833,7 @@ I.e. the first argument is the source folder, and the following arguments are th
 
 If a single file or folder is to be downloaded, then a single argument can be provided.
 
-```bash
+```shell
 ascli aoc files download <single file path>
 ```
 
@@ -5883,41 +5885,41 @@ In order to share a folder with a different, special tags are set, but this is c
 
 Personal shared folders, created by users in a workspace follow the syntax:
 
-```bash
+```shell
 ascli aoc files permission --workspace=<workspace name> <path to folder> ...
 ```
 
 > [!NOTE]
 > The workspace is identified by name, and folder by path, relative to the user's home.
-To use an identifier instead, one can use the percent selector, like `%id:1234`
+> To use an identifier instead, one can use the percent selector, like `%id:1234`
 
 ##### Admin Shared Folders
 
 Admin shared folders, created by administrators in a workspace follow the syntax:
 
-```bash
+```shell
 ascli aoc admin node do <node ID> permission --workspace=<workspace name> <path to folder>
 ```
 
-> [!NOTE]
+> [!TIP]
 > The node is identified by identifier.
-To use an name instead, one can use the percent selector, like `%name:"my node"`
+> To use an name instead, one can use the percent selector, like `%name:"my node"`
 
 ##### Example: List permissions on a shared folder
 
-```bash
+```shell
 ascli aoc files permission /shared_folder_test1 list
 ```
 
 ##### Example: Share a personal folder with other users
 
-```bash
+```shell
 ascli aoc files permission /shared_folder_test1 create @json:'{"with":"laurent"}'
 ```
 
 ##### Example: Revoke shared access
 
-```bash
+```shell
 ascli aoc files permission /shared_folder_test1 delete 6161
 ```
 
@@ -5925,7 +5927,7 @@ ascli aoc files permission /shared_folder_test1 delete 6161
 
 They can be managed with commands:
 
-```bash
+```shell
 ascli aoc files short_link <path to folder> private create
 ascli aoc files short_link <path to folder> private list
 ascli aoc files short_link <path to folder> public list
@@ -5960,19 +5962,19 @@ First, identify the node ID where the shared folder will be created.
 
 To get the node ID of the default node for workspace `my ws`, use the command:
 
-```bash
+```shell
 ascli aoc admin workspace show %name:'my ws' --fields=node_id
 ```
 
 Alternatively (longer):
 
-```bash
+```shell
 ascli aoc admin workspace list --select=@json:'{"name":"my ws"}' --fields=node_id
 ```
 
 Or select a node identifier manually from the list of nodes:
 
-```bash
+```shell
 ascli aoc admin node list --fields=id,name
 ```
 
@@ -5986,7 +5988,7 @@ The node can also be conveniently identified using the **percent selector** inst
 
 If the shared folder does not exist, then create it:
 
-```bash
+```shell
 ascli aoc admin node do 1234 mkdir /folder_on_node
 ```
 
@@ -5994,7 +5996,7 @@ Create the shared folder in workspace `my ws` (set `with` to empty string, or do
 Optionally use `as` to set the name of the shared folder if different from the folder name on the node.
 For other options, refer to the previous section on shared folders.
 
-```bash
+```shell
 ascli aoc admin node do 1234 permission /folder_on_node create @json:'{"with":"","as":"folder_for_users"}' --workspace="my ws"
 ```
 
@@ -6005,15 +6007,15 @@ To share with a user, group, or workspace, use the `with` parameter with the nam
 The `"with"` parameter will perform a lookup, and set fields `access_type` and `access_id` accordingly.
 The native fields `access_type` and `access_id` can also be used, instead of `with`.
 
-```bash
+```shell
 ascli aoc admin node do 1234 permission /folder_on_node create @json:'{"with":"john@example.com","as":"folder_for_one_user"}' --workspace="my ws"
 ```
 
-```bash
+```shell
 ascli aoc admin node do 1234 permission /folder_on_node create @json:'{"with":"group 1","as":"folder_for_a_group"}' --workspace="my ws"
 ```
 
-```bash
+```shell
 ascli aoc admin node do 1234 permission /folder_on_node create @json:'{"with":"my ws","as":"folder_for_all_workspace"}' --workspace="my ws"
 ```
 
@@ -6034,7 +6036,7 @@ Procedure to send a file from org1 to org2:
 - Check that access works and locate the destination folder `mydestfolder`
 - Execute the following:
 
-```bash
+```shell
 ascli -Porg1 aoc files node_info /mydestfolder --format=json --display=data | ascli -Porg2 aoc files upload mysourcefile --transfer=node --transfer-info=@json:@stdin:
 ```
 
@@ -6058,7 +6060,7 @@ The command `aoc files find` allows searching for files in a given workspace.
 
 It works also on `node` resource using the `v4` command:
 
-```bash
+```shell
 ascli aoc admin node --name='my node name' --secret='my_secret_here' v4 find ...
 ```
 
@@ -6148,6 +6150,7 @@ files find /
 files find / '\.partial$'
 files find / @ruby:'->(f){f["type"].eql?("file")}'
 files mkdir /testsrc
+files modify /some_folder @json:'{"mount_point":false}'
 files modify my_test_folder
 files permission my_test_folder list
 files rename /some_folder testdst
@@ -6217,7 +6220,7 @@ If you are using ATS as part of AoC, then authentication is through AoC, not IBM
 First get your IBM Cloud API key.
 For instance, it can be created using the IBM Cloud web interface, or using command line:
 
-```bash
+```shell
 ibmcloud iam api-key-create mykeyname -d 'my sample key'
 ```
 
@@ -6246,15 +6249,15 @@ References:
 Then, to register the key by default for the `ats` plugin, create a preset.
 Execute:
 
-```bash
+```shell
 ascli config preset update my_ibm_ats --ibm-api-key=my_secret_api_key_here
 ```
 
-```bash
+```shell
 ascli config preset set default ats my_ibm_ats
 ```
 
-```bash
+```shell
 ascli ats api_key instances
 ```
 
@@ -6266,11 +6269,11 @@ ascli ats api_key instances
 +--------------------------------------+
 ```
 
-```bash
+```shell
 ascli config preset update my_ibm_ats --instance=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee
 ```
 
-```bash
+```shell
 ascli ats api_key create
 ```
 
@@ -6293,19 +6296,19 @@ Those are directly the parameters expected by the [ATS API](https://developer.ib
 
 Example: create access key on IBM Cloud (Softlayer):
 
-```bash
+```shell
 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:
 
-```bash
+```shell
 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:
 
-```bash
+```shell
 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":"/"}}'
 ```
 
@@ -6314,13 +6317,13 @@ ascli ats access_key create --cloud=azure --region=eastus --params=@json:'{"id":
 
 Example: create access key on Azure:
 
-```bash
+```shell
 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:
 
-```bash
+```shell
 ascli ats access_key list --field=id --format=csv | ascli ats access_key delete @lines:@stdin: --bulk=yes
 ```
 
@@ -6361,11 +6364,11 @@ The URL to be provided with option `url` shall be like `ssh://_server_address_:3
 
 Typically:
 
-```bash
+```shell
 ascli server --url=ssh://hsts.example.com:33001 --username=john --password=_something_here_ ...
 ```
 
-```bash
+```shell
 ascli server --url=ssh://hsts.example.com:33001 --username=john --ssh-keys=~/.ssh/id_rsa ...
 ```
 
@@ -6419,19 +6422,20 @@ If neither SSH password nor key is provided and a transfer token is provided in
 
 Example:
 
-```bash
+```shell
 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.
+> 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.
 
 The value of the `ssh_keys` option can be a single value or an `Array`.
 Each value is a **path** to a private key and is expanded (`~` is replaced with the user's home folder).
 
 Examples:
 
-```bash
+```shell
 ascli server --ssh-keys=~/.ssh/id_rsa
 ascli server --ssh-keys=@list:,~/.ssh/id_rsa
 ascli server --ssh-keys=@json:'["~/.ssh/id_rsa"]'
@@ -6451,13 +6455,13 @@ By default, the SSH library will check if a local `ssh-agent` is running.
 
 On Linux, if you get an error message such as:
 
-```bash
+```shell
 ERROR -- net.ssh.authentication.agent: could not connect to ssh-agent: Agent not configured
 ```
 
 or on Windows:
 
-```bash
+```shell
 ERROR -- net.ssh.authentication.agent: could not connect to ssh-agent: pageant process not running
 ```
 
@@ -6469,11 +6473,11 @@ This means that your environment suggests using an agent, but you don't have suc
 - [Check the Ruby SSH options in start method](https://github.com/net-ssh/net-ssh/blob/master/lib/net/ssh.rb)
 - To disable the use of `ssh-agent`, use the option `ssh_options` like this:
 
-```bash
+```shell
 ascli server --ssh-options=@json:'{"use_agent": false}' ...
 ```
 
-> [!NOTE]
+> [!TIP]
 > This can also be set using a preset.
 
 If one of the SSH private keys is passphrase-protected, then option `passphrase` can be used.
@@ -6495,7 +6499,7 @@ As, most of the time, SSH is used, if a `http` scheme is provided without token,
 
 One can test the `server` application using the well known demo server:
 
-```bash
+```shell
 ascli config initdemo
 ascli server browse /aspera-test-dir-large
 ascli server download /aspera-test-dir-large/200MB
@@ -6505,7 +6509,7 @@ ascli server download /aspera-test-dir-large/200MB
 
 If an SSH private key is used for authentication with a passphrase, the passphrase needs to be provided to both options: `ssh_options` (for browsing) and `ts` (for transfers):
 
-```bash
+```shell
 ascli server --url=ssh://_server_address_here_:33001 --username=_user_here_ --ssh_keys=_private_key_path_here_ --passphrase=_passphrase_here_
 ```
 
@@ -6571,23 +6575,23 @@ Examples of expressions:
 
 - Find all files and folders under `/`
 
-  ```bash
+  ```shell
   ascli node access_keys do self find
   ```
 
 - Find all text files `/Documents`
 
-  ```bash
+  ```shell
   ascli node access_keys do self find /Documents '*.txt'
   ```
 
 The following are examples of Ruby lambda code to be provided in the following template command:
 
-```bash
+```shell
  ascli node access_keys do self find / @ruby:'->(f){[code here]}'
 ```
 
-> [!NOTE]
+> [!TIP]
 > Single quotes are used here above to protect the whole **Ruby** expression from the shell.
 > Then double quotes are used for strings in the **Ruby** expression to not mix with the shell.
 
@@ -6623,12 +6627,12 @@ The following are examples of Ruby lambda code to be provided in the following t
 
 `ascli` commands can be piped in order to combine operations, such as **find and delete**:
 
-```bash
+```shell
 ascli node access_keys do self find / @ruby:'->(f){f["type"].eql?("file") and (DateTime.now-DateTime.parse(f["modified_time"]))>365}' --fields=path --format=csv | ascli node --bulk=yes delete @lines:@stdin:
 ```
 
 > [!NOTE]
-> The pipe `|` character on the last line.
+> The pipe `|` character on the last line is used to chain commands.
 
 ### Listing transfer events
 
@@ -6639,7 +6643,7 @@ If the number of transfers is too large, then the list will be retrieved using s
 
 In addition, it is possible to list "only new information" using option `once_only`.
 
-```bash
+```shell
 ascli node transfer list --once-only=yes
 ```
 
@@ -6655,7 +6659,7 @@ It allows listing transfer sessions and transferred files.
 
 Filtering can be applied:
 
-```bash
+```shell
 ascli node central file list
 ```
 
@@ -6668,12 +6672,16 @@ By providing the `validator` option, offline transfer validation can be done.
 
 There are three commands related to file synchronisation:
 
-- `sync`: Perform a local sync, by executing `async` locally.
-- `ssync` : Calls the newer `async` API on node : `/asyncs` : it can start a sync operation on the server side, and monitor only those.
-- `async`: Calls the legacy `async` API on node : `/async` : get status on sync operation on server side, like Aspera Console.
+| Command | `node` | `shares` | `aoc` | `server` | Description |
+|---------|--------|----------|-------|----------|-------------|
+| `sync`  | Yes    | Yes      | Yes   | Yes      | Perform a local sync, by executing `async` locally. |
+| `async` | Yes    |          |       |          | Uses API `/async`.<br/>Get status on sync operation on server side, like Aspera Console. |
+| `ssync` | Yes    |          |       |          | Uses API `/asyncs`.<br/>It can start a sync operation on the server side, and monitor only those. |
 
 For details on the `sync` action, refer to [IBM Aspera Sync](#ibm-aspera-sync).
 
+`async` subcommands: `show` and `delete` accept special identifier `ALL`.
+
 ### FASP Stream
 
 It is possible to start a faspstream session using the Node API:
@@ -6694,7 +6702,7 @@ Operations are:
 - Start `watchd` and `watchfolderd` services running as a system user having access to files
 - Configure a **Watchfolder** to define automated transfers
 
-```bash
+```shell
 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"}}'
@@ -6706,7 +6714,7 @@ Follow the Aspera Transfer Server configuration to activate this feature.
 
 The following command lists one file that requires validation, and assign it to the unique validator identifier provided:
 
-```bash
+```shell
 ascli node central file list --validator=ascli @json:'{"file_transfer_filter":{"max_result":1}}'
 ```
 
@@ -6720,7 +6728,7 @@ ascli node central file list --validator=ascli @json:'{"file_transfer_filter":{"
 
 To update the status of the file, use the following command:
 
-```bash
+```shell
 ascli node central file update --validator=ascli @json:'{"files":[{"session_uuid": "1a74444c-...","file_id": "084fb181-...","status": "completed"}]}'
 ```
 
@@ -6737,7 +6745,7 @@ Then create a configuration for the **SHOD** instance in the configuration file:
 Create another configuration for the Azure ATS instance: in section **node**, named `azure_ats`.
 Then execute the following command:
 
-```bash
+```shell
 ascli node download /share/sourcefile --to-folder=/destination_folder --preset=aws_shod --transfer=node --transfer-info=@preset:azure_ats
 ```
 
@@ -6750,38 +6758,39 @@ When Node API is used with an **Access key**, extra information can be retrieved
 > [!NOTE]
 > Display of preview on terminal requires installation of extra gem: `rmagick`
 
-```bash
+```shell
 dnf install -y ImageMagick-devel
 gem install rmagick rainbow
 ```
 
 For example, it is possible to display the preview of a file, if it exists, using an access key on node:
 
-```bash
+```shell
 ascli node access_key do self thumbnail /preview_samples/Aspera.mpg
 ```
 
 Previews are mainly used in AoC, this also works with AoC:
 
-```bash
+```shell
 ascli aoc files thumbnail /preview_samples/Aspera.mpg
 ```
 
-> [!NOTE]
+> [!TIP]
 > To specify the file by its file ID, use the selector syntax: `%id:_file_id_here_`
 
 > [!NOTE]
-> To force textual display of the preview on **iTerm**, prefix command with: `env -u TERM_PROGRAM -u LC_TERMINAL` or use option: ``
+> To force textual display of the preview on **iTerm**, prefix command with: `env -u TERM_PROGRAM -u LC_TERMINAL`
 
 ### Create access key
 
-```bash
+```shell
 ascli node access_key create @json:'{"id":"myaccesskey","secret":"my_secret_here","storage":{"type":"local","path":"/data/mydir"}}'
 ```
 
-> [!NOTE]
-> The `id` and `secret` are optional.
+> [!TIP]
+> The `id` and `secret` fields are optional.
 > If not provided, they will be generated and returned into the result.
+> In that case, provide option `--show-secrets=yes` to get the generated secret.
 
 Access keys support extra overriding parameters using parameter: `configuration` and sub keys `transfer` and `server`.
 For example, an access key can be modified or created with the following options:
@@ -6792,7 +6801,7 @@ For example, an access key can be modified or created with the following options
 
 The list of supported options can be displayed using command:
 
-```bash
+```shell
 ascli node info --field=@ruby:'/^access_key_configuration_capabilities.*/'
 ```
 
@@ -6856,18 +6865,19 @@ Using `ascli`, an access key can be created using the `access_key create` on the
 
 Create a private key (organization key) that will be used to sign bearer tokens:
 
-```bash
+```shell
 my_private_pem=./myorgkey.pem
 ascli config genkey $my_private_pem
 ```
 
 > [!NOTE]
-> This key is not used for authentication, it is used to sign bearer tokens.
+> This private key is not used for authentication.
+> It is used to sign bearer tokens.
 > Refer to section [private key](#private-key) for more details on generation.
 
 The corresponding public key shall be placed as an attribute of the **access key** (done with `PUT /access_keys/<id>`):
 
-```bash
+```shell
 ascli node access_key set_bearer_key self @file:$my_private_pem
 ```
 
@@ -6878,7 +6888,7 @@ ascli node access_key set_bearer_key self @file:$my_private_pem
 
 Alternatively, use the following equivalent command, as `ascli` kindly extracts the public key with extension `.pub`:
 
-```bash
+```shell
 ascli node access_key modify %id:self @ruby:'{token_verification_key: File.read("'$my_private_pem'.pub")}'
 ```
 
@@ -6886,17 +6896,16 @@ ascli node access_key modify %id:self @ruby:'{token_verification_key: File.read(
 
 - Select a folder for which we want to grant access to a user, and get its identifier:
 
-  ```bash
+  ```shell
   my_folder_id=$(ascli node access_key do self show / --fields=id)
   ```
 
 > [!NOTE]
->
 > Here we simply select `/`, but any folder can be selected in the access key storage.
 
 - Let's designate a user by its ID:
 
-  ```bash
+  ```shell
   my_user_id=777
   ```
 
@@ -6906,13 +6915,13 @@ ascli node access_key modify %id:self @ruby:'{token_verification_key: File.read(
 
 - Grant this user access to the selected folder:
 
-  ```bash
+  ```shell
   ascli node access_key do self permission %id:$my_folder_id create @json:'{"access_type":"user","access_id":"'$my_user_id'"}'
   ```
 
 - Create a Bearer token for the user:
 
-  ```bash
+  ```shell
   ascli node bearer_token @file:./myorgkey.pem @json:'{"user_id":"'$my_user_id'","_validity":3600}' --output=bearer.txt
   ```
 
@@ -6931,7 +6940,7 @@ Now, let's assume we are the user, the only information received are:
 
 Let's use it:
 
-```bash
+```shell
 ascli node -N --url=https://... --password="Bearer $(cat bearer.txt)" --root-id=$my_folder_id access_key do self br /
 ```
 
@@ -6952,6 +6961,8 @@ access_key do my_ak_name find my_test_folder
 access_key do my_ak_name find my_test_folder @re:'\.jpg$'
 access_key do my_ak_name find my_test_folder @ruby:'->(f){f["name"].end_with?(".jpg")}'
 access_key do my_ak_name mkdir /tst_nd_ak
+access_key do my_ak_name mkfile /mkfile.txt "hello world"
+access_key do my_ak_name mklink /mklink.txt --query=@json:'{"target":"/mkfile.txt","target_node_id":"123"}'
 access_key do my_ak_name node_info /
 access_key do my_ak_name rename /tst_nd_ak test_nd_ak2
 access_key do my_ak_name show %id:1
@@ -6965,16 +6976,18 @@ access_key set_bearer_key self @file:my_private_key
 access_key show %id:self
 api_details
 asperabrowser
-async bandwidth %name:my_node_sync2
-async counters %name:my_node_sync2
-async files %name:my_node_sync2
+async bandwidth %name:SYNC_NAME
+async counters %name:SYNC_NAME
+async delete ALL
+async files %name:SYNC_NAME
+async files %name:SYNC_NAME --once-only=yes
 async list
-async show %name:my_node_sync2
+async show %name:SYNC_NAME
 async show ALL
 basic_token
 bearer_token @file:my_private_key @json:'{"user_id":"666"}' --output=bearer_666
 browse / --log-level=trace2
-cat my_upload_folder/test_file.bin --to-folder=.
+cat my_upload_folder/test_file.bin
 central file list
 central file modify --validator=1 @json:'{"files":[]}'
 central session list
@@ -7007,7 +7020,7 @@ ssync stop %name:my_node_sync
 ssync summary %name:my_node_sync
 stream list
 sync admin status /data/local_sync
-sync pull /aspera-test-dir-tiny --to-folder=/data/local_sync @json:'{"name":"my_node_sync2","reset":true}'
+sync pull /aspera-test-dir-tiny --to-folder=/data/local_sync @json:'{"name":"SYNC_NAME","reset":true}'
 sync pull /aspera-test-dir-tiny --to-folder=/data/local_sync @json:'{"reset":true}'
 transfer list --once-only=yes
 transfer list --query=@json:'{"active_only":true}'
@@ -7042,13 +7055,13 @@ Identify the region and the endpoint URL will be `https://otlp-[region]-saas.ins
 
 For convenience, those parameters can be provided in a preset, e.g. named `otel_default`.
 
-```bash
+```shell
 ascli config preset init otel_default @json:'{"url":"https://otlp-orange-saas.instana.io:4318","key":"*********","interval":1.1}'
 ```
 
 Then it is invoked like this (assuming a default node is configured):
 
-```bash
+```shell
 ascli node telemetry @preset:otel_default
 ```
 
@@ -7071,12 +7084,12 @@ IBM Aspera's newer self-managed application.
 | `public_link` | Public link authentication (set when option `url` is a public link) |
 | `boot`        | Use authentication token copied from browser (experimental)         |
 
-> [!NOTE]
+> [!TIP]
 > If you have a Faspex 5 public link, provide it, unchanged, through the option `url`
 
 For a quick start, one can use the wizard, which will help to create an [Option Preset](#option-preset):
 
-```bash
+```shell
 ascli config wizard
 ```
 
@@ -7119,9 +7132,9 @@ Saving configuration file.
 ```
 
 > [!NOTE]
-> Include the public key `BEGIN` and `END` lines when pasting in the user profile.
+> Paste the entire public key, including the BEGIN and END lines, into the user profile.
 
-For details on the JWT method, see the following section.
+For more information on the JWT method, refer to the section below.
 
 ### Faspex 5 JWT authentication
 
@@ -7143,14 +7156,14 @@ Activation is in two steps:
 
 - The user will authenticate with a private key and set the public key in his Faspex 5 profile.
 
-  > [!NOTE]
-  > If you don't have a private key refer to section [Private Key](#private-key) to generate one.
+  > [!TIP]
+  > If you don’t have a private key, see [Private Key](#private-key) to generate one.
   
   This operation is done by each user using the CLI.
 
-  - As user, click on the user logo, left to the app switcher on top right.
-  - Select `Account Settings`
-  - on the bottom in the text field: `Public key in PEM format` paste the **public** key corresponding to the private key used by the user.
+  - As a user, click the user logo located to the left of the app switcher in the top-right corner.
+  - Select `Account Settings`.
+  - At the bottom, in the `Public key in PEM format` field, paste the **public key** that corresponds to the private key assigned to your account.
 
 Then use these options:
 
@@ -7163,13 +7176,14 @@ Then use these options:
 ```
 
 > [!NOTE]
-> The `private_key` option must contain the PEM **value** (not file path) of the private key which can be read from a file using the modifier: `@file:`, e.g. `@file:/path/to/key.pem`.
+> Use the `private_key` option to provide the PEM content (not the file path).
+> To load from a file, prefix the path with `@file:`, e.g. `@file:/path/to/key.pem`.
 
-As usual, typically a user will create preset to avoid having to type these options each time.
+Typically, users create a preset so they don’t have to enter these options each time.
 
 Example:
 
-```bash
+```shell
 ascli config preset update myf5 --auth=jwt --client-id=_client_id_here_ --client-secret=my_secret_here --username=_username_here_ --private-key=@file:.../path/to/key.pem
 
 ascli config preset set default faspx5 myf5
@@ -7179,7 +7193,7 @@ ascli faspex5 user profile show
 
 ### Faspex 5 web authentication
 
-The administrator must create an **API client** in Faspex for an external web app support:
+For web-based authentication, the administrator must create an **API client** in Faspex for an external web app support:
 
 - As Admin, Navigate to the web UI: Admin &rarr; Configurations &rarr; API Clients &rarr; Create
 - Do not Activate JWT
@@ -7207,7 +7221,7 @@ For `boot` method: (will be removed in future)
 
 Use this token as password and use `--auth=boot`.
 
-```bash
+```shell
 ascli config preset update f5boot --url=https://localhost/aspera/faspex --auth=boot --password=_token_here_
 ```
 
@@ -7291,16 +7305,16 @@ user profile show
 version
 ```
 
-Most commands are directly REST API calls.
+Most commands correspond directly to REST API calls.
 Parameters to commands are carried through option `query`, as extended value, for `list`, or through **Command Parameter** for creation.
 One can conveniently use the JSON format with prefix `@json:`.
 
-> [!NOTE]
+> [!TIP]
 > The API is listed in [Faspex 5 API Reference](https://developer.ibm.com/apis/catalog?search="faspex+5") under **IBM Aspera Faspex API**.
 
 ### Faspex 5: Inbox selection
 
-By default, package operations (send, receive, list) are done on the user's inbox.
+By default, package operations (`send`, `receive`, `list`) are performed on the user's inbox.
 
 To select another inbox, use option `box` with one of the following values:
 
@@ -7316,16 +7330,16 @@ To select another inbox, use option `box` with one of the following values:
 | `pending_history`   | |
 | `all`               | |
 | `ALL`               | **admin only**, all inboxes of all users |
-| Any other value     | Name of a shared inbox if `group_type` is `shared_inboxes` (default)<br/>or workgroup if `group_type` is `workgroups` |
+| Open value          | Name of a shared inbox if `group_type` is `shared_inboxes` (default)<br/>or workgroup if `group_type` is `workgroups` |
 
 > [!NOTE]
-> In case the name of the `box` is an open value, use option `group_type` with either `shared_inboxes` or `workgroups`.
+> In case the name of the `box` is an open value, use option `group_type` set to either `shared_inboxes` or `workgroups`.
 
 ### Faspex 5: Send a package
 
 A package can be sent with the command:
 
-```bash
+```shell
 ascli faspex5 packages send [extended value: Hash with package info] [files...]
 ```
 
@@ -7335,8 +7349,8 @@ Required fields are `title` and `recipients`.
 
 Example (assuming a default preset is created for the connection information):
 
-```bash
-ascli faspex5 packages send @json:'{"title":"some title","recipients":["user@example.com"]}' mybygfile1
+```shell
+ascli faspex5 packages send @json:'{"title":"some title","recipients":["user@example.com"]}' mybigfile1
 ```
 
 Longer example for the payload of `@json:`:
@@ -7406,13 +7420,13 @@ Examples:
 
 - List only available packages: (filtering is done in Faspex)
 
-  ```bash
+  ```shell
   ascli faspex5 packages list --query=@json:'{"status":"completed"}'
   ```
 
 - Similar, using filtering in `ascli`:
 
-  ```bash
+  ```shell
   ascli faspex5 packages list @ruby:'->(p){p["state"].eql?("released")}'
   ```
 
@@ -7465,26 +7479,26 @@ To keep the content encrypted, use option: `--ts=@json:'{"content_protection":nu
 
 If you are a regular user, to list work groups you belong to:
 
-```bash
+```shell
 ascli faspex5 admin workgroup list
 ```
 
 If you are admin or manager, add option: `--query=@json:'{"all":true}'`, this will list items you manage, even if you do not belong to them.
 Example:
 
-```bash
+```shell
 ascli faspex5 admin shared list --query=@json:'{"all":true}' --fields=id,name
 ```
 
 Shared inbox members can also be listed, added, removed, and external users can be invited to a shared inbox.
 
-```bash
+```shell
 ascli faspex5 admin shared_inboxes invite '%name:the shared inbox' john@example.com
 ```
 
 It is equivalent to:
 
-```bash
+```shell
 ascli faspex5 admin shared_inboxes invite '%name:the shared inbox' @json:'{"email_address":"john@example.com"}'
 ```
 
@@ -7496,52 +7510,52 @@ Other payload parameters are possible for `invite` in this last `Hash` **Command
 
 ### Faspex 5: Create Metadata profile
 
-```bash
+```shell
 ascli faspex5 admin metadata_profiles create @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"]}]}'
 ```
 
 ### Faspex 5: Create a Shared inbox with specific metadata profile
 
-```bash
+```shell
 ascli faspex5 admin shared create @json:'{"name":"the shared inbox","metadata_profile_id":1}'
 ```
 
 ### Faspex 5: List content in Shared folder and send package from remote source
 
-```bash
+```shell
 ascli faspex5 shared_folders list --fields=id,name
 ```
 
-```markdown
-+----+----------+
-| id | name     |
-+----+----------+
-| 3  | partages |
-+----+----------+
+```text
+╭────┬──────────────╮
+│ id │ name         │
+╞════╪══════════════╡
+│ 2  │ Server Files │
+╰────┴──────────────╯
 ```
 
-```bash
-ascli faspex5 shared_folders br %name:partages /folder
+```shell
+ascli faspex5 shared_folders br %name:'Server Files' /folder
 ```
 
-```bash
+```shell
 ascli faspex5 packages send @json:'{"title":"hello","recipients":[{"name":"_recipient_here_"}]}' --shared-folder=%name:partages /folder/file
 ```
 
-> [!NOTE]
+> [!TIP]
 > The shared folder can be identified by its numerical `id` or by name using percent selector: `%<field>:<value>`. e.g. `--shared-folder=3`
 
 ### Faspex 5: Receive all packages (cargo)
 
 To receive all packages, only once, through persistency of already received packages:
 
-```bash
+```shell
 ascli faspex5 packages receive ALL --once-only=yes --query=@json:'{"status":"completed"}'
 ```
 
 To initialize, and skip all current package so that next time `ALL` is used, only newer packages are downloaded:
 
-```bash
+```shell
 ascli faspex5 packages receive INIT --once-only=yes
 ```
 
@@ -7551,7 +7565,7 @@ There are two types of invitations of package submission: public or private.
 
 Public invitations are for external users, provide just the email address.
 
-```bash
+```shell
 ascli faspex5 invitations create @json:'{"email_address":"john@example.com"}' --fields=access_url
 ```
 
@@ -7559,24 +7573,24 @@ Private invitations are for internal users, provide the user or shared inbox ide
 
 ### Faspex 5: Cleanup packages
 
-> [!NOTE]
+> [!WARNING]
 > Operation requires admin level.
 
 The default automated cleanup period can be displayed with:
 
-```bash
+```shell
 ascli faspex5 admin configuration show --fields=days_before_deleting_package_records
 ```
 
 This parameter can be modified with:
 
-```bash
+```shell
 ascli faspex5 admin configuration modify @json:'{"days_before_deleting_package_records":30}'
 ```
 
 To start package purge, i.e. permanently remove packages marked for deletion older than `days_before_deleting_package_records`, use command:
 
-```bash
+```shell
 ascli faspex5 admin clean_deleted
 ```
 
@@ -7586,7 +7600,7 @@ ascli faspex5 admin clean_deleted
 
 To delete all packages, one can use the following command:
 
-```bash
+```shell
 ascli faspex5 packages list --box=ALL --format=yaml --fields=id | ascli faspex5 packages delete @yaml:@stdin:
 ```
 
@@ -7598,15 +7612,15 @@ ascli faspex5 packages list --box=ALL --format=yaml --fields=id | ascli faspex5
 
 To unlock a user, you can deactivate and then re-activate the user:
 
-```bash
+```shell
 ascli faspex5 admin accounts modify %name:some.user@example.com @json:'{"account_activated":false}'
 ```
 
-```bash
+```shell
 ascli faspex5 admin accounts modify %name:some.user@example.com @json:'{"account_activated":true}'
 ```
 
-> [!NOTE]
+> [!TIP]
 > Here we use the convenient percent selector, but the numerical ID can be used as well.
 
 To send a password reset link to a user, use command `reset_password` on the `account`.
@@ -7622,7 +7636,7 @@ Nevertheless, on long term, a native approach shall be considered, such as using
 
 It is invoked like this:
 
-```bash
+```shell
 ascli faspex5 postprocessing
 ```
 
@@ -7645,7 +7659,7 @@ When a request on `ascli` is received the following happens:
 
 For example:
 
-```bash
+```shell
 ascli faspex5 postprocessing @json:'{"url":"http://localhost:8080/processing","script_folder":"/opt/scripts"}'
 ```
 
@@ -7669,7 +7683,7 @@ For legacy Faspex client applications that use the `send` API (only) of Faspex v
 
 It takes a single argument which is the URL at which the gateway will be located (locally):
 
-```bash
+```shell
 ascli faspex5 gateway @json:'{"url":"https://localhost:12345/aspera/faspex"}'
 ```
 
@@ -7692,14 +7706,14 @@ For other parameters, see [Web service](#web-service).
 
 If a command is missing, then it is still possible to execute command by calling directly the API on the command line using `curl`:
 
-```bash
+```shell
 curl -H "Authorization: $(ascli ascli bearer)" https://faspex5.example.com/aspera/faspex/api/v5/api_endpoint_here
 ```
 
 ## Plugin: `faspex`: IBM Aspera Faspex v4
 
-> [!NOTE]
-> Faspex v4 is end of support since Sept. 30th, 2024.
+> [!WARNING]
+> Faspex v4 is end of support since September 30th, 2024.
 > So this plugin for Faspex v4 is deprecated.
 > If you still need to use Faspex4, then use `ascli` version 4.19.0 or earlier.
 
@@ -7746,7 +7760,7 @@ By default, `count` is `0` (`10`), it can be increased to issue less HTTP calls.
 
 #### Example: List packages in dropbox
 
-```bash
+```shell
 ascli faspex package list --box=inbox --recipient='*my_dropbox' --query=@json:'{"max":20,"pmax":2,"count":20}'
 ```
 
@@ -7760,14 +7774,14 @@ The command is `package recv`, possible methods are:
 - Provide a public link with option `link`
 - Provide a `faspe:` URI with option `link`
 
-```bash
+```shell
 ascli faspex package recv 12345
 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
+```shell
 ascli faspex package list --recipient='*dropbox_name'
 ascli faspex package recv 125 --recipient='*dropbox_name'
 ```
@@ -7782,7 +7796,7 @@ The content of `delivery_info` is directly the contents of the `send` v3 [API of
 
 Example:
 
-```bash
+```shell
 ascli faspex package send --delivery-info=@json:'{"title":"my title","recipients":["someuser@example.com"]}' /tmp/file1 /home/bar/file2
 ```
 
@@ -7810,7 +7824,7 @@ Like for any transfer, a notification can be sent by email using options: `notif
 
 Example:
 
-```bash
+```shell
 ascli faspex package send --delivery-info=@json:'{"title":"test pkg 1","recipients":["aspera.user1@gmail.com"]}' ~/Documents/Samples/200KB.1 --notify-to=aspera.user1@gmail.com --notify-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"]%>}'
 ```
 
@@ -7822,7 +7836,7 @@ The template can be placed in a file using modifier: `@file:`
 
 Example:
 
-```bash
+```shell
 ascli faspex v4 dropbox create @json:'{"dropbox":{"e_wg_name":"test1","e_wg_desc":"test1"}}'
 ascli faspex v4 dropbox list
 ascli faspex v4 dropbox delete 36
@@ -7862,7 +7876,7 @@ The node configuration name is `my_faspex_node` here.
 It is possible to tell `ascli` to download newly received packages, much like the official cargo client, or drive.
 Refer to the [same section](#receive-new-packages-only-cargo) in the Aspera on Cloud plugin:
 
-```bash
+```shell
 ascli faspex packages recv ALL --once-only=yes --lock-port=12345
 ```
 
@@ -7931,7 +7945,7 @@ Example: Create a Node: Attributes are like API:
 
 Example: Create a share and add a user to it.
 
-```bash
+```shell
 ascli shares admin share create @json:'{"node_id":1,"name":"test1","directory":"test1","create_directory":true}'
 
 share_id=$(ascli shares admin share list --select=@json:'{"name":"test1"}' --fields=id)
@@ -8046,7 +8060,7 @@ If you have those parameters already, then following options shall be provided:
 
 For example, let us create a default configuration:
 
-```bash
+```shell
 ascli config preset update mycos --bucket=mybucket --endpoint=https://s3.us-east.cloud-object-storage.appdomain.cloud --apikey=abcdefgh --crn=crn:v1:bluemix:public:iam-identity::a/xxxxxxx
 ascli config preset set default cos mycos
 ```
@@ -8071,7 +8085,7 @@ Then save the copied value to a file, e.g. : `$HOME/cos_service_creds.json`
 
 or using the IBM Cloud CLI:
 
-```bash
+```shell
 ibmcloud resource service-keys
 ibmcloud resource service-key _service_key_name_here_ --output JSON|jq '.[0].credentials'>$HOME/service_creds.json
 ```
@@ -8113,7 +8127,7 @@ The required options for this method are:
 
 For example, let us create a default configuration:
 
-```bash
+```shell
 ascli config preset update mycos --bucket=laurent --service-credentials=@val:@json:@file:~/service_creds.json --region=us-south
 ascli config preset set default cos mycos
 ```
@@ -8124,7 +8138,7 @@ Let's assume you created a default configuration from one of the two previous st
 
 A subset of `node` plugin operations are supported, basically Node API:
 
-```bash
+```shell
 ascli cos node info
 ascli cos node upload 'faux:///sample1G?1g'
 ```
@@ -8206,7 +8220,7 @@ Specify the preview's folder as shown in:
 By default, the `preview` plugin expects previews to be generated in a folder named `previews` located in the storage root.
 On the transfer server execute:
 
-```bash
+```shell
 PATH=/opt/aspera/bin:$PATH
 
 asconfigurator -x "server;preview_dir,previews"
@@ -8225,7 +8239,7 @@ This size is internally capped to `1<<24` Bytes (16777216), i.e. 16384 KB, i.e.
 To change this parameter in `aspera.conf`, use `asconfigurator`.
 To display the value, use `asuserdata`:
 
-```bash
+```shell
 asuserdata -a | grep max_request_file_create_size_kb
 ```
 
@@ -8233,7 +8247,7 @@ asuserdata -a | grep max_request_file_create_size_kb
   max_request_file_create_size_kb: "1024"
 ```
 
-```bash
+```shell
 asconfigurator -x "server; max_request_file_create_size_kb,16384"
 ```
 
@@ -8257,13 +8271,13 @@ Other OSes should work as well, but are not tested.
 
 To check if all tools are found properly, execute:
 
-```bash
+```shell
 ascli preview check
 ```
 
 #### Image: ImageMagick and `optipng`
 
-```bash
+```shell
 dnf install -y ImageMagick optipng
 ```
 
@@ -8275,14 +8289,14 @@ More info on ImageMagick at <https://imagemagick.org/>
 
 If your OS has only ImageMagick v6, then you can create a script called `magick` and add it to your `PATH`:
 
-```bash
+```shell
 #!/bin/bash
 exec "$@"
 ```
 
 make it executable:
 
-```bash
+```shell
 chmod a+x /usr/local/bin/magick
 ```
 
@@ -8290,7 +8304,7 @@ chmod a+x /usr/local/bin/magick
 
 The easiest method is to download and install the latest released version of `ffmpeg` with static libraries from [https://johnvansickle.com/ffmpeg/](https://johnvansickle.com/ffmpeg/)
 
-```bash
+```shell
 curl -s https://johnvansickle.com/ffmpeg/releases/ffmpeg-release-amd64-static.tar.xz|(mkdir -p /opt && cd /opt && rm -f ffmpeg /usr/bin/{ffmpeg,ffprobe} && rm -fr ffmpeg-*-amd64-static && tar xJvf - && ln -s ffmpeg-* ffmpeg && ln -s /opt/ffmpeg/{ffmpeg,ffprobe} /usr/bin)
 ```
 
@@ -8302,13 +8316,13 @@ The generation of preview in based on the use of LibreOffice's `unoconv`.
 
 - RHEL 8/Rocky Linux 8+
 
-```bash
+```shell
 dnf install unoconv
 ```
 
 - Amazon Linux
 
-```bash
+```shell
 amazon-linux-extras enable libreoffice
 yum clean metadata
 yum install libreoffice-core libreoffice-calc libreoffice-opensymbol-fonts libreoffice-ure libreoffice-writer libreoffice-pyuno libreoffice-impress
@@ -8329,7 +8343,7 @@ The configuration file must be created with the same user used to run so that it
 The `xfer` user has a special protected shell: `aspshell`, so in order to update the configuration, and when changing identity, specify an alternate shell.
 E.g.:
 
-```bash
+```shell
 su -s /bin/bash - xfer
 
 ascli config preset update mypreviewconf --url=https://localhost:9092 --username=my_access_key --password=my_secret --skip-types=office --lock-port=12346
@@ -8342,7 +8356,7 @@ Here we assume that Office file generation is disabled, else remove this option.
 
 One can check if the access key is well configured using:
 
-```bash
+```shell
 ascli -Ppreviewconf node browse /
 ```
 
@@ -8365,19 +8379,19 @@ So, in order to be consistent, and generate the appropriate access rights, the g
 
 Let's do a one shot test, using the configuration previously created:
 
-```bash
+```shell
 su -s /bin/bash - xfer
 ```
 
 or
 
-```bash
+```shell
 sudo -u xfer /bin/bash
 ```
 
 and then:
 
-```bash
+```shell
 ascli preview scan --overwrite=always
 ```
 
@@ -8393,7 +8407,7 @@ Shorter commands can be specified if a configuration preset was created as shown
 
 For example the timeout value can be differentiated depending on the option: event versus scan:
 
-```bash
+```shell
 case "$*" in *trev*) tmout=10m ;; *) tmout=30m ;; esac
 ```
 
@@ -8420,7 +8434,7 @@ Deletion of preview for deleted source files: not implemented yet (TODO).
 If the `scan` or `events` detection method is used, then the option : `skip_folders` can be used to skip some folders.
 It expects a list of path relative to the storage root (docroot) starting with slash, use the `@json:` notation, example:
 
-```bash
+```shell
 ascli preview scan --skip-folders=@json:'["/not_here"]'
 ```
 
@@ -8482,7 +8496,7 @@ If the `mimemagic` gem complains about missing mime info file:
   - Place this file in the root of Ruby (or elsewhere): `C:\RubyVV-x64\freedesktop.org.xml.in`
   - Set a global variable using `SystemPropertiesAdvanced.exe` or using `cmd` (replace `VV` with version) to the exact path of this file:
 
-  ```cmd
+  ```batchfile
   SETX FREEDESKTOP_MIME_TYPES_PATH C:\RubyVV-x64\freedesktop.org.xml.in
   ```
 
@@ -8490,13 +8504,13 @@ If the `mimemagic` gem complains about missing mime info file:
 
 - Linux RHEL 8+:
 
-```bash
+```shell
 dnf install shared-mime-info
 ```
 
 - **macOS**:
 
-```bash
+```shell
 brew install shared-mime-info
 ```
 
@@ -8651,7 +8665,7 @@ Interesting `ascp` features are found in its arguments: (see `ascp` manual):
 > [!NOTE]
 > Usual native `ascp` arguments are available as standard [**transfer-spec**](#transfer-specification) parameters, but not special or advanced options.
 
-> [!NOTE]
+> [!TIP]
 > Only for the [`direct`](#agent-direct) transfer agent (not others, like connect or node), native `ascp` arguments can be provided with parameter `ascp_args` of option `transfer_info`.
 
 #### Server side and configuration
@@ -8661,7 +8675,7 @@ Virtually any transfer on a **repository** on a regular basis might emulate a ho
 > [!NOTE]
 > File detection is not based on events (`inotify`, etc...), but on a simple folder scan on source side.
 
-> [!NOTE]
+> [!TIP]
 > Options may be saved in an [Option Preset](#option-preset) and used with `-P`.
 
 #### Scheduling
@@ -8672,7 +8686,7 @@ Refer to section [Scheduler](#scheduler).
 
 ### Example: Upload hot folder
 
-```bash
+```shell
 ascli server upload source_hot --to-folder=/Upload/target_hot --lock-port=12345 --ts=@json:'{"remove_after_transfer":true,"remove_empty_directories":true,"exclude_newer_than:-8,"src_base":"source_hot"}'
 ```
 
@@ -8683,7 +8697,7 @@ If a transfer takes more than the execution period, then the subsequent executio
 
 ### Example: Unidirectional synchronization (upload) to server
 
-```bash
+```shell
 ascli server upload source_sync --to-folder=/Upload/target_sync --lock-port=12345 --ts=@json:'{"resume_policy":"sparse_csum","exclude_newer_than":-8,"src_base":"source_sync"}'
 ```
 
@@ -8691,7 +8705,7 @@ This can also be used with other folder-based applications: Aspera on Cloud, Sha
 
 ### Example: Unidirectional synchronization (download) from Aspera on Cloud Files
 
-```bash
+```shell
 ascli aoc files download . --to-folder=. --lock-port=12345 --progress-bar=no --display=data --ts=@json:'{"resume_policy":"sparse_csum","target_rate_kbps":50000,"exclude_newer_than":-8,"delete_before_transfer":true}'
 ```
 
@@ -8706,7 +8720,7 @@ ascli aoc files download . --to-folder=. --lock-port=12345 --progress-bar=no --d
 Most plugin provide a `health` command that will check the health status of the application.
 Example:
 
-```bash
+```shell
 ascli console health
 ```
 
@@ -8727,7 +8741,7 @@ Typically, the health check uses the REST API of the application with the follow
 `ascli` can be called by Nagios to check the health status of an Aspera server.
 The output can be made compatible to Nagios with option `--format=nagios` :
 
-```bash
+```shell
 ascli server health transfer --to-folder=/Upload --format=nagios --progress-bar=no
 ```
 
@@ -8758,7 +8772,7 @@ The `smtp` option is a `Hash` (extended value) with the following fields:
 
 ### Example of configuration
 
-```bash
+```shell
 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 my_password_here
@@ -8766,19 +8780,19 @@ ascli config preset set smtp_google password my_password_here
 
 or
 
-```bash
+```shell
 ascli config preset init smtp_google @json:'{"server":"smtp.google.com","username":"john@gmail.com","password":"my_password_here"}'
 ```
 
 or
 
-```bash
+```shell
 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:
 
-```bash
+```shell
 ascli config preset set cli_default smtp @val:@preset:smtp_google
 ascli config preset set default config cli_default
 ```
@@ -8802,7 +8816,7 @@ Other variables are defined depending on context.
 Check settings with `smtp_settings` command.
 Send test email with `email_test`.
 
-```bash
+```shell
 ascli config --smtp=@preset:smtp_google smtp
 ascli config --smtp=@preset:smtp_google email --notify-to=sample.dest@example.com
 ```
@@ -8882,11 +8896,11 @@ Create a file `session.json` with:
 
 ```json
 {"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:
 
-```bash
+```shell
 asession < session.json
 ```
 
@@ -8913,7 +8927,7 @@ NodeJS: [https://www.npmjs.com/package/aspera](https://www.npmjs.com/package/asp
 
 ### Help
 
-```bash
+```shell
 asession -h
 USAGE
     asession
@@ -8977,7 +8991,7 @@ It had the advantage of being relatively easy to installed, as a single executab
 
 Enjoy a coffee on me:
 
-```bash
+```shell
 ascli config coffee --ui=text
 ascli config coffee --ui=text --image=@json:'{"text":true}'
 ascli config coffee
@@ -8995,7 +9009,7 @@ Cause: `ascp` >= 4.x checks fingerprint of the highest server host key, includin
 
 Workaround on client side: To ignore the certificate (SSH fingerprint) add option on client side (this option can also be added permanently to the configuration file):
 
-```bash
+```shell
 --ts=@json:'{"sshfp":null}'
 ```
 
@@ -9041,7 +9055,7 @@ Add the following to option `ssh_options`:
 
 e.g.
 
-```bash
+```shell
 --ssh-options=@json:'{"host_key":["rsa-sha2-512","rsa-sha2-256"],"kex":["curve25519-sha256","diffie-hellman-group14-sha256"],"encryption": ["aes256-ctr", "aes192-ctr", "aes128-ctr"]}'
 ```
 
@@ -9050,7 +9064,7 @@ e.g.
 Newer OpenSSL library expects a clean SSL close.
 To deactivate this error, enable option `IGNORE_UNEXPECTED_EOF` for `ssl_options` in option `http_options`.
 
-```bash
+```shell
 --http-options=@json:'{"ssl_options":["IGNORE_UNEXPECTED_EOF"]}'
 ```
 
@@ -9060,7 +9074,7 @@ This happens on Linux x86 if you try to install `transferd` on a Linux version t
 
 Workaround: Install an older version:
 
-```bash
+```shell
 ascli config transferd install 1.1.2
 ```