Walkthrough guide edits

docs/getting-started.md

@@ -7,6 +7,8 @@ title: Getting Started
 
 You understand subnets from the [overview](https://docs.hiro.so/subnets/overview)—now you can test one out in action. Hiro's Clarinet can serve a local subnet with [`clarinet integrate`](https://docs.hiro.so/clarinet/how-to-guides/how-to-run-integration-environment) as one of the networks in your Stacks development environment.
 
+## What to expect
+
 This guide walks a user through a **subnet demonstration**: minting and transferring NFTs between a main chain (local devnet) and a subnet to showcase subnet's high throughput and low latency functionality. By the end of this guide, the user will
 
 - Deploy the layer-1 contract that governs the interface to your subnet
@@ -64,8 +66,7 @@ Now, we will use Clarinet to create our L1 contract:
 clarinet contract new simple-nft-l1
 ```
 
-This creates the file, _./contracts/simple-nft-l1.clar_, which will include the
-following clarity code:
+This creates the file, _./contracts/simple-nft-l1.clar_, which will include the following Clarity code:
 
 ```clarity
 (define-constant CONTRACT_OWNER tx-sender)
@@ -129,6 +130,8 @@ Note that this contract implements the `mint-from-subnet-trait` and the SIP-009
 
 #### Creating the subnet (L2) contract
 
+Next, we will manually create the subnet contract at _./contracts/simple-nft-l2.clar_ with `touch contracts/simple-nft-l2.clar` in terminal.
+
 Next, we will create the subnet contract at _./contracts/simple-nft-l2.clar_. As mentioned earlier, Clarinet does not support deploying subnet contracts yet, so we will manually create this file and add the following contents:
 
 :::note
@@ -225,20 +228,24 @@ Uncomment, or add, the following line under `[devnet]`:
 enable_subnet_node = true
 ```
 
-Also, in that file, we can see a few default settings that `clarinet` will be using for our subnet. `subnet_contract_id` specifies the L1 contract with which the subnet will be interacting. This will be automatically downloaded from the network and deployed by `clarinet` but you can take a look at it [here](https://explorer.hiro.so/txid/0x7d8a5d649d0f2b7583a456225c2e98b40ba62a124c5187f6dbfa563592b24e76?chain=testnet) if interested.
+### Optional Settings
+
+Also, in that file, we can see a few default settings that `clarinet` will be using for our subnet.
+It is not necessary to modify any of these settings, but doing so allows you to customize your test environment.
+`subnet_contract_id` specifies the L1 contract with which the subnet will be interacting.
+This will be automatically downloaded from the network and deployed by `clarinet` but you can take a look at it [here](https://explorer.hiro.so/txid/0x7d8a5d649d0f2b7583a456225c2e98b40ba62a124c5187f6dbfa563592b24e76?chain=testnet) if interested.
 
 ```toml
-subnet_contract_id = "ST13F481SBR0R7Z6NMMH8YV2FJJYXA5JPA0AD3HP9.subnet-v1-2"
+subnet_contract_id = "ST13F481SBR0R7Z6NMMH8YV2FJJYXA5JPA0AD3HP9.subnet-v1-1"
 ```
 
-`subnet_node_image_url` and `subnet_api_image_url` specify the docket images that will be used for the subnet node and the subnet API node, respectively.
+`subnet_node_image_url` and `subnet_api_image_url` specify the docket images that will be used for the subnet node and the subnet API node, respectively. Make sure your settings match the ones below:
 
 ```toml
-subnet_node_image_url = "hirosystems/stacks-subnets:0.4.1"
+subnet_node_image_url = "hirosystems/stacks-subnets:0.4.2"
 subnet_api_image_url = "hirosystems/stacks-blockchain-api:7.1.0-beta.2"
 ```
 
-You do not need to modify or uncomment any of these, but you can if you'd like to test a custom subnet implementation.
 
 Once the configuration is complete, run the following command to start the
 devnet environment:
@@ -273,11 +280,13 @@ By the end of this section, we will have these several scripts that correspond t
 - _withdraw-l1.js_ - the second step to withdrawal is to undeposit the NFT asset from L1 interface contract
 - _verify.js_ - querying the current owner of an NFT
 
+
 To submit transactions to Hiro's Stacks node and subnet node, we will use the following simple scripts. We will save them in a new directory, _./scripts/_.
 
 ```sh
 mkdir scripts
 cd scripts
+touch {publish,register,mint,deposit,transfer,withdraw-l2,withdraw-l1,verify}.js
 ```
 
 Then we will initialize a Node.js project and install the Stacks.js dependencies:
@@ -384,7 +393,7 @@ async function main() {
   const senderKey = process.env.DEPLOYER_KEY;
   const deployerAddr = process.env.DEPLOYER_ADDR;
   const userAddr = process.env.USER_ADDR;
-  const nonce = await getNonce(deployerAddr, network);
+  const nonce = (await getNonce(deployerAddr, network)) + BigInt(1);
 
   const txOptions = {
     contractAddress: "ST1PQHQKV0RJXZFY1DGX8MNSNYVE3VGZJSRTPGZGM",
@@ -750,11 +759,12 @@ First, we will publish the L2 NFT contract to the subnet:
 node ./publish.js simple-nft-l2 ../contracts/simple-nft-l2.clar 2 0
 ```
 
-Clarinet's interface doesn't show the transactions on the subnet, but we can see
-the transaction in our local explorer instance. In a web browser, visit
-http://localhost:8000. By default, it will open the explorer for the devnet L1.
-To switch to the subnet, select "Network" in the top right, then "Add a
-network." In the popup, choose a name, e.g., "Devnet Subnet," then for the URL, use "http://localhost:13999". You will know this contract deployment succeeded when you see the contract deploy transaction for "simple-nft-l2" in the list of confirmed transactions.
+Clarinet's terminal interface does not show the transactions on the subnet, but we can see the transaction in our local explorer instance. In a web browser, visit http://localhost:8000. By default, it will open the Explorer for the devnet L1. To switch to the subnet, select "Network" in the top right, then "Add a network." In the popup, choose a name, e.g., "Devnet Subnet" and then for the URL, use "http://localhost:13999". You will know this contract deployment succeeded when you see the contract deploy transaction for "simple-nft-l2" in the list of confirmed transactions. Be sure to confirm transactions before proceeding.
+
+:::note
+
+Each of these scripts depend upon the prior transaction to be published to either the L1 devnet or the L2 subnet before the next transaction can be completed successfully (for instance, the `register.js` transaction must be published to a devnet block before the `mint.js` transaction can be called). The Explorer shows these transactions in each new block; be sure to occasionally refresh the Explorer.
+:::
 
 ![contract deploy confirmed](images/subnets-deployment-confirmed.png)
 
@@ -821,10 +831,13 @@ Now, we will initiate a withdrawal from the subnet, by calling the
 node ./withdraw-l2.js 0
 ```
 
-We can confirm that this transaction is successful in the L2 explorer. In the explorer, note the block height that this withdrawal transaction is included in. Fill in this block height for `$height` in the next step.
+We can confirm that this transaction is successful in the L2 explorer. For the second part of the withdraw, we call `withdraw-nft-asset` on the L1 subnet contract:
+
+:::note
+
+In the explorer, note the block height that this withdrawal transaction is included in. Fill in this block height for `$height` in the next step.
 
-For the second part of the withdraw, we call `withdraw-nft-asset` on the L1
-subnet contract:
+:::
 
 ```sh
 node ./withdraw-l1.js $height 0

docs/overview.md

@@ -4,7 +4,7 @@ title: Overview
 
 # Overview
 
-A subnet is a layer-2 scaling solution for the Stacks blockchain, offering low latency and high throughput at the expense of centralization to a federated set of miners, enabling developers to build fast and reliable user experiences on Stacks.
+A subnet is a layer-2 scaling solution for the Stacks blockchain, offering low latency and high throughput, enabling developers to build fast and reliable user experiences on Stacks.
 
 ## Background