Automated scrape: 2025-11-16 00:24:31

Author: github-actions[bot]

merged_docs/all_merged.md

@@ -1,4 +1,4 @@
-# Source: https://cadence-lang.org/docs/language/
+# Source: https://cadence-lang.org/docs/language
 
 The Cadence Programming Language | Cadence
 

merged_docs/essentials_merged.md

@@ -44,7 +44,7 @@ Search
 
 On this page
 
-# Building a Frontend App
+# Building a frontend app
 
 This tutorial builds on the `Counter` contract you deployed in [Cadence Environment Setup](/blockchain-development-tutorials/cadence/getting-started/cadence-environment-setup) and [Smart Contract Interaction](/blockchain-development-tutorials/cadence/getting-started/smart-contract-interaction). It shows you how to create a simple `Next.js` frontend that interacts with the `Counter` smart contract deployed on your local Flow emulator. Instead of using FCL directly, you'll leverage [**@onflow/react-sdk**](/build/tools/react-sdk) to simplify authentication, querying, transactions, and to display real-time transaction status updates using convenient React hooks.
 
@@ -980,7 +980,7 @@ For additional details and advanced usage, refer to the [@onflow/react-sdk docum
 
 [Edit this page](https://github.com/onflow/docs/tree/main/docs/blockchain-development-tutorials/cadence/getting-started/building-a-frontend-app.md)
 
-Last updated on **Oct 30, 2025** by **cshannon1218**
+Last updated on **Nov 14, 2025** by **0xLisanAlGaib**
 
 [Previous
 

scraped_docs/cadence_lang_org_docs/docs_language.md

@@ -44,7 +44,7 @@ Search
 
 On this page
 
-# Production Deployment
+# Production deployment
 
 You've developed locally with the emulator, integrated external dependencies, built sophisticated transactions, implemented comprehensive testing, and created a frontend interface. Now it's time to take your application live and deploy it to Flow's public networks.
 
@@ -752,7 +752,7 @@ npm run build`
 
 [Edit this page](https://github.com/onflow/docs/tree/main/docs/blockchain-development-tutorials/cadence/getting-started/production-deployment.md)
 
-Last updated on **Oct 30, 2025** by **cshannon1218**
+Last updated on **Nov 14, 2025** by **0xLisanAlGaib**
 
 [Previous
 

scraped_docs/developers_flow_com/blockchain_development_tutorials_cadence_getting_started_building_a_frontend_app.md

@@ -44,14 +44,14 @@ On this page
 
 # Using Foundry with Flow
 
-Foundry is a suite of development tools that simplifies the process of developing and deploying Solidity contracts to EVM networks. This guide will walk you through the process of deploying a Solidity contract to Flow EVM using the Foundry development toolchain. You can check out the official Foundry docs [here](https://book.getfoundry.sh/).
+Foundry is a suite of development tools that simplifies the process to develop and deploy Solidity contracts to EVM networks. This guide will walk you through thow to deploy a Solidity contract to Flow EVM with the Foundry development toolchain. You can check out the official Foundry docs [here](https://book.getfoundry.sh/).
 
 In this guide, we'll deploy an ERC-20 token contract to Flow EVM using Foundry. We'll cover:
 
-* Developing and testing a basic ERC-20 contract
-* Deploying the contract to Flow EVM using Foundry tools
-* Querying Testnet state
-* Mutating Testnet state by sending transactions
+* How to develop and test a basic ERC-20 contract
+* Deploy the contract to Flow EVM with Foundry tools
+* How to query the Testnet state
+* How to mutate Testnet state by sending transactions
 
 ## Overview[​](#overview "Direct link to Overview")
 
@@ -62,17 +62,17 @@ To use Flow across all Foundry tools you need to:
    `_10
 
    --rpc-url https://testnet.evm.nodes.onflow.org`
-2. Use the `--legacy` flag to disable [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) style transactions. Flow will support EIP-1559 soon and this flag won't be needed.
+2. Use the `--legacy` flag to turn off [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) style transactions. Flow will support EIP-1559 soon and this flag won't be needed.
 
-As an example, we'll show you how to deploy a fungible token contract to Flow EVM using Foundry. You will see how the above flags are used in practice.
+As an example, we'll show you how to deploy a fungible token contract to Flow EVM with Foundry. You will see how the above flags are used in practice.
 
 ## Example: Deploying an ERC-20 Token Contract to Flow EVM[​](#example-deploying-an-erc-20-token-contract-to-flow-evm "Direct link to Example: Deploying an ERC-20 Token Contract to Flow EVM")
 
 ERC-20 tokens are the most common type of tokens on Ethereum. We'll use [OpenZeppelin](https://www.openzeppelin.com/) starter templates with Foundry on Flow Testnet to deploy our own token called `MyToken`.
 
 ### Installation[​](#installation "Direct link to Installation")
 
-The best way to install Foundry, is to use the `foundryup` CLI tool. You can get it using the following command:
+The best way to install Foundry, is to use the `foundryup` CLI tool. You can get it with the following command:
 
 `_10
 
@@ -90,7 +90,7 @@ You may need to reload your shell after `foundryup` installation.
 
 Check out the official [Installation](https://book.getfoundry.sh/getting-started/installation) guide for more information about different platforms or installing specific versions.
 
-### Wallet Setup[​](#wallet-setup "Direct link to Wallet Setup")
+### Wallet setup[​](#wallet-setup "Direct link to Wallet setup")
 
 We first need to generate a key pair for our EVM account. We can do this using the `cast` tool:
 
@@ -106,7 +106,7 @@ You can verify the balance of the account after funding. Replace `$YOUR_ADDRESS`
 
 cast balance --ether --rpc-url https://testnet.evm.nodes.onflow.org $YOUR_ADDRESS`
 
-### Project Setup[​](#project-setup "Direct link to Project Setup")
+### Project setup[​](#project-setup "Direct link to Project setup")
 
 First, create a new directory for your project:
 
@@ -132,9 +132,9 @@ forge test`
 
 The tests should pass.
 
-### Writing the ERC-20 Token Contract[​](#writing-the-erc-20-token-contract "Direct link to Writing the ERC-20 Token Contract")
+### Write the ERC-20 token contract[​](#write-the-erc-20-token-contract "Direct link to Write the ERC-20 token contract")
 
-We'll use the OpenZeppelin ERC-20 contract template. We can start by adding OpenZeppelin to our project:
+We'll use the OpenZeppelin ERC-20 contract template. To start, we'll add OpenZeppelin to our project:
 
 `_10
 
@@ -176,7 +176,7 @@ _10
 
 The above is a basic ERC-20 token with the name `MyToken` and symbol `MyT`. It also mints the specified amount of tokens to the contract deployer. The amount is passed as a constructor argument during deployment.
 
-Before compiling, we also need to update the test file.
+Before we comnpile, we also need to update the test file.
 
 ### Testing[​](#testing "Direct link to Testing")
 
@@ -422,7 +422,7 @@ _65
 
 }`
 
-You can now make sure everything is okay by compiling the contracts:
+To make sure everything is okay, compile the contracts:
 
 `_10
 
@@ -436,9 +436,9 @@ forge test`
 
 They should all succeed.
 
-### Deploying to Flow Testnet[​](#deploying-to-flow-testnet "Direct link to Deploying to Flow Testnet")
+### Deploy to Flow Testnet[​](#deploy-to-flow-testnet "Direct link to Deploy to Flow Testnet")
 
-We can now deploy `MyToken` using the `forge create` command. We need to provide the RPC URL, private key from a funded account using the faucet, and constructor arguments that is the initial mint amount in this case. We need to use the `--legacy` flag to disable EIP-1559 style transactions. Replace `$DEPLOYER_PRIVATE_KEY` with the private key of the account you created earlier:
+We can now deploy `MyToken` with the `forge create` command. We need to provide the RPC URL, private key from a funded account with the faucet, and constructor arguments that is the initial mint amount in this case. We need to use the `--legacy` flag to turn off EIP-1559 style transactions. Replace `$DEPLOYER_PRIVATE_KEY` with the private key of the account you created earlier:
 
 `_10
 
@@ -462,9 +462,9 @@ _10
 
 The above will print the deployed contract address. We'll use it in the next section to interact with the contract.
 
-### Verifying a Smart Contract[​](#verifying-a-smart-contract "Direct link to Verifying a Smart Contract")
+### Verify a smart contract[​](#verify-a-smart-contract "Direct link to Verify a smart contract")
 
-Once deployed, you can verify the contract so that others can see the source code and interact with it from Flow's block explorer. You can use the [`forge verify-contract`](https://book.getfoundry.sh/reference/forge/forge-verify-contract) command:
+After you deploy the contract, you can verify it so that others can see the source code and interact with it from Flow's block explorer. You can use the [`forge verify-contract`](https://book.getfoundry.sh/reference/forge/forge-verify-contract) command:
 
 `_10
 
@@ -488,9 +488,9 @@ src/MyToken.sol:MyToken`
 
 info
 
-When verifying a Mainnet contract, be sure to use the Mainnet [RPC](/build/evm/networks) and block explorer URLs.
+When you verify a Mainnet contract, be sure to use the Mainnet [RPC](/build/evm/networks) and block explorer URLs.
 
-### Querying Testnet State[​](#querying-testnet-state "Direct link to Querying Testnet State")
+### Query Testnet state[​](#query-testnet-state "Direct link to Query Testnet state")
 
 Based on the given constructor arguments, the deployer should own `42,000,000 MyT`. We can check the `MyToken` balance of the contract owner. Replace `$DEPLOYED_MYTOKEN_ADDRESS` with the address of the deployed contract and `$DEPLOYER_ADDRESS` with the address of the account you funded earlier:
 
@@ -510,7 +510,7 @@ _10
 
 $DEPLOYER_ADDRESS`
 
-This should return the amount specified during deployment. We can also call the associated function directly in the contract:
+This will return the amount specified during deployment. We can also call the associated function directly in the contract:
 
 `_10
 
@@ -544,7 +544,7 @@ _10
 
 ### Sending Transactions[​](#sending-transactions "Direct link to Sending Transactions")
 
-Let's create a second account and move some tokens using a transaction. You can use `cast wallet new` to create a new test account. You don't need to fund it to receive tokens. Replace `$NEW_ADDRESS` with the address of the new account:
+Let's create a second account and move some tokens with a transaction. You can use `cast wallet new` to create a new test account. You don't need to fund it to receive tokens. Replace `$NEW_ADDRESS` with the address of the new account:
 
 `_10
 
@@ -588,7 +588,7 @@ _10
 
 $NEW_ADDRESS`
 
-The deployer should also own less tokens now:
+The deployer will also own fewer tokens now:
 
 `_10
 
@@ -608,7 +608,7 @@ $DEPLOYER_ADDRESS`
 
 [Edit this page](https://github.com/onflow/docs/tree/main/docs/blockchain-development-tutorials/evm/development-tools/foundry.md)
 
-Last updated on **Aug 26, 2025** by **Felipe Cevallos**
+Last updated on **Nov 12, 2025** by **cshannon1218**
 
 [Previous
 
@@ -623,7 +623,7 @@ Build a Fully-Onchain Image Gallery](/blockchain-development-tutorials/evm/image
 Copy as Markdown
 
 * [Overview](#overview)* [Example: Deploying an ERC-20 Token Contract to Flow EVM](#example-deploying-an-erc-20-token-contract-to-flow-evm)
-    + [Installation](#installation)+ [Wallet Setup](#wallet-setup)+ [Project Setup](#project-setup)+ [Writing the ERC-20 Token Contract](#writing-the-erc-20-token-contract)+ [Testing](#testing)+ [Deploying to Flow Testnet](#deploying-to-flow-testnet)+ [Verifying a Smart Contract](#verifying-a-smart-contract)+ [Querying Testnet State](#querying-testnet-state)+ [Sending Transactions](#sending-transactions)
+    + [Installation](#installation)+ [Wallet setup](#wallet-setup)+ [Project setup](#project-setup)+ [Write the ERC-20 token contract](#write-the-erc-20-token-contract)+ [Testing](#testing)+ [Deploy to Flow Testnet](#deploy-to-flow-testnet)+ [Verify a smart contract](#verify-a-smart-contract)+ [Query Testnet state](#query-testnet-state)+ [Sending Transactions](#sending-transactions)
 
 Flow
 

scraped_docs/developers_flow_com/blockchain_development_tutorials_cadence_getting_started_production_deployment.md

@@ -44,15 +44,15 @@ On this page
 
 # Flow Hardhat Guide
 
-Hardhat is an Ethereum development tool designed to facilitate the deployment, testing, and debugging of smart contracts. It provides a streamlined experience for developers working with Solidity contracts.
+Hardhat is an Ethereum development tool designed to facilitate the deployment, testing, and debugging of Solidity smart contracts. It provides a streamlined experience for developers who work with with Solidity contracts.
 
 ## Prerequisites[​](#prerequisites "Direct link to Prerequisites")
 
 ### Node[​](#node "Direct link to Node")
 
 Node v18 or higher, available for [download here](https://nodejs.org/en/download).
 
-For those new to Hardhat, we recommend exploring the [official documentation](https://hardhat.org/tutorial/creating-a-new-hardhat-project) to get acquainted. The following instructions utilize `npm` to initialize a project and install dependencies:
+For those new to Hardhat, we recommend that you exploare the [official documentation](https://hardhat.org/tutorial/creating-a-new-hardhat-project) to get acquainted. The following instructions use `npm` to initialize a project and install dependencies:
 
 ### Wallet[​](#wallet "Direct link to Wallet")
 
@@ -86,13 +86,13 @@ npx hardhat init`
 
 > When prompted, select TypeScript and to use `@nomicfoundation/hardhat-toolbox` to follow along with this guide.
 
-### Fund Your Wallet[​](#fund-your-wallet "Direct link to Fund Your Wallet")
+### Fund Your wallet[​](#fund-your-wallet "Direct link to Fund Your wallet")
 
-To deploy smart contracts, ensure your wallet has **$FLOW**. Obtain funds by navigating to the Flow [Faucet](https://faucet.flow.com/fund-account) and entering your wallet address.
+To deploy smart contracts, ensure your wallet has **$FLOW**. To obtain funds, navigate to the Flow [Faucet](https://faucet.flow.com/fund-account) and enter your wallet address.
 
-## Deploying a Smart Contract with Hardhat[​](#deploying-a-smart-contract-with-hardhat "Direct link to Deploying a Smart Contract with Hardhat")
+## Deploy a smart contract with Hardhat[​](#deploy-a-smart-contract-with-hardhat "Direct link to Deploy a smart contract with Hardhat")
 
-This section guides you through the process of deploying smart contracts on the Flow network using Hardhat.
+This section guides you through the process of how to deploy smart contracts on the Flow network with Hardhat.
 
 ### Configuration[​](#configuration "Direct link to Configuration")
 
@@ -154,11 +154,11 @@ _15
 
 export default config; ``
 
-To keep this example straightforward, we've included the account's private key directly in `hardhat.config.ts`. However, it is crucial to avoid committing private keys to your Git repository for security reasons. Instead, opt for using environment variables for safer handling of sensitive information.
+To keep this example straightforward, we've included the account's private key directly in `hardhat.config.ts`. However, it is crucial to not commit private keys to your Git repository for security reasons. Instead, use environment variables to safely handle sensitive information.
 
-### Deploying HelloWorld Smart Contract[​](#deploying-helloworld-smart-contract "Direct link to Deploying HelloWorld Smart Contract")
+### Deploy HelloWorld smart contract[​](#deploy-helloworld-smart-contract "Direct link to Deploy HelloWorld smart contract")
 
-## HelloWorld Smart Contract[​](#helloworld-smart-contract "Direct link to HelloWorld Smart Contract")
+## HelloWorld smart contract[​](#helloworld-smart-contract "Direct link to HelloWorld smart contract")
 
 `_25
 
@@ -252,7 +252,7 @@ _25
 
 }`
 
-Deploying:
+Deploy:
 
 1. Create a file named `HelloWorld.sol` under `contracts` directory.
 2. Add above `HelloWorld.sol` contract code to new file.
@@ -340,7 +340,7 @@ HelloWorld address: 0x3Fe94f43Fb5CdB8268A801f274521a07F7b99dfb`
 
 You can now search for your deployed contract on the [Flowscan block explorer](https://evm-testnet.flowscan.io/)!
 
-### Get HelloWorld Contract Greeting[​](#get-helloworld-contract-greeting "Direct link to Get HelloWorld Contract Greeting")
+### Get HelloWorld contract greeting[​](#get-helloworld-contract-greeting "Direct link to Get HelloWorld contract greeting")
 
 Now, we want to get the greeting from the deployed `HelloWorld` smart contract.
 
@@ -435,9 +435,9 @@ _23
 Steps:
 
 1. Create a `getGreeting.ts` file in the `scripts` directory.
-2. Paste contents of script above. Make sure to update the contract address with the one from deployment in earlier step.
+2. Paste contents of script above. Make sure to update the contract address with the one from deployment in an earlier step.
 3. Call script to get the greeting, `npx hardhat run scripts/getGreeting.ts --network testnet`
-4. The output should be as follows:
+4. The output will be as follows:
 
 `_10
 
@@ -447,7 +447,7 @@ _10
 
 The greeting is: Hello, World!`
 
-### Update Greeting on HelloWorld Smart Contract[​](#update-greeting-on-helloworld-smart-contract "Direct link to Update Greeting on HelloWorld Smart Contract")
+### Update greeting on HelloWorld smart contract[​](#update-greeting-on-helloworld-smart-contract "Direct link to Update greeting on HelloWorld smart contract")
 
 Next, we'll add a script to update the greeting and log it.
 
@@ -592,7 +592,7 @@ Here are the steps to follow:
 1. Create an `updateGreeting.ts` script in the `scripts` directory.
 2. Paste in the TypeScript above, make sure to update the contract address with the one from deployment in earlier step.
 3. Call the new script, `NEW_GREETING='Howdy!' npx hardhat run ./scripts/updateGreeting.ts --network testnet`
-4. The output should be
+4. The output will be:
 
 `_10
 
@@ -614,9 +614,9 @@ _10
 
 The greeting is: Howdy!`
 
-### Verifying Contract[​](#verifying-contract "Direct link to Verifying Contract")
+### Verify contract[​](#verify-contract "Direct link to Verify contract")
 
-To verify your contract on [Flowscan](https://evm-testnet.flowscan.io/), you can update your Hardhat config file as such including the correct chainID, apiURL and browserURL:
+To verify your contract on [Flowscan](https://evm-testnet.flowscan.io/), you can update your Hardhat config file. To do this, include the correct chainID, apiURL and browserURL:
 
 `_37
 
@@ -768,7 +768,7 @@ npx hardhat verify --network testnet DEPLOYED_CONTRACT_ADDRESS "Constructor argu
 
 [Edit this page](https://github.com/onflow/docs/tree/main/docs/blockchain-development-tutorials/evm/development-tools/hardhat.md)
 
-Last updated on **Aug 26, 2025** by **Felipe Cevallos**
+Last updated on **Nov 12, 2025** by **cshannon1218**
 
 [Previous
 
@@ -783,9 +783,9 @@ Remix](/blockchain-development-tutorials/evm/development-tools/remix)
 Copy as Markdown
 
 * [Prerequisites](#prerequisites)
-  + [Node](#node)+ [Wallet](#wallet)+ [Fund Your Wallet](#fund-your-wallet)* [Deploying a Smart Contract with Hardhat](#deploying-a-smart-contract-with-hardhat)
-    + [Configuration](#configuration)+ [Deploying HelloWorld Smart Contract](#deploying-helloworld-smart-contract)* [HelloWorld Smart Contract](#helloworld-smart-contract)
-      + [Get HelloWorld Contract Greeting](#get-helloworld-contract-greeting)+ [Update Greeting on HelloWorld Smart Contract](#update-greeting-on-helloworld-smart-contract)+ [Verifying Contract](#verifying-contract)
+  + [Node](#node)+ [Wallet](#wallet)+ [Fund Your wallet](#fund-your-wallet)* [Deploy a smart contract with Hardhat](#deploy-a-smart-contract-with-hardhat)
+    + [Configuration](#configuration)+ [Deploy HelloWorld smart contract](#deploy-helloworld-smart-contract)* [HelloWorld smart contract](#helloworld-smart-contract)
+      + [Get HelloWorld contract greeting](#get-helloworld-contract-greeting)+ [Update greeting on HelloWorld smart contract](#update-greeting-on-helloworld-smart-contract)+ [Verify contract](#verify-contract)
 
 Flow