First cadence getting started doc edits.

Author: cshannon1218

docs/blockchain-development-tutorials/cadence/getting-started/building-a-frontend-app.md

@@ -22,13 +22,13 @@ keywords:
 
 # Building a Frontend App
 
-Building on the `Counter` contract you deployed in [Cadence Environment Setup] and [Smart Contract Interaction], this tutorial 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**] to simplify authentication, querying, transactions, and to display real-time transaction status updates using convenient React hooks.
+This tutorial builds on the `Counter` contract you deployed in [Cadence Environment Setup] and [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**] to simplify authentication, querying, transactions, and to display real-time transaction status updates using convenient React hooks.
 
 ## Objectives
 
-After finishing this guide, you will be able to:
+After you complete this tutorial, you will be able to:
 
-- Wrap your Next.js app with a Flow provider using [**@onflow/react-sdk**].
+- Wrap your `Next.js` app with a Flow provider using [**@onflow/react-sdk**].
 - Read data from a Cadence smart contract (`Counter`) using kit's query hook.
 - Send a transaction to update the smart contract's state using kit's mutation hook.
 - Monitor a transaction's status in real time using kit's transaction hook.
@@ -92,7 +92,11 @@ Move-Item -Path .\kit-app-quickstart\.* -Destination . -Force
 Remove-Item -Recurse -Force .\kit-app-quickstart
 ```
 
-**Note:** When moving hidden files (those beginning with a dot) like `.gitignore`, be cautious not to overwrite any important files.
+:::tip
+
+When moving hidden files (those beginning with a dot) like `.gitignore`, be cautious not to overwrite any important files.
+
+:::
 
 ### Step 3: Install @onflow/react-sdk
 
@@ -108,7 +112,7 @@ This library wraps FCL internally and exposes a set of hooks for authentication,
 
 :::warning
 
-You should already have the Flow emulator running from the local development step. If it's not running, you can start it again — but note that restarting the emulator will clear all blockchain state, including any contracts deployed in [Step 2: Local Development].
+You should already have the Flow emulator running from the local development step. If it's not running, you can start it again — but when you restart the emulator, it will clear all blockchain state, which includes any contracts deployed in [Step 2: Local Development].
 
 :::
 
@@ -134,7 +138,7 @@ This will start the [Dev Wallet] on `http://localhost:8701`, which you'll use fo
 
 ## Wrapping Your App with FlowProvider
 
-[**@onflow/react-sdk**] provides a `FlowProvider` component that sets up the Flow Client Library configuration. In Next.js using the App Router, add or update your `src/app/layout.tsx` as follows:
+[**@onflow/react-sdk**] provides a `FlowProvider` component that sets up the Flow Client Library configuration. In `Next.js` using the App Router, add or update your `src/app/layout.tsx` as follows:
 
 ```tsx
 'use client';
@@ -244,7 +248,7 @@ const handleIncrement = () => {
 
 #### Explanation
 
-This sends a Cadence transaction to the blockchain using the `mutate` function. The transaction imports the `Counter` contract and calls its `increment` function. Authorization is handled automatically by the connected wallet during the `prepare` phase. Once submitted, the returned `txId` can be used to track the transaction's status in real time.
+This sends a Cadence transaction to the blockchain using the `mutate` function. The transaction imports the `Counter` contract and calls its `increment` function. The connected wallet handles authorization automatically during the `prepare` phase. After it's submitted, you cna use the returned `txId` to track the transaction's status in real time.
 
 ### Subscribing to Transaction Status
 
@@ -275,7 +279,7 @@ useEffect(() => {
   - `2`: **Finalized** – The transaction has been included in a block, but not yet executed.
   - `3`: **Executed** – The transaction code has run successfully, but the result has not yet been sealed.
   - `4`: **Sealed** – The transaction is fully complete, included in a block, and now immutable onchain.
-- We recommend calling `refetch()` when the status reaches **3 (Executed)** to update your UI more quickly after the transaction runs, rather than waiting for sealing.
+- We recommend that you call `refetch()` when the status reaches **3 (Executed)** to update your UI more quickly after the transaction runs, rather than waiting for sealing.
 - The `statusString` property gives a human-readable version of the current status you can display in the UI.
 
 #### Why `Executed` is Recommended for UI Updates:
@@ -284,7 +288,7 @@ Waiting for `Sealed` provides full onchain confirmation but can introduce a dela
 
 However:
 
-- If you're dealing with critical state changes (e.g., token transfers or contract deployments), prefer waiting for `Sealed`.
+- If you're dealing with critical state changes (for example, token transfers or contract deployments), prefer waiting for `Sealed`.
 - For non-critical UI updates, `Executed` is usually safe and significantly improves perceived performance.
 
 ### Integrating Authentication and Building the Complete UI
@@ -442,9 +446,9 @@ Then visit [http://localhost:3000](http://localhost:3000) in your browser. You s
 - Once logged in, your account address appears with options to **Log Out** and **Increment Count**.
 - When you click **Increment Count**, the transaction is sent; its status updates are displayed in real time below the action buttons, and once the transaction is sealed, the updated count is automatically fetched.
 
-## Wrapping Up
+## Conclusion
 
-By following these steps, you've built a simple Next.js dApp that interacts with a Flow smart contract using [**@onflow/react-sdk**]. In this guide you learned how to:
+By following these steps, you've built a simple `Next.js` dApp that interacts with a Flow smart contract using [**@onflow/react-sdk**]. In this guide you learned how to:
 
 - Wrap your application in a `FlowProvider` to configure blockchain connectivity.
 - Use kit hooks such as `useFlowQuery`, `useFlowMutate`, `useFlowTransactionStatus`, and `useFlowCurrentUser` to manage authentication, query onchain data, submit transactions, and monitor their status.

docs/blockchain-development-tutorials/cadence/getting-started/cadence-environment-setup.md

@@ -19,69 +19,69 @@ keywords:
 
 # Cadence Environment Setup
 
-This comprehensive tutorial will guide you through setting up your complete development environment, deploying your first smart contract, and mastering the fundamentals of Flow development. You'll work hands-on with the Flow CLI, local emulator, and a real smart contract to build practical skills from day one.
+This comprehensive tutorial will guide you through how to set up your complete development environment, deploy your first smart contract, and learn the fundamentals of Flow development. You'll work hands-on with the Flow CLI, local emulator, and a real smart contract to build practical skills from day one.
 
-Flow is a blockchain built for the next generation of apps, games, and digital assets. With its unique multi-role architecture and resource-oriented programming language Cadence, Flow enables developers to create secure, composable, and scalable applications. This tutorial focuses on getting you productive with Flow's developer tools as quickly as possible.
+Flow is a blockchain built for the next generation of apps, games, and digital assets. With its unique multi-role architecture and resource-oriented programming language Cadence, Flow allows developers to create secure, composable, and scalable applications. This tutorial focuses on getting you productive with Flow's developer tools as quickly as possible.
 
 ## What You'll Learn
 
-After completing this tutorial, you'll be able to:
+After you complete this tutorial, you'll be able to:
 
-- **Set up a complete Flow development environment** with CLI tools and VSCode integration
-- **Create and manage Flow projects** using the Flow CLI and understand project structure
-- **Deploy and interact with smart contracts** on the local Flow emulator
-- **Execute scripts and transactions** to read from and modify blockchain state
-- **Understand Flow's account model** and how contracts are deployed to account storage
-- **Navigate the Flow ecosystem** and know where to find help and resources
+- **Set up a complete Flow development environment** with CLI tools and VSCode integration.
+- **Create and manage Flow projects** using the Flow CLI and understand project structure.
+- **Deploy and interact with smart contracts** on the local Flow emulator.
+- **Execute scripts and transactions** to read from and modify blockchain state.
+- **Understand Flow's account model** and how contracts are deployed to account storage.
+- **Navigate the Flow ecosystem** and know where to find help and resources.
 
 ## What You'll Build
 
-You'll work with a `Counter` contract—a simple but comprehensive example that demonstrates core Flow development patterns. This contract maintains a count value and provides functions to increment, decrement, and read the current count. By the end of this tutorial, you'll have:
+You'll work with a `Counter` contract, a simple but comprehensive example that demonstrates core Flow development patterns. This contract maintains a count value and provides functions to increment, decrement, and read the current count. By the end of this tutorial, you'll have:
 
-- A fully functional local Flow development environment
-- A deployed Counter contract running on your local emulator
-- Scripts to query the contract's state
-- Transactions to modify the contract's state
-- Understanding of how to extend this foundation for more complex applications
+- A fully functional local Flow development environment.
+- A deployed Counter contract running on your local emulator.
+- Scripts to query the contract's state.
+- Transactions to modify the contract's state.
+- Understanding of how to extend this foundation for more complex applications.
 
 **Time Commitment:** Approximately 30-45 minutes
 
 **Prerequisites:**
 
 - Basic command line familiarity
 - Code editor (VSCode recommended)
-- Node.js installed (for future frontend development)
+- `Node.js` installed (for future frontend development)
 
 ---
 
 ### Install Flow CLI
 
 The [Flow Command Line Interface] (CLI) is a set of tools that developers can use to interact with the Flow blockchain by managing accounts, sending transactions, deploying smart contracts, running the emulator, and more. This quickstart will get you familiar with its main concepts and functionality.
 
-The first thing you'll need to do is install the Flow CLI. If you have [homebrew] installed you can run:
+The first thing you'll need to do is install the Flow CLI. If you have [homebrew] installed, run:
 
 ```zsh
 brew install flow-cli
 ```
 
-**For other operating systems,** please refer to the [installation guide] for detailed instructions.
+**For other operating systems,** refer to the [installation guide] for detailed instructions.
 
 **Verify Installation:**
 
 ```zsh
 flow version
 ```
 
-You should see output showing your Flow CLI version.
+You will see output showing your Flow CLI version.
 
 ### Install VSCode Extension
 
 Install the [Flow Cadence VSCode Extension] from the marketplace. This extension provides:
 
-- Syntax highlighting for Cadence
-- Code completion and IntelliSense
-- Error checking and diagnostics
-- Integrated development tools
+- Syntax highlighting for Cadence.
+- Code completion and IntelliSense.
+- Error checking and diagnostics.
+- Integrated development tools.
 
 ## Create Your First Project
 
@@ -93,13 +93,13 @@ flow init
 
 When prompted:
 
-1. **Project name:** Enter your preferred project name
+1. **Project name:** Enter your preferred project name.
 2. Select `Basic Cadence project (no dependencies)`.
 
 The `flow init` command creates:
 
-- **`flow.json`**: Central configuration file containing accounts, contracts, deployments, and network settings
-- **`emulator-account.pkey`**: Private key for the default emulator account
+- **`flow.json`**: Central configuration file containing accounts, contracts, deployments, and network settings.
+- **`emulator-account.pkey`**: Private key for the default emulator account.
 - **`cadence/`**: Directory structure for your Cadence code:
   - `contracts/`: Smart contract files
   - `scripts/`: Read-only blockchain queries
@@ -130,10 +130,10 @@ flow emulator start
 
 Keep this terminal running. The emulator provides:
 
-- Local blockchain environment
-- Fast transaction processing
-- No real-world costs
-- Complete Flow feature set
+- Local blockchain environment.
+- Fast transaction processing.
+- No real-world costs.
+- Complete Flow feature set.
 
 ## Your First Contract
 
@@ -179,18 +179,18 @@ access(all) contract Counter {
 
 **Key Components:**
 
-- **Contract Declaration**: `access(all) contract Counter` creates a public contract named Counter
-- **State Variable**: `access(all) var count: Int` stores the counter value, accessible to everyone
-- **Events**: `CounterIncremented` and `CounterDecremented` notify listeners when changes occur
-- **Initializer**: `init()` sets the initial count to 0 when the contract is deployed
+- **Contract Declaration**: `access(all) contract Counter` creates a public contract named Counter.
+- **State Variable**: `access(all) var count: Int` stores the counter value, accessible to everyone.
+- **Events**: `CounterIncremented` and `CounterDecremented` notify listeners when changes occur.
+- **Initializer**: `init()` sets the initial count to 0 when the contract is deployed.
 - **Public Functions**:
   - `increment()`: Increases count by 1 and emits an event
   - `decrement()`: Decreases count by 1 and emits an event
   - `getCount()`: Returns the current count (read-only, marked with `view`)
 
 ### Create and Configure Deployment Account
 
-When you created a project you'll see that a `Counter` contract was added to your [`flow.json` configuration file](../../../build/tools/flow-cli/flow.json/configuration.md), but it's not set up for deployment yet. We could deploy it to the automatically created `emulator-account`, but for this example lets also create a new account on the emulator to deploy it to.
+When you create a project, you'll see that a `Counter` contract was added to your [`flow.json` configuration file](../../../build/tools/flow-cli/flow.json/configuration.md), but it's not set up for deployment yet. We could deploy it to the automatically created `emulator-account`, but for this example, lets also create a new account on the emulator to deploy it to.
 
 :::info
 
@@ -211,7 +211,7 @@ When prompted:
 
 This adds the new account to your `flow.json` configuration file.You'll now see this account in your [`flow.json`](../../../build/tools/flow-cli/flow.json/configuration.md).
 
-Once you have created you accounts, then you can view all your accounts on the with the Flow CLI with:
+After you've created you accounts, then you can view all your accounts on the with the Flow CLI with:
 
 ```zsh
 📋 Account Status Across Networks
@@ -244,7 +244,7 @@ This is a great tool to visualize your different accounts and balances when you
 
 ### Configure Contract Deployment
 
-To deploy the `Counter` contract to the emulator, you'll need to add it to your project configuration. You can do this by running:
+To deploy the `Counter` contract to the emulator, you'll need to add it to your project configuration. To do this, run:
 
 ```zsh
 flow config add deployment
@@ -267,7 +267,7 @@ To deploy the `Counter` contract to the emulator, run:
 flow project deploy
 ```
 
-You should see output similar to:
+You'll see output similar to:
 
 ```zsh
 Deploying 1 contracts for accounts: test-account
@@ -293,7 +293,7 @@ You should see:
 Result: 0
 ```
 
-This confirms your contract is deployed and functioning correctly. The counter starts at 0, as defined in the contract's `init()` function.
+This confirms your contract is deployed and functional. The counter starts at zero (0), as defined in the contract's `init()` function.
 
 If we wanted to generate a new script, we could run:
 
@@ -311,7 +311,7 @@ For more information about generating Cadence files, see the [Generating Cadence
 
 :::tip
 
-If you'll like to learn more about writing scripts, please check out the docs for [basic scripts].
+To learn more about writing scripts, check out the docs for [basic scripts].
 
 :::
 
@@ -331,9 +331,9 @@ flow transactions send cadence/transactions/IncrementCounter.cdc --signer test-a
 
 The transaction output shows detailed information including:
 
-- Transaction ID and block information
-- Status confirmation (`✅ SEALED`)
-- Events emitted (including `CounterIncremented`)
+- Transaction ID and block information.
+- Status confirmation (`✅ SEALED`).
+- Events emitted (including `CounterIncremented`).
 
 ```zsh
 Transaction ID: 9cc7ac4d3d5239016965aba89b9692d3401a48a090d1ad1a8d9ef9cfca685e6e
@@ -383,7 +383,7 @@ Result: 1
 
 :::tip
 
-If you want to learn more about writing transactions, please read the docs for [basic transactions].
+To learn more about writing transactions, read the docs for [basic transactions].
 
 :::
 
@@ -393,28 +393,28 @@ You've successfully established a solid foundation for building on Flow. Let's r
 
 ✅ **Complete Flow Development Environment**
 
-- Flow CLI installed and configured for project management
-- Local Flow emulator running and ready for development
-- Project creation and management workflow with `flow init`
+- Flow CLI installed and configured for project management.
+- Local Flow emulator running and ready for development.
+- Project creation and management workflow with `flow init`.
 
 ✅ **Smart Contract Deployment Skills**
 
-- Counter contract successfully deployed to your local emulator
-- Account creation and contract deployment configuration mastered
+- Counter contract successfully deployed to your local emulator.
+- Account creation and contract deployment configuration mastered.
 
 ✅ **Blockchain Interactions**
 
-- Scripts to query contract state (reading blockchain data)
-- Transactions to modify contract state (writing to blockchain)
-- Real-time interaction with blockchain data through CLI commands
+- Scripts to query contract state (reading blockchain data).
+- Transactions to modify contract state (writing to blockchain).
+- Real-time interaction with blockchain data through CLI commands.
 
 ### Resources for Continued Learning
 
 As you continue your Flow development journey:
 
-- **[Flow Discord Community]**: Connect with other developers, get help, and share your projects
-- **[Cadence Language Reference]**: Deep dive into Flow's programming language features and best practices
-- **[Flow GitHub]**: Explore open source tools, examples, and contribute to the ecosystem
+- **[Flow Discord Community]**: Connect with other developers, get help, and share your projects.
+- **[Cadence Language Reference]**: Deep dive into Flow's programming language features and best practices.
+- **[Flow GitHub]**: Explore open source tools, examples, and contribute to the ecosystem.
 
 The foundation you've built today will serve you well as you explore Flow's capabilities and build applications that take advantage of blockchain's unique properties: permanence, transparency, and decentralization.