update the quick start guide with corrections

Author: kmurphypolygon

docs/cdk/concepts/transaction-lifecycle.md

@@ -41,7 +41,7 @@ Depending on the data availability design choices of the L2, if the L2 is a [rol
 
 ## Aggregated
 
-The final step of the transaction lifecycle is to generate a ZK-proof that proves the batch of transactions is valid. Batches of transactions are read by the [aggregator](./architecture.md#aggregator) which utilizes a [prover](./architecture.md#prover) to generate a ZK-proof that is posted back to Ethereum.
+The final step of the transaction lifecycle is to generate a ZK-proof that proves the batch of transactions is valid. Batches of transactions are read by the [aggregator](./architecture.md#aggregator-and-prover) which utilizes a [prover](./architecture.md#aggregator-and-prover) to generate a ZK-proof that is posted back to Ethereum.
 
 ![Aggregator posting ZK-proof](../../img/cdk/aggregate-batches.png)
 

docs/cdk/getting-started/local-deployment.md

@@ -67,15 +67,15 @@ You might as well need the following tools to interact with the environment...
 
 ### Understanding the deployment steps
 
-There are two key configurations files which help you understand what happens during a deployment.
+There are two configuration files which help you understand what happens during a deployment.
 
-#### [`main.star`](https://github.com/0xPolygon/kurtosis-cdk/blob/main/main.star)
+#### 1. [`main.star`](https://github.com/0xPolygon/kurtosis-cdk/blob/main/main.star)
 
-The `main.star` file defines the step-by-step instructions of the deployment process. It is the main "hub" of the chain setup process; orchestrating the setup of all the components in sequential order by pulling in necessary logic from other files.
+The `main.star` file contains the step-by-step instructions for the deployment process. It orchestrates the setup of all the components in sequential order and pulls in any necessary logic from other files.
 
 It defines the following steps for the deployment process:
 
-| Step Number | Deployment Step                                                                            | Relevant Starlark Code                                                                                               | Enabled by Default |
+| Step number | Deployment step                                                                            | Relevant Starlark code                                                                                               | Enabled by default |
 | ----------- | ------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- | ------------------ |
 | 1           | Deploy a local layer 1 devnet chain                                                        | [ethereum.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/ethereum.star)                                   | True               |
 | 2           | Deploy the zkEVM smart contracts on the L1                                                 | [deploy_zkevm_contracts.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/deploy_zkevm_contracts.star)       | True               |
@@ -88,11 +88,13 @@ It defines the following steps for the deployment process:
 | 9           | Apply a load test to the chain                                                             | [load_test.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/workload.star)                                  | False              |
 | 10          | Deploy [Blutgang](https://github.com/rainshowerLabs/blutgang) for load balancing & caching | [cdk_blutgang.star](https://github.com/0xPolygon/kurtosis-cdk/blob/main/cdk_blutgang.star)                           | False              |
 
-You can customize (or skip) the logic for each of these steps by modifying the logic in the respective files.
+You can customize (or skip) any of these steps by modifying the logic in the respective files.
 
-#### [`params.yml`](https://github.com/0xPolygon/kurtosis-cdk/blob/main/params.yml) 
+#### 2. [`params.yml`](https://github.com/0xPolygon/kurtosis-cdk/blob/main/params.yml) 
 
-The `params.yml` file defines the parameters of the chain and the deployment process. It includes configurations for simple parameters such as the chain ID and more complex configurations such as the gas token smart contract address.
+The `params.yml` file defines the parameters of the chain and the deployment process. 
+
+It includes configurations for simple parameters such as the chain ID and more complex configurations such as the gas token smart contract address.
 
 You can modify each of these parameters to customize the chain to your specific needs.
 
@@ -151,49 +153,48 @@ Now that your chain is running, you can explore and interact with each component
 
 Below are a few examples of how you can interact with the chain.
 
-### Sending test transactions
+### Read/write operations
 
-Let’s perform some basic read and write operations on the L2 using Foundry.
+Let's do some read and write operations and test transactions on the L2 with Foundry.
 
-Export the RPC URL of your L2 to an environment variable called `ETH_RPC_URL` with the following command:
+1. Export the RPC URL of your L2 to an environment variable called `ETH_RPC_URL` with the following command:
 
-```bash
-export ETH_RPC_URL="$(kurtosis port print cdk-v1 zkevm-node-rpc-001 http-rpc)"
-```
+      ```bash
+      export ETH_RPC_URL="$(kurtosis port print cdk-v1 cdk-erigon-node-001 http-rpc)"
+      ```
 
-Then, use `cast` to view information about the chain, such as the latest block number:
+2. Use `cast` to view information about the chain, such as the latest block number:
 
-```bash
-cast block-number
-```
+      ```bash
+      cast block-number
+      ```
 
-View the balance of an address, such as the pre-funded admin account:
+3. View the balance of an address, such as the pre-funded admin account:
 
-```bash
-cast balance --ether 0xE34aaF64b29273B7D567FCFc40544c014EEe9970
-```
+      ```bash
+      cast balance --ether 0xE34aaF64b29273B7D567FCFc40544c014EEe9970
+      ```
 
-Send simple transactions to the chain, such as a transfer of some ETH:
+4. Send simple transactions to the chain, such as a transfer of some ETH:
 
-```bash
-cast send --legacy --value 0.01ether 0x0000000000000000000000000000000000000000 --private-key "0x12d7de8621a77640c9241b2595ba78ce443d05e94090365ab3bb5e19df82c625"
-```
+      ```bash
+      cast send --legacy --value 0.01ether 0x0000000000000000000000000000000000000000 --private-key "0x12d7de8621a77640c9241b2595ba78ce443d05e94090365ab3bb5e19df82c625"
+      ```
 
 !!! info
-
       The `0xE34...9970` and `0x12d...c625` public-private key pair used in the above commands is the default admin account configured in `params.yml`.
 
 ### Load testing the chain
 
-Use the [polycli loadtest](https://github.com/maticnetwork/polygon-cli/blob/main/doc/polycli_loadtest.md) command to send multiple transactions at once to the chain to test its performance:
+Use the [`polycli loadtest`](https://github.com/maticnetwork/polygon-cli/blob/main/doc/polycli_loadtest.md) command to send multiple transactions at once to the chain to test its performance:
 
 ```bash
 polycli loadtest --rpc-url "$ETH_RPC_URL" --legacy --verbosity 700 --requests 500 --rate-limit 5 --mode t --private-key "0x12d7de8621a77640c9241b2595ba78ce443d05e94090365ab3bb5e19df82c625"
 ```
 
 ### Viewing transaction finality
 
-A common way to check the status of the system is to ensure that batches are being sent and verified on the L1 chain.
+A common way to check the status of the system is by ensuring that batches are sent and verified on the L1 chain.
 
 Use `cast` to view the progression of batches from trusted, virtual, and verified states:
 
@@ -208,17 +209,35 @@ cast rpc zkevm_verifiedBatchNumber  # Latest batch verified or "proven" on the L
 To open the bridge interface and bridge tokens across the L1 and L2, run the following command:
 
 ```bash
-open $(kurtosis port print cdk-v1 zkevm-bridge-proxy-001 bridge-interface)
+open $(kurtosis port print cdk-v1 zkevm-bridge-proxy-001 web-ui)
 ```
 
+!!! tip
+      If the `open` command doesn't work, you can find the URL's in the Kurtosis output.
+
 ### Viewing chain metrics
 
-To view information such as how many transactions are being processed, the amount of gas being used, the time since a batch was last verified, how many addresses have bridged, and much more, a Grafana dashboard is included in the deployed observability stack which can be opened by running the following command:
+!!! warning
+      - Observability defaults to false.
+      - Turn on observability in the deployment by setting the `deploy_observability` parameter to `true` in `params.yml`.
+      - Redeploy Kurtosis.
+
+Once the observability function is activated, you can see information such as:
+
+- How many transactions are being processed. 
+- The amount of gas being used. 
+- The time since a batch was last verified. 
+- How many addresses have bridged.
+
+Open the Grafana dashboard by running the following command:
 
 ```bash
 open $(kurtosis port print cdk-v1 grafana-001 dashboards)
 ```
 
+!!! tip
+      If the `open` command doesn't work, you can find the URL's in the Kurtosis output.
+
 From the hamburger menu, navigate to `Dashboards` and select the `Panoptichain` dashboard to view all of the metrics.
 
 ![Panoptichain Dashboard](../../img/cdk/grafana.png)
@@ -233,8 +252,10 @@ kurtosis clean --all
 
 ## Going to production
 
-While it is possible to run a CDK chain on your own, we strongly recommend getting in touch with the [Polygon Labs team directly](https://share-eu1.hsforms.com/1aI6l7_bFTn-vWl0NIFVzDQc8xid), or one of our [Implementation Providers](https://ecosystem.polygon.technology/spn/cdk/) for production deployments.
+While it is possible to run a CDK chain on your own, we strongly recommend getting in touch with the [Polygon team directly](https://share-eu1.hsforms.com/1aI6l7_bFTn-vWl0NIFVzDQc8xid), or one of our [implementation providers](https://ecosystem.polygon.technology/spn/cdk/) for production deployments.
 
-## Dive deeper into the CDK
+## Further reading
 
-For more detailed information on the CDK’s architecture, components, and how to customize your chain, refer to the [CDK architecture documentation](https://docs.polygon.technology/cdk/architecture/cdk-zkevm/).
+- For more information on CDK architecture, components, and how to customize your chain, refer to the [CDK architecture documentation](https://docs.polygon.technology/cdk/architecture/cdk-zkevm/).
+- For detailed how to's, including how to create a native token, check out our [how to guides](../how-to/use-native-token.md).
+- For detailed conceptual information on zero-knowledge stacks, check out our [concepts documentation](../concepts/layer2s.md).