GITBOOK-221: No subject

r0gue-io · Nov 12, 2024 · 6410a4a · 6410a4a
1 parent 7bda181
commit 6410a4a
Show file tree

Hide file tree

Showing 5 changed files with 4 additions and 4 deletions.
diff --git a/pop-cli-for-smart-contracts/SUMMARY.md b/pop-cli-for-smart-contracts/SUMMARY.md
@@ -17,8 +17,8 @@
 * [Running E2E tests](guides/running-e2e-tests.md)
 * [Deploy on Pop](guides/deploy-on-pop-testnet.md)
 * [Deploy your contract locally](guides/deploy-your-contract-locally/README.md)
-  * [Deploy your contract locally](guides/deploy-your-contract-locally/deploy-your-contract-locally.md)
-  * [Deploy your contract on Pop locally](guides/deploy-your-contract-locally/deploy-your-contract-on-pop-locally.md)
+  * [Deploy locally on a Solochain](guides/deploy-your-contract-locally/deploy-locally-on-a-solochain.md)
+  * [Deploy locally on Pop](guides/deploy-your-contract-locally/deploy-locally-on-pop.md)
 
 ## TUTORIALS
 

diff --git a/pop-cli-for-smart-contracts/guides/calling-your-contract.md b/pop-cli-for-smart-contracts/guides/calling-your-contract.md
@@ -2,7 +2,7 @@
 
 Now that your contract is deployed locally, we can start interacting with it.
 
-Grab the contract address that was outputted from the [previous step](deploy-your-contract-locally/deploy-your-contract-locally.md).
+Grab the contract address that was outputted from the [previous step](deploy-your-contract-locally/deploy-locally-on-a-solochain.md).
 
 ```shell
 pop call contract -p ./flipper --contract 5CLPm1CeUvJhZ8GCDZCR7nWZ2m3XXe4X5MtAQK69zEjut36A --message get --suri //Alice

diff --git a/pop-cli-for-smart-contracts/guides/deploy-your-contract-locally/README.md b/pop-cli-for-smart-contracts/guides/deploy-your-contract-locally/README.md
@@ -7,4 +7,4 @@ There are two paths to deploy your contract locally:
 
 Both options are fine for local ink! smart contract development.
 
-For cross-chain messaging features and to use Pop API, you will need option 2: Pop.
+To develop cross-chain messaging features (which are inherent to Polkadot) and to use Pop API, you will need option 2: Deploy locally on Pop.
diff --git a/...t-locally/deploy-your-contract-locally.md → ...-locally/deploy-locally-on-a-solochain.md b/...t-locally/deploy-your-contract-locally.md → ...-locally/deploy-locally-on-a-solochain.md
diff --git a/...ly/deploy-your-contract-on-pop-locally.md → ...contract-locally/deploy-locally-on-pop.md b/...ly/deploy-your-contract-on-pop-locally.md → ...contract-locally/deploy-locally-on-pop.md
Original file line number	Diff line number	Diff line change
Expand Up		@@ -7,4 +7,4 @@ There are two paths to deploy your contract locally:

		Both options are fine for local ink! smart contract development.

		For cross-chain messaging features and to use Pop API, you will need option 2: Pop.
		To develop cross-chain messaging features (which are inherent to Polkadot) and to use Pop API, you will need option 2: Deploy locally on Pop.