storytelling clean up cookbook --> smart-contracts

Author: dawnkelly09

smart-contracts/cookbook/.nav.yml

@@ -1,5 +1,5 @@
 nav:
-- 'Overview': index.md # TODO: Update name of page
+- 'Overview': index.md 
 - 'Get Tokens from the Faucet': /smart-contracts/faucet/ 
 - 'EVM Smart Contracts': smart-contracts
 - 'Create a DApp': dapps

smart-contracts/cookbook/dapps/zero-to-hero.md

@@ -352,7 +352,7 @@ This file defines the contract address, ABI, and functions to create a viem [con
 
 ## Create the Wallet Connection Component
 
-Now, let's create a component to handle wallet connections. Create a new file called `components/WalletConnect.tsx`:
+Now, you can create a component to handle wallet connections. Create a new file called `components/WalletConnect.tsx`:
 
 ```typescript title="WalletConnect.tsx"
 "use client";
@@ -535,7 +535,7 @@ This component handles connecting to the wallet, switching networks if necessary
 
 ## Create the Read Contract Component
 
-Now, let's create a component to read data from the contract. Create a file called `components/ReadContract.tsx`:
+Next, create a component to read data from the contract. Create a file called `components/ReadContract.tsx`:
 
 ```typescript title="ReadContract.tsx"
 'use client';
@@ -608,7 +608,7 @@ This component reads the `storedNumber` value from the contract and displays it
 
 ## Create the Write Contract Component
 
-Finally, let's create a component that allows users to update the stored number. Create a file called `components/WriteContract.tsx`:
+Finally, create a component that allows users to update the stored number. Create a file called `components/WriteContract.tsx`:
 
 ```typescript title="WriteContract.tsx"
 "use client";

smart-contracts/cookbook/eth-dapps/uniswap-v2.md

@@ -28,7 +28,7 @@ Before starting, make sure you have:
 
 ## Set Up the Project
 
-Let's start by cloning the Uniswap V2 project:
+Start by cloning the Uniswap V2 project:
 
 1. Clone the Uniswap V2 repository:
 

smart-contracts/cookbook/index.md

@@ -1,5 +1,5 @@
 ---
-title: Smart Contracts Cookbook Index
+title: Smart Contracts Cookbook
 description: Explore our full collection of tutorials and guides to learn step-by-step how to build, deploy, and work with smart contracts on Polkadot.
 categories: Basics, dApps, Smart Contracts
 ---

smart-contracts/cookbook/smart-contracts/deploy-basic/hardhat.md

@@ -1,25 +1,27 @@
 ---
-title: Deploy a Basic Contract with Hardhat
+title: Deploy a Contract with Hardhat
 description: Learn how to deploy a basic smart contract to Polkadot Hub using Hardhat, Perfect for professional workflows requiring comprehensive testing and debugging.
 categories: Smart Contracts
 ---
 
-# Deploy a Basic Contract with
+# Deploy Basic Contract with Hardhat
 
 ## Introduction
 
 This guide demonstrates how to deploy a basic Solidity smart contract to Polkadot Hub using [Hardhat](https://hardhat.org/){target=\_blank}, which provides a comprehensive development environment with built-in testing, debugging, and deployment capabilities. It's ideal for professional development workflows and team projects.
 
 ## Prerequisites
 
-- Basic understanding of Solidity programming.
-- [Node.js](https://nodejs.org/en/download){target=\_blank} v22.13.1 or later.
-- Test tokens for gas fees (available from the [Polkadot faucet](https://faucet.polkadot.io/){target=\_blank}). See the [step-by-step instructions](/smart-contracts/faucet/#get-test-tokens){target=\_blank}.
+Before you begin, ensure you have the following:
+
+- A basic understanding of [Solidity](https://www.soliditylang.org/){target=\_blank} programming.
+- [Node.js](https://nodejs.org/en/download){target=\_blank} v22.13.1 or later installed.
+- Test tokens for gas fees, available from the [Polkadot faucet](https://faucet.polkadot.io/){target=\_blank}. See [Get Test Tokens](/smart-contracts/faucet/#get-test-tokens){target=\_blank} for a guide to using the faucet.
 - A wallet with a private key for signing transactions.
 
 ## Set Up Your Project
 
-Initialize your Hardhat project:
+Use the following terminal commands to create a directory and initialize your Hardhat project inside of it:
 
 ```bash
 mkdir hardhat-deployment
@@ -29,7 +31,7 @@ npx hardhat --init
 
 ## Configure Hardhat
 
-Edit `hardhat.config.js`:
+Open `hardhat.config.js` and update to add `polkadotHubTestnet` to the `networks` configuration as highlighted in the following example code:
 
 ```javascript title='hardhat.config.js' hl_lines='39-43'
 import type { HardhatUserConfig } from 'hardhat/config';
@@ -85,15 +87,21 @@ export default config;
 !!! tip
     Learn how to use Hardhat's [Config Variables](https://hardhat.org/docs/learn-more/configuration-variables){target=\_blank} to handle your private keys in a secure way.
 
-## Create Your Contract
+## Create the Contract
+
+Follow these steps to create your smart contract:
+
+1. Delete the default contract file(s) in the `contracts` directory.
 
-Replace the default contract in `contracts/Storage.sol`:
+2. Create a new file named `Storage.sol` inside the `contracts` directory.
 
-```solidity
-// SPDX-License-Identifier: MIT
-pragma solidity ^0.8.9;
+3. Add the following code to create the `Storage.sol` smart contract:
 
-contract Storage {
+  ```solidity
+  // SPDX-License-Identifier: MIT
+  pragma solidity ^0.8.9;
+
+  contract Storage {
     uint256 private storedNumber;
 
     function store(uint256 num) public {
@@ -103,31 +111,47 @@ contract Storage {
     function retrieve() public view returns (uint256) {
         return storedNumber;
     }
-}
-```
+  }
+  ```
+
+## Compile the Contract
 
-## Compile
+Compile your `Storage.sol` contract using the following command:
 
 ```bash
 npx hardhat build
 ```
 
+You will see a message in the terminal confirming the contract was successfully compiled similar to the following:
+
+<div id="termynal" data-termynal>
+  <span data-ty="input"><span class="file-path"></span>npx hardhat build</span>
+  <span data-ty>Downloading solc 0.8.28</span>
+  <span data-ty>Downloading solc 0.8.28 (WASM build)</span>
+  <span data-ty>Compiled 1 Solidity file with solc 0.8.28 (evm target: cancun)</span>
+  <span data-ty="input"><span class="file-path"></span></span>
+</div>
+
 ## Set Up Deployment
 
-Create a deployment module in `ignition/modules/Storage.ts`:
+1. Delete the default file(s) inside the `ignition/modules` directory.
 
-```typescript title="ignition/modules/Storage.ts"
-import { buildModule } from '@nomicfoundation/hardhat-ignition/modules';
+2. Create a new file named `Storage.ts` inside the `ignition/modules` directory.
 
-export default buildModule('StorageModule', (m) => {
-  const storage = m.contract('Storage');
-  return { storage };
-});
-```
+3. Open `ignition/modules/Storage.ts` and add the following code to create your deployment module:
+
+  ```typescript title="ignition/modules/Storage.ts"
+  import { buildModule } from '@nomicfoundation/hardhat-ignition/modules';
+
+  export default buildModule('StorageModule', (m) => {
+    const storage = m.contract('Storage');
+    return { storage };
+  });
+  ```
 
 ## Deploy the Contract
 
-Deploy to Polkadot Hub TestNet:
+Deploy your contract to Polkadot Hub TestNet using the following command:
 
 ```bash
 npx hardhat ignition deploy ignition/modules/Storage.ts --network polkadotHubTestnet 

smart-contracts/cookbook/smart-contracts/deploy-basic/remix.md

@@ -1,19 +1,21 @@
 ---
-title: Deploy a Basic Contract with Remix IDE
+title: Deploy a Contract with Remix IDE
 description: Learn how to deploy a basic smart contract to Polkadot Hub using Remix IDE Ideal for rapid prototyping, learning, and visual development.
 categories: Smart Contracts
 ---
 
-# Deploy a Basic Contract with Remix IDE
+# Deploy Basic Contract with Remix IDE
 
 ## Introduction
 
 This guide demonstrates how to deploy a basic Solidity smart contract to Polkadot Hub using [Remix IDE](https://remix.ethereum.org/){target=\_blank}, which offers a visual, browser-based environment perfect for rapid prototyping and learning. It requires no local installation and provides an intuitive interface for contract development.
 
 ## Prerequisites
 
-- Basic understanding of Solidity programming.
-- Test tokens for gas fees (available from the [Polkadot faucet](https://faucet.polkadot.io/){target=\_blank}). See the [step-by-step instructions](/smart-contracts/faucet/#get-test-tokens){target=\_blank}.
+Before you begin, ensure you have the following:
+
+- A basic understanding of [Solidity](https://www.soliditylang.org/){target=\_blank} programming.
+- Test tokens for gas fees, available from the [Polkadot faucet](https://faucet.polkadot.io/){target=\_blank}. See [Get Test Tokens](/smart-contracts/faucet/#get-test-tokens){target=\_blank} for a guide to using the faucet.
 - A wallet with a private key for signing transactions.
 
 ## Access Remix
@@ -24,16 +26,16 @@ The interface will load with a default workspace containing sample contracts. In
 
 ![](/images/smart-contracts/cookbook/smart-contracts/deploy-basic/deploy-basic/deploy-basic-01.webp)
 
-## Compile
+## Compile the Contract
 
-1. Navigate to the **Solidity Compiler** tab, which is the third icon in the left sidebar.
+1. Navigate to the **Solidity Compiler** tab.
 2. Click **Compile Storage.sol** or press `Ctrl+S`.
 
 ![](/images/smart-contracts/cookbook/smart-contracts/deploy-basic/deploy-basic/deploy-basic-02.webp)
 
-Compilation errors and warnings appear in the terminal panel at the bottom of the screen.
+If any issues arise during Compilation, errors and warnings will appear in the terminal panel at the bottom of the screen.
 
-## Deploy
+## Deploy the Contract
 
 1. Navigate to the **Deploy & Run Transactions** tab.
 2. Click the **Environment** dropdown and select **Injected Provider - MetaMask** (ensure your MetaMask wallet is connected to Polkadot Hub TestNet).
@@ -42,7 +44,7 @@ Compilation errors and warnings appear in the terminal panel at the bottom of th
 
 ![](/images/smart-contracts/cookbook/smart-contracts/deploy-basic/deploy-basic/deploy-basic-03.webp)
 
-Your deployed contract will appear in the **Deployed Contracts** section, ready for interaction.
+Once successfully deployed, your contract will appear in the **Deployed Contracts** section, ready for interaction.
 
 ## Where to Go Next