update

Author: chenzhitong

docs/n3/develop/deploy/invoke.md

@@ -64,7 +64,7 @@ invoke <scriptHash> <operation> [contractParameters=null] [sender=null]  [signer
 When invoking a contract in Neo-GUI, you can click `Cosignature` at the bottom of the page, choose `Public key`, and then click `Sign` to add the signature.  
 
 :::note
- When you invoke the transfer method of the NEP-17 contract using the transfer command, the wallet will automatically appends the signature to the from field. You don't need to add it manually.
+When you invoke the transfer method of the NEP-17 contract using the transfer command, the wallet will automatically appends the signature to the from field. You don't need to add it manually.
 :::
 
 ## Invoking between contracts

docs/n3/develop/network/private-chain/private-chain2.md

@@ -211,7 +211,7 @@ You can refer to the following example：
 ```
 
 :::note
- If the plugin RpcServer is installed, you also need to modify the port numbers in the plugin config.json file to make them different from each other and from the ports in config.json of the node.
+If the plugin RpcServer is installed, you also need to modify the port numbers in the plugin config.json file to make them different from each other and from the ports in config.json of the node.
 :::
 
 ## Installing consensus plugin
@@ -311,7 +311,7 @@ In the genesis block of the NEO network, 100 million NEO and 30 million GAS are
    ![](../assets/initial-balance.png)
 
 :::note
- You must create multi-party signature address in at least three wallets so as to sign the transfer transaction successfully.
+You must create multi-party signature address in at least three wallets so as to sign the transfer transaction successfully.
 :::
 
 #### Transferring NEO to a normal address

docs/n3/develop/network/private-chain/solo.md

@@ -84,7 +84,7 @@ Here is an example:
 ## Starting the private chain
 
 :::note
- If the node has downloaded Neo test net block files, you need to delete the Data folder before running Neo-CLI, otherwise the private chain will not be able to properly generate blocks.
+If the node has downloaded Neo test net block files, you need to delete the Data folder before running Neo-CLI, otherwise the private chain will not be able to properly generate blocks.
 :::
 
 To start the private chain, enter the neo-cli directory and run neo-cli.exe, or run the command line and enter  `dotnet neo-cli.dll`. The private chain is set up successfully when it goes as shown below:
@@ -156,7 +156,7 @@ In the genesis block of the Neo network, 100 million NEO and 30 million GAS are
 
 6. Enter `list asset`，then you should see 100 million NEO and 30 million GAS displayed.
 
-7. Create a new wallet using the command `create wallet ` and copy the wallet address.
+7. Create a new wallet using the command `create wallet` and copy the wallet address.
 
 8. Open the wallet `consensus.json` again and transfer NEO and GAS to the new created wallet with the `send` command. For example, `send neo NWu2gb7PzhZb4ci9LvW4gBYAQFMGb1s1o7 100000000`, `send gas NWu2gb7PzhZb4ci9LvW4gBYAQFMGb1s1o7 10000000`.
 

docs/n3/develop/tool/sdk/introduction.md

@@ -18,9 +18,9 @@ This document is applicable to Neo N3. It is recommended you use NEO SDK in conj
 
 1. In Visual Studio 2019, create a new .NET project
 
-:::note
-The .NET version of the project cannot be earlier than the .NET version used by the Neo SDK.
-:::
+    :::note
+   The .NET version of the project cannot be earlier than the .NET version used by the Neo SDK.
+    :::
 
 2. Right-click the project and select `Manage NuGet Packages`.
 
@@ -33,10 +33,10 @@ The .NET version of the project cannot be earlier than the .NET version used by
    ```
 
 :::note
- If you use SDK to construct a transaction that requires a signature, you need to ensure that the RpcClient obeject and the network it is connected to are configured the same way, or the transaction constructed by the SDK will not be validated in the blockchain. To do so, load Neo-CLI config.json when constructing the RpcClient object, for example:
+If you use SDK to construct a transaction that requires a signature, you need to ensure that the RpcClient obeject and the network it is connected to are configured the same way, or the transaction constructed by the SDK will not be validated in the blockchain. To do so, load Neo-CLI config.json when constructing the RpcClient object, for example:
+
+RpcClient client = new RpcClient(new Uri("http://localhost:20332"), null, null, ProtocolSettings.Load("config.json"))
 :::
->
-> RpcClient client = new RpcClient(new Uri("http://localhost:20332"), null, null, ProtocolSettings.Load("config.json"))
 
 ## Exception handing
 

docs/n3/develop/tool/sdk/rpc.md

@@ -4,6 +4,7 @@ The `RpcClient` encapsulates all the interfaces provided by RpcServer. You can s
 
 
 ## Initializing RpcClient
+
 Before you can send RPC requests you need to initialize  `RpcClient` first. Choose the RPC server port of a Neo node according to your own needs. Here is an example:
 
 Test net node：
@@ -21,7 +22,7 @@ RpcClient client = new RpcClient(new Uri("http://localhost:20332"), null, null,
 ```
 
 :::note
- Typically, only one RpcClient instance needs to be initialized in an application, not needing in each method.
+Typically, only one RpcClient instance needs to be initialized in an application, not needing in each method.
 :::
 
 ## Blockchain data
@@ -79,6 +80,7 @@ UInt256 hash256 = UInt256.Parse(hexString);
 ```
 
 ### Get the block header information
+
 Get the specific block header information by the block hash or block index:
 
 ```cs
@@ -106,6 +108,7 @@ string serializedBlockHeader = await client.GetBlockHeaderHexAsync("10000").Conf
 ```
 
 ### GetContractStateAsync
+
 Gets the contract information from the contract hash or contract ID
 
 ```cs
@@ -117,6 +120,7 @@ ContractState contractState = client.GetContractState(-1);
 ```
 
 ### GetRawMempoolAsync
+
 Gets hash list of the confirmed transactions in the memory.
 
 ```cs
@@ -167,13 +171,15 @@ string value = await client.GetStorageAsync("03febccf81ac85e3d795bc5cbd4e84e9078
 ```
 
 ### GetTransactionHeightAsync
+
 Gets the block height of the specified transaction by transaction ID:
 
 ```cs
 uint height = await client.GetTransactionHeightAsync("f4250dab094c38d8265acc15c366dc508d2e14bf5699e12d9df26577ed74d657").ConfigureAwait(false);
 ```
 
 ### GetNextBlockValidatorsAsync
+
 Gets the consensus nodes information and voting status in the current network.
 
 ```cs
@@ -197,13 +203,15 @@ string[] committees = await client.GetCommitteeAsync().ConfigureAwait(false);
 ## Node
 
 ### GetConnectionCount
+
 Gets the number of nodes connected to this node.
 
 ```cs
 int connectionCount = await client.GetConnectionCountAsync().ConfigureAwait(false);
 ```
 
 ### GetPeersAsync
+
 Gets a list of currently connected / unconnected nodes for this node, including IP address and port.
 
 ```cs
@@ -219,6 +227,7 @@ if (connected.Length > 0)
 ```
 
 ### GetVersionAsync
+
 Gets the version of the node receiving the RPC request:
 
 ```cs
@@ -227,6 +236,7 @@ string version = rpcVersion.UserAgent;
 ```
 
 ### SendRawTransactionAsync
+
 Sends and broadcasts the serialized transaction.
 
 ```cs
@@ -240,6 +250,7 @@ UInt256 txHash = await client.SendRawTransactionAsync(transaction).ConfigureAwai
 ```
 
 ### SubmitBlockAsync
+
 Sends and broadcasts the serialized block：
 
 ```cs
@@ -249,6 +260,7 @@ UInt256 blockHash = await client.SubmitBlockAsync("00000000000000000000000000000
 ## Smart contract
 
 ### InvokeFunctionAsync
+
 Invokes the specific method of the smart contract through the specified smart contract script hash, method name, and parameters, and returns the result after running in the virtual machine.
 
 ```cs
@@ -288,6 +300,7 @@ long gasConsumed = rpcInvokeResult.GasConsumed;
 ```
 
 ### InvokeScriptAsync
+
 Returns the result after running the specified script in the virtual machine.
 
 ```cs
@@ -308,6 +321,7 @@ string address = unclaimedGas.Address;
 ## Tools
 
 ### ListPluginsAsync
+
 Lists all the plugins loaded in the node.
 
 ```cs
@@ -320,6 +334,7 @@ foreach (var item in rpcPlugins)
 ```
 
 ### ValidateAddressAsync
+
 Validates if the specified address is a valid Neo address.
 
 ```cs
@@ -329,6 +344,7 @@ bool isValid = result.IsValid;
 ```
 
 ## Wallets
+
 The node local wallet interface contains the function of accessing the local wallet file. Before using the methods described in this section, you need to open the wallet using the openwallet method.
 
 This method is disabled by default in the node configuration file for preventing high security risks.
@@ -344,41 +360,47 @@ bool result = await client.OpenWalletAsync(path, password).ConfigureAwait(false)
 ```
 
 ### CloseWalletAsync
+
 Closes the wallet and clears the wallet information in memory.
 
 ```cs
 bool result = await client.CloseWalletAsync().ConfigureAwait(false);
 ```
 
 ### DumpPrivKeyAsync
+
 Exports the private key of the specified address.
 
 ```cs
 string wif = await client.DumpPrivKeyAsync("NVVwFw6XyhtRCFQ8SpUTMdPyYt4Vd9A1XQ").ConfigureAwait(false);
 ```
 
 ### GetBalanceAsync
+
 Returns balance of the specified asset in the wallet by the asset id. This method is applicable to the native contract assets and NEP-17 compliant assets.
 
 ```cs
 BigDecimal balance = await client.GetWalletBalanceAsync(NativeContract.NEO.Hash.ToString()).ConfigureAwait(false);
 ```
 
 ### GetNewAddressAsync
+
 Creates a new account in the wallet and returns the corresponding address.
 
 ```cs
 string address = await client.GetNewAddressAsync().ConfigureAwait(false);
 ```
 
 ### GetUnclaimedGasAsync
+
 Displays amount of the unclaimed GAS in the wallet.
 
 ```cs
 BigInteger amount = await client.GetWalletUnclaimedGasAsync().ConfigureAwait(false);
 ```
 
 ### ImportPrivKeyAsync
+
 Imports the private key into the wallet.
 
 ```cs
@@ -387,13 +409,15 @@ RpcAccount account = await client.ImportPrivKeyAsync(wif).ConfigureAwait(false);
 ```
 
 ### ListAddressAsync
+
 Lists all the addresses in the wallet.
 
 ```cs
 List<RpcAccount> acoounts = await client.ListAddressAsync().ConfigureAwait(false);
 ```
 
 ### SendFromAsync
+
 Transfers asset from a specified address to another address.
 
 ```cs
@@ -403,13 +427,15 @@ string toAddress= "NZs2zXSPuuv9ZF6TDGSWT1RBmE8rfGj7UW";
 string amount = "100";
 JObject result = await client.SendFromAsync(assetId, fromAddress, toAddress, amount).ConfigureAwait(false);
 ```
+
 If the JSON transaction information is returned the transaction was sent successfully, or the transaction failed to be sent.
 
 If the signature is incomplete transaction to be signed is returned.
 
 If the balance is insufficient an error is returned.
 
 ### SendManyAsync
+
 Transfers assets to multiple addresses. You can specify the sending address.
 
 ```cs
@@ -428,13 +454,15 @@ outs.Add(new RpcTransferOut
 });
 JObject result = await client.SendManyAsync("", outs).ConfigureAwait(false);
 ```
+
 If the JSON transaction information is returned the transaction was sent successfully, or the transaction failed to be sent.
 
 If the signature is incomplete transaction to be signed is returned.
 
 If the balance is insufficient an error is returned.
 
 ### SendToAddressAsync
+
 Transfers asset to the specified address.
 
 ```cs
@@ -443,6 +471,7 @@ string toAddress = "NZs2zXSPuuv9ZF6TDGSWT1RBmE8rfGj7UW";
 string amount = "100";
 JObject result = await client.SendToAddressAsync(assetId, toAddress, amount).ConfigureAwait(false);
 ```
+
 If the JSON transaction information is returned the transaction was sent successfully, or the transaction failed to be sent.
 
 If the signature is incomplete transaction to be signed is returned.
@@ -452,6 +481,7 @@ If the balance is insufficient an error is returned.
 ## Plugins
 
 ### GetApplicationLogAsync
+
 Gets the contract log by the specific transaction ID. The plugin ApplicationLogs is required for invoking this method. 
 
 ```cs
@@ -476,6 +506,7 @@ RpcNep17Balances balances = await client.GetNep17BalancesAsync(address).Configur
 ```
 
 ### GetNep17TransfersAsync
+
 Returns all NEP-17 transaction records at the specific address. The plugin TokensTracker is required for invoking this method.
 
 If start and end timestamps are specified, transactions occurred in the time range is returned.

docs/n3/develop/tool/sdk/transaction.md

@@ -3,10 +3,11 @@
 `RpcClient` encapsulates the transaction construction module, which allows you to construct transactions in Neo N3 with specific parameters and methods to personalize your functions. This document introduces the relevant methods.
 
 :::note
- If you use SDK to construct a transaction that requires a signature, you need to ensure that the RpcClient object and the network it is connected to are configured the same way, or the transaction constructed by the SDK will not be validated in the blockchain. To do so, load Neo-CLI config.json when constructing the RpcClient object, for example:
+If you use SDK to construct a transaction that requires a signature, you need to ensure that the RpcClient object and the network it is connected to are configured the same way, or the transaction constructed by the SDK will not be validated in the blockchain. To do so, load Neo-CLI config.json when constructing the RpcClient object, for example:
+
+RpcClient client = new RpcClient(new Uri("http://localhost:20332"), null, null, ProtocolSettings.Load("config.json"))
 :::
->
-> RpcClient client = new RpcClient(new Uri("http://localhost:20332"), null, null, ProtocolSettings.Load("config.json"))
+
 
 ## Transaction construction process
 
@@ -18,7 +19,7 @@
     byte[] script = scriptHash.MakeScript("transfer", sender, receiver, 1，"data");
     ```
 
-2. Construct `TransactionManagerFactory` with the parameter `RpcClient `; Construct `TransactionManager` with the parameters `Script` and`Signers`:
+2. Construct `TransactionManagerFactory` with the parameter `RpcClient`; Construct `TransactionManager` with the parameters `Script` and`Signers`:
 
     ```cs
     TransactionManager txManager = await new TransactionManagerFactory(client)
@@ -33,13 +34,15 @@
     // add signature for the transaction with sendKey
     txManager.AddSignature(sendKey);
     ```
+
     - multiple signatures
 
     ```cs
     // add multi-signatures for the transaction with sendKey
     txManager.AddMultiSig(key1, 2, receiverKey.PublicKey, key2.PublicKey, key3.PublicKey);
     txManager.AddMultiSig(key2, 2, receiverKey.PublicKey, key2.PublicKey, key3.PublicKey);
     ```
+    
     - multi-signature contract
 
       The nature of multi-signature comes from multi-signature contracts. You need to construct a multi-signature contract before you can obtain the multi-signature address and transfer assets. The following example uses 3 accounts to create a multi-signature contract which requires at least 2 account signatures for signing.
@@ -51,7 +54,7 @@
     UInt160 multiAccount = multiContract.Script.ToScriptHash();
     ```
 
-5. Verify signatures and add `Witness` to the transaction body.
+4. Verify signatures and add `Witness` to the transaction body.
 
     If there are not enough signatures or fees an exception will be thrown.