docs: supported Node.JS version and dashmate command description

README.md

@@ -50,7 +50,7 @@ this repository may be used on the following networks:
 
 - Clone the repo
 - Install prerequisites:
-  - [node.js](https://nodejs.org/) v16.10.0+
+  - [node.js](https://nodejs.org/) Any v16 version
   - [docker](https://docs.docker.com/get-docker/) v20.10+
 - Run `corepack enable` to enable [corepack](https://nodejs.org/dist/latest/docs/api/corepack.html) and install yarn
 - Run `yarn setup` to install dependencies and configure and build all packages

packages/dapi/README.md

@@ -23,7 +23,7 @@ npm install
 
 ### Dependencies
 
-DAPI targets the latest LTS release of Node.js. Currently, this is Node v10.13.
+DAPI targets the latest v16 release of Node.js.
 
 DAPI requires the latest version of [dashcore](https://github.com/dashevo/dash-evo-branches/tree/evo) with Evolution features (special branch repo).
 

packages/dashmate/README.md

@@ -31,7 +31,7 @@ Distribution package for Dash Masternode installation
 ### Dependencies
 
 * [Docker](https://docs.docker.com/engine/installation/) (v20.10+)
-* [Node.js](https://nodejs.org/en/download/) (v16.0+, NPM v8.0+)
+* [Node.js](https://nodejs.org/en/download/) (v16, NPM v8.0+)
 
 For Linux installations you may optionally wish to follow the [post-installation steps](https://docs.docker.com/engine/install/linux-postinstall/) to manage Docker as a non-root user, otherwise you will have to run CLI and Docker commands with `sudo`.
 
@@ -226,14 +226,12 @@ The `reset` command removes all data corresponding to the specified config and a
 ```
 USAGE
   $ dashmate reset [--config <value>] [-v] [-h] [-f] [-p]
-
 FLAGS
   -f, --force          skip running services check
   -h, --hard           reset config as well as data
   -p, --platform-only  reset platform data only
   -v, --verbose        use verbose mode for output
   --config=<value>     configuration name to use
-
 DESCRIPTION
   Reset node data
 ```
@@ -243,6 +241,22 @@ To reset a node:
 $ dashmate reset
 ```
 
+#### Hard reset
+With the hard reset mode enabled, the corresponding config will be reset in addition to the platform data. After a hard reset, it is necessary to run the node [setup](#setup-node) to proceed.
+```bash
+$ dashmate reset --hard
+```
+
+#### Manual reset
+Manual reset is used when local setup corrupts and hard reset does not fix it. This could happen, when dashmate configuration becomes incompatible after a major upgrade, making you unable to execute any commands.
+```bash
+docker stop $(docker ps -q)
+docker system prune
+docker volume prune
+rm -rf ~/.dashmate/
+```
+
+
 ### Reindex dashcore chain data
 
 The `reindex` command rebuilds the block chain index using the downloaded block data.
@@ -255,51 +269,23 @@ The `reindex` command works for regular and local configurations.
 
 ```
 Reindex Core
-
 USAGE
   $ dashmate core reindex [-v] [--config <value>]
-
 FLAGS
   -v, --verbose     use verbose mode for output
   --config=<value>  configuration name to use
-
 DESCRIPTION
   Reindex Core
-
   Reindex Core data
 ```
 
-With the hard reset mode enabled, the corresponding config will be reset as well. To proceed, running the node [setup](#setup-node) is required.
-
-To reset a node:
-```bash
-$ dashmate reset
-=======
-#### Hard reset
-
-``dashmate reset --hard``
-
-With the hard reset mode enabled, the corresponding config will be reset as well. This command cleans up all related containers and volumes. To proceed, running the node [setup](#setup-node) is required.
-
-#### Manual reset
-
-Manual reset is used when local setup corrupts and hard reset does not fix it. This could happen, when dashmate configuration becomes incompatible after a major upgrade, making you unable to execute any commands.
-
-```bash
-docker stop $(docker ps -q)
-docker system prune
-docker volume prune
-rm -rf ~/.dashmate/
-```
-
 ### Full node
-
 It is also possible to start a full node instead of a masternode. Modify the config setting as follows:
-
 ```bash
 dashmate config set core.masternode.enable false
 ```
 
+
 ### Node groups
 
 CLI allows to [setup](#setup-node) and operate multiple nodes. Only the `local` preset is supported at the moment.