Fix typos

Author: DOBEN

source/mainnet/net/references/multi-sig.rst

@@ -12,7 +12,7 @@ each credential has one or several public-private key pair(s).
 .. note::
 
    A public-private key pair are related keys used for asymmetric cryptography.
-   The private key is used to sign/authorize an action relatd to the account. NEVER share your private key with anyone.
+   The private key is used to sign/authorize an action related to the account. NEVER share your private key with anyone.
    In contrast, the public key is shared with other entities to verify that a signature is generated
    by the associated private key.
 
@@ -25,11 +25,11 @@ The ``concordium-client`` tool (version 6.3.0 or above) facilitates creating, si
 transactions for multi-sig accounts.
 This page will go through the main steps as follows:
 
--  Create a multi-sig account by adding keys with the ``concordium-client`` tool to an account.
+-  Create a multi-sig account by adding keys via an on-chain transaction to an account.
 -  Configure the ``concordium-client`` tool to use a multi-sig account.
 -  Create a multi-sig transaction with the ``concordium-client`` tool.
 -  Add an additional signature to a multi-sig transaction with the ``concordium-client`` tool.
--  Send a multi-sig transaction with the ``concordium-client`` tool on chain.
+-  Send a multi-sig transaction with the ``concordium-client`` tool on-chain.
 
 Create a multi-sig account
 ==========================
@@ -40,13 +40,15 @@ A default account can be converted into a multi-sig account.
 
 .. note::
 
-   The Desktop wallet is the only wallet currently that has its own independent flow of creating a multi-sig account via its front end and
-   generating multi-sig transactions. The two guides :ref:`multi-sig accounts<overview-shared-accounts>` and
-   :ref:`multi-sig transactions<create-multisig>` will cover the flows in the Desktop wallet.
-   The partially-signed transaction file as generated by
-   the Desktop wallet is currently NOT compatible with file generated by the ``concordium-client`` tool.
-   You need to add additional signatures and send the transaction on-chain with the
-   wallet/tool the file was initially generated with.
+   The desktop wallet is the only wallet currently that has its independent flow of creating a multi-sig
+   account via its front end and generating multi-sig transactions. The two guides
+   :ref:`multi-sig accounts<overview-shared-accounts>` and :ref:`multi-sig transactions<create-multisig>` will
+   explain the flows for the desktop wallet.
+   The multi-sig transaction file, as generated by the desktop wallet, is currently NOT compatible with
+   the file generated by the ``concordium-client`` tool. You need to add additional signatures and send
+   the transaction on-chain with the wallet/tool the file was initially generated with. The intention is to use
+   the file format of the ``concordium-client`` tool in all Concordium tooling related to multi-sig signing
+   in the future and to replace the desktop wallet's file format.
 
 To add additional keys to an existing account on Concordium using the ``concordium-client`` tool, you can either:
 
@@ -111,7 +113,7 @@ To add additional keys to an existing account on Concordium using the ``concordi
       {
          "keys": {
             "0": {
-               "verifyKey": "<Hex encoding without '0x' of the public key already on chain>"
+               "verifyKey": "<Hex encoding without '0x' of the public key already on-chain>"
             },
             "1": {
                "verifyKey": "<Hex encoding without '0x' of the public key from your newly generated key pair>"
@@ -133,7 +135,7 @@ To add additional keys to an existing account on Concordium using the ``concordi
 
    - Step 1: Create an additional credential.
 
-   We recommend using the flow in the Desktop wallet to :ref:`create a credential file<create-credentials-file>`.
+   We recommend using the flow in the desktop wallet to :ref:`create a credential file<create-credentials-file>`.
    Alternatively, you can `clone the project <https://github.com/Concordium/concordium-base/blob/main/rust-bins/src/bin/user_cli.rs>`_
    and run its command locally to generate a credential file.
 
@@ -161,7 +163,7 @@ Configure the tool to use a multi-sig account
 To configure the ``concordium-client`` tool to use a multi-sig account, you can either:
 
 - pass in the signing keys via a file every time you sign a transaction (Option 1).
--  configure the ``concordium-client`` tool once to include the additional keys in its local key directory (Option 2).
+- configure the ``concordium-client`` tool once to include the additional keys in its local key directory (Option 2).
 
 To view the key directory path that the ``concordium-client`` tool is using, run the following command:
 
@@ -170,7 +172,7 @@ To view the key directory path that the ``concordium-client`` tool is using, run
       $concordium-client config show
 
 The goal is to add additional keys for your account to the local key directory of the ``concordium-client``
-tool in this section (Option 2). The first option is covered in the
+tool in this section (Option 2). The guide for the first option is in the
 :ref:`following section<sign-with-keyfile>`.
 
 .. dropdown:: Import the keys by adapting the key export file format from the browser wallet
@@ -265,10 +267,10 @@ tool in this section (Option 2). The first option is covered in the
          ...
       }
 
-   .. note::
+.. note::
 
-      This command updates the keys in the key directory of your local ``concordium-client`` tool. No transaction
-      is sent on-chain.
+   These commands update the keys in the key directory of your local ``concordium-client`` tool. No transaction
+   is sent on-chain.
 
 
 Create a multi-sig transaction
@@ -280,7 +282,7 @@ Multi-sig transactions can be created for all active transaction types which are
 ``UpdateCredential``, and ``UpdateCredentialsKeys``.
 
 To create a multi-sig transaction, execute a transaction-creating command and add an ``--out`` flag.
-This flag will cause ``concordium-client`` to output the partially-signed
+This flag will cause ``concordium-client`` to output the multi-sig
 transaction into the specified file instead of sending it on-chain.
 
 If you omit the ``--signers`` flag, ``concordium-client`` will output
@@ -295,7 +297,7 @@ run the following command:
 
    $concordium-client transaction send --receiver 4bbdAUCDK2D6cUvUeprGr4FaSaHXKuYmYVjyCa4bXSCu3NUXzA --amount 1 --out ./transaction.json --energy 5000 --sender 4jxvYasaPncfmCFCLZCvuL5cZuvR5HAQezCHZH7ZA7AGsRYpix --grpc-port 20000 --grpc-ip node.testnet.concordium.com
 
-The partially-signed transaction is output into the file ``transaction.json`` and has the following format:
+The multi-sig transaction is outputted into the ``transaction.json`` file and has the following format:
 
 .. code-block:: json
    :force:
@@ -321,7 +323,7 @@ The partially-signed transaction is output into the file ``transaction.json`` an
 .. _sign-with-keyfile:
 
 If you want to sign the transaction with keys that are not in the local key directory, you need to provide
-the keys as a separte file with the ``--keys`` flag. Keys provided with a flag take precedence and no
+the keys as a separate file with the ``--keys`` flag. Keys provided with a flag take precedence and no
 lookup of local keys in the key directory is performed.
 
 For example, to create a multi-sig transaction to send 1 CCD to an account on testnet using keys for signing
@@ -358,7 +360,7 @@ where ``keypair.json`` is a file of the following format:
    }
 
 
-If you want to create a partially-signed transaction with no signatures at all, you can use an
+If you want to create a multi-sig transaction with no signatures at all, you can use an
 empty ``keypair.json`` file of the following format:
 
 .. code-block:: json
@@ -374,7 +376,7 @@ empty ``keypair.json`` file of the following format:
 Add an additional signature to a multi-sig transaction
 ======================================================
 
-For example, to sign the partially-signed testnet transaction in the file ``transaction.json`` (created in the
+For example, to sign the multi-sig testnet transaction in the ``transaction.json`` file (created in the
 previous section) on a potentially different device by a different entity, run the following command:
 
 .. code-block:: console
@@ -386,19 +388,20 @@ previous section) on a potentially different device by a different entity, run t
    All keys (as present in the local key directory) associated with the ``signer`` account
    are used to sign the transaction since the ``--signers`` flag is omitted in the above command.
    Check that the ``signer`` account in the ``transaction.json`` file, is the account you want
-   to lookup its keys and sign with.
+   to look up its keys and sign with.
 
 .. note::
 
    If you want to sign with specific keys from the local key directory,
    you can specify some of them with the ``--signers`` flag (e.g. ``--signer "0:0,0:1"``).
 
 .. note::
+
    If you want to sign the transaction with keys that are not in the local key directory,
-   you can checkout the ``--keys`` flag :ref:`here<sign-with-keyfile>`.
+   you can use the ``--keys`` flag as described :ref:`here<sign-with-keyfile>`.
 
-The additional signatures generated are added to the partially-signed transaction into the
-file ``transaction.json`` and the file will look similar to the following format:
+The additional signatures generated are added to the multi-sig transaction into the
+``transaction.json`` file and the file will look similar to the following format:
 
 .. code-block:: json
    :force:
@@ -425,8 +428,8 @@ file ``transaction.json`` and the file will look similar to the following format
 Send a multi-sig transaction on-chain
 =====================================
 
-For example, to send the partially-signed testnet transaction from the file ``transaction.json`` (created in the
-previous section) on chain, run the following command:
+For example, to send the multi-sig testnet transaction from the ``transaction.json`` file (created in the
+previous section) on-chain, run the following command:
 
 .. code-block:: console