replace nep5 (#1292)

Author: Celia18305

docs/en-us/develop/deploy/deploy.md

@@ -1,6 +1,6 @@
 # Deploying Smart Contracts
 
-When a smart contract is deployed on the blockchain, it can be used by other users or invoked by other contracts. This section describes how to deploy and invoke the smart contract in the Neo blockchain using Neo-CLI or Neo-GUI. The instructions in this section are generic and applicable to all contract types including NEP-5 assets. 
+When a smart contract is deployed on the blockchain, it can be used by other users or invoked by other contracts. This section describes how to deploy and invoke the smart contract in the Neo blockchain using Neo-CLI or Neo-GUI. The instructions in this section are generic and applicable to all contract types including NEP-17 assets. 
 
 ## What contracts need to be deployed?
 
@@ -10,7 +10,7 @@ From the programming language perspective, only when a smart contract will be us
 
 - When a smart contract has variable incoming parameters, it must serve as a storage. The caller or other smart contracts provide the parameters.
 - When a smart contract uses storage it must serve as a class library.
-- When a smart contract implements NEP-5 standard assets, the contract needs to be deployed on the blockchain.
+- When a smart contract implements NEP-17 standard assets, the contract needs to be deployed on the blockchain.
 
 ### How to deploy?
 

docs/en-us/develop/deploy/invoke.md

@@ -65,7 +65,7 @@ When invoking a contract in Neo-GUI, you can click `Cosignature` at the bottom o
 
 > [!Note]
 >
-> When you invoke the transfer method of the NEP-5 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/en-us/develop/tool/sdk/monitor.md

@@ -2,7 +2,7 @@
 
 The `RPC` module provides methods to get basic information of blockchain data and status, such as block height, block content, transaction details, and contracts. 
 
-For some specific information of contracts, such as the block maximum transaction number, system fee per byte, NEP-5 contract details, you need to invoke specific contract methods, which will be introduced in this document.
+For some specific information of contracts, such as the block maximum transaction number, system fee per byte, NEP-17 contract details, you need to invoke specific contract methods, which will be introduced in this document.
 
 
 ## Getting blockchain data from RPC interfaces

docs/en-us/develop/tool/sdk/rpc.md

@@ -356,7 +356,7 @@ string wif = await client.DumpPrivKeyAsync("NVVwFw6XyhtRCFQ8SpUTMdPyYt4Vd9A1XQ")
 ```
 
 ### 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-5 compliant assets.
+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.
 
 ```c#
 BigDecimal balance = await client.GetWalletBalanceAsync(NativeContract.NEO.Hash.ToString()).ConfigureAwait(false);

docs/en-us/develop/tool/sdk/wallet.md

@@ -136,7 +136,7 @@ WalletAPI walletAPI = new WalletAPI(client);
 >
 > The type of account balance is usually BigInteger, which is a representation after rounding the decimal part. It needs to be divided by Factor to get the actual Token amount.
 
-Inquiry NEP-5 asset balance using the string parameter:
+Inquiry NEP-17 asset balance using the string parameter:
 
 ```c#
 // get the neo balance of account
@@ -200,7 +200,7 @@ In Neo N3 GAS is automatically claimed when NEO is transferred. You can construc
 
 ## Asset Transfer
 
-`WalletAPI` encapsulates transfer methods of NEP-5 assets.
+`WalletAPI` encapsulates transfer methods of NEP-17 assets.
 
 Use string parameters: 
 

docs/en-us/exchange/client.md

@@ -50,7 +50,7 @@ Neo-CLI provides the following features：
   For more API information, refer to [API Reference](../reference/rpc/latest-version/api.md).
 
 
-- Provides transaction information of NEP-5 assets.
+- Provides transaction information of NEP-17 assets.
 
 
 ### Creating a Wallet

docs/en-us/node/gui/blockchain.md

@@ -42,7 +42,7 @@ The transaction list shows the confirmed transactions on the current blockchain.
 You can view the following information by switching tabs in this page:
 
 - **Transaction**: Displays the basic information of the transaction, such as the block, size, time stamp, as well as the transaction transfer record and the witness of the transaction.
-- **Notifications**: Displays the execution log of the smart contract in the transaction, including information such as whether the NEP-5 transfer was successful.
+- **Notifications**: Displays the execution log of the smart contract in the transaction, including information such as whether the NEP-17 transfer was successful.
 
 For information about the basic concept of transactions refer to [Transaction](../../basic/concept/transaction.md).
 

docs/en-us/reference/rpc/latest-version/api/getwalletbalance.md

@@ -57,4 +57,4 @@ balance: the balance of the asset in the wallet. Since the NEP-17 assets adopt t
 > [!Note]
 >
 > * Only when your client synchronizes to the block that the contract was deployed, execution of this API will return the correct value, otherwise execution of the API will result in an error.
-> * When the input parameter is a script hash of a non-NEP-5 smart contract, execution of the API will result in an error.
+> * When the input parameter is a script hash of a non-NEP-17 smart contract, execution of the API will result in an error.

docs/en-us/reference/scapi/framework/services/Contract/IsPayable.md

@@ -1,6 +1,6 @@
 # Contract.IsPayable
 
-Whether the contract is able to accept NEP-5 assets
+Whether the contract is able to accept NEP-17 assets
 
 Namespace: [Neo.SmartContract.Framework.Services](../../services.md)
 

docs/zh-cn/develop/deploy/deploy.md

@@ -10,7 +10,7 @@
 
 - 当一个智能合约有可变的传入参数，此时它必须作为一个类库，由调用者或者其它的智能合约提供参数。
 - 当一个智能合约使用存储区（Storage）时，必须作为一个类库。
-- 当一个智能合约实现了 NEP-5（合约资产）时，需要将该合约部署到区块链上。
+- 当一个智能合约实现了 NEP-17（合约资产）时，需要将该合约部署到区块链上。
 
 智能合约的部署是通过交易调用 API 来部署。通常的做法是通过 Neo-CLI 或 Neo-GUI 的智能合约发布功能来部署合约。
 

docs/zh-cn/develop/deploy/invoke.md

@@ -65,7 +65,7 @@ invoke <scriptHash> <operation> [contractParameters=null] [sender=null] [signerA
 
 > [!Note]
 >
-> 在通过转账命令调用 NEP-5 合约的 transfer 方法时，钱包会自动对 from 字段进行附加签名。此时不需要手动添加。
+> 在通过转账命令调用 NEP-17 合约的 transfer 方法时，钱包会自动对 from 字段进行附加签名。此时不需要手动添加。
 
 ## 合约之间的互相调用
 

docs/zh-cn/develop/tool/sdk/rpc.md

@@ -332,7 +332,7 @@ string wif = await client.DumpPrivKeyAsync("NVVwFw6XyhtRCFQ8SpUTMdPyYt4Vd9A1XQ")
 ```
 
 ### 余额查询
-根据指定的资产哈希，返回钱包中对应资产的余额信息。该方法适用于原生合约资产及符合 NEP-5 标准的合约资产：
+根据指定的资产哈希，返回钱包中对应资产的余额信息。该方法适用于原生合约资产及符合 NEP-17 标准的合约资产：
 
 ```c#
 BigDecimal balance = await client.GetWalletBalanceAsync(NativeContract.NEO.Hash.ToString()).ConfigureAwait(false);

docs/zh-cn/develop/write/nep17.md

@@ -165,7 +165,7 @@ transfer 事件变更为 Transfer 事件 （首字母大写）。
 
 ### IsPayable
 
-在 Neo Legacy 中部署合约时需要勾选 IsPayable 表示能否接收 NEP-5 资产。
+在 Neo Legacy 中部署合约时需要勾选 IsPayable 表示能否接收 NEP-17 资产。
 
 在 Neo N3 中移除了 payable 检查，相应逻辑将放到 `onNEP17Payment` 方法中。
 

docs/zh-cn/node/gui/blockchain.md

@@ -43,7 +43,7 @@
 在该页面切换选项卡可以查看以下信息：
 
 - **交易体**：显示交易的基本信息，如所在区块、大小、时间戳等，以及交易的转账记录和交易的见证人。
-- **交易日志**：显示交易中智能合约的执行日志，包括 NEP-5 转账是否成功等信息。
+- **交易日志**：显示交易中智能合约的执行日志，包括 NEP-17 转账是否成功等信息。
 
 关于交易的基本概念请参考 [交易](../../basic/concept/transaction.md)。
 

docs/zh-cn/reference/govapi/supportedStandards.md

@@ -21,7 +21,7 @@ var result = Contract.Call(nativeHash, "supportedStandards", new object[] { });
 	"type": "Array",
 	"value": [{
 		"type": "ByteString",
-		"value": "NEP-5"
+		"value": "NEP-17"
 	}, {
 		"type": "ByteString",
 		"value": "NEP-10"

docs/zh-cn/reference/scapi/framework/services/Contract/IsPayable.md

@@ -1,6 +1,6 @@
 # Contract.IsPayable 属性
 
-该合约能否接收 NEP-5 资产。
+该合约能否接收 NEP-17 资产。
 
 命名空间：[Neo.SmartContract.Framework.Services](../../services.md)
 
@@ -12,7 +12,7 @@
 public extern bool IsPayable
 ```
 
-属性值：布尔值，该合约能否接收 NEP-5 资产。
+属性值：布尔值，该合约能否接收 NEP-17 资产。