Cadence getting started edits.

Author: cshannon1218

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

@@ -40,7 +40,7 @@ After you complete this tutorial, you will be able to:
 - [Flow CLI] installed.
 - Node.js and npm installed.
 
-## Setting Up the Next.js App
+## Set Up the Next.js app
 
 Follow these steps to set up your Next.js project and integrate [**@onflow/react-sdk**].
 
@@ -50,7 +50,7 @@ You can visit this [React-sdk Demo] to see how the hooks and components are used
 
 :::
 
-### Step 1: Create a New Next.js App
+### Step 1: Create a new Next.js app
 
 Run the following command in your project directory:
 
@@ -66,7 +66,7 @@ During setup, choose the following options:
 
 This command creates a new Next.js project named `kit-app-quickstart` inside your current directory. We're generating the frontend in a subdirectory so we can next move it into our existing project structure from the previous steps (you can't create an app in a non-empty directory).
 
-### Step 2: Move the Next.js App Up a Directory
+### Step 2: Move the Next.js app Up a directory
 
 Move the contents of the `kit-app-quickstart` directory into your project root. You can use the gui in your editor, or the console.
 
@@ -108,7 +108,7 @@ npm install @onflow/react-sdk
 
 This library wraps FCL internally and exposes a set of hooks for authentication, querying, sending transactions, and tracking transaction status.
 
-## Configuring the Local Flow Emulator and Dev Wallet
+## Configure the local Flow Emulator and Dev Wallet
 
 :::warning
 
@@ -136,7 +136,7 @@ flow dev-wallet
 
 This will start the [Dev Wallet] on `http://localhost:8701`, which you'll use for authentication during development.
 
-## Wrapping Your App with FlowProvider
+## Wrap 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:
 
@@ -174,11 +174,11 @@ This configuration initializes the kit with your local emulator settings and map
 
 For more information on Discovery configurations, refer to the [Wallet Discovery Guide].
 
-## Interacting With the Chain
+## Interact With the chain
 
 Now that we've set our provider, lets start interacting with the chain.
 
-### Querying the Chain
+### Query the chain
 
 First, use the kit's [`useFlowQuery`] hook to read the current counter value from the blockchain.
 
@@ -212,7 +212,7 @@ This script fetches the counter value, formats it via the `NumberFormatter`, and
 
 :::
 
-### Sending a Transaction
+### Send a transaction
 
 Next, use the kit's [`useFlowMutate`] hook to send a transaction that increments the counter.
 
@@ -250,7 +250,7 @@ const handleIncrement = () => {
 
 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
+### Subscribe to transaction status
 
 Use the kit's [`useFlowTransactionStatus`] hook to monitor and display the transaction status in real time.
 
@@ -282,7 +282,7 @@ useEffect(() => {
 - 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:
+#### Why we recommend `Executed` for UI Updates:
 
 Waiting for `Sealed` provides full onchain confirmation but can introduce a delay — especially in local or test environments. Since most transactions (like incrementing a counter) don't require strong finality guarantees, you can typically refetch data once the transaction reaches `Executed` for a faster, more responsive user experience.
 
@@ -291,7 +291,7 @@ However:
 - 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
+### Integrate authentication and build the complete UI
 
 Finally, integrate the query, mutation, and transaction status hooks with authentication using `useFlowCurrentUser`. Combine all parts to build the complete page.
 
@@ -417,7 +417,7 @@ In this tutorial, we inlined Cadence code for simplicity. For real projects, we
 
 :::
 
-## Running the App
+## Run the app
 
 Start your development server:
 

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

@@ -17,13 +17,13 @@ keywords:
   - VSCode extension
 ---
 
-# Cadence Environment Setup
+# Cadence environment eetup
 
 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 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
+## What you'll learn
 
 After you complete this tutorial, you'll be able to:
 
@@ -34,7 +34,7 @@ After you complete this tutorial, you'll be able to:
 - **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
+## 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:
 
@@ -74,7 +74,7 @@ flow version
 
 You will see output showing your Flow CLI version.
 
-### Install VSCode Extension
+### Install VSCode extension
 
 Install the [Flow Cadence VSCode Extension] from the marketplace. This extension provides:
 
@@ -83,7 +83,7 @@ Install the [Flow Cadence VSCode Extension] from the marketplace. This extension
 - Error checking and diagnostics.
 - Integrated development tools.
 
-## Create Your First Project
+## Create your first project
 
 Navigate to your desired development directory and create a new Flow project:
 
@@ -118,7 +118,7 @@ For additional details on how `flow.json` is configured, review the [configurati
 
 :::
 
-### Start the Flow Emulator
+### Start the Flow emulator
 
 The emulator is a local version of the Flow blockchain that you can use to test your contracts and scripts. It's a great way to develop and test your contracts locally - before you try them on the `testnet` or `mainnet`.
 
@@ -135,11 +135,11 @@ Keep this terminal running. The emulator provides:
 - No real-world costs.
 - Complete Flow feature set.
 
-## Your First Contract
+## Your first contract
 
 Now let's examine, deploy, and interact with the Counter contract that was created in your project.
 
-### Examine the Counter Contract
+### Examine the Counter contract
 
 Open `cadence/contracts/Counter.cdc` in your editor. Let's break down this contract:
 
@@ -177,7 +177,7 @@ access(all) contract Counter {
 }
 ```
 
-**Key Components:**
+**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.
@@ -188,7 +188,7 @@ access(all) contract Counter {
   - `decrement()`: Decreases count by 1 and emits an event
   - `getCount()`: Returns the current count (read-only, marked with `view`)
 
-### Create and Configure Deployment Account
+### Create and configure deployment account
 
 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.
 
@@ -242,7 +242,7 @@ This shows which networks your configured accounts are accessible on:
 
 This is a great tool to visualize your different accounts and balances when you are developing.
 
-### Configure Contract Deployment
+### Configure contract deployment
 
 To deploy the `Counter` contract to the emulator, you'll need to add it to your project configuration. To do this, run:
 
@@ -259,7 +259,7 @@ Follow the prompts:
 
 This configures your `flow.json` to deploy the Counter contract to your test account on the emulator.
 
-### Deploy the Contract
+### Deploy the contract
 
 To deploy the `Counter` contract to the emulator, run:
 
@@ -279,7 +279,7 @@ Counter -> 0x179b6b1cb6755e31 (a98c155fe7afc8eb2af5551748759b08a80a0ae85d1b09f92
 
 That's it! You've just deployed your first contract to the Flow Emulator.
 
-### Verify Deployment with a Script
+### Verify deployment with a script
 
 Scripts are used to read data from the Flow blockchain. There is no state modification. Let's verify the deployment by reading the counter value. Run the included script:
 
@@ -315,9 +315,9 @@ To learn more about writing scripts, check out the docs for [basic scripts].
 
 :::
 
-### Executing Transactions
+### Execute transactions
 
-Now let's increment the counter using a transaction:
+Now let's increment the counter with a transaction:
 
 ```zsh
 flow transactions send cadence/transactions/IncrementCounter.cdc
@@ -391,24 +391,24 @@ To learn more about writing transactions, read the docs for [basic transactions]
 
 You've successfully established a solid foundation for building on Flow. Let's recap what you've accomplished and learned. Through this hands-on tutorial, you've successfully built a complete Flow development foundation:
 
-✅ **Complete Flow Development Environment**
+✅ **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`.
 
-✅ **Smart Contract Deployment Skills**
+✅ **Smart contract deployment skills**
 
 - Counter contract successfully deployed to your local emulator.
 - Account creation and contract deployment configuration mastered.
 
-✅ **Blockchain Interactions**
+✅ **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.
 
-### Resources for Continued Learning
+### Resources for continued learning
 
 As you continue your Flow development journey:
 

docs/blockchain-development-tutorials/cadence/getting-started/index.md

@@ -17,7 +17,7 @@ keywords:
   - Production deployment
 ---
 
-# Getting Started with Cadence
+# Getting started with Cadence
 
 The Cadence is designed for the next generation of apps, games, and digital assets. This comprehensive tutorial series will guide you from setting up your development environment to deploying production-ready applications on Flow's mainnet while a complete Counter application that demonstrates all essential Flow development patterns.
 
@@ -33,7 +33,7 @@ The Cadence is designed for the next generation of apps, games, and digital asse
   ></iframe>
 </div>
 
-## What You'll Learn
+## What you'll learn
 
 In this tutorial series, you'll discover how to:
 
@@ -45,7 +45,7 @@ In this tutorial series, you'll discover how to:
 - Deploy applications to testnet and mainnet with production best practices.
 - Implement monitoring, security, and maintenance for live blockchain applications.
 
-## What You'll Build
+## What you'll build
 
 Throughout these tutorials, you'll build a complete **Counter Application** that demonstrates the core aspects of Flow development:
 
@@ -56,31 +56,31 @@ Throughout these tutorials, you'll build a complete **Counter Application** that
 
 By the end, you'll have a fully functional blockchain application and the skills to build your own Flow projects.
 
-## Environment Setup
+## Environment setup
 
 Learn how to set up your Flow development environment and deploy your first smart contract. This foundational tutorial covers CLI installation, project creation, contract deployment, and basic blockchain interaction patterns using the local Flow emulator.
 
 Tutorial: [Cadence Environment Setup]
 
-## Smart Contract Interaction
+## Smart contract interaction
 
 Gain advanced Flow development skills including dependency management, sophisticated transaction patterns, and comprehensive testing strategies. Learn to integrate external contracts, handle complex state changes, and implement test-driven development workflows.
 
 Tutorial: [Smart Contract Interaction]
 
-## Building a Frontend App
+## Building a frontend app
 
 Create a `Next.js` frontend application that interacts with your Flow smart contracts using `@onflow/react-sdk`. Implement wallet authentication, real-time data queries, transaction submission, and status monitoring for a complete user experience.
 
 Tutorial: [Building a Frontend App]
 
-## Production Deployment
+## Production deployment
 
 To take your application live, deploy to Flow's testnet and mainnet networks. Learn security best practices, production configuration, monitoring strategies, and maintenance practices you can use to manage live blockchain applications.
 
 Tutorial: [Production Deployment]
 
-## Next Steps
+## Next steps
 
 After you complete these tutorials, you'll have the fundamental skills needed for Flow development. Consider exploring our other tutorial series to expand your blockchain development expertise: