Merge pull request #10686 from EOSIO/huangminghuang/revert-incorret-doc

Revert the incorrect doc changes from PR #10657

docs/01_nodeos/02_usage/03_development-environment/10_local-single-node-testnet-consensus.md

@@ -5,7 +5,7 @@ link_text: Local Single-Node Testnet With Consensus Protocol
 
 ## Goal
 
-This section describes how to set up a single-node blockchain configuration running on a single host with [consensus protocol](https://developers.eos.io/welcome/v2.2/protocol/consensus_protocol) enabled.  This is referred to as a _**single host, single-node testnet with consensus**_.  We will set up one node on your local computer and have it produce blocks. The following diagram depicts the desired single host testnet.
+This section describes how to set up a single-node blockchain configuration running on a single host with [consensus protocol](https://developers.eos.io/welcome/latest/protocol/consensus_protocol) enabled.  This is referred to as a _**single host, single-node testnet with consensus**_.  We will set up one node on your local computer and have it produce blocks. The following diagram depicts the desired single host testnet.
 
 ![Single host single node testnet](single-host-single-node-testnet.png)
 

docs/01_nodeos/02_usage/03_development-environment/index.md

@@ -21,7 +21,7 @@ This is the go-to option for smart contract developers, aspiring Block Producers
 While this option can technically be used for smart contract development, it may be overkill. This is most beneficial for those who are working on aspects of core development, such as benchmarking, optimization and experimentation. It's also a good option for hands-on learning and concept proofing.
 
 * [Configure Nodeos as a Local Two-Node Testnet](20_local-multi-node-testnet.md)
-* [Configure Nodeos as a Local 21-Node Testnet](https://developers.eos.io/welcome/v2.2/tutorials/bios-boot-sequence)
+* [Configure Nodeos as a Local 21-Node Testnet](https://developers.eos.io/welcome/latest/tutorials/bios-boot-sequence)
 
 ## Official Testnet
 

docs/01_nodeos/03_plugins/net_api_plugin/index.md

@@ -8,7 +8,7 @@ The `net_api_plugin` provides four RPC API endpoints:
 * connections
 * status
 
-See [Net API Reference Documentation](https://developers.eos.io/manuals/eos/v2.2/nodeos/plugins/net_api_plugin/api-reference/index).
+See [Net API Reference Documentation](https://developers.eos.io/manuals/eos/latest/nodeos/plugins/net_api_plugin/api-reference/index).
 
 [[caution | Caution]]
 | This plugin exposes endpoints that allow management of p2p connections. Running this plugin on a publicly accessible node is not recommended as it can be exploited.

docs/01_nodeos/07_features/15_private_chain_access/05_tutorial.md

@@ -372,7 +372,7 @@ info  2021-07-09T19:55:01.424 thread-0  producer_plugin.cpp:428       on_incomin
 At this point, all nodes `node4` (bios node), `node1`, `node2`, and `node3` should be communicating securely using TLS. This is evident from the logs which show successful handshakes and nodes 1 to 3 receiving the first blocks from bios node 4. Note, however, that only the bios node is producing so far.
 
 [[info | Note]]
-| To create a fully operational private network with multiple producing nodes, you need to synchronize the generation of the certificate files among all producer participants according to a mutually established "chain of trust", then pass the certificate files at the time each node is launched using the `p2p-tls-***` parameters and perform a similar procedure to the [bios-boot-tutorial.py](https://github.com/EOSIO/eos/blob/develop/tutorials/bios-boot-tutorial/bios-boot-tutorial.py) script from the [Bios Boot Sequence](https://developers.eos.io/welcome/v2.2/tutorials/bios-boot-sequence) tutorial.
+| To create a fully operational private network with multiple producing nodes, you need to synchronize the generation of the certificate files among all producer participants according to a mutually established "chain of trust", then pass the certificate files at the time each node is launched using the `p2p-tls-***` parameters and perform a similar procedure to the [bios-boot-tutorial.py](https://github.com/EOSIO/eos/blob/develop/tutorials/bios-boot-tutorial/bios-boot-tutorial.py) script from the [Bios Boot Sequence](https://developers.eos.io/welcome/latest/tutorials/bios-boot-sequence) tutorial.
 
 2. Activate required EOSIO protocol features:
 

docs/01_nodeos/08_troubleshooting/index.md

@@ -46,4 +46,4 @@ cleos --url http://localhost:8888 get info | grep server_version
 
 ### Error 3070000: WASM Exception Error
 
-If you try to deploy the `eosio.bios` contract or `eosio.system` contract in an attempt to boot an EOSIO-based blockchain and you get the following error or similar: `Publishing contract... Error 3070000: WASM Exception Error Details: env.set_proposed_producers_ex unresolveable`, it is because you have to activate the `PREACTIVATE_FEATURE` protocol first. More details about it and how to enable it can be found in the [Bios Boot Sequence Tutorial](https://developers.eos.io/welcome/v2.2/tutorials/bios-boot-sequence/#112-set-the-eosiosystem-contract). For more information, you may also visit the [Nodeos Upgrade Guides](https://developers.eos.io/manuals/eos/v2.2/nodeos/upgrade-guides/).
+If you try to deploy the `eosio.bios` contract or `eosio.system` contract in an attempt to boot an EOSIO-based blockchain and you get the following error or similar: `Publishing contract... Error 3070000: WASM Exception Error Details: env.set_proposed_producers_ex unresolveable`, it is because you have to activate the `PREACTIVATE_FEATURE` protocol first. More details about it and how to enable it can be found in the [Bios Boot Sequence Tutorial](https://developers.eos.io/welcome/latest/tutorials/bios-boot-sequence/#112-set-the-eosiosystem-contract). For more information, you may also visit the [Nodeos Upgrade Guides](https://developers.eos.io/manuals/eos/latest/nodeos/upgrade-guides/).

docs/02_cleos/02_how-to-guides/how-to-create-a-wallet.md

@@ -13,9 +13,9 @@ Make sure you meet the following requirements:
 [[info | Note]]
 | `cleos` is bundled with the EOSIO software. [Installing EOSIO](../../00_install/index.md) will also install `cleos`.
 
-* Understand what an [account](https://developers.eos.io/welcome/v2.2/glossary/index/#account) is and its role in the blockchain.
-* Understand [Accounts and Permissions](https://developers.eos.io/welcome/v2.2/protocol-guides/accounts_and_permissions) in the protocol documents.
-* Understand what a [public](https://developers.eos.io/welcome/v2.2/glossary/index/#public-key) and [private](https://developers.eos.io/welcome/v2.2/glossary/index/#private-key) key pair is.
+* Understand what an [account](https://developers.eos.io/welcome/latest/glossary/index/#account) is and its role in the blockchain.
+* Understand [Accounts and Permissions](https://developers.eos.io/welcome/latest/protocol-guides/accounts_and_permissions) in the protocol documents.
+* Understand what a [public](https://developers.eos.io/welcome/latest/glossary/index/#public-key) and [private](https://developers.eos.io/welcome/latest/glossary/index/#private-key) key pair is.
 
 ## Steps
 

docs/02_cleos/02_how-to-guides/how-to-delegate-CPU-resource.md

@@ -13,9 +13,9 @@ Make sure you meet the following requirements:
 | `cleos` is bundled with the EOSIO software. [Installing EOSIO](../../00_install/index.md) will also install `cleos`.
 
 * Ensure the reference system contracts from [`eosio.contracts`](https://github.com/EOSIO/eosio.contracts) repository is deployed and used to manage system resources.
-* Understand what an [account](https://developers.eos.io/welcome/v2.2/glossary/index/#account) is and its role in the blockchain.
-* Understand [CPU bandwidth](https://developers.eos.io/welcome/v2.2/glossary/index/#cpu) in an EOSIO blockchain.
-* Understand [NET bandwidth](https://developers.eos.io/welcome/v2.2/glossary/index/#net) in an EOSIO blockchain.
+* Understand what an [account](https://developers.eos.io/welcome/latest/glossary/index/#account) is and its role in the blockchain.
+* Understand [CPU bandwidth](https://developers.eos.io/welcome/latest/glossary/index/#cpu) in an EOSIO blockchain.
+* Understand [NET bandwidth](https://developers.eos.io/welcome/latest/glossary/index/#net) in an EOSIO blockchain.
 
 ## Steps
 

docs/02_cleos/02_how-to-guides/how-to-delegate-net-resource.md

@@ -13,9 +13,9 @@ Make sure you meet the following requirements:
 | `cleos` is bundled with the EOSIO software. [Installing EOSIO](../../00_install/index.md) will also install `cleos`.
 
 * Ensure the reference system contracts from [`eosio.contracts`](https://github.com/EOSIO/eosio.contracts) repository is deployed and used to manage system resources.
-* Understand what an [account](https://developers.eos.io/welcome/v2.2/glossary/index/#account) is and its role in the blockchain.
-* Understand [NET bandwidth](https://developers.eos.io/welcome/v2.2/glossary/index/#net) in an EOSIO blockchain.
-* Understand [CPU bandwidth](https://developers.eos.io/welcome/v2.2/glossary/index/#cpu) in an EOSIO blockchain.
+* Understand what an [account](https://developers.eos.io/welcome/latest/glossary/index/#account) is and its role in the blockchain.
+* Understand [NET bandwidth](https://developers.eos.io/welcome/latest/glossary/index/#net) in an EOSIO blockchain.
+* Understand [CPU bandwidth](https://developers.eos.io/welcome/latest/glossary/index/#cpu) in an EOSIO blockchain.
 
 ## Steps
 

docs/02_cleos/02_how-to-guides/how-to-get-block-information.md

@@ -12,8 +12,8 @@ Make sure to meet the following requirements:
 [[info | Note]]
 | `cleos` is bundled with the EOSIO software. [Installing EOSIO](../../00_install/index.md) will also install `cleos`.
 
-* Understand what a [block](https://developers.eos.io/welcome/v2.2/glossary/index/#block) is and its role in the blockchain.
-* Understand the [block lifecycle](https://developers.eos.io/welcome/v2.2/protocol-guides/consensus_protocol/#5-block-lifecycle) in the EOSIO consensus protocol.
+* Understand what a [block](https://developers.eos.io/welcome/latest/glossary/index/#block) is and its role in the blockchain.
+* Understand the [block lifecycle](https://developers.eos.io/welcome/latest/protocol-guides/consensus_protocol/#5-block-lifecycle) in the EOSIO consensus protocol.
 
 ## Steps
 

docs/02_cleos/02_how-to-guides/how-to-get-transaction-information.md

@@ -10,7 +10,7 @@ Make sure you meet the following requirements:
 * Install the currently supported version of `cleos`.
 [[info | Note]]
 | `cleos` is bundled with the EOSIO software. [Installing EOSIO](../../00_install/index.md) will also install `cleos`.
-* Understand how transactions work in an EOSIO blockchain. For more information on transactions, see the [Transactions Protocol](https://developers.eos.io/welcome/v2.2/protocol-guides/transactions_protocol) section.
+* Understand how transactions work in an EOSIO blockchain. For more information on transactions, see the [Transactions Protocol](https://developers.eos.io/welcome/latest/protocol-guides/transactions_protocol) section.
 
 ## Command Reference
 

docs/02_cleos/02_how-to-guides/how-to-import-a-key.md

@@ -12,7 +12,7 @@ Make sure you meet the following requirements:
 * Install the currently supported version of `cleos`.
 [[info | Note]]
 | `cleos` is bundled with the EOSIO software. [Installing EOSIO](../../00_install/index.md) will also install `cleos`.
-* Understand what a [public key](https://developers.eos.io/welcome/v2.2/glossary/index/#public-key) and [private key](https://developers.eos.io/welcome/v2.2/glossary/index/#private-key) is.
+* Understand what a [public key](https://developers.eos.io/welcome/latest/glossary/index/#public-key) and [private key](https://developers.eos.io/welcome/latest/glossary/index/#private-key) is.
 
 ## Command Reference
 

docs/02_cleos/02_how-to-guides/how-to-list-all-key-pairs.md

@@ -14,7 +14,7 @@ Make sure you meet the following requirements:
 * Install the currently supported version of `cleos`.
 [[info | Note]]
 | `cleos` is bundled with the EOSIO software. [Installing EOSIO](../../00_install/index.md) will also install `cleos`.
-* Understand what a [public key](https://developers.eos.io/welcome/v2.2/glossary/index/#public-key) and [private key](https://developers.eos.io/welcome/v2.2/glossary/index/#private-key) is.
+* Understand what a [public key](https://developers.eos.io/welcome/latest/glossary/index/#public-key) and [private key](https://developers.eos.io/welcome/latest/glossary/index/#private-key) is.
 
 ## Command Reference
 

docs/02_cleos/02_how-to-guides/how-to-stake-resource.md

@@ -9,16 +9,16 @@ This how-to guide provides instructions on how to stake resources, NET and/or CP
 * Ensure the [reference system contracts](https://developers.eos.io/manuals/eosio.contracts/v1.9/build-and-deploy) are deployed and used to manage system resources.
 
 * Understand the following:
-  * What an [account](https://developers.eos.io/welcome/v2.2/glossary/index/#account) is.
+  * What an [account](https://developers.eos.io/welcome/latest/glossary/index/#account) is.
   * What [NET bandwidth](https://developers.eos.io/manuals/eosio.contracts/latest/key-concepts/net) is.
   * What [CPU bandwidth](https://developers.eos.io/manuals/eosio.contracts/latest/key-concepts/cpu) is.
-  * The [`delegatebw` cleos sub-command](https://developers.eos.io/manuals/eos/v2.2/cleos/command-reference/system/system-delegatebw).
+  * The [`delegatebw` cleos sub-command](https://developers.eos.io/manuals/eos/latest/cleos/command-reference/system/system-delegatebw).
 
 ## Command Reference
 
 See the following reference guides for command line usage and related options for the `cleos` command:
 
-* The [`delegatebw` cleos sub-command](https://developers.eos.io/manuals/eos/v2.2/cleos/command-reference/system/system-delegatebw).
+* The [`delegatebw` cleos sub-command](https://developers.eos.io/manuals/eos/latest/cleos/command-reference/system/system-delegatebw).
 
 ## Procedure
 

docs/02_cleos/02_how-to-guides/how-to-submit-a-sponsored-transaction.del

@@ -7,17 +7,17 @@ This how-to guide provides instructions on how to submit, or push, a sponsored t
 * Install the currently supported version of `cleos`
 
 * Understand the following:
-  * What a [transaction](https://developers.eos.io/welcome/v2.2/glossary/index/#transaction) is.
+  * What a [transaction](https://developers.eos.io/welcome/latest/glossary/index/#transaction) is.
   * How to generate a valid transaction JSON.
-    * Consult [cleos push transaction](https://developers.eos.io/manuals/eos/v2.2/cleos/command-reference/push/push-transaction) reference, and pay attention to option `-d` and `-j`.
-    * Consult [push transaction](https://developers.eos.io/manuals/eos/v2.2/nodeos/plugins/chain_api_plugin/api-reference/index#operation/push_transaction) endpoint for chain api plug-in, and pay attention to the payload definition.
+    * Consult [cleos push transaction](https://developers.eos.io/manuals/eos/latest/cleos/command-reference/push/push-transaction) reference, and pay attention to option `-d` and `-j`.
+    * Consult [push transaction](https://developers.eos.io/manuals/eos/latest/nodeos/plugins/chain_api_plugin/api-reference/index#operation/push_transaction) endpoint for chain api plug-in, and pay attention to the payload definition.
   * [How To Submit A Transaction](./how-to-submit-a-transaction).
 
 ## Command Reference
 
 See the following reference guides for command line usage and related options for the `cleos` command:
 
-* The [cleos push transaction](https://developers.eos.io/manuals/eos/v2.2/cleos/command-reference/push/push-transaction) reference.
+* The [cleos push transaction](https://developers.eos.io/manuals/eos/latest/cleos/command-reference/push/push-transaction) reference.
 
 ## Procedure
 

docs/02_cleos/02_how-to-guides/how-to-submit-a-transaction.md

@@ -7,16 +7,16 @@ This how-to guide provides instructions on how to submit, or push, a transaction
 * Install the currently supported version of `cleos`
 
 * Understand the following:
-  * What a [transaction](https://developers.eos.io/welcome/v2.2/glossary/index/#transaction) is.
+  * What a [transaction](https://developers.eos.io/welcome/latest/glossary/index/#transaction) is.
   * How to generate a valid transaction JSON.
-    * Consult [cleos push transaction](https://developers.eos.io/manuals/eos/v2.2/cleos/command-reference/push/push-transaction) reference, and pay attention to option `-d` and `-j`.
-    * Consult [push transaction](https://developers.eos.io/manuals/eos/v2.2/nodeos/plugins/chain_api_plugin/api-reference/index#operation/push_transaction) endpoint for chain api plug-in, and pay attention to the payload definition.
+    * Consult [cleos push transaction](https://developers.eos.io/manuals/eos/latest/cleos/command-reference/push/push-transaction) reference, and pay attention to option `-d` and `-j`.
+    * Consult [push transaction](https://developers.eos.io/manuals/eos/latest/nodeos/plugins/chain_api_plugin/api-reference/index#operation/push_transaction) endpoint for chain api plug-in, and pay attention to the payload definition.
 
 ## Command Reference
 
 See the following reference guides for command line usage and related options for the `cleos` command:
 
-* The [cleos push transaction](https://developers.eos.io/manuals/eos/v2.2/cleos/command-reference/push/push-transaction) reference.
+* The [cleos push transaction](https://developers.eos.io/manuals/eos/latest/cleos/command-reference/push/push-transaction) reference.
 
 ## Procedure
 

docs/02_cleos/02_how-to-guides/how-to-transfer-an-eosio.token-token.md

@@ -9,14 +9,14 @@ This how-to guide provides instructions on how to transfer tokens created by `eo
 * `eosio.token` contract is deployed on the network you are connected to.
 
 * Understand the following:
-  * What a [transaction](https://developers.eos.io/welcome/v2.2/glossary/index/#transaction) is.
+  * What a [transaction](https://developers.eos.io/welcome/latest/glossary/index/#transaction) is.
   * Token transfers are irreversible.
 
 ## Command Reference
 
 See the following reference guides for command line usage and related options for the `cleos` command:
 
-* The [cleos transfer](https://developers.eos.io/manuals/eos/v2.2/cleos/command-reference/transfer) reference.
+* The [cleos transfer](https://developers.eos.io/manuals/eos/latest/cleos/command-reference/transfer) reference.
 
 ## Procedure
 

docs/02_cleos/02_how-to-guides/how-to-vote.md

@@ -9,7 +9,7 @@ This how-to guide provides instructions on how to vote for block producers.
 * Ensure the [reference system contracts](https://developers.eos.io/manuals/eosio.contracts/latest/build-and-deploy) are deployed and used to manage system resources.
 
 * Understand the following:
-  * What is a [block producer](https://developers.eos.io/welcome/v2.2/protocol/consensus_protocol#11-block-producers).
+  * What is a [block producer](https://developers.eos.io/welcome/latest/protocol/consensus_protocol#11-block-producers).
   * How does [voting](https://developers.eos.io/manuals/eosio.contracts/latest/key-concepts/vote) work.
 
 * Unlock your wallet.
@@ -18,7 +18,7 @@ This how-to guide provides instructions on how to vote for block producers.
 
 See the following reference guides for command line usage and related options for the `cleos` command:
 
-* The [cleos system voteproducer prods](https://developers.eos.io/manuals/eos/v2.2/cleos/command-reference/system/system-voteproducer-prods) reference.
+* The [cleos system voteproducer prods](https://developers.eos.io/manuals/eos/latest/cleos/command-reference/system/system-voteproducer-prods) reference.
 
 ## Procedure
 

docs/02_cleos/03_command-reference/net/peers.md

@@ -109,4 +109,4 @@ cleos -u http://127.0.0.1:8001 net peers
 ]
 ```
 
-**Note:** The `last_handshake` field contains the chain state of each connected peer as of the last handshake message with the node. For more information read the [Handshake Message](https://developers.eos.io/welcome/v2.2/protocol/network_peer_protocol#421-handshake-message) in the *Network Peer Protocol* document.
+**Note:** The `last_handshake` field contains the chain state of each connected peer as of the last handshake message with the node. For more information read the [Handshake Message](https://developers.eos.io/welcome/latest/protocol/network_peer_protocol#421-handshake-message) in the *Network Peer Protocol* document.

docs/02_cleos/03_command-reference/net/status.md

@@ -63,4 +63,4 @@ cleos -u http://127.0.0.1:8002 net status localhost:9001
 }
 ```
 
-**Note:** The `last_handshake` field contains the chain state of the specified peer as of the last handshake message with the node. For more information read the [Handshake Message](https://developers.eos.io/welcome/v2.2/protocol/network_peer_protocol#421-handshake-message) in the *Network Peer Protocol* document.
+**Note:** The `last_handshake` field contains the chain state of the specified peer as of the last handshake message with the node. For more information read the [Handshake Message](https://developers.eos.io/welcome/latest/protocol/network_peer_protocol#421-handshake-message) in the *Network Peer Protocol* document.