Feat/no trailing spaces in *.md files (#3432)

Author: cthulhu-rider

.github/workflows/trailng-spaces.yml

@@ -0,0 +1,15 @@
+name: Trailing spaces
+
+on:
+  pull_request:
+    branches:
+      - master
+      - support/**
+
+jobs:
+  example:
+    runs-on: ubuntu-latest
+    name: Search spaces in *.md files
+    steps:
+      - uses: actions/checkout@v4
+      - uses: ocular-d/[email protected]

CREDITS.md

@@ -8,7 +8,7 @@ In alphabetical order:
 - Alexey Vanin
 - Anastasia Prasolova
 - Anatoly Bogatyrev
-- Evgeny Kulikov 
+- Evgeny Kulikov
 - Evgeny Stratonikov
 - Leonard Liubich
 - Sergei Liubich

config/mainnet/README.md

@@ -1,12 +1,12 @@
 # N3 Mainnet Storage node configuration
 
 Here is a template for simple storage node configuration in N3 Mainnet.
-Make sure to specify correct values instead of `<...>` placeholders. 
+Make sure to specify correct values instead of `<...>` placeholders.
 Do not change `contracts` section. Run the latest neofs-node release with
 the fixed config `neofs-node -c config.yml`
 
 To use NeoFS in the Mainnet, you need to deposit assets to NeoFS contract.
-The contract sript hash is `2cafa46838e8b564468ebd868dcafdd99dce6221` 
+The contract sript hash is `2cafa46838e8b564468ebd868dcafdd99dce6221`
 (N3 address `NNxVrKjLsRkWsmGgmuNXLcMswtxTGaNQLk`)
 
 ## Tips

config/testnet/README.md

@@ -6,8 +6,8 @@ docker image and run it with docker-compose.
 
 ## Build image
 
-Prepared **neofs-storage-testnet** image is available at Docker Hub. 
-However, if you need to rebuild it for some reason, run 
+Prepared **neofs-storage-testnet** image is available at Docker Hub.
+However, if you need to rebuild it for some reason, run
 `make image-storage-testnet` command.
 
 ```
@@ -19,13 +19,13 @@ Successfully tagged nspccdev/neofs-storage-testnet:0.25.1
 
 ## Deploy node
 
-To run a storage node in N3 Testnet environment, you should deposit GAS assets, 
+To run a storage node in N3 Testnet environment, you should deposit GAS assets,
 update docker-compose file and start the node.
 
 ### Deposit
 
-The Storage Node owner should deposit GAS to NeoFS smart contract. It generates a 
-bit of sidechain GAS in the node's wallet. Sidechain GAS is used to send bootstrap tx. 
+The Storage Node owner should deposit GAS to NeoFS smart contract. It generates a
+bit of sidechain GAS in the node's wallet. Sidechain GAS is used to send bootstrap tx.
 
 First, obtain GAS in N3 Testnet chain. You can do that with
 [faucet](https://neowish.ngd.network) service.
@@ -34,7 +34,7 @@ Then, make a deposit by transferring GAS to NeoFS contract in N3 Testnet.
 You can provide scripthash in the `data` argument of transfer tx to make a
 deposit to a specified account. Otherwise, deposit is made to the tx sender.
 
-NeoFS contract scripthash in N3 Testnet is `b65d8243ac63983206d17e5221af0653a7266fa1`, 
+NeoFS contract scripthash in N3 Testnet is `b65d8243ac63983206d17e5221af0653a7266fa1`,
 so the address is `NadZ8YfvkddivcFFkztZgfwxZyKf1acpRF`.
 
 See a deposit example with `neo-go`.
@@ -57,7 +57,7 @@ NEOFS_GRPC_0_ENDPOINT=65.52.183.157:36512
 NEOFS_NODE_ADDRESSES=65.52.183.157:36512
 ```
 
-Set up your [UN/LOCODE](https://unece.org/trade/cefact/unlocode-code-list-country-and-territory) 
+Set up your [UN/LOCODE](https://unece.org/trade/cefact/unlocode-code-list-country-and-territory)
 attribute.
 
 ```
@@ -66,7 +66,7 @@ NEOFS_NODE_ADDRESSES=65.52.183.157:36512
 NEOFS_NODE_ATTRIBUTE_2=UN-LOCODE:RU LED
 ```
 
-You can validate UN/LOCODE attribute in 
+You can validate UN/LOCODE attribute in
 [NeoFS LOCODE database](https://github.com/nspcc-dev/neofs-locode-db/releases/tag/v0.1.0)
 with neofs-cli.
 
@@ -79,7 +79,7 @@ Subdivision: [SPE] Sankt-Peterburg
 Coordinates: 59.53, 30.15
 ```
 
-It is recommended to pass the node's key as a file. To do so, convert your wallet 
+It is recommended to pass the node's key as a file. To do so, convert your wallet
 WIF to 32-byte hex (via `neofs-cli` for example) and save it to a file.
 
 ```
@@ -104,8 +104,8 @@ Then, specify the path to this file in `docker-compose.yml`
 ```
 
 
-NeoFS objects will be stored on your machine. By default, docker-compose 
-is configured to store objects in named docker volume `neofs_storage`. You can 
+NeoFS objects will be stored on your machine. By default, docker-compose
+is configured to store objects in named docker volume `neofs_storage`. You can
 specify a directory on the filesystem to store objects there.
 
 ```yaml
@@ -120,7 +120,7 @@ Run the node with `docker-compose up` command and stop it with `docker-compose d
 
 ### Debug
 
-To print node logs, use `docker logs neofs-testnet`. To print debug messages in 
+To print node logs, use `docker logs neofs-testnet`. To print debug messages in
 log, set up log level to debug with this env:
 
 ```yaml

docs/cli-adm.md

@@ -3,21 +3,21 @@
 ## Overview
 
 Admin tool provides an easier way to deploy and maintain private installation
-of NeoFS. Private installation provides a set of N3 consensus nodes, NeoFS 
-Alphabet, and Storage nodes. Admin tool generates consensus keys, initializes 
+of NeoFS. Private installation provides a set of N3 consensus nodes, NeoFS
+Alphabet, and Storage nodes. Admin tool generates consensus keys, initializes
 the sidechain, and provides functions to update the network and register new
 Storage nodes.
 
 ## Build
 
-To build binary locally, use `make bin/neofs-adm` command. 
+To build binary locally, use `make bin/neofs-adm` command.
 
-For clean build inside a docker container, use `make docker/bin/neofs-adm`. 
+For clean build inside a docker container, use `make docker/bin/neofs-adm`.
 
 Build docker image with `make image-adm`.
 
-At NeoFS private install deployment, neofs-adm requires compiled NeoFS 
-contracts. Find them in the latest release of 
+At NeoFS private install deployment, neofs-adm requires compiled NeoFS
+contracts. Find them in the latest release of
 [neofs-contract repository](https://github.com/nspcc-dev/neofs-contract/releases).
 
 
@@ -27,7 +27,7 @@ contracts. Find them in the latest release of
 
 Config section provides `init` command that creates a configuration file for
 private installation deployment and updates. Config file is optional, all
-parameters can be passed by arguments or read from standard input (wallet 
+parameters can be passed by arguments or read from standard input (wallet
 passwords).
 
 Config example:
@@ -58,14 +58,14 @@ credentials:     # passwords for consensus node / alphabet wallets
 
 #### Network deployment
 
-- `generate-alphabet` generates a set of wallets for consensus and 
-  Alphabet nodes. 
+- `generate-alphabet` generates a set of wallets for consensus and
+  Alphabet nodes.
 
 - `init` initializes the sidechain by deploying smart contracts and
   setting provided NeoFS network configuration.
 
-- `generate-storage-wallet` generates a wallet for the Storage node that 
-  is ready for deployment. It also transfers a bit of sidechain GAS, so this 
+- `generate-storage-wallet` generates a wallet for the Storage node that
+  is ready for deployment. It also transfers a bit of sidechain GAS, so this
   wallet can be used for NeoFS bootstrap.
 
 #### Network maintenance
@@ -79,7 +79,7 @@ credentials:     # passwords for consensus node / alphabet wallets
 
 - `renew-domain` updates expiration date of the given domain for one year.
 
-- `refill-gas` transfers sidechain GAS to the specified wallet. 
+- `refill-gas` transfers sidechain GAS to the specified wallet.
 
 - `update-contracts` updates contracts to a new version.
 
@@ -91,7 +91,7 @@ info. These commands **do not migrate actual objects**.
 - `dump-containers` saves all containers and metadata registered in the container
   contract to a file.
 
-- `restore-containers` restores previously saved containers by their repeated registration in 
+- `restore-containers` restores previously saved containers by their repeated registration in
  the container contract.
 
 - `list-containers` output all containers ids.

docs/cli-commands/neofs-cli_acl_extended_create.md

@@ -13,8 +13,8 @@ Action is 'allow' or 'deny'.
 Operation is an object service verb: 'get', 'head', 'put', 'search', 'delete', 'getrange', or 'getrangehash'.
 
 Filter consists of <typ>:<key><match><value>
-  Typ is 'obj' for object applied filter or 'req' for request applied filter. 
-  Key is a valid unicode string corresponding to object or request header key. 
+  Typ is 'obj' for object applied filter or 'req' for request applied filter.
+  Key is a valid unicode string corresponding to object or request header key.
     Well-known system object headers start with '$Object:' prefix.
     User defined headers start without prefix.
     Read more about filter keys at github.com/nspcc-dev/neofs-api/blob/master/proto-docs/acl.md#message-eaclrecordfilter
@@ -24,10 +24,10 @@ Filter consists of <typ>:<key><match><value>
     '>' | '>=' | '<' | '<=' for integer comparison.
   Value is a valid unicode string corresponding to object or request header value. Numeric filters must have base-10 integer values.
 
-Target is 
-  'user' for container owner, 
+Target is
+  'user' for container owner,
   'system' for Storage nodes in container and Inner Ring nodes,
-  'others' for all other request senders, 
+  'others' for all other request senders,
   'address:<adr1>,<adr2>,...' for exact request sender, where <adr> is a base58 25-byte address. Example: NSiVJYZej4XsxG5CUpdwn7VRQk8iiiDMPM.
 
 When both '--rule' and '--file' arguments are used, '--rule' records will be placed higher in resulting extended ACL table.

docs/cli-commands/neofs-cli_completion.md

@@ -19,15 +19,15 @@ Zsh:
   If shell completion is not already enabled in your environment you will need
   to enable it.  You can execute the following once:
   $ echo "autoload -U compinit; compinit" >> ~/.zshrc
-  
+
   To load completions for each session, execute once:
   $ neofs-cli completion zsh > "${fpath[1]}/_neofs-cli"
-  
+
   You will need to start a new shell for this setup to take effect.
 
 Fish:
   $ neofs-cli completion fish | source
-  
+
   To load completions for each session, execute once:
   $ neofs-cli completion fish > ~/.config/fish/completions/neofs-cli.fish
 

docs/cli-commands/neofs-cli_container_create.md

@@ -4,7 +4,7 @@ Create new container
 
 ### Synopsis
 
-Create new container and register it in the NeoFS. 
+Create new container and register it in the NeoFS.
 It will be stored in FS chain when inner ring will accepts it.
 
 ```

docs/cli-commands/neofs-cli_container_delete.md

@@ -4,7 +4,7 @@ Delete existing container
 
 ### Synopsis
 
-Delete existing container. 
+Delete existing container.
 Only owner of the container has a permission to remove container.
 
 ```

docs/cli-commands/neofs-cli_session_create.md

@@ -6,8 +6,8 @@ Create session token
 
 Create session token.
 
-Default lifetime of session token is 10 epochs 
-if none of --expire-at or --lifetime flags is specified. 
+Default lifetime of session token is 10 epochs
+if none of --expire-at or --lifetime flags is specified.
 
 
 ```