From 04ccc497d6bbd7d5c66493822a686caeabb3c903 Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Tue, 15 Aug 2023 11:01:09 +0100
Subject: [PATCH 01/16] updates foundry tutorial link

---
 docs/developing/get-started.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/developing/get-started.md b/docs/developing/get-started.md
index b4613626..a91f0f40 100644
--- a/docs/developing/get-started.md
+++ b/docs/developing/get-started.md
@@ -12,7 +12,7 @@ import TabItem from '@theme/TabItem';
 
 
 :::note
-Just in case you are not using our #ai-support channel in Discord to accelerate your access to the documentation, here is a bare bones Get Started.
+This is a bare bones Get Started; alternatively browse the full support available here.
 ::: 
 
 ## Get test NEON for Neon Devnet
@@ -108,7 +108,7 @@ See the [Truffle tutorial](https://docs.neonfoundation.io/docs/developing/deploy
 </TabItem>
 <TabItem value="Foundry" label="Foundry" default>
 
-Foundry doesn’t have a config file like Hardhat or Truffle to configure the network settings. Rather, the RPC endpoint and the private key are specified in the command line when passing foundry commands. See the [Foundry tutorial](https://github.com/sukanyaparashar/simple-erc20-foundry).
+Foundry doesn’t have a config file like Hardhat or Truffle to configure the network settings. Rather, the RPC endpoint and the private key are specified in the command line when passing foundry commands. See the [Foundry tutorial](https://github.com/neonlabsorg/examples/tree/main/simple-erc20-foundry).
 
 </TabItem>
 </Tabs>

From f395eb7cf2f3d7e55d54fbc0000dab5f53f12001 Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Tue, 15 Aug 2023 13:34:50 +0100
Subject: [PATCH 02/16] backup location for Grammarly style guide

---
 .github/styles/Grammarly.csv | 107 +++++++++++++++++++++++++++++++++++
 1 file changed, 107 insertions(+)
 create mode 100644 .github/styles/Grammarly.csv

diff --git a/.github/styles/Grammarly.csv b/.github/styles/Grammarly.csv
new file mode 100644
index 00000000..364c312b
--- /dev/null
+++ b/.github/styles/Grammarly.csv
@@ -0,0 +1,107 @@
+"Original text",Rule,Explanation
+"OX",0x,"Existing style, maintain consistency"
+"24:7",24/7,"Existing style, maintain consistency"
+"api;Api",API,"Existing style, maintain consistency"
+"amongst",among,"Existing style, maintain consistency"
+"Berkley Packet Filter;berkeley packet filter",Berkeley Packet Filter,"Existing style, maintain consistency"
+"bi-weekly","biweekly","Existing style, maintain consistency"
+"cex",CEX,"Acronyms in caps"
+"CEXes",CEXs,"Existing style, maintain consistency"
+"cryptobots;Cryptobots","CryptoBots","Brand name"
+"cryptopunks;Cryptopunks",CryptoPunks,"Brand name"
+"devnet",Devnet,"If this is Neon's Devnet or any other systems' use proper noun."
+"DOA",DAO,"Oops, typo"
+"DApp,Dapp,DAPP",dApp,"Exception is sentence start = DApp"
+"DApps,Dapps,DAPPs,DAPPS",dApps,"Exception is sentence start = DApps"
+""dex",DEX,"Acronyms in caps"
+"DEXes",DEXs,"Existing style, maintain consistency"
+discord,Discord,"Brand name"
+dockerfile,Dockerfile,"Existing style, maintain consistency"
+"Eterum,Etherum",Ethereum,"Watch out, typo" 
+"ERC 20;Erc-20;ERc-20;Erc 20;ERc 20,ERC20;Erc20;ERc20",ERC-20,"Existing style, maintain consistency"
+"ERC 721;Erc-721;ERc-721;Erc 721;ERc 721,ERC721;Erc721;ERc721",ERC-721,"Existing style, maintain consistency"
+"end-point;end point",endpoint,"Existing style, maintain consistency"
+"evm;Evm",EVM,"Existing style, maintain consistency"
+"Github,github,gitHub",GitHub,"Brand name"
+"gHz,ghz",GHz,"Standard, maintain consistency"
+"Javascript,javascript",JavaScript,"Brand name, maintain consistency"
+"json,Json",JSON,"when referring to a file type or the standard, use caps"
+"&",and,"Only apply & in heading or TL;DR (with the exception of webpage copy where space is an issue)"
+"re-balancing,rebalancing","Existing style, maintain consistency"
+"non-deterministic,nondeterministic","Existing style, maintain consistency"
+"world-wide,worldwide","Stay consistent!"
+"full withdrawl;full-withdrawl","Full Withdrawal","caps for the adjective or noun of a component of the system"
+"front-end;front end","frontend","Existing style, maintain consistency"
+"Decentralized finance",DeFi,"Apply acronym"
+"off boarding;off-boarding",offboarding,"Existing style, maintain consistency"
+"back-end;backend","backend","back-end is used as an adjective only."
+"ID;id",Id,"Existing style, maintain consistency"
+admin,Admin,"Use proper noun (caps) for an active component of a system e.g., ""The Admin authorizes the user""."
+"Validity rollup;validity rollup","Validity Rollup",
+"off chain;offchain",off-chain,"as an adjective off-chain would be the form plus this style has been extended for all uses"
+"permissionless,permissionlessly",,"This should quiet the standard spelling flag"
+"Layer 1;l1;layer 1",L1,"Use the acronym"
+"Ethereum MainNet;Ethereum-Mainnet","Ethereum Mainnet ","Existing style, maintain consistency"
+built-in,builtin,"This should quiet standard spelling flag"
+governor,Governor,"Caps for a noun of an active component in the system"
+"mainnet",Mainnet,"If this is Neon's Mainnet or any other named systems' use proper noun."
+"Main-Net;Main-net;MainNet;main net;main-net;mainNet",Mainnet,"Existing style, maintain consistency"
+"Maker DAO, Maker-DAO",MakerDAO,"Brand name"
+"Merkel Patricia-Trie;Merkel Patricia Trie",Merkel-Patricia Trie,"Standard"
+"Metamask;Meta mask;metamask;metaMask",MetaMask,"Brand name"
+"multi sig;multi-sig",multisig,"Existing style, maintain consistency"
+"the Neon EVM",Neon EVM,"Existing style, maintain consistency"
+"NoenEVM;Noen EVM;NeonEVM",Neon EVM,"Existing style, maintain consistency"
+"Neon Scan;NoenScan",NeonScan,"PascalCase for tools. Existing style, maintain consistency"
+"Neon pass;Neon Pass,NoenPass",NeonPass,"PascalCase for tools. Existing style, maintain consistency"
+"Neon faucet;Neon Faucet,NoenFaucet",NeonFaucet,"PascalCase for tools. Existing style, maintain consistency"
+"Neon",NEON,"NEON caps is the token, Neon the noun should rarely be used > provide component instead"
+"NEONS, Neons, neons",NEON,"The plural of NEON is NEON"
+"proxy",Proxy,"Existing style, maintain consistency"
+"NeonProxy, Noen proxy, Neon proxy",Neon Proxy,"Existing style, maintain consistency"
+"Nft",NFT,"Acronymn as caps"
+"node JS,Node JS",NodeJS,"Brand name"
+"L2 rollup","L2 Rollup","as per ""On the Road"" Medium post"
+"on boarding;on-boarding",onboarding,"Existing style, maintain consistency"
+"rollup",Rollup,"proper noun for all rollup types - IF compounded proper noun for leading name also"
+"Optimistic rollup;optimistic rollup","Optimistic Rollup","proper noun"
+operator,Operator,"caps for a noun of an active component of the system"
+"on chain;onchain",on-chain,"as an adjective on-chain would be the form plus this style has been extended for all uses"
+"OpenZepelin;OpenZeppellin",OpenZeppelin,"Brand name"
+"PRC",RPC,"Did you mean RPC as in Remote Procedure Call endpoint?"
+"Side chains, Side-chains;side chains, side-chains",sidechains,"Existing style, maintain consistency"
+smart-contract,"smart contract","Existing style, maintain consistency"
+"Side chain;Side-chain;side chain;side-chain",sidechain,"Existing style, maintain consistency"
+"sealevel,Sea Level",Sealevel,"Brand name"
+"singing",signing,"Do you really mean to sing?!"
+"solana,Solna",Solana,"Watch out, typo" 
+"stable coin",stablecoin,"Existing style, maintain consistency"
+"Stark-Ex;Stark-ex;Starkex;starkex",StarkEx,"Proper noun's form"
+"StarkEx Contract;StarkEx Smart Contract;StarkEx smart Contract;Starkex Contract","StarkEx smart contract","Trial style: Proper noun plus ""common"" noun"
+"STARK key;Stark Key;starkKey","Stark key","Treat as a noun. Do not split the individual words with an adjective, rather place the adjective before the term.
+StrakEx,StarkEx,"typo fix"
+"Sushiswap",SushiSwap,"Brand name"
+"Stark;stark",STARK,"style is all caps for this proper noun"
+"pseudo code;pseudocode",pseudo-code,"Existing style, maintain consistency"
+"StrakGate",StarkGate,"typo fix"
+"StarkNet;StrakNet",Starknet,"typo fix"
+"spl",SPL,"Acronym has caps"
+"time lock;time-lock",timelock,"Existing style, maintain consistency"
+"testnet",Testnet,"If this is Neon's Testnet or any other systems' use proper noun."
+"Test-Net;test-net;TestNet;Test net;test-net;testNet",Testnnet,"Existing style, maintain consistency"
+"tps",TPS,"Acronym has caps"
+"trx;TRX",tx,"Existing style to abbreviate transaction, NO CAPS, maintain consistency"
+"tvl",TVL,"Acronym has caps"
+"the Neon,The Neon","Neon","The Neon EVM can be stated as Neon EVM"
+"the Mainnet,The Mainnet","Mainnet","The Mainnet can be stated as Mainnet"
+"the Devnet,The Devnet","Devnet","The Devnet can be stated as Devnet"
+"UniSwap,uniswap",Uniswap,"Brand name"
+"U.S,U.S.",US,"Existing style, maintain consistency"
+"U.S.A,U.S.A.",US,"Existing style, maintain consistency"
+"white paper",whitepaper,"Existing style, maintain consistency"
+"White paper",Whitepaper,"Existing style, maintain consistency"
+"web3,web 3,Web 3",Web3,"Existing style, maintain consistency"
+"ZK-rollup;ZKRollup;zk-rollup;zkRollup",ZK-Rollup,"Existing style, maintain consistency"
+"zk SNARK",zk-SNARK,"Existing style, maintain consistency"
+"zk STARK",zk-STARK,"Existing style, maintain consistency"
+

From df29a3f644c50a32a9c03444a4684cf4269475d3 Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Thu, 17 Aug 2023 10:37:02 +0100
Subject: [PATCH 03/16] adds to backup style

---
 .github/styles/Grammarly.csv | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/.github/styles/Grammarly.csv b/.github/styles/Grammarly.csv
index 364c312b..854512b3 100644
--- a/.github/styles/Grammarly.csv
+++ b/.github/styles/Grammarly.csv
@@ -41,7 +41,8 @@ admin,Admin,"Use proper noun (caps) for an active component of a system e.g., ""
 "off chain;offchain",off-chain,"as an adjective off-chain would be the form plus this style has been extended for all uses"
 "permissionless,permissionlessly",,"This should quiet the standard spelling flag"
 "Layer 1;l1;layer 1",L1,"Use the acronym"
-"Ethereum MainNet;Ethereum-Mainnet","Ethereum Mainnet ","Existing style, maintain consistency"
+"Layer 2;l1;layer 2",L2,"Use the acronym"
+"Ethereum MainNet;Ethereum-Mainnet","Ethereum Mainnet","Existing style, maintain consistency"
 built-in,builtin,"This should quiet standard spelling flag"
 governor,Governor,"Caps for a noun of an active component in the system"
 "mainnet",Mainnet,"If this is Neon's Mainnet or any other named systems' use proper noun."
@@ -69,6 +70,9 @@ operator,Operator,"caps for a noun of an active component of the system"
 "on chain;onchain",on-chain,"as an adjective on-chain would be the form plus this style has been extended for all uses"
 "OpenZepelin;OpenZeppellin",OpenZeppelin,"Brand name"
 "PRC",RPC,"Did you mean RPC as in Remote Procedure Call endpoint?"
+"p2p",P2P,"Brand name"
+"POH,poh",PoH,"Existing style, maintain consistency"
+"POS,pos",PoS,"Existing style, maintain consistency"
 "Side chains, Side-chains;side chains, side-chains",sidechains,"Existing style, maintain consistency"
 smart-contract,"smart contract","Existing style, maintain consistency"
 "Side chain;Side-chain;side chain;side-chain",sidechain,"Existing style, maintain consistency"
@@ -89,6 +93,7 @@ StrakEx,StarkEx,"typo fix"
 "time lock;time-lock",timelock,"Existing style, maintain consistency"
 "testnet",Testnet,"If this is Neon's Testnet or any other systems' use proper noun."
 "Test-Net;test-net;TestNet;Test net;test-net;testNet",Testnnet,"Existing style, maintain consistency"
+"TL:DR,tl:dr,tl;dr",TL;DR,"Existing style, maintain consistency"
 "tps",TPS,"Acronym has caps"
 "trx;TRX",tx,"Existing style to abbreviate transaction, NO CAPS, maintain consistency"
 "tvl",TVL,"Acronym has caps"

From 016d35adf48f9445b416d5a0015c023ff127aa80 Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Tue, 22 Aug 2023 14:53:24 +0100
Subject: [PATCH 04/16] Fixes (#73)

* updates foundry tutorial link

* backup location for Grammarly style guide

* adds to backup style
---
 .github/styles/Grammarly.csv   | 112 +++++++++++++++++++++++++++++++++
 docs/developing/get-started.md |   4 +-
 2 files changed, 114 insertions(+), 2 deletions(-)
 create mode 100644 .github/styles/Grammarly.csv

diff --git a/.github/styles/Grammarly.csv b/.github/styles/Grammarly.csv
new file mode 100644
index 00000000..854512b3
--- /dev/null
+++ b/.github/styles/Grammarly.csv
@@ -0,0 +1,112 @@
+"Original text",Rule,Explanation
+"OX",0x,"Existing style, maintain consistency"
+"24:7",24/7,"Existing style, maintain consistency"
+"api;Api",API,"Existing style, maintain consistency"
+"amongst",among,"Existing style, maintain consistency"
+"Berkley Packet Filter;berkeley packet filter",Berkeley Packet Filter,"Existing style, maintain consistency"
+"bi-weekly","biweekly","Existing style, maintain consistency"
+"cex",CEX,"Acronyms in caps"
+"CEXes",CEXs,"Existing style, maintain consistency"
+"cryptobots;Cryptobots","CryptoBots","Brand name"
+"cryptopunks;Cryptopunks",CryptoPunks,"Brand name"
+"devnet",Devnet,"If this is Neon's Devnet or any other systems' use proper noun."
+"DOA",DAO,"Oops, typo"
+"DApp,Dapp,DAPP",dApp,"Exception is sentence start = DApp"
+"DApps,Dapps,DAPPs,DAPPS",dApps,"Exception is sentence start = DApps"
+""dex",DEX,"Acronyms in caps"
+"DEXes",DEXs,"Existing style, maintain consistency"
+discord,Discord,"Brand name"
+dockerfile,Dockerfile,"Existing style, maintain consistency"
+"Eterum,Etherum",Ethereum,"Watch out, typo" 
+"ERC 20;Erc-20;ERc-20;Erc 20;ERc 20,ERC20;Erc20;ERc20",ERC-20,"Existing style, maintain consistency"
+"ERC 721;Erc-721;ERc-721;Erc 721;ERc 721,ERC721;Erc721;ERc721",ERC-721,"Existing style, maintain consistency"
+"end-point;end point",endpoint,"Existing style, maintain consistency"
+"evm;Evm",EVM,"Existing style, maintain consistency"
+"Github,github,gitHub",GitHub,"Brand name"
+"gHz,ghz",GHz,"Standard, maintain consistency"
+"Javascript,javascript",JavaScript,"Brand name, maintain consistency"
+"json,Json",JSON,"when referring to a file type or the standard, use caps"
+"&",and,"Only apply & in heading or TL;DR (with the exception of webpage copy where space is an issue)"
+"re-balancing,rebalancing","Existing style, maintain consistency"
+"non-deterministic,nondeterministic","Existing style, maintain consistency"
+"world-wide,worldwide","Stay consistent!"
+"full withdrawl;full-withdrawl","Full Withdrawal","caps for the adjective or noun of a component of the system"
+"front-end;front end","frontend","Existing style, maintain consistency"
+"Decentralized finance",DeFi,"Apply acronym"
+"off boarding;off-boarding",offboarding,"Existing style, maintain consistency"
+"back-end;backend","backend","back-end is used as an adjective only."
+"ID;id",Id,"Existing style, maintain consistency"
+admin,Admin,"Use proper noun (caps) for an active component of a system e.g., ""The Admin authorizes the user""."
+"Validity rollup;validity rollup","Validity Rollup",
+"off chain;offchain",off-chain,"as an adjective off-chain would be the form plus this style has been extended for all uses"
+"permissionless,permissionlessly",,"This should quiet the standard spelling flag"
+"Layer 1;l1;layer 1",L1,"Use the acronym"
+"Layer 2;l1;layer 2",L2,"Use the acronym"
+"Ethereum MainNet;Ethereum-Mainnet","Ethereum Mainnet","Existing style, maintain consistency"
+built-in,builtin,"This should quiet standard spelling flag"
+governor,Governor,"Caps for a noun of an active component in the system"
+"mainnet",Mainnet,"If this is Neon's Mainnet or any other named systems' use proper noun."
+"Main-Net;Main-net;MainNet;main net;main-net;mainNet",Mainnet,"Existing style, maintain consistency"
+"Maker DAO, Maker-DAO",MakerDAO,"Brand name"
+"Merkel Patricia-Trie;Merkel Patricia Trie",Merkel-Patricia Trie,"Standard"
+"Metamask;Meta mask;metamask;metaMask",MetaMask,"Brand name"
+"multi sig;multi-sig",multisig,"Existing style, maintain consistency"
+"the Neon EVM",Neon EVM,"Existing style, maintain consistency"
+"NoenEVM;Noen EVM;NeonEVM",Neon EVM,"Existing style, maintain consistency"
+"Neon Scan;NoenScan",NeonScan,"PascalCase for tools. Existing style, maintain consistency"
+"Neon pass;Neon Pass,NoenPass",NeonPass,"PascalCase for tools. Existing style, maintain consistency"
+"Neon faucet;Neon Faucet,NoenFaucet",NeonFaucet,"PascalCase for tools. Existing style, maintain consistency"
+"Neon",NEON,"NEON caps is the token, Neon the noun should rarely be used > provide component instead"
+"NEONS, Neons, neons",NEON,"The plural of NEON is NEON"
+"proxy",Proxy,"Existing style, maintain consistency"
+"NeonProxy, Noen proxy, Neon proxy",Neon Proxy,"Existing style, maintain consistency"
+"Nft",NFT,"Acronymn as caps"
+"node JS,Node JS",NodeJS,"Brand name"
+"L2 rollup","L2 Rollup","as per ""On the Road"" Medium post"
+"on boarding;on-boarding",onboarding,"Existing style, maintain consistency"
+"rollup",Rollup,"proper noun for all rollup types - IF compounded proper noun for leading name also"
+"Optimistic rollup;optimistic rollup","Optimistic Rollup","proper noun"
+operator,Operator,"caps for a noun of an active component of the system"
+"on chain;onchain",on-chain,"as an adjective on-chain would be the form plus this style has been extended for all uses"
+"OpenZepelin;OpenZeppellin",OpenZeppelin,"Brand name"
+"PRC",RPC,"Did you mean RPC as in Remote Procedure Call endpoint?"
+"p2p",P2P,"Brand name"
+"POH,poh",PoH,"Existing style, maintain consistency"
+"POS,pos",PoS,"Existing style, maintain consistency"
+"Side chains, Side-chains;side chains, side-chains",sidechains,"Existing style, maintain consistency"
+smart-contract,"smart contract","Existing style, maintain consistency"
+"Side chain;Side-chain;side chain;side-chain",sidechain,"Existing style, maintain consistency"
+"sealevel,Sea Level",Sealevel,"Brand name"
+"singing",signing,"Do you really mean to sing?!"
+"solana,Solna",Solana,"Watch out, typo" 
+"stable coin",stablecoin,"Existing style, maintain consistency"
+"Stark-Ex;Stark-ex;Starkex;starkex",StarkEx,"Proper noun's form"
+"StarkEx Contract;StarkEx Smart Contract;StarkEx smart Contract;Starkex Contract","StarkEx smart contract","Trial style: Proper noun plus ""common"" noun"
+"STARK key;Stark Key;starkKey","Stark key","Treat as a noun. Do not split the individual words with an adjective, rather place the adjective before the term.
+StrakEx,StarkEx,"typo fix"
+"Sushiswap",SushiSwap,"Brand name"
+"Stark;stark",STARK,"style is all caps for this proper noun"
+"pseudo code;pseudocode",pseudo-code,"Existing style, maintain consistency"
+"StrakGate",StarkGate,"typo fix"
+"StarkNet;StrakNet",Starknet,"typo fix"
+"spl",SPL,"Acronym has caps"
+"time lock;time-lock",timelock,"Existing style, maintain consistency"
+"testnet",Testnet,"If this is Neon's Testnet or any other systems' use proper noun."
+"Test-Net;test-net;TestNet;Test net;test-net;testNet",Testnnet,"Existing style, maintain consistency"
+"TL:DR,tl:dr,tl;dr",TL;DR,"Existing style, maintain consistency"
+"tps",TPS,"Acronym has caps"
+"trx;TRX",tx,"Existing style to abbreviate transaction, NO CAPS, maintain consistency"
+"tvl",TVL,"Acronym has caps"
+"the Neon,The Neon","Neon","The Neon EVM can be stated as Neon EVM"
+"the Mainnet,The Mainnet","Mainnet","The Mainnet can be stated as Mainnet"
+"the Devnet,The Devnet","Devnet","The Devnet can be stated as Devnet"
+"UniSwap,uniswap",Uniswap,"Brand name"
+"U.S,U.S.",US,"Existing style, maintain consistency"
+"U.S.A,U.S.A.",US,"Existing style, maintain consistency"
+"white paper",whitepaper,"Existing style, maintain consistency"
+"White paper",Whitepaper,"Existing style, maintain consistency"
+"web3,web 3,Web 3",Web3,"Existing style, maintain consistency"
+"ZK-rollup;ZKRollup;zk-rollup;zkRollup",ZK-Rollup,"Existing style, maintain consistency"
+"zk SNARK",zk-SNARK,"Existing style, maintain consistency"
+"zk STARK",zk-STARK,"Existing style, maintain consistency"
+
diff --git a/docs/developing/get-started.md b/docs/developing/get-started.md
index b4613626..a91f0f40 100644
--- a/docs/developing/get-started.md
+++ b/docs/developing/get-started.md
@@ -12,7 +12,7 @@ import TabItem from '@theme/TabItem';
 
 
 :::note
-Just in case you are not using our #ai-support channel in Discord to accelerate your access to the documentation, here is a bare bones Get Started.
+This is a bare bones Get Started; alternatively browse the full support available here.
 ::: 
 
 ## Get test NEON for Neon Devnet
@@ -108,7 +108,7 @@ See the [Truffle tutorial](https://docs.neonfoundation.io/docs/developing/deploy
 </TabItem>
 <TabItem value="Foundry" label="Foundry" default>
 
-Foundry doesn’t have a config file like Hardhat or Truffle to configure the network settings. Rather, the RPC endpoint and the private key are specified in the command line when passing foundry commands. See the [Foundry tutorial](https://github.com/sukanyaparashar/simple-erc20-foundry).
+Foundry doesn’t have a config file like Hardhat or Truffle to configure the network settings. Rather, the RPC endpoint and the private key are specified in the command line when passing foundry commands. See the [Foundry tutorial](https://github.com/neonlabsorg/examples/tree/main/simple-erc20-foundry).
 
 </TabItem>
 </Tabs>

From a4fee95f17a2106cbfcf164c2a3cf57d46c693d4 Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Thu, 24 Aug 2023 16:22:22 +0100
Subject: [PATCH 05/16] updates style and applies style to Galan

---
 .github/styles/Grammarly.csv               | 10 +++++++---
 .github/styles/Vocab/Neon/accept.txt       |  1 +
 .github/styles/Vocab/Neon/reject.txt       |  4 ++++
 docs/operating/transaction-gas.md          |  4 ++--
 docs/single-source-snippets/_gas-price.mdx |  4 ++--
 5 files changed, 16 insertions(+), 7 deletions(-)

diff --git a/.github/styles/Grammarly.csv b/.github/styles/Grammarly.csv
index 854512b3..bdfb6b10 100644
--- a/.github/styles/Grammarly.csv
+++ b/.github/styles/Grammarly.csv
@@ -1,8 +1,12 @@
 "Original text",Rule,Explanation
+"&",and,"Only apply & in heading or TL;DR (with the exception of webpage copy where space is an issue)"
 "OX",0x,"Existing style, maintain consistency"
 "24:7",24/7,"Existing style, maintain consistency"
+"ALANS, alans",Alan,"The plural of Alan is Alan"
+"ALAN, alan",Alan,"Existing style, maintain consistency"
 "api;Api",API,"Existing style, maintain consistency"
 "amongst",among,"Existing style, maintain consistency"
+"back-end;backend","backend","back-end is used as an adjective only."
 "Berkley Packet Filter;berkeley packet filter",Berkeley Packet Filter,"Existing style, maintain consistency"
 "bi-weekly","biweekly","Existing style, maintain consistency"
 "cex",CEX,"Acronyms in caps"
@@ -26,15 +30,14 @@ dockerfile,Dockerfile,"Existing style, maintain consistency"
 "gHz,ghz",GHz,"Standard, maintain consistency"
 "Javascript,javascript",JavaScript,"Brand name, maintain consistency"
 "json,Json",JSON,"when referring to a file type or the standard, use caps"
-"&",and,"Only apply & in heading or TL;DR (with the exception of webpage copy where space is an issue)"
-"re-balancing,rebalancing","Existing style, maintain consistency"
 "non-deterministic,nondeterministic","Existing style, maintain consistency"
 "world-wide,worldwide","Stay consistent!"
 "full withdrawl;full-withdrawl","Full Withdrawal","caps for the adjective or noun of a component of the system"
 "front-end;front end","frontend","Existing style, maintain consistency"
 "Decentralized finance",DeFi,"Apply acronym"
+"GALANS, Galans, galans",Galan,"The plural of Galan is Galan"
+"GALAN, galan",Galan,"Existing style, maintain consistency"
 "off boarding;off-boarding",offboarding,"Existing style, maintain consistency"
-"back-end;backend","backend","back-end is used as an adjective only."
 "ID;id",Id,"Existing style, maintain consistency"
 admin,Admin,"Use proper noun (caps) for an active component of a system e.g., ""The Admin authorizes the user""."
 "Validity rollup;validity rollup","Validity Rollup",
@@ -73,6 +76,7 @@ operator,Operator,"caps for a noun of an active component of the system"
 "p2p",P2P,"Brand name"
 "POH,poh",PoH,"Existing style, maintain consistency"
 "POS,pos",PoS,"Existing style, maintain consistency"
+"re-balancing,rebalancing","Existing style, maintain consistency"
 "Side chains, Side-chains;side chains, side-chains",sidechains,"Existing style, maintain consistency"
 smart-contract,"smart contract","Existing style, maintain consistency"
 "Side chain;Side-chain;side chain;side-chain",sidechain,"Existing style, maintain consistency"
diff --git a/.github/styles/Vocab/Neon/accept.txt b/.github/styles/Vocab/Neon/accept.txt
index 08c86c9a..44cc174b 100644
--- a/.github/styles/Vocab/Neon/accept.txt
+++ b/.github/styles/Vocab/Neon/accept.txt
@@ -10,6 +10,7 @@ DeFi platform
 ESLint
 Ethereum
 [Ff]ailover
+Galan
 gcc
 gif
 Gitter
diff --git a/.github/styles/Vocab/Neon/reject.txt b/.github/styles/Vocab/Neon/reject.txt
index e2b86adc..fd44a1cc 100644
--- a/.github/styles/Vocab/Neon/reject.txt
+++ b/.github/styles/Vocab/Neon/reject.txt
@@ -7,3 +7,7 @@ mainNet
 MainMet
 testNet
 TestNet
+GALAN
+GALANS
+galan
+NeonEVM
\ No newline at end of file
diff --git a/docs/operating/transaction-gas.md b/docs/operating/transaction-gas.md
index 2a0b0fe6..036e378c 100644
--- a/docs/operating/transaction-gas.md
+++ b/docs/operating/transaction-gas.md
@@ -47,7 +47,7 @@ For example:
 - $NEON = $0.25
 - $SOL = $10
 - PRX_OPERATOR_FEE = "1"
-- Gas price = 10 / 0.25 * (1 + 1) = 80 Galans
+- Gas price = 10 / 0.25 * (1 + 1) = 80 Galan
 
 Neon recommends that Neon Operators should initially set `PRX_OPERATOR_FEE` to “1.0” for Mainnet launch. This allows Operators to cover their hardware costs while transaction demands are low. As demand grows, Operators may adjust their fees in response.
 
@@ -60,7 +60,7 @@ An Operator has two options:
 - **Recommended**: set up the `PRX_MINIMAL_GAS_PRICE` to 1 as per the default value in EVMs
 - Set up the `PRX_MINIMAL_GAS_PRICE` to reject low offers 
 
-> For example, by setting the gas price minimum to 65 Galans, Neon Proxy rejects transactions with a gas price of less than 65.
+> For example, by setting the gas price minimum to 65 Galan, Neon Proxy rejects transactions with a gas price of less than 65.
 
 If a transaction request arrives with a gas price below that of the Operator costs + Operator fee, but with a gas price larger than the designated `PRX_MINIMAL_GAS_PRICE`, the Neon Proxy accepts the transaction into mempool. 
 
diff --git a/docs/single-source-snippets/_gas-price.mdx b/docs/single-source-snippets/_gas-price.mdx
index 6901e591..29080e3f 100644
--- a/docs/single-source-snippets/_gas-price.mdx
+++ b/docs/single-source-snippets/_gas-price.mdx
@@ -4,9 +4,9 @@ The **gas price** is the cost of 1 unit of gas in NEON. This price is calculated
 
 which can also be represented as:
 
-> (1 + Proxy Operator fee) \* SOL-to-NEON-rate Galans
+> (1 + Proxy Operator fee) \* SOL-to-NEON-rate Galan
 
-This amount is usually displayed for users in Galans (10<sup>-9</sup> NEONs).
+This amount is usually displayed for users in Galan (10<sup>-9</sup> NEONs).
 
 The final formula for the gas fee for a Neon transaction with N iterations and S newly allocated bytes is:
 

From 5a22ceeb95a1a3a1302cb526ed542bcbdab2cd59 Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Mon, 28 Aug 2023 12:08:15 +0100
Subject: [PATCH 06/16] applies discussed updates to remove duplication

---
 ...solana.md => local_proxy_remote_solana.md} | 64 +++++++++++--------
 .../op2_local_proxy_local_solana.md           | 48 --------------
 sidebars.js                                   |  8 +--
 3 files changed, 38 insertions(+), 82 deletions(-)
 rename docs/developing/dev_environment/{op3_local_proxy_remote_solana.md => local_proxy_remote_solana.md} (59%)
 delete mode 100644 docs/developing/dev_environment/op2_local_proxy_local_solana.md

diff --git a/docs/developing/dev_environment/op3_local_proxy_remote_solana.md b/docs/developing/dev_environment/local_proxy_remote_solana.md
similarity index 59%
rename from docs/developing/dev_environment/op3_local_proxy_remote_solana.md
rename to docs/developing/dev_environment/local_proxy_remote_solana.md
index 9f411daa..a94d21ca 100644
--- a/docs/developing/dev_environment/op3_local_proxy_remote_solana.md
+++ b/docs/developing/dev_environment/local_proxy_remote_solana.md
@@ -1,60 +1,68 @@
 ---
 title: "Local Proxy to Remote Solana"
-proofedDate: na
+proofedDate: 20230828
 iterationBy: na
 includedInSite: true
 approvedBy: na
-comment: 
+comment: Local to local was updated -- todo verify this page; may need update also e.g. instruction says For Devnet/Testnet, it should be `eeLSJgWzzxrqKv1UxtRVVH8FX3qCQWUs9QuAjJpETGU` but are Devnet and Testnet not two different entities?
 ---
 
+:::info
+The [Proxy local testing tutorial](/docs/operating/basic) describes how to perform testing with a local Proxy to a local Solana node. This option can be useful for developers who want to debug their Solidity contracts by hosting both Proxy and Solana nodes locally. This page provides a tutorial that demonstrates how to transact from a local Proxy to a public, remote Solana.
+:::
+
+
 ## Prerequisites
-[Docker](https://docs.docker.com/get-docker/) must be already installed on your device. `docker-compose` v1.29 is recommended.
+[Docker](https://docs.docker.com/get-docker/); `docker-compose` v1.29 is recommended.
 
-## Network Configuration
-  * The target Solana cluster is accessed via the locally-hosted proxy.
-  * Solana [Testnet](https://docs.solana.com/clusters#testnet)/[Devnet](https://docs.solana.com/clusters#devnet)/[Mainnet](https://docs.solana.com/clusters#mainnet-beta) is used, and the proxy interacts with it through the Neon EVM.
+## Network configuration
+  * The target Solana cluster is accessed via the locally-hosted Proxy.
+  * Solana [Testnet](https://docs.solana.com/clusters#testnet)/[Devnet](https://docs.solana.com/clusters#devnet)/[Mainnet](https://docs.solana.com/clusters#mainnet-beta) is used, and the Proxy interacts with it through Neon EVM.
 
-## Setting up a Local Proxy
-First, set up and host a proxy locally as per the following steps. After executing these commands, the proxy will be available at `http://localhost:9090/solana`. This address and port are set by default.
+## Set up a local Proxy
+First, set up and host a Proxy locally as per the following steps. After executing these commands, the Proxy will be available at `http://localhost:9090/solana`. This address and port are set by default.
 
 ### Step 1: Docker
-Docker images themselves are never "started" and never "running". The `docker run` command takes the Docker image as a template and produces a container from it. Before starting your proxy container, you need to start service containers.
+Docker images themselves are never "started" and never "running". The `docker run` command takes the Docker image as a template and produces a container from it. Before starting your Proxy container, you need to start service containers.
 
 Make sure that you have a daemon running by executing the following command:
 ```bash
 docker info
 ```
+
+:::tip
 If you see something like this:
 ```console
-Cannot connect to the Docker daemon at <docker.sock>. Is the docker daemon running?
+Can't connect to the Docker daemon at <docker.sock>. Is the docker daemon running?
 ```
-you need to run the daemon first:
+run the daemon first:
 ```bash
 sudo systemctl start docker
 ```
+:::
 
 ### Step 2: Run the Database, Indexer, and Proxy Services
-In this step, you will create the services necessary for the function of the proxy (including database and indexer services), as well as the proxy service itself. These services, the functions of which are described below, will be created from a docker-compose.yml file.
+In this step, you will create the services necessary for the function of the Proxy (including database and indexer services), as well as the Proxy service itself. These services, the functions of which are described below, will be created from a docker-compose.yml file.
 
 #### Database Services
-This container aims to handle the database that stores all the relevant Ethereum processing metadata linked to each other: **`transactions`**, **`blocks`**, **`receipts`**, **`accounts`** etc. This data is consumed by the **Indexer** service.
+This container aims to handle the database that stores all the relevant Ethereum processing metadata linked to each other: **`transactions`**, **`blocks`**, **`receipts`**, **`accounts`**, etc. This data is consumed by the **Indexer** service.
 
-Currently, Neon EVM proxies are hardcoded to work with PostgreSQL. To connect the proxy to a database, you need to start a PostgreSQL container. The default settings are hardcoded in the following docker-compose.yml file. If you want to use your proxy with other settings, you need to register as an operator so that the Neon EVM can recognize your keys.
+Currently, Neon EVM proxies are hard coded to work with PostgreSQL. To connect the Proxy to a database, you need to start a PostgreSQL container. The default settings are hard coded in the following docker-compose.yml file. If you want to use your Proxy with other settings, you need to register as an Operator so that Neon EVM can recognize your keys.
 
-> Only authorized operators can change the settings of these parameters.
+> Only authorized Operators can change the settings of these parameters. Learn more about [operating a Neon Proxy](/docs/operating/operator-introduction.md)
 
 #### Indexer Service
-The indexer service indexes all the relevant Ethereum processing metadata consisting of **`signatures`**, **`transactions`**, **`blocks`**, **`receipts`**, **`accounts`**, etc. It gathers all this data from the Solana blockchain, filtering them by the EVM contract address. It also makes it possible to provide our users with the Ethereum API according to the data provided by the whole known operators.
+The indexer service indexes all the relevant Ethereum processing metadata consisting of **`signatures`**, **`transactions`**, **`blocks`**, **`receipts`**, **`accounts`**, etc. It gathers all this data from the Solana blockchain, filtering them by the EVM contract address. It enables us to provide our users with the Ethereum API.
 
 #### Proxy Service
 The Proxy service is a core service that allows Ethereum-like transactions to be processed on Solana, taking full advantage of Solana-native functionality, including the ability to execute transactions in parallel.
 
-The Neon EVM address is registered inside `neonlabsorg/proxy`, so the proxy knows which Neon EVM is running in the Solana cluster. After executing this command, the proxy will be available at `http://localhost:9090/solana`. This address and port are set by default.
+The Neon EVM address is registered inside `neonlabsorg/proxy`, so the Proxy knows which Neon EVM is running in the Solana cluster. After executing this command, the Proxy will be available at `http://localhost:9090/solana`. This address and port are set by default.
 
 #### Create and Run Services with Docker Compose
-In order to create and run these abovementioned services, 
+In order to create and run these services, 
 
-1. Create "keys" folder and put your whitelisted key into it. Note that the file with operator key should be named `id.json`.
+1. Create a "keys" folder and put your allowlisted key into it. Note that the file with the Operator key should be named `id.json`.
 ```bash
 mkdir keys
 mv {PATH_TO_WHITELISTED_KEYS} keys/
@@ -62,7 +70,7 @@ mv {PATH_TO_WHITELISTED_KEYS} keys/
 
 2. Set the following environment variables
    - `EVM_LOADER`
-     - For devnet/testnet, it should be `eeLSJgWzzxrqKv1UxtRVVH8FX3qCQWUs9QuAjJpETGU`
+     - For Devnet/Testnet, it should be `eeLSJgWzzxrqKv1UxtRVVH8FX3qCQWUs9QuAjJpETGU`
    - `SOLANA_URL`
      - Refer to the [RPC Endpoints table](#rpc-endpoints)
    - `PROXY_VERSION`
@@ -97,23 +105,23 @@ Creating indexer ... done
 Creating proxy ... done
 ```
 
-## Connecting to Solana Cluster RPC Endpoints
+## Connect to a Solana cluster RPC endpoint
 
-A proxy connects to a public [Solana cluster RPC endpoint](https://docs.solana.com/cluster/rpc-endpoints) depending on the `SOLANA_URL` value set. The table below shows the *endpoint* value that is set automatically based on the value of the `CONFIG` flag.
+A Proxy connects to a public [Solana cluster RPC endpoint](https://docs.solana.com/cluster/rpc-endpoints) depending on the `SOLANA_URL` value set. The table below shows the *endpoint* value that is set automatically based on the value of the `CONFIG` flag.
 
-### RPC Endpoints
+### RPC endpoints
 CONFIG | RPC Endpoint
 :-|:-
-devnet | `https://api.devnet.solana.com`
-testnet | `https://api.testnet.solana.com`
-mainnet | `https://api.mainnet-beta.solana.com`
+Devnet | `https://api.devnet.solana.com`
+Testnet | `https://api.testnet.solana.com`
+Mainnet | `https://api.mainnet-beta.solana.com`
 
 To use a different endpoint, you need to specify the variable `-e SOLANA_URL='http://<Solana node RPC endpoint>'` on the command line. For example, in order to use devnet, add the flag `-e SOLANA_URL='https://api.devnet.solana.com'`.
 
-When a proxy is deployed, it generates a wallet containing a key pair. If you do not need the new wallet and want to use the keys you already have, you need to specify the path to your wallet on the command line.
+When a Proxy is deployed, it generates a wallet containing a key pair. If you do not need the new wallet and want to use the keys you already have, you need to specify the path to your wallet on the command line.
 
 **Command Line Options**
   * `~/.config/solana/id.json` — absolute path to your key pair file stored locally
-  * `--name proxy` — specifies the proxy name
+  * `--name proxy` — specifies the Proxy name
 
 <!-- retired to retire linked page If you are not registered as an operator, you can only use test public keys. A list of available public keys is accessible in the  {Neon Proxy RPC Endpoints} (clusters/neon_proxy_rpc_endpoints.md) section. You do not need to specify the key using the `-v` flag, since it is already hard-coded into the Devnet/Testnet containers. -->
diff --git a/docs/developing/dev_environment/op2_local_proxy_local_solana.md b/docs/developing/dev_environment/op2_local_proxy_local_solana.md
deleted file mode 100644
index 38758c88..00000000
--- a/docs/developing/dev_environment/op2_local_proxy_local_solana.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: "Local Proxy to Local Solana"
-proofedDate: na
-iterationBy: na
-includedInSite: true
-approvedBy: na
-comment: 
----
-
-This option will let you connect to Solana via a proxy, when **both** are hosted locally. This option can be useful for developers that want to debug their Solidity contracts by hosting a proxy and a Solana node locally.
-
-## Prerequisites
-[Docker](https://docs.docker.com/get-docker/) must be already installed on your device. `docker-compose` v1.29 is recommended.
-
-## Network Configuration
-  * Both the Solana node and the proxy are hosted locally
-  * The proxy interacts with the Solana node through the Neon EVM
-
-## Setting up Local Proxy and Local Solana Node
-
-Download the `docker-compose-test.yml` file to your currently directory using the following command:
-```bash
-wget https://raw.githubusercontent.com/neonlabsorg/proxy-model.py/master/proxy/docker-compose-test.yml
-```
-
-Execute the command:
-```bash
-sudo REVISION=stable docker-compose -f docker-compose-test.yml up -d --quiet-pull
-```
-
-The output should look like this:
-```console
-Creating solana ... done
-Creating evm_loader ... done
-Creating postgres ... done
-Creating proxy ... done
-Creating indexer ... done
-```
-As soon as the latest command is completed, the proxy will start to deploy the Neon EVM in a local Solana node. After that, the proxy and Solana will be available at the URLs `http://localhost:9090/solana` and `http://localhost:8899`, respectively. The Neon faucet will also be available at `http://localhost:3333`.
-
----  
-
-> **Note:**  
-> For your proxy, you can use the dedicated Neon server, or a separate server that you will need to deploy and log into.
->
-> For the Solana endpoint, you can use a separate node hosted on Devnet or Testnet.  
->
-You can also use a Solana node that is not hosted on any network. In this case, you will need to configure this node and synchronize it with the Devnet or Testnet network. Then you will need to deploy the local proxy and configure it to work with this node. In addition, you will also need to connect to the EVM loader deployed within Devnet or Testnet.
diff --git a/sidebars.js b/sidebars.js
index a7c3e968..d6f972d3 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -110,13 +110,9 @@ const sidebars = {
       ]
     },
     {
-      type: 'category',
+      type: 'doc',
       label: 'Set up Local Neon EVM',
-      items: [
-        'developing/dev_environment/op2_local_proxy_local_solana',
-        'developing/dev_environment/op3_local_proxy_remote_solana',
-        'clusters/solana_cluster'
-      ]
+      id: 'developing/dev_environment/local_proxy_remote_solana'
     },
     { type: 'html', value: '<div class="sidebar-menu-divider"/>' },
     { type: 'html', value: '<h4 class="sidebar-menu-title">Learn</h4>' },

From ca3a895a244a806743fa4e7bfb24378fbe520558 Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Mon, 28 Aug 2023 16:39:06 +0100
Subject: [PATCH 07/16] finishes proof and updates style guide

---
 .../styles/Google-adapted/Substitutions.yml   |  9 ++++----
 .github/vale-todo.txt                         | 15 +++++++++++++
 .../local_proxy_remote_solana.md              | 22 +++++++++----------
 3 files changed, 31 insertions(+), 15 deletions(-)
 create mode 100644 .github/vale-todo.txt

diff --git a/.github/styles/Google-adapted/Substitutions.yml b/.github/styles/Google-adapted/Substitutions.yml
index db89b9c9..dcb0f360 100644
--- a/.github/styles/Google-adapted/Substitutions.yml
+++ b/.github/styles/Google-adapted/Substitutions.yml
@@ -60,7 +60,7 @@ swap:
   cryptobots: CryptoBots
   Cryptobots: CryptoBots
   curated roles: predefined roles
-  devnet: DevNet
+  '(?:dev net|Dev net|Dev-net|DevNet)': Devnet|Proper noun for named devnet (and sentence start)
   DAPP|DApp: dApp
   data are: data is
   deselect: clear
@@ -108,7 +108,7 @@ swap:
   '(?:log into|Log into|login to|Login to)': log in to
   long press: touch & hold
   '(?:mac OS|macos|Mac OS|Mac os)': macOS
-  '(?:main net|Main net|main-net|Main-net)': MainNet|PascalCase for named mainnet (and sentence start)
+  '(?:main net|Main net|main-net|Main-net|MainNet)': Mainnet|Proper noun for named mainnet (and sentence start)
   '(?:market-makers|Market-makers)': market makers|Market makers
   make sure: ensure
   '(?:Meta Mask|Meta mask|Meta-Mask|meta mask|meta-mask|metaMask)': MetaMask
@@ -145,16 +145,17 @@ swap:
   static IP address: static external IP address
   stylesheet: style sheet
   synch: sync
+  '(?:test net|Test net|Test-net|Test-net)': Testnet|Proper noun for named testnet (and sentence start)
   tablename: table name
   tablet: device
   touch: tap
   TX: tx
-  url:  URL
+  url: URL
   usecase: use case
   U.S.: US
   U.S.A.: USA
   '(?:validity rollup|validity Rollup)': Validity Rollup
   World Wide Web: web
-  web3: Web3
+  '(?:web3|web 3|Web 3)': Web3
   '(?:ZK Rollup|ZK rollup|ZK-Rollup|zk rollup|zk-rollup)': ZK-rollup
 
diff --git a/.github/vale-todo.txt b/.github/vale-todo.txt
new file mode 100644
index 00000000..343467a8
--- /dev/null
+++ b/.github/vale-todo.txt
@@ -0,0 +1,15 @@
+TODO: add to vale
+
+Indexer as proper noun
+Database suggestion -- if active component of the system, then proper noun
+
+
+Kill first-person rule from Google adapted
+
+Drop one of these triggers (only needs 1)
+   
+ 119:149  warning     Consider using 'to' instead of  write-good-adapted.exchange  
+                      'in order to'. This makes it                                 
+                      simpler and clearer.                                         
+ 119:149  warning     Use 'to' instead of 'in order   Google-adapted.Substitutions 
+                      to'.                 
\ No newline at end of file
diff --git a/docs/developing/dev_environment/local_proxy_remote_solana.md b/docs/developing/dev_environment/local_proxy_remote_solana.md
index a94d21ca..05bd10f3 100644
--- a/docs/developing/dev_environment/local_proxy_remote_solana.md
+++ b/docs/developing/dev_environment/local_proxy_remote_solana.md
@@ -20,7 +20,7 @@ The [Proxy local testing tutorial](/docs/operating/basic) describes how to perfo
   * Solana [Testnet](https://docs.solana.com/clusters#testnet)/[Devnet](https://docs.solana.com/clusters#devnet)/[Mainnet](https://docs.solana.com/clusters#mainnet-beta) is used, and the Proxy interacts with it through Neon EVM.
 
 ## Set up a local Proxy
-First, set up and host a Proxy locally as per the following steps. After executing these commands, the Proxy will be available at `http://localhost:9090/solana`. This address and port are set by default.
+First, set up and host a Proxy locally as per the following steps. After executing these commands, the Proxy is available at `http://localhost:9090/solana`. This address and port are set by default.
 
 ### Step 1: Docker
 Docker images themselves are never "started" and never "running". The `docker run` command takes the Docker image as a template and produces a container from it. Before starting your Proxy container, you need to start service containers.
@@ -41,8 +41,8 @@ sudo systemctl start docker
 ```
 :::
 
-### Step 2: Run the Database, Indexer, and Proxy Services
-In this step, you will create the services necessary for the function of the Proxy (including database and indexer services), as well as the Proxy service itself. These services, the functions of which are described below, will be created from a docker-compose.yml file.
+### Step 2: Run the Database, Indexer, and Proxy services
+In this step, you will create the services necessary for the function of the Proxy (including Database and Indexer services), as well as the Proxy service itself. These services, whose functions follow, are controlled by a docker-compose.yml file.
 
 #### Database Services
 This container aims to handle the database that stores all the relevant Ethereum processing metadata linked to each other: **`transactions`**, **`blocks`**, **`receipts`**, **`accounts`**, etc. This data is consumed by the **Indexer** service.
@@ -51,16 +51,16 @@ Currently, Neon EVM proxies are hard coded to work with PostgreSQL. To connect t
 
 > Only authorized Operators can change the settings of these parameters. Learn more about [operating a Neon Proxy](/docs/operating/operator-introduction.md)
 
-#### Indexer Service
-The indexer service indexes all the relevant Ethereum processing metadata consisting of **`signatures`**, **`transactions`**, **`blocks`**, **`receipts`**, **`accounts`**, etc. It gathers all this data from the Solana blockchain, filtering them by the EVM contract address. It enables us to provide our users with the Ethereum API.
+#### Indexer service
+The Indexer service indexes all the relevant Ethereum processing metadata consisting of **`signatures`**, **`transactions`**, **`blocks`**, **`receipts`**, **`accounts`**, etc. It gathers all this data from the Solana blockchain, filtering them by the EVM contract address. It enables us to provide our users with the Ethereum API.
 
-#### Proxy Service
+#### Proxy service
 The Proxy service is a core service that allows Ethereum-like transactions to be processed on Solana, taking full advantage of Solana-native functionality, including the ability to execute transactions in parallel.
 
 The Neon EVM address is registered inside `neonlabsorg/proxy`, so the Proxy knows which Neon EVM is running in the Solana cluster. After executing this command, the Proxy will be available at `http://localhost:9090/solana`. This address and port are set by default.
 
-#### Create and Run Services with Docker Compose
-In order to create and run these services, 
+#### Create and run services with Docker Compose
+In order to create and run these services: 
 
 1. Create a "keys" folder and put your allowlisted key into it. Note that the file with the Operator key should be named `id.json`.
 ```bash
@@ -107,7 +107,7 @@ Creating proxy ... done
 
 ## Connect to a Solana cluster RPC endpoint
 
-A Proxy connects to a public [Solana cluster RPC endpoint](https://docs.solana.com/cluster/rpc-endpoints) depending on the `SOLANA_URL` value set. The table below shows the *endpoint* value that is set automatically based on the value of the `CONFIG` flag.
+A Proxy connects to a public [Solana cluster RPC endpoint](https://docs.solana.com/cluster/rpc-endpoints) depending on the `SOLANA_URL` value set. The following table shows the *endpoint* value that's set automatically based on the value of the `CONFIG` flag.
 
 ### RPC endpoints
 CONFIG | RPC Endpoint
@@ -116,9 +116,9 @@ Devnet | `https://api.devnet.solana.com`
 Testnet | `https://api.testnet.solana.com`
 Mainnet | `https://api.mainnet-beta.solana.com`
 
-To use a different endpoint, you need to specify the variable `-e SOLANA_URL='http://<Solana node RPC endpoint>'` on the command line. For example, in order to use devnet, add the flag `-e SOLANA_URL='https://api.devnet.solana.com'`.
+To use a different endpoint, you need to specify the variable `-e SOLANA_URL='http://<Solana node RPC endpoint>'` on the command line. For example, to use Devnet, add the flag `-e SOLANA_URL='https://api.devnet.solana.com'`.
 
-When a Proxy is deployed, it generates a wallet containing a key pair. If you do not need the new wallet and want to use the keys you already have, you need to specify the path to your wallet on the command line.
+When a Proxy is deployed, it generates a wallet containing a key pair. If you don't need the new wallet and want to use the keys you already have, you need to specify the path to your wallet on the command line.
 
 **Command Line Options**
   * `~/.config/solana/id.json` — absolute path to your key pair file stored locally

From 19f6e7a0eee367872a2c8f8fd29e0446a0fbd84f Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Fri, 1 Sep 2023 12:02:06 +0100
Subject: [PATCH 08/16] style only

---
 .github/styles/Grammarly.csv | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.github/styles/Grammarly.csv b/.github/styles/Grammarly.csv
index 854512b3..c0d8ecff 100644
--- a/.github/styles/Grammarly.csv
+++ b/.github/styles/Grammarly.csv
@@ -106,6 +106,8 @@ StrakEx,StarkEx,"typo fix"
 "white paper",whitepaper,"Existing style, maintain consistency"
 "White paper",Whitepaper,"Existing style, maintain consistency"
 "web3,web 3,Web 3",Web3,"Existing style, maintain consistency"
+"Wrapped","Wrapped","Be very careful using this term Neon EVM does NOT wrap tokens: NeonPass provides an ERC-20 interface to SPL tokens: no mint, no burn"
+"wrapped",,"wrapped","Be very careful using this term Neon EVM does NOT wrap tokens: NeonPass provides an ERC-20 interface to SPL tokens: no mint, no burn"
 "ZK-rollup;ZKRollup;zk-rollup;zkRollup",ZK-Rollup,"Existing style, maintain consistency"
 "zk SNARK",zk-SNARK,"Existing style, maintain consistency"
 "zk STARK",zk-STARK,"Existing style, maintain consistency"

From 19c80057a65a11c33a43c35561b7fb4551400e66 Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Fri, 1 Sep 2023 12:51:37 +0100
Subject: [PATCH 09/16] added mainnet contract

---
 .../dev_environment/local_proxy_remote_solana.md           | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/developing/dev_environment/local_proxy_remote_solana.md b/docs/developing/dev_environment/local_proxy_remote_solana.md
index 05bd10f3..ef558266 100644
--- a/docs/developing/dev_environment/local_proxy_remote_solana.md
+++ b/docs/developing/dev_environment/local_proxy_remote_solana.md
@@ -4,7 +4,7 @@ proofedDate: 20230828
 iterationBy: na
 includedInSite: true
 approvedBy: na
-comment: Local to local was updated -- todo verify this page; may need update also e.g. instruction says For Devnet/Testnet, it should be `eeLSJgWzzxrqKv1UxtRVVH8FX3qCQWUs9QuAjJpETGU` but are Devnet and Testnet not two different entities?
+comment: 
 ---
 
 :::info
@@ -69,8 +69,9 @@ mv {PATH_TO_WHITELISTED_KEYS} keys/
 ```
 
 2. Set the following environment variables
-   - `EVM_LOADER`
-     - For Devnet/Testnet, it should be `eeLSJgWzzxrqKv1UxtRVVH8FX3qCQWUs9QuAjJpETGU`
+   - `EVM_LOADER`, i.e. the contract address for Neon EVM
+     - For Devnet/Testnet, use: `eeLSJgWzzxrqKv1UxtRVVH8FX3qCQWUs9QuAjJpETGU`
+     - For Mainnet, use: `NeonVMyRX5GbCrsAHnUwx1nYYoJAtskU1bWUo6JGNyG`
    - `SOLANA_URL`
      - Refer to the [RPC Endpoints table](#rpc-endpoints)
    - `PROXY_VERSION`

From ea2df1023307faf01ba05a48e76fc1f637b3722e Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Mon, 4 Sep 2023 15:58:57 +0100
Subject: [PATCH 10/16] adds keys for review

---
 docs/developing/dev_environment/local_proxy_remote_solana.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/developing/dev_environment/local_proxy_remote_solana.md b/docs/developing/dev_environment/local_proxy_remote_solana.md
index ef558266..01c74c04 100644
--- a/docs/developing/dev_environment/local_proxy_remote_solana.md
+++ b/docs/developing/dev_environment/local_proxy_remote_solana.md
@@ -13,7 +13,9 @@ The [Proxy local testing tutorial](/docs/operating/basic) describes how to perfo
 
 
 ## Prerequisites
-[Docker](https://docs.docker.com/get-docker/); `docker-compose` v1.29 is recommended.
+- [Docker](https://docs.docker.com/get-docker/); `docker-compose` v1.29 is recommended.
+- Operator keys. Test [public keys are available](https://github.com/neonlabsorg/neon-evm/tree/develop/evm_loader/program/config).
+
 
 ## Network configuration
   * The target Solana cluster is accessed via the locally-hosted Proxy.

From 88268cc29c83dba3473d5ed23b6417db918c9db1 Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Wed, 13 Sep 2023 09:18:29 +0100
Subject: [PATCH 11/16] Feature/ndev 1996/neon transfer demo (#75)

* NDEV-1996,PROD-157. Changed neon transfer docs page. Added iframe for Neon Transfer Demo.

* Move integrating_walletconnect.md -> integrating_walletconnect.mdx

* edits for NDEV

* completes first pass review

* Added comment answers.

* fixes subject structure

---------

Co-authored-by: Igor Prokopev <ip@neonlabs.org>
---
 README.md                                     |   4 +-
 .../interacting_with_spl_tokens.md            |   2 +-
 docs/developing/integrate/neon_transfer.mdx   | 181 ++++++++++++++++++
 .../developing/integrate/neon_transfer_sdk.md | 134 -------------
 ...nnect.md => integrating_walletconnect.mdx} | 111 +++++------
 docs/quick_start.mdx                          |   2 -
 docs/tokens/token_list.md                     |   2 +-
 sidebars.js                                   |  10 +-
 src/components/DemoFrame/index.tsx            |  15 ++
 src/components/DemoFrame/styles.css           |   7 +
 10 files changed, 263 insertions(+), 205 deletions(-)
 create mode 100644 docs/developing/integrate/neon_transfer.mdx
 delete mode 100644 docs/developing/integrate/neon_transfer_sdk.md
 rename docs/developing/integrate/wallets/{integrating_walletconnect.md => integrating_walletconnect.mdx} (69%)
 create mode 100644 src/components/DemoFrame/index.tsx
 create mode 100644 src/components/DemoFrame/styles.css

diff --git a/README.md b/README.md
index 8ea4eeca..0c8984c8 100644
--- a/README.md
+++ b/README.md
@@ -85,12 +85,12 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
 <Tabs>
-	<TabItem value="View" label="View your balance" default>
+	<TabItem value="Opt1" label="First option" default>
 
 ************
 
 </TabItem>
-<TabItem value="Retrieve" label="Retrieve your balance" default>
+<TabItem value="Opt2" label="Second option" default>
 
 	*********
 </TabItem>
diff --git a/docs/developing/deploy_facilities/interacting_with_spl_tokens.md b/docs/developing/deploy_facilities/interacting_with_spl_tokens.md
index 7afc54d2..288e4a0c 100644
--- a/docs/developing/deploy_facilities/interacting_with_spl_tokens.md
+++ b/docs/developing/deploy_facilities/interacting_with_spl_tokens.md
@@ -25,7 +25,7 @@ This allows Solana liquidity to be available to EVM bytecode contracts (Solidity
 |Mainnet| 0x6B226a13F5FE3A5cC488084C08bB905533804720|
 
 :::info
-To be able to use an SPL token from a Solana account balance, it must be transferred to a Neon EVM account via the [NeonPass SDK](/docs/developing/integrate/neon_transfer_sdk).
+To be able to use an SPL token from a Solana account balance, it must be transferred to a Neon EVM account via [NeonPass](/docs/developing/integrate/neon_transfer).
 :::
 
 ## ERC-20 Factory Contract
diff --git a/docs/developing/integrate/neon_transfer.mdx b/docs/developing/integrate/neon_transfer.mdx
new file mode 100644
index 00000000..f743ce40
--- /dev/null
+++ b/docs/developing/integrate/neon_transfer.mdx
@@ -0,0 +1,181 @@
+---
+title: Neon Transfer Client
+proofedDate: na
+iterationBy: na
+includedInSite: true
+approvedBy: na
+comment: Vale not setup for mdx on this branch -- needs merge of branch with fix to do full proof. Grammarly proofing done
+---
+
+import { DemoFrame } from '@site/src/components/DemoFrame';
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+
+This page explains how to pass tokens between Solana and Neon EVM programmatically.
+
+## TL;DR
+
+- [NeonPass UI](https://devnet.neonpass.live) is available as an npm package
+- [React demo](https://codesandbox.io/s/neon-transfer-demo-z93nlj) available.
+
+## Introduction
+
+This page describes how to use the Neon token pass tool: providing the same functionality as the [NeonPass UI](https://devnet.neonpass.live).
+The tool is an npm package that supports the transfer of SPL or ERC-20 tokens between Solana and Neon EVM.
+
+
+## Prerequisites
+
+- You need to provide Solana and Neon EVM providers from supported official libraries such as `@solana/web3.js` or `web3.js`, `ether.js` and `WalletConnect`.
+- Supported browser plugins (e.g. Phantom or MetaMask wallets).
+
+<!-- I don't understand provide providers above -->
+<!-- Should provide access for providers in browser plugins (It is developer abstractions) -->
+
+## Step 1: Install and setup
+
+### 1.1 Install the package
+
+<Tabs>
+  <TabItem value="Opt1" label="Yarn" default>
+
+```sh
+yarn add neon-portal
+```
+
+</TabItem>
+<TabItem value="Opt2" label="npm" default>
+
+```sh
+npm install neon-portal --save
+```
+</TabItem>
+</Tabs>
+
+### 1.2 Enable access to wallets
+
+Next, create access for providers and connect wallets for Neon EVM and Solana networks.
+
+:::note
+The following example uses `web3.js`, but it is also possible  to use [alternatives](#alternative-libraries).
+:::
+
+```javascript
+import { clusterApiUrl } from '@solana/web3.js';
+import Web3 from 'web3';
+
+const SOLANA_DEVNET = clusterApiUrl('devnet');
+const NEON_DEVNET = new Web3.providers.HttpProvider('https://devnet.neonevm.org');
+const connection = new Connection(SOLANA_DEVNET, 'confirmed');
+const web3 = new Web3(NEON_DEVNET);
+
+// Simple way to use private keys for wallets
+// For integration of browser ext., read official wallets docs.
+const solanaWallet = Keypair.fromSecretKey(decode(`<your private Solana key>`));
+const neonWallet = web3.eth.accounts.privateKeyToAccount(`<your private Neon EVM key>`);
+```
+### 1.3 Configure parameters
+
+We employ the `evmParams` method from Neon EVM to obtain specific addresses and constants required for seamless operations.
+
+```javascript
+const proxyApi = new NeonProxyRpcApi(urls);
+// ...
+const neonProxyStatus = await proxyApi.evmParams();
+const neonEvmProgram = new PublicKey(neonProxyStatus.NEON_EVM_ID);
+const neonTokenMint = new PublicKey(neonProxyStatus.NEON_TOKEN_MINT);
+```
+
+:::note
+For testing, use `NEON_TRANSFER_CONTRACT_DEVNET` or `NEON_TRANSFER_CONTRACT_MAINNET` constants. These objects contain snapshots with the latest `neonProxyStatus` state.
+:::
+
+## Step 2: Transfer tokens
+
+### Transfer NEON
+
+<Tabs>
+  <TabItem value="Opt1" label="Solana to Neon EVM" default>
+
+
+This example will generate a transaction to transfer NEON from Solana to Neon EVM. It utilizes the functions found in the `neon-transfer.ts` file.
+
+```javascript
+const neonToken: SPLToken = {
+  ...NEON_TOKEN_MODEL,
+  address_spl: proxyStatus.NEON_TOKEN_MINT,
+  chainId: CHAIN_ID
+};
+const transaction = await solanaNEONTransferTransaction(solanaWallet, neonWallet, neonEvmProgram, neonTokenMint, neonToken, amount); // Solana Transaction object
+transaction.recentBlockhash = (await connection.getLatestBlockhash('finalized')).blockhash; // Network blockhash
+const solanaSignature = await sendSolanaTransaction(connection, transaction, [signer], false, { skipPreflight: false }); // method for sign and send transaction to network
+console.log(solanaSignature);
+```
+
+</TabItem>
+<TabItem value="Opt2" label="Neon EVM to Solana" default>
+
+Similarly, to transfer NEON from Neon EVM to Solana, use this pattern:
+
+```javascript
+const transaction = await neonNeonWeb3Transaction(web3, neonWallet, NEON_TRANSFER_CONTRACT_DEVNET, solanaWallet, amount); // Neon EVM Transaction object
+const neonSignature = await sendNeonTransaction(web3, transaction, neonWallet); // method for sign and send transaction to network
+console.log(neonSignature);
+```
+
+</TabItem>
+</Tabs>
+
+
+### Transfer ERC-20 tokens
+
+When working with Devnet, Testnet, or Mainnet, different ERC-20 tokens are utilized. We maintain a JSON [list of supported tokens](https://github.com/neonlabsorg/token-list). Alternatively, please refer to the [token list](/docs/tokens/token_list.md).
+
+<!-- todo we need a single source of truth not 2 different pages to go to which may drift! Suggest JSON as API to feed the docs site -->
+
+<Tabs>
+  <TabItem value="Opt1" label="Solana to Neon EVM" default>
+
+To transfer ERC-20 tokens from Solana to Neon EVM, use the following patterns:
+
+```javascript
+const token = tokenList[0];
+const transaction = await neonTransferMintWeb3Transaction(connection, web3, proxyApi, proxyStatus, neonEvmProgram, solanaWallet, neonWallet, token, amount);
+transaction.recentBlockhash = (await connection.getLatestBlockhash()).blockhash;
+const solanaSignature = await sendSolanaTransaction(connection, transaction, [signer], true, { skipPreflight: false });
+console.log(solanaSignature);
+```
+
+</TabItem>
+<TabItem value="Opt2" label="Neon EVM to Solana" default>
+
+Similarly, to transfer ERC-20 tokens from Neon EVM to Solana:
+
+```javascript
+const token = tokenList[0];
+const mintPubkey = new PublicKey(token.address_spl);
+const associatedToken = getAssociatedTokenAddressSync(mintPubkey, solanaWallet);
+const solanaTransaction = createMintSolanaTransaction(solanaWallet, mintPubkey, associatedToken, proxyStatus);
+solanaTransaction.recentBlockhash = (await connection.getLatestBlockhash()).blockhash;
+const neonTransaction = await createMintNeonWeb3Transaction(web3, neonWallet.address, associatedToken, token, amount);
+const signedSolanaTransaction = await sendSolanaTransaction(connection, solanaTransaction, [signer], true, { skipPreflight: false });
+const signedNeonTransaction = await sendNeonTransaction(web3, neonTransaction, neonWallet);
+console.log(signedSolanaTransaction, signedNeonTransaction);
+```
+
+</TabItem>
+</Tabs>
+
+
+## Alternative libraries
+
+We employ the [web3.js](https://web3js.readthedocs.io/en/v1.10.0/) library to streamline our code within the Neon Transfer codebase. However, you can opt for alternatives such as [ethers.js](https://docs.ethers.org/v6/), or [WalletConnect](https://walletconnect.com/).
+
+## React App
+
+The following [live demo with an open codebase](https://github.com/neonlabsorg/neon-client-transfer/tree/master/examples/react/neon-transfer-react) supports the tooling via React App.
+
+<DemoFrame id='neon-transfer-react'
+  src='https://codesandbox.io/embed/neon-transfer-demo-z93nlj?fontsize=14&hidenavigation=1&theme=dark'
+  title='Neon-Transfer-Demo'></DemoFrame>
diff --git a/docs/developing/integrate/neon_transfer_sdk.md b/docs/developing/integrate/neon_transfer_sdk.md
deleted file mode 100644
index c46ada64..00000000
--- a/docs/developing/integrate/neon_transfer_sdk.md
+++ /dev/null
@@ -1,134 +0,0 @@
----
-title: Neon Transfer SDK
-proofedDate: na
-iterationBy: na
-includedInSite: true
-approvedBy: na
-comment: todo this requires overhaul 
----
-
-This page provides you with the information required to pass tokens between Solana and Neon EVM programmatically. 
-
-## TL;DR
-
-- The tool is available as an npm package
-- The package provides the same function as the [NeonPass UI](https://devnet.neonpass.live)
-
-## Introduction
-
-The following npm package provides a token pass tool: the same package provides the functionality to [NeonPass UI](https://devnet.neonpass.live). It's built to be compliant with the React hooks architecture, but you are welcome to use clean core functions.
-
-You need to provide the addresses for a Solana-compatible wallet such as a Phantom wallet and an EVM-compatible wallet such as a MetaMask wallet. Both of these addresses are passed as required properties. The module checks whether both wallet objects: window.solana and window.ethereum, exist. If they don't, it throws an error. 
-
-<!-- Is this relevant to end user?
-  For clean working configuration example we have to rebuild connect status buttons, their transfer callbacks and error handling. -->
-
-## Step 1: install and setup
-
-Firstly, install the package:
-
-```sh
-npm install neon-portal --save
-```
-
-## Step 2: understand the parameters
-
-The following table provides details of the required and optional parameters. 
-
-
-|Property name |   Type|Description| is required |
-|:-------------|:------:|:------------------------------------------------------------------------------:|:------------|
-|solanaWalletAddress |  String  |Address for Solana-compatible wallet  |        true |
-|neonWalletAddress |  String  | Address of existing EVM-compatible wallet associated with a Neon Account | true |
-|web3 | Object| Connection module of Ethereum Web3.js framework. Connects the App to the Neon EVM network.| true |
-|connection |  Object  | Connection module of Solana-Web3.js framework. You may connect to your own node if you have one. Else you will be provided with the default RPC.|        true |
-|onBeforeCreateInstructions | function |Function executed at the start of transfer intitation. It's used in both transfer functions (`createNeonTransfer` and `createSolanaTransfer`).  | false |
-|onCreateNeonAccountInstruction | function | Function, executed on instruction build <!-- todo find out more --> | false |
-|onBeforeSignTransaction | function | Function called before transaction is signed by Solana-compatible wallet. <!-- todo unpack whether is used by "both" txs -->| false |
-|onBeforeNeonSign | function |Function used when you transfer from Neon EVM to Solana. Called before request for tx approval.    |       false |
-|onSuccessSign | function | Function, that extracts signatures after the tx is signed. With transfer to Neon, the function requires one argument - the Solana transaction signature. On transfer to Solana, it requires two arguments: Solana and Neon signatures. <!-- todo follow up and verify that this is genuine --> |false |
-|onErrorSign | function | Function called if wallet throws an error after sign attempt. |false |
-
-## Examples
-
-### Vanilla JS
-
-```javascript
-import { NeonPortal } from "neon-portal"
-//for transfer ERC20 tokens use:
-import { MintPortal } from "neon-portal"
-
-const eventParams = {
-  onBeforeSignTransaction: () => {
-    /* Your state changes here */
-  },
-  /* ... */
-};
-const portal = new NeonPortal({
-  solanaWalletAddress: publicKey,
-  neonWalletAddress: account,
-  customConnection: connection,
-  /*
-    You can pass events as properties, but these functions will be called at portal context.
-  */
-  ...eventParams,
-});
-button.addEventListener("onClick", (e) => {
-  /*
-    If you want to save context of event function - pass it as first argument
-    Else first argument should be undefined
-  */
-  portal.createNeonTransfer(eventParams, amount, splToken);
-});
-```
-
-### React
-
-You can use the React hook provided by the package. This hook allows you to pass event parameters as objects. The module can be used by the React wrapper:
-
-```javascript
-import {useNeonTransfer} from "neon-portal/src/react"
-```
-
-
-For example:
-
-
-``` javascript
-export const useTransfering = () => {
-  const { setPending, setSign, setError } = useStates()
-  const { publicKey } = useWallet()
-  const { account, library } = useWeb3React();
-  // The following function `useConnection` defaults to a publically-available RPC. If you are using your own Solana node in the context of your App, pass the RPC address as a second argument to the neon transfer hook. 
-  const connection = useConnection()
-  // The next line calls the React hook `useNeonTransfer`, this will import both functions: createNeonTransfer and createSolanaTransfer.
-  const { createNeonTransfer, createSolanaTransfer } = useNeonTransfer(
-    {
-      onBeforeCreateInstruction: () => {
-        setPending(true)
-      },
-      onBeforeSignTransaction: () => {
-        setPending(false)
-        setTransfering(true)
-      },
-      /*
-    sig - Signature of the sending wallet, i.e. of the user approving the transaction request
-    txHash - Identifier of the transaction on Neon EVM <!-- todo need to confirm is this a txHash on Neon NOT on Solana ?? -->
-    */
-      onSuccessSign: (sig, txHash) => {
-        setSign(sig, txHash)
-        setTransfering(false)
-      },
-      onErrorSign: (e) => {
-        setError(e.message)
-        setPending(false)
-      },
-    },
-    connection,
-    library, // Web3 Library instance  
-    publicKey, // Phantom wallet public key
-    account // MetaMask wallet public key associated with a Neon Account
-  )
-  return { createNeonTransfer, createSolanaTransfer }
-}
-```
diff --git a/docs/developing/integrate/wallets/integrating_walletconnect.md b/docs/developing/integrate/wallets/integrating_walletconnect.mdx
similarity index 69%
rename from docs/developing/integrate/wallets/integrating_walletconnect.md
rename to docs/developing/integrate/wallets/integrating_walletconnect.mdx
index ee2d3706..8e8fb844 100644
--- a/docs/developing/integrate/wallets/integrating_walletconnect.md
+++ b/docs/developing/integrate/wallets/integrating_walletconnect.mdx
@@ -6,39 +6,37 @@ includedInSite: true
 approvedBy: na
 comment: TODO suggest a boilerplate ReactApp such as codepen be setup as an example to refer to -- this will then allow better support at Step 4 " connect your preferred wallet with Neon EVM DevNet within the WalletConnect interface. " to be included rather than just alluded to
 ---
-
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import devnet from '@site/static/img/doc-images/developing/integrate/protocols/walletconnect/devnet.png';
 import projectid from '@site/static/img/doc-images/developing/integrate/protocols/walletconnect/projectid.png';
 import connected from '@site/static/img/doc-images/developing/integrate/protocols/walletconnect/connected.png';
 
-
 ## Introduction
 
 [WalletConnect](https://docs.walletconnect.com/2.0/) is a protocol providing a decentralized standard to connect Web3 wallets and dApps.
 
 This guide lays out a step-by-step process to configure a React or HTML dApp on NeonEVM using WalletConnect's [Web3Modal SDK](https://docs.walletconnect.com/2.0/web3modal/about).
 
-Web3Modal is a library that allows users to connect to any dApp via the WalletConnect interface. 
+Web3Modal is a library that allows users to connect to any dApp via the WalletConnect interface.
 
 :::info
 
-Check out Web3Modal code on [GitHub](https://github.com/WalletConnect/web3modal). 
+Check out Web3Modal code on [GitHub](https://github.com/WalletConnect/web3modal).
 
 Web3Modal supports:
 
-- [React](https://docs.walletconnect.com/2.0/reactnative/walletconnectmodal/about)
+- [React](https://docs.walletconnect.com/2.0/web3modal/react/wagmi/installation)
 - [HTML](https://docs.walletconnect.com/2.0/web/web3modal/html/wagmi/installation)
 
 :::
 
 ## Get Started
 
-### Step 1: Create a project 
+### Step 1: Create a project
+
+Log into [WalletConnect Cloud](https://cloud.walletconnect.com/) to create a new project and copy the Project ID.
 
-Log into [WalletConnect Cloud](https://cloud.walletconnect.com/) to create a new project and copy the Project ID. 
- 
 <!-- following text style works -- not convinced image class is working >> alt is to use  docusaurus method -- but that means keeping images in static folder NOT granular as per current method applied in this site https://docusaurus.io/docs/static-assets -->
 
 > <img src={projectid} width="450" />
@@ -55,38 +53,40 @@ From WalletConnect's project page:
 
 ### Step 3: Configure your app
 
-For this guide, we are configuring a React App. 
+For this guide, we are configuring a React App.
 <!-- yet we also provide a pure HTML path, yes?? -->
 
 3.1 Install the required packages into your app:
 
-
 <Tabs>
-  <TabItem value="npm" label="npm" default>
+<TabItem value="npm" label="npm" default>
+
+```bash
+npm install @web3modal/ethereum @web3modal/react wagmi ethers@^5
+```
 
-```npm install @web3modal/ethereum @web3modal/react wagmi ethers@^5```
-  </TabItem>
-  <TabItem value="yarn" label="yarn">
+</TabItem>
+<TabItem value="yarn" label="yarn">
 
-```yarn add @web3modal/ethereum @web3modal/react wagmi ethers@^5```
-  </TabItem>
+```
+yarn add @web3modal/ethereum @web3modal/react wagmi ethers@^5
+```
+
+</TabItem>
 </Tabs>
 
 
-3.2 Set `projectId`={your_project_ID} in your .env file.
+3.2 Set `projectId={your_project_ID}` in your `.env` file.
 
-3.3 Import the following packages in your app.js file:
+3.3 Import the following packages in your `app.jsx` file:
 
-```
+```javascript
 import { EthereumClient, w3mConnectors, w3mProvider } from '@web3modal/ethereum'
-import { Web3Modal } from '@web3modal/react'
 import { configureChains, createClient, WagmiConfig } from 'wagmi'
 import { neonDevnet } from '@wagmi/chains'
 
-
 const chains = [neonDevnet]
-const projectId = “<import_from_env>”
-
+const projectId = "<import_from_env>"
 
 const { provider } = configureChains(chains, [w3mProvider({ projectId })])
 const wagmiClient = createClient({
@@ -94,59 +94,50 @@ const wagmiClient = createClient({
     connectors: w3mConnectors({ projectId, version: 1, chains }),
     provider
 })
-const ethereumClient = new EthereumClient(wagmiClient, chains)
 ```
 
 3.4 Pass your ethereumClient and `projectId` to the Web3Modal component:
 
 <Tabs>
-  <TabItem value="React/Next" label="React/Next" default>
-
-```JS
-function App() 
-  {
-   return (
-     <>
-       <WagmiConfig client={wagmiClient}>
-         <HomePage />
-       </WagmiConfig>
-
-
-       <Web3Modal projectId={projectId} ethereumClient={ethereumClient} />
-     </>
-   )
-  }
-```
-  </TabItem>
-  <TabItem value="HTML" label="HTML">
+<TabItem value="React/Next" label="app.jsx" default>
+
+```javascript
+import { Web3Modal } from '@web3modal/react'
 
-```HTML
-export const web3Modal = new Web3Modal(
- {
-   projectId,
- },
- ethereumClient
-);
+const web3Modal = new Web3Modal({ projectId }, ethereumClient); // for using in code
+const ethereumClient = new EthereumClient(wagmiClient, chains)
 
-index.html
+function App() {
+  return <>
+    <WagmiConfig client={wagmiClient}>
+      <HomePage />
+    </WagmiConfig>
+    <Web3Modal projectId={projectId} ethereumClient={ethereumClient} />
+  </>
+}
+```
 
+</TabItem>
+<TabItem value="HTML" label="HTML">
+
+```html
 <body>
-   <div id="app">
-     <w3m-core-button></w3m-core-button>
-   </div>
-   <script type="module" src="main.js"></script>
- </body>
+  <div id="app">
+    <w3m-core-button></w3m-core-button>
+  </div>
+  <script type="module" src="main.js"></script>
+</body>
  ```
-  </TabItem>
+
+</TabItem>
 </Tabs>
 
 
 ### Step 4: Connect your wallet
 
-Start your application:
- `npm start`/`yarn start`  
+Start your application: `npm/yarn start`
 
-You may now  connect your preferred wallet with Neon EVM DevNet within the WalletConnect interface. 
+You may now  connect your preferred wallet with Neon EVM DevNet within the WalletConnect interface.
 
 <!-- would like to support the end user with details for this step also -->
 
diff --git a/docs/quick_start.mdx b/docs/quick_start.mdx
index c9b06ab8..6a2b7172 100644
--- a/docs/quick_start.mdx
+++ b/docs/quick_start.mdx
@@ -9,8 +9,6 @@ comment:
 import {QuickStartList} from '@site/src/components/QuickStartList'
 import {CommonBannerBlock} from '@site/src/components/CommonBannerBlock'
 import {ServiceLink} from '@site/src/components/ServiceLink'
-import {PageHelpful} from '@site/src/components/PageHelpful'
-import {FeedbackForm} from '@site/src/components/FeedbackForm'
 
 
 *Neon EVM is a synergetic solution for anyone looking to scale Ethereum dApps on Solana in a developer-friendly manner and tap into Solana's vibrant ecosystem.*
diff --git a/docs/tokens/token_list.md b/docs/tokens/token_list.md
index 020ae20d..46c62b45 100644
--- a/docs/tokens/token_list.md
+++ b/docs/tokens/token_list.md
@@ -24,7 +24,7 @@ For the most up-to-date list of tokens whose contracts are deployed in Neon EVM
 
 ## Token list: NeonPass-supported tokens
 
-The following tables provide the addresses of ERC-20 interface contracts for the tokens available through [NeonPass](docs/developing/integrate/neon_transfer_sdk.md).
+The following tables provide the addresses of ERC-20 interface contracts for the tokens available through [NeonPass](docs/developing/integrate/neon_transfer.mdx).
 
 ## ERC-20 interface addresses on Neon
 
diff --git a/sidebars.js b/sidebars.js
index a7c3e968..63bc32b6 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -34,7 +34,7 @@ const sidebars = {
       label: '💰 Tokens',
       items: [
         'tokens/neon_token',
-        'tokens/gas_fees',      
+        'tokens/gas_fees',
         'tokens/token_list'
       ]
     },
@@ -85,7 +85,7 @@ const sidebars = {
       items: [
         'developing/deploy_facilities/interacting_with_spl_tokens',
         'tokens/token_list',
-        'developing/integrate/neon_transfer_sdk'
+        'developing/integrate/neon_transfer'
         ]
     },
     {
@@ -96,7 +96,7 @@ const sidebars = {
         'developing/integrate/wallets/integrating_walletconnect',
         'developing/integrate/oracles/integrating_chainlink',
         'developing/integrate/oracles/integrating_pyth',
-        'developing/integrate/middleware/the-graph'      
+        'developing/integrate/middleware/the-graph'
       ]
     },
     {
@@ -138,7 +138,7 @@ const sidebars = {
         'architecture/eth_sol_solution',
         'architecture/solana-accounts'
       ]
-    },   
+    },
     { type: 'html', value: '<div class="sidebar-menu-divider"/>' },
     { type: 'html', value: '<h4 class="sidebar-menu-title">Operate</h4>' },
     {
@@ -154,7 +154,7 @@ const sidebars = {
         'operating/enhanced',
         'operating/installation/setup_kubernetes'
       ]
-    },    
+    },
     {
       type: 'category',
       label: 'Configuration',
diff --git a/src/components/DemoFrame/index.tsx b/src/components/DemoFrame/index.tsx
new file mode 100644
index 00000000..d16fc242
--- /dev/null
+++ b/src/components/DemoFrame/index.tsx
@@ -0,0 +1,15 @@
+import React from 'react';
+import './styles.css';
+
+export const DemoFrame = (props: { src: string, title?: string; }) => {
+  return <>
+    <iframe className='demo-frame'
+            src={props.src}
+            title={props.title ?? ''}
+            allow='accelerometer; ambient-light-sensor; camera; encrypted-media; geolocation; gyroscope; hid; microphone; midi; payment; usb; vr; xr-spatial-tracking'
+            sandbox='allow-forms allow-modals allow-popups allow-presentation allow-same-origin allow-scripts'
+    ></iframe>
+  </>;
+};
+
+export default DemoFrame;
diff --git a/src/components/DemoFrame/styles.css b/src/components/DemoFrame/styles.css
new file mode 100644
index 00000000..84841705
--- /dev/null
+++ b/src/components/DemoFrame/styles.css
@@ -0,0 +1,7 @@
+.demo-frame {
+  width: 100%;
+  height: 500px;
+  border: 0;
+  border-radius: 4px;
+  overflow: hidden;
+}

From 1f6efc2bc92f8e38732f4bc1b74d282253808457 Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Tue, 19 Sep 2023 13:19:34 +0100
Subject: [PATCH 12/16] Proof (#47)

* removes: includedInSite:false item

* begins a QA/proofing round

* updates style guide with legal guiderails

* updates style guide with legal guiderails

* updates to legal guide rails

* updates Grammarly to include additional legal warnings, fixes non-alignment with style in 1 doc

* minor fix
---
 .../styles/Google-adapted/Abbreviations.yml   |   4 +-
 .github/styles/Google-adapted/FirstPerson.yml |   1 -
 .github/styles/Grammarly.csv                  | 135 +++++++--
 .github/styles/Vocab/Neon/accept.txt          |   3 +-
 docs/about/terminology.md                     | 278 ------------------
 docs/architecture/eth_sol_solution.md         |  94 +++---
 docs/architecture/neon_evm_arch.md            |  14 +-
 .../wallets/integrating_walletconnect.mdx     |   8 +-
 8 files changed, 183 insertions(+), 354 deletions(-)
 delete mode 100644 docs/about/terminology.md

diff --git a/.github/styles/Google-adapted/Abbreviations.yml b/.github/styles/Google-adapted/Abbreviations.yml
index 98efb6ca..65dcc778 100644
--- a/.github/styles/Google-adapted/Abbreviations.yml
+++ b/.github/styles/Google-adapted/Abbreviations.yml
@@ -65,8 +65,8 @@ exceptions:
   - NET
   - NFT
   - NEON
-  - N-trx
-  - N-trxes
+  - N-tx
+  - N-txs
   - NodeJS
   - NOTE
   - NVDA
diff --git a/.github/styles/Google-adapted/FirstPerson.yml b/.github/styles/Google-adapted/FirstPerson.yml
index d4a1ca40..0b7b8828 100644
--- a/.github/styles/Google-adapted/FirstPerson.yml
+++ b/.github/styles/Google-adapted/FirstPerson.yml
@@ -11,4 +11,3 @@ tokens:
   - \bme\b
   - \bmy\b
   - \bmine\b
-  - ours?
diff --git a/.github/styles/Grammarly.csv b/.github/styles/Grammarly.csv
index 854512b3..1c341223 100644
--- a/.github/styles/Grammarly.csv
+++ b/.github/styles/Grammarly.csv
@@ -1,85 +1,158 @@
 "Original text",Rule,Explanation
-"OX",0x,"Existing style, maintain consistency"
+"&",and,"Only apply & in heading or TL;DR (with the exception of webpage copy where space is an issue)"
+"OX,ox,Ox,oX",0x,"Existing style, maintain consistency"
 "24:7",24/7,"Existing style, maintain consistency"
-"api;Api",API,"Existing style, maintain consistency"
+"Advisory,advisory","Information","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "amongst",among,"Existing style, maintain consistency"
-"Berkley Packet Filter;berkeley packet filter",Berkeley Packet Filter,"Existing style, maintain consistency"
-"bi-weekly","biweekly","Existing style, maintain consistency"
+"Anonymous","Pseudonymous","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"api;Api",API,"Existing style, maintain consistency"
+"Backdoor","Alternative","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"best","a good option","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Berkley Packet Filter",Berkeley Packet Filter,"Existing style, maintain consistency"
+"Betting","Predicting","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Bi-weekly,","biweekly","Existing style, maintain consistency"
+"Black market","Unregulated market","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Blow up","Increase rapidly","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Boom","Surge","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Bribe","Incentivize (but use carefully)","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Bubble","Surge","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"bulletproof","resilient","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Bust","Decline","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Cash cow","Profitable venture","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Cash-out","Withdraw","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "cex",CEX,"Acronyms in caps"
-"CEXes",CEXs,"Existing style, maintain consistency"
+"CEXes,CEX's",CEXs,"Existing style, maintain consistency"
+"Cheat","Deceive","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Collude","Collaborate (but use carefully. Only use if there is evidence of collaboration or clear intent)","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Con","Deception","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "cryptobots;Cryptobots","CryptoBots","Brand name"
 "cryptopunks;Cryptopunks",CryptoPunks,"Brand name"
-"devnet",Devnet,"If this is Neon's Devnet or any other systems' use proper noun."
+"devnet,devNet","Devnet",If this is Neon's Devnet or any other systems' use proper noun."
 "DOA",DAO,"Oops, typo"
 "DApp,Dapp,DAPP",dApp,"Exception is sentence start = DApp"
 "DApps,Dapps,DAPPs,DAPPS",dApps,"Exception is sentence start = DApps"
-""dex",DEX,"Acronyms in caps"
-"DEXes",DEXs,"Existing style, maintain consistency"
+dex",DEX,"Acronyms in caps"
+"DEXes;DEX's",DEXs,"Existing style, maintain consistency"
 discord,Discord,"Brand name"
 dockerfile,Dockerfile,"Existing style, maintain consistency"
+"Double-dip","Reinvest","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Dump","Release","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Easy money","Potential returns","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Elusive","Challenging","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "Eterum,Etherum",Ethereum,"Watch out, typo" 
 "ERC 20;Erc-20;ERc-20;Erc 20;ERc 20,ERC20;Erc20;ERc20",ERC-20,"Existing style, maintain consistency"
 "ERC 721;Erc-721;ERc-721;Erc 721;ERc 721,ERC721;Erc721;ERc721",ERC-721,"Existing style, maintain consistency"
 "end-point;end point",endpoint,"Existing style, maintain consistency"
+"Evasive","Avoidant","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "evm;Evm",EVM,"Existing style, maintain consistency"
+"Explosive","Significant","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Fake","Inauthentic","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"failproof","robust","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Flip","Trade","(as in quick profit) Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Front-run","Anticipate","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Gamble","Decision","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"guarantee","Suggest","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "Github,github,gitHub",GitHub,"Brand name"
 "gHz,ghz",GHz,"Standard, maintain consistency"
+"Goldmine","Opportunity","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Heist","Theft","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Hidden","Lesser-known","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"hot","trending","(as in a hot investment)Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Hustle","Endeavor","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Hype","Excitement","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"insider","expert","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"In the black","Profitable","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"In the red","Unprofitable","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Illicit","Unauthorized","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Jackpot","Successful outcome","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "Javascript,javascript",JavaScript,"Brand name, maintain consistency"
 "json,Json",JSON,"when referring to a file type or the standard, use caps"
-"&",and,"Only apply & in heading or TL;DR (with the exception of webpage copy where space is an issue)"
-"re-balancing,rebalancing","Existing style, maintain consistency"
-"non-deterministic,nondeterministic","Existing style, maintain consistency"
-"world-wide,worldwide","Stay consistent!"
-"full withdrawl;full-withdrawl","Full Withdrawal","caps for the adjective or noun of a component of the system"
+"Kickback","Commission","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Kill","Excel","(as in 'kill in profits') Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "front-end;front end","frontend","Existing style, maintain consistency"
 "Decentralized finance",DeFi,"Apply acronym"
 "off boarding;off-boarding",offboarding,"Existing style, maintain consistency"
 "back-end;backend","backend","back-end is used as an adjective only."
 "ID;id",Id,"Existing style, maintain consistency"
+"Investment","Contribution","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 admin,Admin,"Use proper noun (caps) for an active component of a system e.g., ""The Admin authorizes the user""."
 "Validity rollup;validity rollup","Validity Rollup",
 "off chain;offchain",off-chain,"as an adjective off-chain would be the form plus this style has been extended for all uses"
 "permissionless,permissionlessly",,"This should quiet the standard spelling flag"
 "Layer 1;l1;layer 1",L1,"Use the acronym"
-"Layer 2;l1;layer 2",L2,"Use the acronym"
+"Layer 2;l2;layer 2",L2,"Use the acronym"
+"Lure","Attract","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "Ethereum MainNet;Ethereum-Mainnet","Ethereum Mainnet","Existing style, maintain consistency"
 built-in,builtin,"This should quiet standard spelling flag"
 governor,Governor,"Caps for a noun of an active component in the system"
 "mainnet",Mainnet,"If this is Neon's Mainnet or any other named systems' use proper noun."
 "Main-Net;Main-net;MainNet;main net;main-net;mainNet",Mainnet,"Existing style, maintain consistency"
 "Maker DAO, Maker-DAO",MakerDAO,"Brand name"
+"Manipulate","Influence","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "Merkel Patricia-Trie;Merkel Patricia Trie",Merkel-Patricia Trie,"Standard"
 "Metamask;Meta mask;metamask;metaMask",MetaMask,"Brand name"
+"Money-laundering","","Avoid entirely -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "multi sig;multi-sig",multisig,"Existing style, maintain consistency"
-"the Neon EVM",Neon EVM,"Existing style, maintain consistency"
-"NoenEVM;Noen EVM;NeonEVM",Neon EVM,"Existing style, maintain consistency"
+"NoenEVM;Noen EVM;NeonEVM;Neon EVM", Neon evm,"Existing style, maintain consistency"
+"Neon Labs","Neon EVM","It is highly unlikely that you need to use Neon Labs in the public domain. Rather just refer to the main Brand."
+"Neon Protocol","Neon EVM","It is highly unlikely that you need to use Neon Protocol in the public domain. Rather just refer to the main Brand."
+"Neon Foundation","Neon EVM","It is highly unlikely that you need to use Neon Foundation in the public domain. Rather just refer to the main Brand."
 "Neon Scan;NoenScan",NeonScan,"PascalCase for tools. Existing style, maintain consistency"
 "Neon pass;Neon Pass,NoenPass",NeonPass,"PascalCase for tools. Existing style, maintain consistency"
 "Neon faucet;Neon Faucet,NoenFaucet",NeonFaucet,"PascalCase for tools. Existing style, maintain consistency"
 "Neon",NEON,"NEON caps is the token, Neon the noun should rarely be used > provide component instead"
 "NEONS, Neons, neons",NEON,"The plural of NEON is NEON"
-"proxy",Proxy,"Existing style, maintain consistency"
+"No-brainer","Clear Choice","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "NeonProxy, Noen proxy, Neon proxy",Neon Proxy,"Existing style, maintain consistency"
 "Nft",NFT,"Acronymn as caps"
 "node JS,Node JS",NodeJS,"Brand name"
+"non-deterministic,nondeterministic","Existing style, maintain consistency"
+"Loophole","Strategy","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "L2 rollup","L2 Rollup","as per ""On the Road"" Medium post"
 "on boarding;on-boarding",onboarding,"Existing style, maintain consistency"
-"rollup",Rollup,"proper noun for all rollup types - IF compounded proper noun for leading name also"
+"Off-the-record","Unofficial","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Offshore","Overseas","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "Optimistic rollup;optimistic rollup","Optimistic Rollup","proper noun"
 operator,Operator,"caps for a noun of an active component of the system"
 "on chain;onchain",on-chain,"as an adjective on-chain would be the form plus this style has been extended for all uses"
 "OpenZepelin;OpenZeppellin",OpenZeppelin,"Brand name"
+"plummet","decrease","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "PRC",RPC,"Did you mean RPC as in Remote Procedure Call endpoint?"
 "p2p",P2P,"Brand name"
 "POH,poh",PoH,"Existing style, maintain consistency"
 "POS,pos",PoS,"Existing style, maintain consistency"
+"Profit","Return","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Ponzi","","Avoid entirely -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Promising","Potential","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"proxy",Proxy,"Existing style, maintain consistency"
+"Pump","Promote","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Pyramid","","Avoid entirely -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Quick-rich","Growth potential","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Racket","Deceptive business","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"re-balancing,rebalancing","Existing style, maintain consistency"
+"Risk-free","Lower-risk","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Rig","Influence","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Rogue","Unaligned","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"rollup",Rollup,"proper noun for all rollup types - IF compounded proper noun for leading name also"
+"Safe","Secure","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Scheme","Plan","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Scam","Fraudulent activity","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"sealevel,Sea Level",Sealevel,"Brand name"
+"secret","proprietary","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Shady","Questionable","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Shill","Advocate","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "Side chains, Side-chains;side chains, side-chains",sidechains,"Existing style, maintain consistency"
 smart-contract,"smart contract","Existing style, maintain consistency"
 "Side chain;Side-chain;side chain;side-chain",sidechain,"Existing style, maintain consistency"
-"sealevel,Sea Level",Sealevel,"Brand name"
 "singing",signing,"Do you really mean to sing?!"
+"skyrocket","increase","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Skyrocket","Increase","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Slaughter","Outperform","(as in 'slaughter the market') Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Smuggle","Transfer","(but be cautious when it comes to using Transfer for monetary value) Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "solana,Solna",Solana,"Watch out, typo" 
+"speculate","consider","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "stable coin",stablecoin,"Existing style, maintain consistency"
+"Shadow","","(as in shadow banking) Avoid entirely -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "Stark-Ex;Stark-ex;Starkex;starkex",StarkEx,"Proper noun's form"
 "StarkEx Contract;StarkEx Smart Contract;StarkEx smart Contract;Starkex Contract","StarkEx smart contract","Trial style: Proper noun plus ""common"" noun"
 "STARK key;Stark Key;starkKey","Stark key","Treat as a noun. Do not split the individual words with an adjective, rather place the adjective before the term.
@@ -90,22 +163,38 @@ StrakEx,StarkEx,"typo fix"
 "StrakGate",StarkGate,"typo fix"
 "StarkNet;StrakNet",Starknet,"typo fix"
 "spl",SPL,"Acronym has caps"
+"Stealth","Discretion","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Surefire","Likely","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Swindle","Deceptive practice","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Tax haven","Tax-efficient jurisdiction","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"The fastest,the fastest,The Fastest,THE FASTEST","","Warning -- this is a legally sensitive term. Consult with legal before using this in relation to Neon EVM's product."
+"The cheapest,the cheapest,The Cheapest,THE CHEAPEST","","Warning -- this is a legally sensitive term. Consult with legal before using this in relation to Neon EVM's product."
+"the Neon EVM",Neon EVM,"Existing style, maintain consistency"
 "time lock;time-lock",timelock,"Existing style, maintain consistency"
+"Tip","Suggestion","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "testnet",Testnet,"If this is Neon's Testnet or any other systems' use proper noun."
 "Test-Net;test-net;TestNet;Test net;test-net;testNet",Testnnet,"Existing style, maintain consistency"
 "TL:DR,tl:dr,tl;dr",TL;DR,"Existing style, maintain consistency"
 "tps",TPS,"Acronym has caps"
 "trx;TRX",tx,"Existing style to abbreviate transaction, NO CAPS, maintain consistency"
 "tvl",TVL,"Acronym has caps"
-"the Neon,The Neon","Neon","The Neon EVM can be stated as Neon EVM"
-"the Mainnet,The Mainnet","Mainnet","The Mainnet can be stated as Mainnet"
-"the Devnet,The Devnet","Devnet","The Devnet can be stated as Devnet"
+"the Neon,The Neon","Neon","In most instances, 'The Neon EVM' can be stated as Neon EVM"
+"the Mainnet,The Mainnet","Mainnet","In most instances, The Mainnet can be stated as Mainnet"
+"the Devnet,The Devnet","Devnet","'The Devnet' should most often simply be stated as Devnet"
+"unbeatable","competitive","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Undetectable","Discreet","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Under the table","","Avoid entirely -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Underground","Informal","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"Unicorn (unless referring to startups valued at $1B+)","Rare opportunity","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "UniSwap,uniswap",Uniswap,"Brand name"
+"Untraceable","Private","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "U.S,U.S.",US,"Existing style, maintain consistency"
 "U.S.A,U.S.A.",US,"Existing style, maintain consistency"
+"web3,web 3,Web 3",Web3,"Existing style, maintain consistency"
 "white paper",whitepaper,"Existing style, maintain consistency"
 "White paper",Whitepaper,"Existing style, maintain consistency"
-"web3,web 3,Web 3",Web3,"Existing style, maintain consistency"
+"Windfall","Earnings","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"World-wide,world-wide","worldwide","Stay consistent!"
 "ZK-rollup;ZKRollup;zk-rollup;zkRollup",ZK-Rollup,"Existing style, maintain consistency"
 "zk SNARK",zk-SNARK,"Existing style, maintain consistency"
 "zk STARK",zk-STARK,"Existing style, maintain consistency"
diff --git a/.github/styles/Vocab/Neon/accept.txt b/.github/styles/Vocab/Neon/accept.txt
index 08c86c9a..91be2141 100644
--- a/.github/styles/Vocab/Neon/accept.txt
+++ b/.github/styles/Vocab/Neon/accept.txt
@@ -31,6 +31,7 @@ MakerDAO
 Markdown
 Merkel-Patricia Trie
 MetaMask
+N-tx
 Neon
 NEON
 NEON token
@@ -57,7 +58,7 @@ React.js
 readline
 rst
 Sealevel
-S-trx
+S-tx
 S-trexes
 Solana
 Solana cluster
diff --git a/docs/about/terminology.md b/docs/about/terminology.md
deleted file mode 100644
index 6f56ec1f..00000000
--- a/docs/about/terminology.md
+++ /dev/null
@@ -1,278 +0,0 @@
----
-title: Terminology
-proofedDate: na
-iterationBy: na
-includedInSite: false
-approvedBy: na
-comments: checking this is on link-fixer branch
----
-
-### Application Binary Interface (ABI)
-A JSON-based description on how to convert user actions between their JSON and binary representations. The ABI may also describe how to convert the database state to/from JSON. Once you have described your contract via an ABI, this allows developers and users to interact with your contract seamlessly via JSON.  
-
----  
-
-### Account
-A unique identifier that is required to interact with Solana. Unlike most other cryptocurrencies, transfers are sent to a readable account name instead of a public key, while keys attributed to the account are used to sign transactions.  
-
----  
-
-### Block
-A special structure for recording a group of transactions in blockchain systems. A block consists of a header and a list of transactions. The block header includes its hash, the hash of the previous block, transaction hashes, and additional overhead information.  
-
----  
-
-### Blockchain
-A database with a strict structure and certain rules for building chains of transactions and accessing information which excludes data theft, fraud, violation of property rights, and more.  
-
----  
-
-### Block log
-An append-only log of blocks written to disk and containing all the irreversible blocks.  
-
----  
-
-### Berkeley Packet Filter (BPF)
-A technology used in computer operating systems to analyze network traffic. It provides a raw interface to data link layers, permitting raw link-layer packets to be sent and received.  
-
----  
-
-### Container
-An object created using a Docker image and containing all the necessary components for the operation of the application. The container is a secure platform for the operation of the application.  
-
----  
-
-### Cryptographic Hash Function (CHF)
-A type of hash function that takes an input (or `message`) and returns a fixed-size alphanumeric string. The alphanumeric string is called the `hash value`, `message digest`, `digital fingerprint`, `digest`, or `checksum`.  
-
----  
-
-### Daemon
-A program on Linux systems that is launched by the system itself and runs in the background without direct user interaction.  
-
----  
-
-### Decentralized Application (dApp)
-An application built on a decentralized network that combines a smart contract and a frontend user interface.  
-
----  
-
-### Digital signature
-A mathematical algorithm used to verify the authenticity and integrity of digital messages or documents. A valid digital signature helps to reassure the recipient that the message was created by a known sender, and that the message was not altered in transit. Digital signatures are a standard feature of most cryptographic protocol suites, and are also commonly used for software distribution, financial transactions, contract management software, and other cases where it is important to detect and/or prevent forgery or tampering.  
-
----  
-
-### Docker
-Software used to automate application installation in the virtualization environment at the operating system level. Packages an application, along with all its environments and dependencies, into a container that can be ported to any Linux system with cgroups support in the kernel, and also provides a container management environment.  
-
----  
-
-### Docker Compose
-A command line tool for managing multiple Docker multi-container applications.  
-
----  
-
-### Dockerfile
-A file containing instructions and parameters for creating a Docker image for specific tasks.  
-
----  
-
-### Docker image
-A read-only template on the Docker platform that is used to create containers.  
-
----  
-
-### Delegated Proof-of-Stake (DPoS)
-A consensus algorithm initially developed by Daniel Larimer in 2013 for BitShares. It is sometimes referred to as the more “democratic” version of Proof-of-Stake (PoS).  
-
----  
-
-### ERC-20
-The token standard used for Ethereum smart contracts. Developed in 2015, ERC-20 defines a common list of rules that Ethereum tokens must implement. This gives developers the ability to program how new tokens will function within the Ethereum ecosystem.  
-
----  
-
-### ERC-721
-A more complex token standard than ERC-20 that is split across a number of contracts with multiple optional extensions. Unlike ERC-20, tokens of this standard are not interchangeable. No two ERC-721 tokens are the same, and each have different characteristics.  
-
----  
-
-### Gwei
-A denomination, or smaller unit, of the cryptocurrency ETH, which is used on the Ethereum network. Gwei is the most commonly used unit of ETH because gas prices are easily specified in gwei. For example, instead of saying that your gas costs *0.000000001* ETH, you can say your gas costs *1* gwei.  
-
----  
-
-### Head block
-The head block is the last block written to the blockchain, stored in reversible blocks.  
-
----  
-
-### Key
-A string of characters (bit string) that is used by the cryptographic algorithm for encrypting and decrypting messages, setting and verifying digital signatures, and identification. Keys are symmetric (the same key is used for encryption and decryption), and asymmetric (public and private).  
-
----  
-
-### Merkle Mountain Range
-A type of merkle tree that can be visualized as many (perfect) merkle trees which are then combined into 1, by creating a single root from all of their peaks.  
-
----  
-
-### Merkle-Patricia Tree
-A hash tree that stores key-value pairs, with the keys being represented in binary form. The nodes of this tree consist of two types: prefix nodes that contain part of the path, and end nodes that contain the stored value.  
-
----  
-
-### MetaMask
-A software cryptocurrency wallet that is used to interact with the Ethereum blockchain. It allows users to access their Ethereum wallet through a browser extension or mobile app, which can then be used to interact with decentralized applications.  
-
----  
-
-### Minimum Viable Product (MVP)
-A product with minimal features and/or functionality, but enough to satisfy early consumers. Its purpose is to gather feedback and learnings to inform further product development.  
-
----  
-
-### NeonPass
-An open-source service for transferring SPL tokens to Neon EVM.  
-
----  
-
-### NeonSwap
-An open-source service being a fork of [Uniswap V2](https://uniswap.org/blog/uniswap-v2) and modified to work with Neon EVM.  
-
----  
-
-### Node
-A separate software device that is connected to the blockchain network according to the client-server scheme. Nodes are active elements and form the basis of the blockchain network technology.  
-
----  
-
-### Phantom
-A software cryptocurrency wallet reimagined for DeFi. Phantom makes it safe and easy for you to store, send, receive, collect, and swap tokens on the Solana blockchain.  
-
----  
-
-### Plugin
-A software component built as a separate module that adds new capabilities to the main program.  
-
----  
-
-### Private key
-A secret number (code string) that you can use to securely access your wallet or bitcoin address, and do transactions.  
-
----  
-
-### Proof-of-History (PoH)
-The blockchain algorithm for time synchronization. Instead of using the traditional timestamps, PoH is able to prove that a message or event occurred at a certain time after one event, but before another.  
-
----  
-
-### Proof-of-Stake (PoS)
-Proof-of-Stake is a method of cryptocurrency protection in which the probability of forming the next block on the blockchain depends on the existing stake of the participant and not on powerful equipment, as is the case with Proof-of-Work (PoW).  
-
----  
-
-### Public key
-A publicly available key that is required for users to receive transactions into their account. A public key can be inferred from a signature.  
-
----  
-
-### Remix
-An online Integrated Development Environment (IDE) used to write, compile, deploy, and debug Solidity code. This web tool can be connected with MetaMask and used to deploy smart contracts to both the Solana Testnet and Solana Mainnet.
-
----  
-
-### Remote Procedure Call (RPC)
-A system that lets users send queries and commands to a system remotely.  
-
----  
-
-### Rivest-Shamir-Adleman (RSA)
-A public key cryptosystem that is widely used for secure data transmission.  
-
----  
-
-### Serialization
-The process of turning an object in memory into a stream of bytes so it can be stored on disk or sent over the network.  
-
----  
-
-### Signature
-A mathematical algorithm used to demonstrate the authenticity of digital messages or documents.  
-
----  
-
-### Slippage
-The difference between where the computer signaled the entry and exit for a trade and where actual clients, with actual money, entered and exited the market using the computer’s signals.
-
----  
-
-### Slot
-The period of time during which a block is created. Collectively, slots create a logical clock. Slots are ordered sequentially and non-overlapping, comprising roughly equal time.  
-
----  
-
-### Smart contract
-A computer protocol intended to facilitate, verify, or enforce the negotiation or performance of a contract.  
-
----  
-
-### Sollet
-Sollet (Sollet.io) is browser-based wallet for Solana and SPL tokens. It was created by the Project Serum team.  
-
----  
-
-### Solana Program Library (SPL)
-A contract containing a system registry of tokens that are in the system along with the Solana balances of their accounts.  
-
----  
-
-### SPL token
-A token registered in the *[Solana Program Library (SPL)](https://spl.solana.com/token)*.  
-
----  
-
-### Staked tokens
-Tokens allocated for a stake acquisition that can’t be used for anything else in this state. The user can stake active tokens listed on their balance, or deposit them. The user can also perform the reverse operation: withdraw tokens from the staked state to active.  
-
----  
-
-### Tmpfs
-A temporary file storage paradigm implemented in many Unix-like operating systems. It is intended to appear as a mounted file system, but data is stored in volatile memory instead of a persistent storage device.  
-
----  
-
-### Transaction
-A combination of one or more actions that results in a complete all-or-nothing change to the blockchain. Usually the executional result of a smart contract.  
-
----  
-
-### Uniswap
-A decentralized exchange. Liquidity providers can earn fees by providing the required tokens or ETH for both sides of a trade. Uniswap is widely used and therefore has one of the highest liquidities for a wide range of tokens.  
-
----  
-
-### USDT
-USDT is the ticker symbol for the Tether stablecoin cryptocurrency.  
-
----  
-
-### Wallet
-Wallets are clients that store keys that may or may not be associated with the permissions of one or more accounts. Ideally a wallet has a locked (encrypted) and unlocked (decrypted) state, which is protected by a high entropy password.  
-
----  
-
-### Web3
-In the context of Ethereum, Web3 is a collection of decentralized apps that run on the blockchain and allow anyone to participate without monetizing their personal data.  
-
----  
-
-### Wormhole
-The Solana Wormhole is an Ethereum bridge that helps transfer wealth from the Ethereum blockchain to the Solana blockchain. It also helps transfer liquidity between the Ethereum ERC-20 token standard to the Solana SPL token standard.  
-
----  
-
-### ZK-STARK
-Zero-Knowledge Scalable Transparent Argument of Knowledge (zk-STARK) is a cryptographic protocol that uses public zero-knowledge probabilistically-verifiable proofs. This technology allows users to exchange verified information without disclosing it, or to perform computations with a third party without disclosing the computation.  
-
----  
diff --git a/docs/architecture/eth_sol_solution.md b/docs/architecture/eth_sol_solution.md
index 799e6fac..c1d03aec 100644
--- a/docs/architecture/eth_sol_solution.md
+++ b/docs/architecture/eth_sol_solution.md
@@ -1,10 +1,10 @@
 ---
 title: Ethereum & Solana in Synergy
-proofedDate: na
+proofedDate: partial vale docs/architecture/eth_sol_solution.md
 iterationBy: na
 includedInSite: true
 approvedBy: na
-comment:
+comment: Vladimir asked for BPF to be removed -- Yuri was going to investigate more about why -- todo in place inline
 ---
 
 *This section describes a unique solution that allows Ethereum users to use the key features of Solana and vice versa.*
@@ -14,50 +14,51 @@ comment:
   * **BPF** - the Berkeley Packet Filter virtual machine
   * **Contract** - smart contract
   * **dApp** - a decentralized application (plural: dApps)
-  * **N-trx** - a neon transaction formed according to the Ethereum network and executed inside Neon EVM
+  * **N-tx** - a Neon transaction formed according to the Ethereum network and executed inside Neon EVM
   * **EVM** - the Ethereum Virtual Machine
   * **Proxy** - Neon Web3 Proxy
-  * **S-trx** - a transaction formed according to the rules of the Solana network
+  * **S-tx** - a transaction formed according to the rules of the Solana network
 
 
-## Key Capabilities of Ethereum
+## Key capabilities of Ethereum
 
 Ethereum’s core innovation, the EVM, is a Turing-complete software that runs on the Ethereum network. The EVM allows developers to build and deploy dApps, which makes the process of creating blockchain applications much easier and more efficient. Contracts are treated as autonomous scripts or stateful dApps that are stored in the Ethereum blockchain for execution by the EVM at a later stage.
 
-Ethereum has a large number of developer tools available in its ecosystem, including *MetaMask*, *Remix*, and *Truffle*. The toolkit allows users to write dApps in Solidity, which is the standard language for developing contracts.
+Ethereum has a large number of developer tools available in its Ecosystem, including *MetaMask*, *Remix*, and *Truffle*. The toolkit allows users to write dApps in Solidity, which is the standard language for developing contracts.
 
-Ethereum is the flagship of the crypto world. It runs numerous distributed applications that have proven themselves in the market and are in demand all over the world.
+Ethereum is the flagship of the crypto world. It runs numerous dApps that have proven themselves in the market and are in demand all over the world.
 
 
-## Key Capabilities of Solana
+## Key capabilities of Solana
 
 Solana is an exceptionally fast, secure, and relatively inexpensive blockchain network.  
 The Solana blockchain provides:
   * High performance, including:
     * Short block processing time
-    * Processing many transactions per second due to the ability to execute transactions in parallel.
-  * Low transaction fees.
-  * The ability to increase the number of nodes in the network without reducing the performance of the network as a whole.
-  * The capability to build in coding languages *C*, *C++*, and *Rust*.
+    * Processing many transactions per second due to the ability to execute transactions in parallel
+  * Low transaction fees
+  * The ability to increase the number of nodes in the network without reducing the performance of the network as a whole
+  * The capability to build in coding languages *C*, *C++*, and *Rust*
 
 
-## The Goal
+## The goal
 
-The goal is to find a solution that combined the best of both Ethereum and Solana. This solution would allow:
-  * Solana users to use unique Ethereum toolkits to write dApps in Solidity.
-  * Ethereum dApps to be deployed on Solana, thereby attracting a huge audience of Ethereum users to the Solana blockchain.
-  * Ethereum users to significantly increase the speed of transactions and reduce the fee charged for their execution by using Solana.
+The goal was to find a solution that combined the best of both Ethereum and Solana. This solution allows:
+  * Solana users to use Ethereum toolkits to write dApps in Solidity
+  * Ethereum dApps to deploy on Solana, thereby attracting the huge audience of Ethereum users to the Solana blockchain
+  * Ethereum users to significantly increase the speed of transactions and reduce the fee charged for their execution by using Solana
 
 
-## The Proposed Solution
+## The solution
 
-To achieve our goal, the following solution was proposed and implemented by the Neon Labs development team:
-  * The EVM was integrated with Solana and named Neon EVM (an emulator implemented using Rust).
-  * The Neon EVM operates inside Solana providing parallel transaction processing and a low transaction fee.
-  * The Neon Web3 Proxy was created to mediate interactions between the Ethereum user (account) and Neon EVM. The main function of the proxy is to provide an API for external clients.
+Neon EVM provides:
+  * An EVM integrated with Solana (an emulator implemented using Rust)
+  * Solana's parallel transaction processing and a low transaction fee
+  * Neon Proxy: to mediate interactions between the Ethereum user (account) and Neon EVM
+  > The main function of the Proxy is to provide an API for external clients
 
 
-## The Solution in Detail
+## The solution in detail
 
 The block diagram of the solution is shown in Fig. 1.
 
@@ -70,38 +71,53 @@ Fig. 1
 </div>
 
 ### Berkeley Packet Filter (BPF)
+
 The BPF virtual machine is installed in Solana, allowing developers to embed other virtual machines inside Solana.  
 
-Using BPF capabilities, a contract called Neon EVM is created in Solana, and the EVM was loaded inside it.  
+Using BPF capabilities, a contract called Neon EVM was created in Solana with the EVM loaded inside it.  
 
 Because Solana has a contract update mechanism, the Neon EVM contract can also be updated independently from updates to the Solana node itself. This allows developers to update EVM versions without updating all the blockchain nodes.  
 
-### Neon Web3 Proxy
-A user can form transactions under an Ethereum account and sign them with a public key generated in Ethereum. Transactions formed according to Ethereum rules are sent to the input of the Proxy component. This component converts N-trxs into transactions under Solana rules.  
+### Neon Proxy
+
+A user can form transactions under an Ethereum account and sign them with a public key generated in Ethereum. Transactions formed according to Ethereum rules are sent to the input of the Proxy component. This component converts N-txs into transactions under Solana rules.  
+
+Converting a transaction in a one-to-one format is difficult due to two Solana constraints:
+- The size of N-tx can exceed that of S-tx
+- The amount of resources that an S-tx can spend is limited
 
-The size of N-trx can exceed that of S-trx. Also, the amount of resources that an S-trx can spend is limited. Converting a transaction in a one-to-one format is difficult due to the potential lack of resources. Therefore, it was decided to generate multiple S-trxs for one N-trx. Each transaction generated is signed with a proxy key. The proxy sends the generated batch of transactions to Solana.  
+To overcome these, Neon Proxy generates multiple S-txs for one N-tx. Each transaction generated is signed with a Neon Proxy key. Neon Proxy then sends the batch of transactions to Solana.  
 
 ### Web3 API
-The proxy provides the full Web3 API to interact with external clients. In Ethereum, some contracts work at the blockchain level, and there is also an API that is supported by an Ethereum node. Clients that are created for Ethereum contracts support standard interfaces. For a client (such as MetaMask or Remix) to work in a web browser, it must work via the Web3 API. With Neon EVM, Ethereum dApps can be deployed on Solana without any edits to the source code or recompilation: dApps look and function exactly the same.  
 
-Clients will work on a different blockchain if they are provided the same interface. You can do this by changing the address for where these clients need to go. Ethereum contracts and clients do not need to be rewritten to work in Solana; you just need to register the proxy address. Any client can run a proxy to deploy a contract inside Solana. The interface that the clients interact with will be the same as for dApps running on Ethereum.
+Neon Proxy provides the full Web3 API to interact with external clients. In Ethereum, some contracts work at the blockchain level, and there is also an API that is supported by an Ethereum node. Clients that are created for Ethereum contracts support standard interfaces. For a client (such as MetaMask or Remix) to work in a web browser, it must work via the Web3 API. With Neon EVM, Ethereum dApps can be deployed on Solana with minimal reconfiguration of the source code: dApps look and function exactly the same.  
+
+Clients work on a different blockchain via the same interface by changing the address to which the clients are directed. This allows Ethereum contracts and clients to work in Solana by updating the registered proxy address and minimal reconfiguration. Any client can run a proxy to deploy a contract inside Solana. The interface that the clients interact with will be the same as for dApps running on Ethereum.
+
+<!-- not yet true that any client can run a proxy to deploy a contract inside Solana is it todo -->
 
 ### Neon EVM
+
 The Neon EVM runs inside BPF, which is run by Solana. The Neon EVM is a Solana contract, so it recognizes the transaction format from the received batch. Neon EVM extracts data from each transaction, and therefore it can retrieve all the original user information that was placed in the transaction.  
 
-The Neon EVM also validates the signature that is in the transaction. If the signature is authentic, the Neon EVM takes the contract code that the transaction is addressed to and starts to execute it. As soon as the contract code has been executed successfully, Neon EVM records a new state.  
+(<!-- I can't unpack the preceeding p todo -->)
+
+The Neon EVM also validates the N-tx signature. If the signature is authentic, the Neon EVM takes the contract code that the transaction is addressed to and starts to execute it. As soon as the contract code has been executed successfully, Neon EVM records a new state.  
 
-For example, if the transaction is a token transfer, the contract code sends tokens from one account to another. The Neon EVM simply records this new state.  
+For example, if the transaction is a token transfer, the contract code sends tokens from one account to another. The Neon EVM records this new state.  
 
 The user can also form a transaction to load a contract inside Neon EVM. In this case, the contract code will be written for Ethereum. A bytecode of this contract code will be loaded inside the Neon EVM. The contract itself and its data will be stored inside Solana.  
 
-### Account Data Storage
-Solana stores account data. The Neon EVM has access to this storage, and uses the account data. After an account is registered in Solana, the account data is placed in this storage. Ethereum accounts are also stored here, but in the Solana representation. For each Ethereum address there is a corresponding account in the Solana representation. A contract code is placed in a corresponding account of this storage.  
+### Account data storage
+
+Solana stores account data in temporary storage. The Neon EVM has access to this storage, and uses the account data. After an account is registered in Solana, the account data is placed in this storage. Each Ethereum address corresponds to a Solana account, and contract code is placed into the corresponding account's storage.  
 
 Neon EVM interacts with a set of data that is stored on Solana's accounts. The Neon EVM can take a contract code from there using the corresponding account address to validate a transaction. The Neon EVM contains a virtual machine inside it that runs according to Ethereum rules.  
 
+<!-- final line of the above p does not belong here todo -->
+
 
-## How Neon Works
+## How Neon works
 
 A user calls a client that generates a transaction and sends it to the proxy, which is running the Neon EVM emulator inside it. (Fig. 2). The transaction is formed in accordance with the Ethereum rules, and contains mandatory fields, including:
   * **Nonce** - the number of transactions sent from the current address
@@ -119,16 +135,16 @@ Fig. 2
 
 </div>
 
-To perform this transaction, the Neon EVM emulator makes a request to Solana to get state data. The proxy requests a blockchain state from Solana and makes a test launch of N-trx using the Solana state. On the basis of the data received, Proxy forms the new transaction according to Solana's rules. The transaction generated for Solana will contain the packaged N-trx, as well as the account data required to complete the transaction, including:
-  * The Payer. (The account that pays for the transaction.)
-  * Other accounts involved in the execution of this transaction.  
+To perform this transaction, the Neon EVM emulator makes a request to Solana to get state data. The proxy requests a blockchain state from Solana and makes a test launch of N-tx using the Solana state. On the basis of the data received, Neon Proxy forms the new transaction according to Solana's rules. The transaction generated for Solana will contain the packaged N-tx, as well as the account data required to complete the transaction, including:
+  * The payer: the account that pays for the transaction
+  * Other accounts involved in the execution of this transaction
 
 Next, the transaction is forwarded inside Solana, where participants of the transaction are determined according to the account data. The data added includes details about people who initiate and take part in processing the transaction. The operator of the proxy is specified as the payer. The payer will be rewarded for completing the transaction.  
 
-Next, the transaction is transferred to Neon EVM, where its signature is checked according to Ethereum rules. If the signature is valid, the transaction will be transferred to the Solana blockchain for execution. Since testing of N-trx is carried out, it is possible to provide Solana with all the necessary information to run the execution of the N-trx in parallel.  
+Next, the transaction is transferred to Neon EVM, where its signature is checked according to Ethereum rules. If the signature is valid, the transaction will be transferred to the Solana blockchain for execution. Since testing of N-tx is carried out, it is possible to provide Solana with all the necessary information to run the execution of the N-tx in parallel.  
 
 
-## Benefits of the Neon Solution
+## Benefits of the Neon solution
 
 Neon's solution offers the following benefits:
   * No changes or additional resources are required to implement dApps on Solana.
diff --git a/docs/architecture/neon_evm_arch.md b/docs/architecture/neon_evm_arch.md
index 1ae86719..03c37141 100644
--- a/docs/architecture/neon_evm_arch.md
+++ b/docs/architecture/neon_evm_arch.md
@@ -33,14 +33,14 @@ The components of the architecture are:
 ### Neon EVM User (user)
 Any user who has an account in Neon EVM with a balance in ETH, ERC-20, or ERC-721 tokens.  
 
-### Solana Transaction (S-trx)
+### Solana Transaction (S-tx)
 A transaction formed according to Solana network rules with a signature produced by Solana rules.  
 
-### Neon Transaction (N-trx)
+### Neon Transaction (N-tx)
 A transaction formed according to Ethereum rules with a signature produced by Ethereum rules.  
 
 ### Neon EVM Client (client)
-An application that has an EVM (Solidity, Vyper, etc.) bytecode contract loaded into Neon EVM. The application generates a transaction N-trx according to Ethereum rules and sends it to a proxy. Before sending N-trx, the client transfers the required funds to the Solana deposit to cover the costs of an operator.  
+An application that has an EVM (Solidity, Vyper, etc.) bytecode contract loaded into Neon EVM. The application generates a transaction N-tx according to Ethereum rules and sends it to a proxy. Before sending N-tx, the client transfers the required funds to the Solana deposit to cover the costs of an operator.  
 
 ### Neon EVM Operator (operator)
 A role performed by a Solana account using a software tool. Within Neon EVM, an operator is provided with software in the form of a proxy in order to fulfill certain functions. The operator can deploy one or more proxies. The operator can also configure one proxy for multiple operators, as well as run several proxies with different settings.  
@@ -50,9 +50,9 @@ The software that an operator uses to do their job. Although the proxy is not a
 
 The proxy contains an EVM emulator that pre-tests the execution of the transaction. This testing determines the number of coins required on the operator's balance, as well as the current exchange rate of SOL to ETH. Each operator configures their proxy server with this course in mind. This relates to economic motivation.  
 
-A proxy converts N-trx into transactions under Solana rules. N-trx is signed by a user, while S-trxs are signed by an operator. The Neon transaction text is loaded from the received S-trxs into a separate account that is created in Solana. Neon EVM receives a command to execute the transaction located at the address of this account.  
+A proxy converts N-tx into transactions under Solana rules. N-tx is signed by a user, while S-txs are signed by an operator. The Neon transaction text is loaded from the received S-txs into a separate account that is created in Solana. Neon EVM receives a command to execute the transaction located at the address of this account.  
 
-More details on how the proxy converts a N-trx to multiple S-trxs can be found [here](https://neonlabsorg.medium.com/neon-web3-proxy-facilitating-seamless-transactions-on-neon-evm-b33c2041aa08).
+More details on how the proxy converts a N-tx to multiple S-txs can be found [here](https://neonlabsorg.medium.com/neon-web3-proxy-facilitating-seamless-transactions-on-neon-evm-b33c2041aa08).
 
 Below is a list of the main Neon Web3 Proxy features that are implemented in the Neon EVM:
   * Receiving requests over Web3 API protocol
@@ -165,9 +165,9 @@ The ERC-20 wrapper allows users to transfer their SPL tokens on the ERC-20 Balan
 ### Payment Queues
 
 **The Issue**  
-If the ERC-20 TKN contract contains only one map for all users and their balances, it can result in an issue: if the majority of users pay with ETH tokens, then the same contract will appear inside each N-trx, where the value will need to be changed.  
+If the ERC-20 TKN contract contains only one map for all users and their balances, it can result in an issue: if the majority of users pay with ETH tokens, then the same contract will appear inside each N-tx, where the value will need to be changed.  
 
-This will cause all N-trxs to line up “single file”, and they cannot be executed in parallel. This is because at the final step, the funds would be transferred from the user's balance to the operator's balance within one contract.  
+This will cause all N-txs to line up “single file”, and they cannot be executed in parallel. This is because at the final step, the funds would be transferred from the user's balance to the operator's balance within one contract.  
 
 **The Solution**  
 The default token type field is added to the Neon account along with the balance. This field provides a special option that will allow a user to select a type of token for payment. The ERC-20 wrapper can be used to transfer SPL tokens from outside to an operator's account.  
diff --git a/docs/developing/integrate/wallets/integrating_walletconnect.mdx b/docs/developing/integrate/wallets/integrating_walletconnect.mdx
index 8e8fb844..4ca29d23 100644
--- a/docs/developing/integrate/wallets/integrating_walletconnect.mdx
+++ b/docs/developing/integrate/wallets/integrating_walletconnect.mdx
@@ -4,8 +4,9 @@ proofedDate: 20230427
 iterationBy: HB
 includedInSite: true
 approvedBy: na
-comment: TODO suggest a boilerplate ReactApp such as codepen be setup as an example to refer to -- this will then allow better support at Step 4 " connect your preferred wallet with Neon EVM DevNet within the WalletConnect interface. " to be included rather than just alluded to
+comment: TODO suggest a boilerplate ReactApp such as codepen be setup as an example to refer to -- this will then allow better support at Step 4 " connect your preferred wallet with Neon EVM DevNet within the WalletConnect interface. " to be included rather than just alluded to. See also comments inline
 ---
+
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import devnet from '@site/static/img/doc-images/developing/integrate/protocols/walletconnect/devnet.png';
@@ -16,7 +17,7 @@ import connected from '@site/static/img/doc-images/developing/integrate/protocol
 
 [WalletConnect](https://docs.walletconnect.com/2.0/) is a protocol providing a decentralized standard to connect Web3 wallets and dApps.
 
-This guide lays out a step-by-step process to configure a React or HTML dApp on NeonEVM using WalletConnect's [Web3Modal SDK](https://docs.walletconnect.com/2.0/web3modal/about).
+This guide lays out a step-by-step process to configure a React or HTML dApp on Neon EVM using WalletConnect's [Web3Modal SDK](https://docs.walletconnect.com/2.0/web3modal/about).
 
 Web3Modal is a library that allows users to connect to any dApp via the WalletConnect interface.
 
@@ -54,6 +55,7 @@ From WalletConnect's project page:
 ### Step 3: Configure your app
 
 For this guide, we are configuring a React App.
+
 <!-- yet we also provide a pure HTML path, yes?? -->
 
 3.1 Install the required packages into your app:
@@ -137,7 +139,7 @@ function App() {
 
 Start your application: `npm/yarn start`
 
-You may now  connect your preferred wallet with Neon EVM DevNet within the WalletConnect interface.
+You may now  connect your preferred wallet with Neon EVM Devnet within the WalletConnect interface.
 
 <!-- would like to support the end user with details for this step also -->
 

From 39e6e1e64b4da487e7a42bbb470d0295da7b7a43 Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Tue, 19 Sep 2023 13:29:43 +0100
Subject: [PATCH 13/16] updates link

---
 docs/developing/dev_environment/local_proxy_remote_solana.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/developing/dev_environment/local_proxy_remote_solana.md b/docs/developing/dev_environment/local_proxy_remote_solana.md
index 01c74c04..189fbad3 100644
--- a/docs/developing/dev_environment/local_proxy_remote_solana.md
+++ b/docs/developing/dev_environment/local_proxy_remote_solana.md
@@ -14,7 +14,7 @@ The [Proxy local testing tutorial](/docs/operating/basic) describes how to perfo
 
 ## Prerequisites
 - [Docker](https://docs.docker.com/get-docker/); `docker-compose` v1.29 is recommended.
-- Operator keys. Test [public keys are available](https://github.com/neonlabsorg/neon-evm/tree/develop/evm_loader/program/config).
+- Operator keys. Test [public keys are available](https://github.com/neonlabsorg/proxy-model.py/tree/develop/proxy/operator-keypairs).
 
 
 ## Network configuration

From 6610096a9cc3527e86a6ad612e84175c6f76845b Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Tue, 19 Sep 2023 15:07:36 +0100
Subject: [PATCH 14/16] removes links to non-existant pages

---
 docs/developing/deploy_facilities/using_remix.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/developing/deploy_facilities/using_remix.md b/docs/developing/deploy_facilities/using_remix.md
index f892059b..b946c2ea 100644
--- a/docs/developing/deploy_facilities/using_remix.md
+++ b/docs/developing/deploy_facilities/using_remix.md
@@ -7,7 +7,7 @@ approvedBy: na
 comment: 
 ---
 
-*This tutorial will show you step by step how to use [Remix](about/terminology.md#remix) and [MetaMask](about/terminology.md#metamask) to create and deploy a simple smart contract on Solana. Although the instructions use Solana's [Devnet](https://docs.solana.com/clusters#devnet), they may also be applicable to Solana's [Testnet](https://docs.solana.com/clusters#testnet) or Solana's [Mainnet Beta](https://docs.solana.com/clusters#mainnet-beta).*
+*This tutorial demonstrates step by step how to use Remix and MetaMask to create and deploy a simple smart contract on Solana. Although the instructions use Solana's [Devnet](https://docs.solana.com/clusters#devnet), they may also be applicable to Solana's [Testnet](https://docs.solana.com/clusters#testnet) or Solana's [Mainnet Beta](https://docs.solana.com/clusters#mainnet-beta).*
 
 ## Requirements
 Before you start, make sure that the following is true:

From 7fff446a37a71b4a264f4a873f5a4de9329219cd Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Tue, 19 Sep 2023 15:31:15 +0100
Subject: [PATCH 15/16] removes links to non-existant pages

---
 docs/clusters/solana_cluster.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/clusters/solana_cluster.md b/docs/clusters/solana_cluster.md
index 93bf6f41..9d88b41f 100644
--- a/docs/clusters/solana_cluster.md
+++ b/docs/clusters/solana_cluster.md
@@ -2,9 +2,9 @@
 title: Solana Clusters
 proofedDate: na
 iterationBy: na
-includedInSite: true
+includedInSite: false
 approvedBy: na
-comment: checking this is on link-fixer branch
+comment: todo find out whether this page should be included in site -- no sidebar for this
 ---
 
 A Solana cluster is a set of independently owned computers working together to verify the output of user-submitted programs. A Solana cluster can be utilized any time a user wants to preserve an immutable record of events in time or programmatic interpretations of those events. 
@@ -28,7 +28,7 @@ This is a permissionless, persistent cluster for early token holders and launch
 
 ### Synchronization
 Fast, reliable synchronization is one of the main challenges for achieving high throughput. Traditional blockchains synchronize on large chunks of transactions called blocks. As a consensus algorithm, they use *[Proof-of-Work](https://en.wikipedia.org/wiki/Proof_of_work)* or *[Proof-of-Stake](https://en.wikipedia.org/wiki/Proof_of_stake)*.  
-Unlike traditional synchronization methods, Solana takes a complete approach, which it calls *[Proof-of-History](https://docs.neonfoundation.io/docs/about/terminology/#proof-of-history-poh)*. Solana uses an optimistic method of processing blocks. (It was introduced in 1981 and is called [Optimistic Concurrency Control](https://en.wikipedia.org/wiki/Optimistic_concurrency_control).)  
+Unlike traditional synchronization methods, Solana takes a complete approach, which it calls *[Proof-of-History](https://docs.solana.com/cluster/synchronization)*. Solana uses an optimistic method of processing blocks. (It was introduced in 1981 and is called [Optimistic Concurrency Control](https://en.wikipedia.org/wiki/Optimistic_concurrency_control).)  
 The peculiarity of this method is that Solana technically never sends a *[block](about/terminology.md#block)*, but uses the term to describe the sequence of entries that validators vote on to achieve *confirmation*. By processing the transactions optimistically, there is effectively no delay between the time the last entry is received and the time when the node can vote. In the event consensus is not achieved, a node simply rolls back its state.
 
 

From 6223601c68ebcdb8b3e7b7c7a4c89ad346f0a305 Mon Sep 17 00:00:00 2001
From: m4sterbunny <m4sterbunny@gmail.com>
Date: Tue, 19 Sep 2023 15:56:37 +0100
Subject: [PATCH 16/16] removes links to non-existant pages

---
 docs/clusters/solana_cluster.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/clusters/solana_cluster.md b/docs/clusters/solana_cluster.md
index 9d88b41f..843797d4 100644
--- a/docs/clusters/solana_cluster.md
+++ b/docs/clusters/solana_cluster.md
@@ -29,7 +29,7 @@ This is a permissionless, persistent cluster for early token holders and launch
 ### Synchronization
 Fast, reliable synchronization is one of the main challenges for achieving high throughput. Traditional blockchains synchronize on large chunks of transactions called blocks. As a consensus algorithm, they use *[Proof-of-Work](https://en.wikipedia.org/wiki/Proof_of_work)* or *[Proof-of-Stake](https://en.wikipedia.org/wiki/Proof_of_stake)*.  
 Unlike traditional synchronization methods, Solana takes a complete approach, which it calls *[Proof-of-History](https://docs.solana.com/cluster/synchronization)*. Solana uses an optimistic method of processing blocks. (It was introduced in 1981 and is called [Optimistic Concurrency Control](https://en.wikipedia.org/wiki/Optimistic_concurrency_control).)  
-The peculiarity of this method is that Solana technically never sends a *[block](about/terminology.md#block)*, but uses the term to describe the sequence of entries that validators vote on to achieve *confirmation*. By processing the transactions optimistically, there is effectively no delay between the time the last entry is received and the time when the node can vote. In the event consensus is not achieved, a node simply rolls back its state.
+The peculiarity of this method is that Solana technically never sends a *block*, but uses the term to describe the sequence of entries that validators vote on to achieve *confirmation*. By processing the transactions optimistically, there is effectively no delay between the time the last entry is received and the time when the node can vote. In the event consensus is not achieved, a node simply rolls back its state.
 
 
 > **More details**