Updated instructions for SDK

Author: syrettaman

docs/getting_started/create_account.md

@@ -84,11 +84,11 @@ You will be asked to input your password to export the keypair. The keypair will
 To add your keypair, type the following command below:
 === "Linux / macOS"
     ```bash
-    ./pchain_client keys import --public-key <PUBLIC_KEY> --private-key <PRIVATE_KEY> --name <NAME>
+    ./pchain_client keys import --public <PUBLIC_KEY> --private <PRIVATE_KEY> --name <NAME>
     ```
 === "Windows"
     ```PowerShell
-    pchain_client.exe keys import --public-key <PUBLIC_KEY> --private-key <PRIVATE_KEY> --name <NAME>
+    pchain_client.exe keys import --public <PUBLIC_KEY> --private <PRIVATE_KEY> --name <NAME>
     ```
 
 You will be asked to input your password to import the new keypair.

docs/smart_contract_sdk/build_contract.md

@@ -5,7 +5,7 @@ tags:
   - Smart Contract
 ---
 
-# Building the Contract with 'pchain_compile'
+# Building the Contract with pchain_compile
 
 **pchain_compile** is a CLI build tool for smart contract developers to build their source code to WASM binaries for deployment on 
 ParallelChain Mainnet. 
@@ -29,3 +29,23 @@ The WASM binary generated from a generic cargo build process has the following d
 
 `pchain_compile` supports Linux, macOS and Windows. Depending on the operating system, they can be downloaded from Assets of ParallelChain Lab's Git Hub [release page](https://github.com/parallelchain-io/pchain-compile/releases/tag/v0.4.0).
 
+!!! Pre-Requisites
+    `pchain_compile` builds the source code in a docker environment. To know more about Docker and install it, refer to the [official instructions](https://docs.docker.com/engine/install/).
+
+
+
+## Build WASM Binary
+---
+
+In order to build a `WASM` binary of the smart contract, run the following command:
+
+=== "Linux / macOS"
+    ```bash
+    ./pchain_compile build --source <PATH_TO_SMART_CONTRACT_CODE>
+    ```
+=== "Windows"
+    ```PowerShell
+    ./pchain_compile.exe build --source <PATH_TO_SMART_CONTRACT_CODE>
+    ```
+
+A `.wasm` file will be generated in the current directory. It will be needed for the [next section](./deploy_contract.md).

docs/smart_contract_sdk/call_contract.md

@@ -51,7 +51,7 @@ Here is the command to call a contract:
     call \
     --target <CONTRACT_ADDRESS> \   
     --method <contract_METHOD> \
-    --argument <CALL_ARGUMENT_FILE_PATH_WITH_FILE_NAME>
+    --arguments <CALL_ARGUMENT_FILE_PATH_WITH_FILE_NAME>
     --amount <AMOUNT_TO_CONTRACT> \
     ```
 === "Windows"
@@ -64,7 +64,7 @@ Here is the command to call a contract:
     call \
     --target <CONTRACT_ADDRESS> \   
     --method <contract_METHOD> \
-    --argument <CALL_ARGUMENT_FILE_PATH_WITH_FILE_NAME>
+    --arguments <CALL_ARGUMENT_FILE_PATH_WITH_FILE_NAME>
     --amount <AMOUNT_TO_CONTRACT> \
     ```
 

docs/smart_contract_sdk/deploy_contract.md

@@ -19,7 +19,7 @@ You can deploy the contract using the pchain_client command line tool. You shoul
     --max-base-fee-per-gas <MAX_BASE_FEE_PER_GAS> \
     --priority-fee-per-gas <PRIORITY_FEE_PER_GAS> \
     deploy \
-    --contract-code <CONTRACT_FILE_PATH_WITH_FILE_NAME> \
+    --contract-code <WASM_BINARY_PATH> \
     --cbi-version <CBI_VERSION> 
     ```
 === "Windows"
@@ -30,7 +30,7 @@ You can deploy the contract using the pchain_client command line tool. You shoul
     --max-base-fee-per-gas <MAX_BASE_FEE_PER_GAS> \
     --priority-fee-per-gas <PRIORITY_FEE_PER_GAS> \ 
     deploy \
-    --contract-code <CONTRACT_FILE_PATH_WITH_FILE_NAME> \
+    --contract-code <WASM_BINARY_PATH> \
     --cbi-version <CBI_VERSION> 
     ```