Update BoAT_User_Guide_en.md
fix the issue full text modification.
@@ -582,8 +582,7 @@ Token transfer from this account to other accounts (not all blockchain protocols
Take Ethereum as an example:
````
-BOAT_RESULT BoatEthTransfer(BoatEthTx *tx_ptr,
- BCHAR *value_hex_str);
+BOAT_RESULT BoatEthTransfer(BoatEthTx *tx_ptr, BCHAR *value_hex_str);
````
Parameters:
@@ -809,8 +808,7 @@ The manual construction of transactions needs to follow the ABI interface of the
-Set transaction parameter nonce:
```
-BOAT_RESULT BoatEthTxSetNonce(BoatEthTx *tx_ptr,
-BUINT64 nonce);
+BOAT_RESULT BoatEthTxSetNonce(BoatEthTx *tx_ptr, BUINT64 nonce);
```
Nonce is usually set to BOAT_ETH_NONCE_AUTO, and the nonce value is obtained from the network.
@@ -818,13 +816,11 @@ Nonce is usually set to BOAT_ETH_NONCE_AUTO, and the nonce value is obtained fro
-If necessary, set the "value" parameter of the transaction(in the initialized transaction object, value defaults to 0):
```
-BOAT_RESULT BoatEthTxSetValue(BoatEthTx *tx_ptr,
-BoatFieldMax32B *value_ptr);
+BOAT_RESULT BoatEthTxSetValue(BoatEthTx *tx_ptr, BoatFieldMax32B *value_ptr);
```
-**Step 3** For contract calls (transactions) that change the state of the blockchain, set the "data" parameter of the transaction:
```
-BOAT_RESULT BoatEthTxSetData(BoatEthTx *tx_ptr,
-BoatFieldVariable *data_ptr);
+BOAT_RESULT BoatEthTxSetData(BoatEthTx *tx_ptr, BoatFieldVariable *data_ptr);
```
Among them, the format of data_ptr follows the Ethereum ABI, including the first 4 bytes of the Keccak-256 hash of the contract function prototype as the Function Selector, and then the parameters are arranged in sequence:
<https://solidity.readthedocs.io/en/develop/abi-spec.html>
