From b1b549c1bfb0411287d9225ae9978754a90396c7 Mon Sep 17 00:00:00 2001
From: Kumar Anirudha <mail@anirudha.dev>
Date: Tue, 2 Apr 2024 17:55:13 +0530
Subject: [PATCH 1/3] updated deploy to publish

---
 framework/docs/src/4_get_started/7_module_deployment.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/framework/docs/src/4_get_started/7_module_deployment.md b/framework/docs/src/4_get_started/7_module_deployment.md
index ae6d325c26..8b3e933a0c 100644
--- a/framework/docs/src/4_get_started/7_module_deployment.md
+++ b/framework/docs/src/4_get_started/7_module_deployment.md
@@ -31,11 +31,11 @@ Now you can go ahead and deploy the module to the network(s) you want to make it
 running the following command:
 
 ```bash
-$ just deploy uni-1
+$ just publish uni-1
 > Deploying module...
 ```
 
-This will use the module's `examples/deploy.rs` script to deploy the module to the `uni-1` network. The resulting
+This will use the module's `examples/publish.rs` script to deploy the module to the `uni-1` network. The resulting
 code-id of your contract should now be in the `state.json` file created for you. The script will also attempt to
 register the module on the Abstract Version Control, hence the mnemonic used in the script should be the same as the one
 you used to create the account and register the namespace.

From 331007d9722256ece0a22572a63f9fa4e457ca44 Mon Sep 17 00:00:00 2001
From: Kumar Anirudha <mail@anirudha.dev>
Date: Wed, 3 Apr 2024 23:08:08 +0530
Subject: [PATCH 2/3] updated readme instructions on compiling

---
 .../docs/src/4_get_started/2_installation.md    |  4 ++--
 .../src/4_get_started/7_module_deployment.md    | 17 +++++++++++++----
 2 files changed, 15 insertions(+), 6 deletions(-)

diff --git a/framework/docs/src/4_get_started/2_installation.md b/framework/docs/src/4_get_started/2_installation.md
index 32850b9f5b..71199822ce 100644
--- a/framework/docs/src/4_get_started/2_installation.md
+++ b/framework/docs/src/4_get_started/2_installation.md
@@ -81,7 +81,7 @@ The template contains a scaffold contract that you can use as a starting point f
 
 If there's anything you don't understand about the template please don't hesitate to reach out to us on our <a href="https://discord.com/invite/uch3Tq3aym" target="_blank">Discord</a> server.
 
-## Front-end layout
+<!-- ## Front-end layout
 
 To generate the front-end scaffold, you can run `just ts-codegen`, which will run a code generation script for you found in the `typescript/scripts` folder. The code generation script will generate TypeScript code based on the specifications defined in the contract schemas.
 
@@ -93,7 +93,7 @@ follows:
 - `Template.message-composer.ts`: Aids in crafting messages necessary for interacting with a specific
   blockchain contract, particularly for updating configurations. It contains a class that generates message objects that can be sent to the blockchain for execution.
 - `Template.msg-builder.ts`: Provides static methods on abstract classes to create message objects for querying or executing actions on the blockchain. It essentially facilitates the building of structured messages for blockchain interactions.
-- `Template.types.ts`: Defines various data structures and types that represent the structure of messages and responses within the blockchain module, aiding in maintaining consistency across different operations in the module.
+- `Template.types.ts`: Defines various data structures and types that represent the structure of messages and responses within the blockchain module, aiding in maintaining consistency across different operations in the module. -->
 
 ## Tools used in the template
 
diff --git a/framework/docs/src/4_get_started/7_module_deployment.md b/framework/docs/src/4_get_started/7_module_deployment.md
index 8b3e933a0c..3ccec7c19c 100644
--- a/framework/docs/src/4_get_started/7_module_deployment.md
+++ b/framework/docs/src/4_get_started/7_module_deployment.md
@@ -14,6 +14,8 @@ network.
 
 ### Compiling your module
 
+Once you have confirmed that your module works as expected you can spin up a local node and deploy Abstract + your app onto the chain. You need [Docker](https://www.docker.com/) installed for this step. 
+
 You can compile your module by running the following command:
 
 ```bash
@@ -25,13 +27,20 @@ $ just wasm
 > it from <a href="https://docs.docker.com/get-docker/" target="_blank">here</a>.
 
 This should result in an `artifacts` directory being created in your project root. Inside you will find
-a `my_module.wasm` file that is your module's binary.
+a `my_module.wasm` file that is your module's binary. 
+
+```admonish warning
+Make sure it's the same name as mentioned in `Cargo.toml` file. If not, just edit it to match.
+```
+
+### Publish your module
+
+Before attempting to publish your app you need to add your mnemonic to the `.env` file. **Don't use a mnemonic that has mainnet funds for this.** Make sure this account has funds. If you don't have the deployment will fail. Get funds from respective chain faucets or ask for some test tokens on Abstract Discord.
 
-Now you can go ahead and deploy the module to the network(s) you want to make it available on. You can do this by
-running the following command:
+Now you can go ahead and publish the module to the network(s) you want to make it available on. You can do this by running the following command:
 
 ```bash
-$ just publish uni-1
+$ just publish uni-6
 > Deploying module...
 ```
 

From fc98b920dbc2bd1b8b14b67312b00d64ced87047 Mon Sep 17 00:00:00 2001
From: Kumar Anirudha <mail@anirudha.dev>
Date: Thu, 4 Apr 2024 19:41:51 +0530
Subject: [PATCH 3/3] removed warning on name of app

---
 framework/docs/src/4_get_started/7_module_deployment.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/framework/docs/src/4_get_started/7_module_deployment.md b/framework/docs/src/4_get_started/7_module_deployment.md
index 3ccec7c19c..169e4bebc2 100644
--- a/framework/docs/src/4_get_started/7_module_deployment.md
+++ b/framework/docs/src/4_get_started/7_module_deployment.md
@@ -29,10 +29,6 @@ $ just wasm
 This should result in an `artifacts` directory being created in your project root. Inside you will find
 a `my_module.wasm` file that is your module's binary. 
 
-```admonish warning
-Make sure it's the same name as mentioned in `Cargo.toml` file. If not, just edit it to match.
-```
-
 ### Publish your module
 
 Before attempting to publish your app you need to add your mnemonic to the `.env` file. **Don't use a mnemonic that has mainnet funds for this.** Make sure this account has funds. If you don't have the deployment will fail. Get funds from respective chain faucets or ask for some test tokens on Abstract Discord.