diff --git a/testnet-onboarding-demo.md b/testnet-onboarding-demo.md
index 69b1932..1c84198 100644
--- a/testnet-onboarding-demo.md
+++ b/testnet-onboarding-demo.md
@@ -8,7 +8,7 @@
 
 ### Laconic Wallet
 
-- The `laconicd-wallet` can be installed using an APK on a Android device or run as a website using `laconic-wallet-web`
+- The `laconic-wallet` can be installed using an APK on an Android device or run as a website using `laconic-wallet-web`
 - Follow one of the following (`Setup On Android` or `Setup As Website`) sections as desired
 
 #### Setup On Android
@@ -185,7 +185,7 @@
     export SUMSUB_SECRET_KEY=
     ```
 
-  - Set the env config for app and apk deployments:
+  - Set the env config for app and api deployments:
 
     ```bash
     cat <<EOF > onboarding-app-deployment/config.env
@@ -427,7 +427,7 @@
     ```
 
 - Create a deployment spec-file for Alice's L1 nitro-node:
-  - Create spec files for the deployment:
+  - Create spec file for the deployment:
 
     ```bash
     laconic-so --stack ~/cerc/nitro-stack/stack-orchestrator/stacks/nitro-node deploy init --output l1alice-nitro-spec.yml
@@ -465,7 +465,7 @@
     ```
 
 - Create a deployment spec-file for Alice's L2 nitro-node:
-  - Create spec files for the deployment:
+  - Create spec file for the deployment:
 
     ```bash
     laconic-so --stack ~/cerc/nitro-stack/stack-orchestrator/stacks/nitro-node deploy init --output l2alice-nitro-spec.yml
@@ -535,7 +535,7 @@
 
     NOTE: The `fixturenet-optimism-contracts` service will configure and deploy the Optimism contracts to L1, exiting when complete. This may take several minutes; you can follow the progress by following the container's logs
 
-    - Follow Nitro contracts deployment logs:
+    - Follow optimism contracts deployment logs:
 
       ```bash
       laconic-so deployment --dir fixturenet-optimism-deployment logs -f fixturenet-optimism-contracts
@@ -648,7 +648,12 @@
   laconic-so deployment --dir onboarding-api-deployment start
   ```
 
-  The `testnet-onboarding-app` should now be accessible at <http://localhost:3000>
+  Check the logs of the onboarding-app
+  ```bash
+  docker ps | grep testnet-onboarding-app
+  ```
+
+  Once the container is healthy, the `testnet-onboarding-app` will be accessible at <http://localhost:3000>
 
 - Run Laconic Wallet
 
@@ -703,14 +708,6 @@
 
 ## Demo
 
-- In laconic-wallet, click on `Create wallet` and update the `laconicd` network using `Edit Network` button:
-
-  ```bash
-  Network name    - laconicd
-  New RPC URL     - http://127.0.0.1:26657
-  Gas Price       - 1
-  ```
-
 - Start the stack for stage 0 laconicd (run command in directory where stage0-deployment had been created)
 
   ```bash
@@ -720,6 +717,14 @@
   laconic-so deployment --dir stage0-deployment logs laconicd -f
   ```
 
+- In laconic-wallet, click on `Create wallet` and update the `laconicd` network using `Edit Network` button:
+
+  ```bash
+  Network name    - laconicd
+  New RPC URL     - http://127.0.0.1:26657
+  Gas Price       - 1
+  ```
+
 - Run laconic-faucet:
 
   - Get private key of funded faucet account from stage 0 laconicd chain:
@@ -1000,7 +1005,7 @@
   - Perform the user verification steps
   - Select the desired participant role (`Validator` or `Participant`) and accept the onboarding terms and conditions
   - In the next step, fund your laconic account by clicking on the `REQUEST TOKENS FROM FAUCET` button; ensure that the displayed balance is updated
-  - Send transaction request to the Wallet
+  - Send transaction request to the wallet
     - From wallet, approve and send transaction to laconicd chain
   - Repeat onboarding for other (Charlies's) account by clicking on the web app header "Testnet Onboarding"
   - List the participants on stage 1 (run in the directory where laconicd deployment was  created):