EOSIO · nksanthosh · Jul 7, 2021 · Jan 4, 2021 · Jan 4, 2021 · Jan 5, 2021
diff --git a/.gitmodules b/.gitmodules
@@ -9,6 +9,7 @@
 [submodule "eosio_llvm"]
 	path = eosio_llvm
 	url = /~https://github.com/eosio/llvm
+	branch = eosio
 [submodule "libraries/native/softfloat"]
 	path = libraries/native/softfloat
 	url = /~https://github.com/EOSIO/berkeley-softfloat-3.git
diff --git a/docs/02_installation/index.md b/docs/02_installation/index.md
@@ -22,8 +22,8 @@ brew remove eosio.cdt
 ## Debian Package Install
 
 ```sh
-wget /~https://github.com/EOSIO/eosio.cdt/releases/download/v1.8.0/eosio.cdt_1.8.0-1-ubuntu-18.04_amd64.deb
-sudo apt install ./eosio.cdt_1.8.0-1-ubuntu-18.04_amd64.deb
+wget /~https://github.com/EOSIO/eosio.cdt/releases/download/v1.8.0-rc1/eosio.cdt_1.8.0-rc1-ubuntu-18.04_amd64.deb
+sudo apt install ./eosio.cdt_1.8.0-rc1-ubuntu-18.04_amd64.deb
 ```
 
 ## Debian Package Uninstall
@@ -35,8 +35,8 @@ sudo apt remove eosio.cdt
 ## RPM Package Install
 
 ```sh
-wget /~https://github.com/EOSIO/eosio.cdt/releases/download/v1.8.0/eosio.cdt-1.8.0-1.el7.x86_64.rpm
-sudo yum install ./eosio.cdt-1.8.0-1.el7.x86_64.rpm
+wget /~https://github.com/EOSIO/eosio.cdt/releases/download/v1.8.0-rc1/eosio.cdt-1.8.0-rc1.el7.x86_64.rpm
+sudo yum install ./eosio.cdt-1.8.0-rc1.el7.x86_64.rpm
 ```
 
 ## RPM Package Uninstall

diff --git a/docs/03_command-reference/eosio-cc.md b/docs/03_command-reference/eosio-cc.md
@@ -71,4 +71,5 @@ compiler options:
   -sysroot=<string>        - Set the system root directory
   -v                       - Show commands to run and use verbose output
   -w                       - Suppress all warnings
+  --warn-action-read-only  - Issue a warning if a read-only action uses a write API and continue compilation
 ```
diff --git a/docs/03_command-reference/eosio-cpp.md b/docs/03_command-reference/eosio-cpp.md
@@ -72,6 +72,7 @@ compiler options:
   -v                       - Show commands to run and use verbose output
   -w                       - Suppress all warnings
   -no-missing-ricardian-clause - Defaults to false, disables warnings for missing Ricardian clauses
+  --warn-action-read-only  - Issue a warning if a read-only action uses a write API and continue compilation
 ```
 
 ## Notes

diff --git a/docs/05_features/10_resource_payer.md b/docs/05_features/10_resource_payer.md
@@ -0,0 +1,46 @@
+---
+content_title: Resource Payer
+---
+
+## Overview
+
+The *Resource Payer* feature, also known as *Transaction Sponsorship*, allows to specify the resource payer for a transaction. As a direct consequence the application developers have a simple and secure way to sponsor, or decline to sponsor, transactions on behalf of their users.
+
+## Concept
+
+Before the `EOSIO 2.2` version, the CPU and NET resource costs for transactions on EOSIO-based blockchains were paid by the end users of the application. This fact made attracting and onboarding new users difficult.
+
+The *Resource Payer* feature makes it easier for both smart contract and full stack developers on EOSIO-based blockchains to allow their users to transact without having to pay for CPU and NET resource costs in a simple and secure manner. This new feature makes the process of onboarding new users straightforward.
+
+Blockchain application developers can use the *Resource Payer* on any EOSIO-based blockchain that enables it via the newly introduced `RESOURCE_PAYER` upgrade protocol feature.
+
+### Related Concepts
+
+A [transaction](https://developers.eos.io/welcome/latest/glossary/index/#transaction) consists of one or more actions executed atomically on the blockchain which alter the state of the blockchain.
+
+You need system resources, [CPU](https://developers.eos.io/welcome/latest/glossary/index/#cpu) and [NET](https://developers.eos.io/welcome/latest/glossary/index/#net), to be able to execute transactions.
+
+The *Resource Payer* feature allows the application developers to designate the payer of the CPU and NET resources cost to a random blockchain [account](https://developers.eos.io/welcome/latest/glossary/index/#account).
+
+The *Resource Payer* feature is not available by default. To enable the feature, the `RESOURCE_PAYER` upgrade protocol feature must be enabled. For more information about upgrading protocol features, read the [Consensus Protocol Upgrade Process](https://developers.eos.io/manuals/eos/latest/nodeos/upgrade-guides/1.8-upgrade-guide/#upgrade-process-for-all-eosio-networks-including-test-networks) documentation.
+
+When you send the transaction to the blockchain, if you want to designate the resource payer, you must specify in the transaction definition the payer information which consists of the following:
+
+* The payer account name
+* The maximum CPU limit amount the payer supports expressed in microseconds
+* The maximum NET limit amount the payer supports expressed in bytes
+
+The resource payer information must be defined as a transaction extension and placed in the transaction’s extension list. For more details please see the examples provided in the following section.
+
+## Examples
+
+Find below one example that illustrate how to send transaction to the blockchain which contain resource payer information.
+
+### EOSJS
+
+To send a transaction to the blockchain using javascript via the `eosjs` library, follow the [How To Send A Transaction](https://developers.eos.io/manuals/eos/latest/cleos/how-to-guides/how-to-submit-a-transaction) steps and note in the json example the resource payer information set in the ``transaction_extensions`` field.
+
+### Cleos
+
+[[info | Cleos Support Will Be Available Starting With v2.2 RC2 Onwards]]
+| The ability to send transaction with resource payer information using `cleos` will be added in the v2.2 RC2 release version.
diff --git a/...ractices/12_return_values_from_actions.md → ...features/20_return_values_from_actions.md b/...ractices/12_return_values_from_actions.md → ...features/20_return_values_from_actions.md
diff --git a/.../05_best-practices/13_binary-extension.md → docs/05_features/30_binary-extension.md b/.../05_best-practices/13_binary-extension.md → docs/05_features/30_binary-extension.md
@@ -1,5 +1,5 @@
 ---
-content_title: The eosio::binary_extension type
+content_title: The eosio::binary_extension Type
 ---
 
 Let's fully explain what the `eosio::binary_extension` type is, what it does, and why we need it for contract upgrades in certain situations.
@@ -327,7 +327,7 @@ struct [[eosio::table]] structure {
 }
 ```
 
-And their corresponding sections in the `.abi` files:
+Find below their corresponding sections in the `.abi` files:
 
 **binary_extension_contract.abi**
 

diff --git a/...practices/10_native-tester-compilation.md → ..._features/40_native-tester-compilation.md b/...practices/10_native-tester-compilation.md → ..._features/40_native-tester-compilation.md
@@ -1,5 +1,5 @@
 ---
-content_title: How to use native tester/compilation
+content_title: Native Tester And Compilation
 ---
 
 As of v1.5.0 native compilation can be performed and a new set of libraries to facilitate native testing and native "scratch pad" compilation. [`eosio-cc`](../03_command-reference/eosio-cc.md), [`eosio-cpp`](../03_command-reference/eosio-cpp.md) and [`eosio-ld`](../03_command-reference/eosio-ld.md) now support building "smart contracts" and unit tests natively for quick tests to help facilitate faster development \(note the default implementations of eosio `intrinsics` are currently asserts that state they are unavailable, these are user definable.\)

diff --git a/...est-practices/09_deferred_transactions.md → docs/05_features/99_deferred_transactions.md b/...est-practices/09_deferred_transactions.md → docs/05_features/99_deferred_transactions.md
@@ -1,5 +1,5 @@
 ---
-content_title: Deferred transactions
+content_title: Deferred Transactions
 ---
 
 Deferred communication conceptually takes the form of action notifications sent to a peer transaction. Deferred actions get scheduled to run, at best, at a later time, at the producer's discretion. There is no guarantee that a deferred action will be executed.

diff --git a/docs/06_how-to-guides/10_compile/01_compile-a-contract-via-cli.md b/docs/06_how-to-guides/10_compile/01_compile-a-contract-via-cli.md
@@ -10,7 +10,7 @@ This guide provides instructions how to compile a smart contract using the comma
 
 See the following code reference:
 
-* The [`eosio-cpp`](https://developers.eos.io/manuals/eosio.cdt/latest/command-reference/eosio-cpp) tool.
+* The [`eosio-cpp`](https://developers.eos.io/manuals/eosio.cdt/v1.8/command-reference/eosio-cpp) tool.
 
 ## Before you begin
 
@@ -32,11 +32,11 @@ Follow the following steps to compile your contract.
     ```
 
     Where:
-    - `eosio-cpp` = Is the [`eosio-cpp`](https://developers.eos.io/manuals/eosio.cdt/latest/command-reference/eosio-cpp) tool.
+    - `eosio-cpp` = Is the [`eosio-cpp`](https://developers.eos.io/manuals/eosio.cdt/v1.8/command-reference/eosio-cpp) tool.
     - `-abigen` = It instructs the `eosio-cpp` tool to generate ABI file.
     - `../src/hello.cpp` = Is the input cpp source file to be compiled.
     - `-o hello.wasm` = It instructs the `eosio-cpp` tool who to name the output wasm file.
-    - `-I ../include/` = It tells `eosio-cpp` tool what the include folder path is, in this particular case it is relative path.
+    - `-I ../include/` = It tells `eosio-cpp` tool what the include folder path is, in this particular case it is a relative path.
 
 3. Verify the following two files were generated:
 

diff --git a/docs/06_how-to-guides/10_compile/03_compiling-contracts-with-cmake.md b/docs/06_how-to-guides/10_compile/03_compiling-contracts-with-cmake.md
@@ -4,7 +4,7 @@ content_title: How to compile a smart contract with CMake
 
 ## Overview
 
-This guide provides instructions on how to compile a smart contract with CMake.
+This guide provides instructions to compile a smart contract with CMake.
 
 ## Before you begin
 

diff --git a/...6_how-to-guides/20_authorization/how_to_restrict_access_to_an_action_by_user.md b/...6_how-to-guides/20_authorization/how_to_restrict_access_to_an_action_by_user.md
@@ -16,10 +16,10 @@ This guide provides instructions how to perform authorization checks in a smart
 
 See the following code reference guides for functions which can be used to implement authorization checks in a smart contract:
 
-* function [has_auth(name n)](https://developers.eos.io/manuals/eosio.cdt/v1.8/namespaceeosio#function-has_auth)
-* function [require_auth(name n)](https://developers.eos.io/manuals/eosio.cdt/v1.8/namespaceeosio/#function-require_auth-12)
+* function [has_auth(name n)](https://developers.eos.io/manuals/eosio.cdt/latest/namespaceeosio#function-has_auth)
+* function [require_auth(name n)](https://developers.eos.io/manuals/eosio.cdt/latest/namespaceeosio/#function-require_auth-12)
 * function [require_auth2(capi_name name, capi_name permission)](https://developers.eos.io/manuals/eosio.cdt/v1.8/group__action__c#function-require_auth2)
-* function [check(bool pred, ...)](https://developers.eos.io/manuals/eosio.cdt/v1.8/group__system/#function-check)
+* function [check(bool pred, ...)](https://developers.eos.io/manuals/eosio.cdt/latest/group__system/#function-check)
 
 ## Procedure
 

diff --git a/docs/06_how-to-guides/30_key-value-api/index.md b/docs/06_how-to-guides/30_key-value-api/index.md
@@ -12,7 +12,7 @@ The Key-Value API provides a set of C++ classes and structures which facilitates
 
 ## Concept
 
-The Key-Value API, or KV API, is a new option for developers to create datastore key value tables on-chain. KV API is more flexible than multi-index and allows developers to search the table in a more human-readable way, unlike multi-index tables where search is over 64-bit values.
+The Key-Value API, or KV API, is a new option for developers to create datastore key value tables on-chain. KV API is more flexible than multi-index and allows developers to search for the table in a more human-readable way, unlike multi-index tables where search is over 64-bit values.
 
 On top of flexibility, this new API has a simpler interface and it helps the developer to avoid complex C++ templates constructs.
 

diff --git a/docs/06_how-to-guides/30_key-value-api/kv_map/10_how-to-use-kv-map.md b/docs/06_how-to-guides/30_key-value-api/kv_map/10_how-to-use-kv-map.md
@@ -19,15 +19,15 @@ To accomplish this task do the following:
 
 See the following code reference:
 
-* The [`kv::map`](https://developers.eos.io/manuals/eosio.cdt/v1.8/classeosio_1_1kv_1_1map) class.
+* The [`kv::map`](https://developers.eos.io/manuals/eosio.cdt/latest/classeosio_1_1kv_1_1map) class.
 
 ## Before you begin
 
 Make sure you have the following prerequisites in place:
 
 * An EOSIO development environment, for details consult the [Get Started Guide](https://developers.eos.io/welcome/latest/getting-started-guide/index)
 * A smart contract named `smrtcontract`
-* A user defined type named `person`, which defines the data stored in the map
+* A user defined type, `struct` or `class`, which defines the data stored in the map, named `person`
 
 Refer to the following reference implementation for your starting point:
 
@@ -83,6 +83,4 @@ In conclusion, the above instructions show how to define and use a `Key-Value Ma
 
 ## Next Steps
 
-The following option is available when you complete the procedure:
-
 * You [can add values](30_how-to-upsert-into-kv-map.md) in the map object created.
diff --git a/docs/06_how-to-guides/30_key-value-api/kv_map/30_how-to-upsert-into-kv-map.md b/docs/06_how-to-guides/30_key-value-api/kv_map/30_how-to-upsert-into-kv-map.md
@@ -13,7 +13,7 @@ Make sure you have the following prerequisites in place:
 
 * An EOSIO development environment, for details consult the [Get Started Guide](https://developers.eos.io/welcome/latest/getting-started-guide/index)
 * A smart contract named `smrtcontract`
-* A user defined type named `person`, which defines the data stored in the map
+* A user defined type, `struct` or `class`, which defines the data stored in the map, named `person`
 * A `kv map` object, name `my_map`, which stores objects of type `person`, with unique keys of type `int`
 
 Refer to the following reference implementation for your starting point:
@@ -111,7 +111,5 @@ In conclusion, the above instructions show how to upsert into `Key-Value Map` (`
 
 ## Next Steps
 
-The following options are available when you complete the procedure:
-
 * [Verify](70_how-to-find-in-kv-map.md) if the newly inserted `person` actually exists in the map. To accomplish this task use the `find()` function of the `kv_map`.
 * [Delete](40_how-to-delete-from-kv-map.md) the newly created or updated `person` from the map. To accomplish this task, use the `erase()` function of the `kv map`.
diff --git a/docs/06_how-to-guides/30_key-value-api/kv_map/40_how-to-delete-from-kv-map.md b/docs/06_how-to-guides/30_key-value-api/kv_map/40_how-to-delete-from-kv-map.md
@@ -13,7 +13,7 @@ Make sure you have the following prerequisites in place:
 
 * An EOSIO development environment, for details consult the [Get Started Guide](https://developers.eos.io/welcome/latest/getting-started-guide/index)
 * A smart contract named `smrtcontract`
-* A user defined type named `person`, which defines the data stored in the map
+* A user defined type, `struct` or `class`, which defines the data stored in the map, named `person`
 * A `kv map` object, name `my_map`, which stores objects of type `person`, with unique keys of type `int`
 
 Refer to the following reference implementation for your starting point:

diff --git a/docs/06_how-to-guides/30_key-value-api/kv_map/50_how-to-iterate-kv-map.md b/docs/06_how-to-guides/30_key-value-api/kv_map/50_how-to-iterate-kv-map.md
@@ -13,7 +13,7 @@ Make sure you have the following prerequisites in place:
 
 * An EOSIO development environment, for details consult the [Get Started Guide](https://developers.eos.io/welcome/latest/getting-started-guide/index)
 * A smart contract named `smrtcontract`
-* A user defined type named `person`, which defines the data stored in the map
+* A user defined type, `struct` or `class`, which defines the data stored in the map, named `person`
 * A `kv map` object, name `my_map`, which stores objects of type `person`, with unique keys of type `int`.
 
 Refer to the following reference implementation for your starting point:

diff --git a/docs/06_how-to-guides/30_key-value-api/kv_map/70_how-to-find-in-kv-map.md b/docs/06_how-to-guides/30_key-value-api/kv_map/70_how-to-find-in-kv-map.md
@@ -13,7 +13,7 @@ Make sure you have the following prerequisites in place:
 
 * An EOSIO development environment, for details consult the [Get Started Guide](https://developers.eos.io/welcome/latest/getting-started-guide/index)
 * A smart contract named `smrtcontract`
-* A user defined type named `person`, which defines the data stored in the map
+* A user defined type, `struct` or `class`, which defines the data stored in the map, named `person`
 * A `kv map` object, name `my_map`, which stores objects of type `person`, with unique keys of type `int`.
 
 Refer to the following reference implementation for your starting point:
@@ -106,7 +106,5 @@ In conclusion, the above instructions show how to find an object in `Key-Value M
 
 ## Next Steps
 
-The following options are available when you complete the procedure:
-
 * [Update](30_how-to-upsert-into-kv-map.md) the `person` found.
 * [Delete](40_how-to-delete-from-kv-map.md) the `person` found.
diff --git a/...06_how-to-guides/30_key-value-api/kv_map/90_how-to-allow-users-to-pay-kv-map.md b/...06_how-to-guides/30_key-value-api/kv_map/90_how-to-allow-users-to-pay-kv-map.md
@@ -11,7 +11,7 @@ Make sure you have the following prerequisites in place:
 
 * An EOSIO development environment, for details consult the [Get Started Guide](https://developers.eos.io/welcome/latest/getting-started-guide/index)
 * A smart contract named `smrtcontract`
-* A user defined type named `person`, which defines the data stored in the map
+* A user defined type, `struct` or `class`, which defines the data stored in the map, named `person`
 * A `kv map` object, name `my_map`, which stores objects of type `person`, with unique keys of type `int`.
 
 Refer to the following reference implementation for your starting point:
@@ -108,7 +108,5 @@ In conclusion, the above instructions show how to require the user to pay for th
 
 ## Next Steps
 
-The following options are available when you complete the procedure:
-
 * [Verify](70_how-to-find-in-kv-map.md) if the newly inserted `person` actually exists in the map. To accomplish this task use the `find()` function of the `kv_map`.
 * [Delete](40_how-to-delete-from-kv-map.md) the newly created or updated `person` from the map. To accomplish this task, use the `erase()` function of the `kv map`.
diff --git a/docs/06_how-to-guides/30_key-value-api/kv_table/10_how-to-use-kv-table.md b/docs/06_how-to-guides/30_key-value-api/kv_table/10_how-to-use-kv-table.md
@@ -17,8 +17,8 @@ To accomplish this task, define the user type which will be stored in the `kv ta
 Make sure you have the following prerequisites in place:
 
 * An EOSIO development environment, for details consult the [Get Started Guide](https://developers.eos.io/welcome/latest/getting-started-guide/index).
-* A smart contract named `smrtcontract`.
-* A user defined type named `person`, which defines the data stored in the table.
+* A smart contract named `smrtcontract`
+* A user defined type, `struct` or `class`, which defines the data stored in the map, named `person`
 
 Refer to the following reference implementation for your starting point:
 
@@ -48,7 +48,7 @@ Complete the following steps to define the `address_table` type, based on the `e
 1. Define the structure or class `address_table` in the scope of your smart contract class, for the abi generation to find it and place it into the abi file.
 2. Derive `address_table` from `eosio::`kv::table` class template. Pass the `person` user defined type as the type parameter for `eosio::`kv::table` base class and the name of the `kv table`, let’s say `kvaddrbook`.
 3. Annotate `address_table` type with `[[eosio::table]]`, and make sure it is placed after the `struct` keyword but before the name of the type.
-4. Define a primary index `first_name_idx` based on the property `person::first_name`. Every `kv table` requires a primary index to be defined based on a property that stores unique values.
+4. Define a primary index `first_name_idx` based on the data member `person::first_name`. Every `kv table` requires a primary index to be defined on a data member that stores unique values.
 5. In the `address_table` constructor, call the `init(...)` base class method with the two parameters:
     1. The first parameter, of type `eosio::name`, is the contract that owns the table.
     2. The second parameter is the `account_name_uidx` primary index.
@@ -80,8 +80,6 @@ In conclusion, the above instructions show how to define and use a `Key-Value Ta
 
 ## Next Steps
 
-The following options are available when you complete the procedure:
-
 * You can [create one or more unique indexes](20_how-to-create-indexes-kv-table.md) using the `KV_NAMED_INDEX` macro or the `eosio::kv::table::index` template class.
 * You can [create one or more non-unique indexes](20_how-to-create-indexes-kv-table.md) using the `KV_NAMED_INDEX` macro or the `eosio::kv::table::index` template class.
 * You can access the defined `kv table` and perform operations on it and its defined indexes: