From 3b0cc22d198671a61c466b57175fe48204acf40c Mon Sep 17 00:00:00 2001
From: Ana <84312885+AnaLoznianu@users.noreply.github.com>
Date: Tue, 10 Oct 2023 17:37:14 +0300
Subject: [PATCH] Update install.md

---
 developers/ocean-cli/install.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/developers/ocean-cli/install.md b/developers/ocean-cli/install.md
index 78ddb1a1..d1a81c4f 100644
--- a/developers/ocean-cli/install.md
+++ b/developers/ocean-cli/install.md
@@ -37,11 +37,17 @@ To successfully configure the CLI tool, two essential steps must be undertaken:
 
 ### Private Key Configuration
 
-The CLI tool requires the configuration of the account's private key. This private key serves as the means by which the CLI tool establishes a connection to the associated wallet. It plays a crucial role in authenticating and authorizing operations performed by the tool.
+The CLI tool requires the configuration of the account's 'private key'(by exporting env "PRIVATE_KEY") or a 'mnemonic'(by exporting env "MNEMONIC").
+Both serve as the means by which the CLI tool establishes a connection to the associated wallet. It plays a crucial role in authenticating and authorizing operations performed by the tool. You must choose either one option or the other. The tool will not utilize both simultaneously.
 
 ```bash
 export PRIVATE_KEY="XXXX"
 ```
+or 
+
+```bash
+export MNEMONIC="XXXX"
+```
 
 ### RPC Endpoint Specification
 Additionally, it is imperative to specify the RPC endpoint that corresponds to the desired network for executing operations. The CLI tool relies on this user-provided RPC endpoint to connect to the network required for its functions. This connection to the network is vital as it enables the CLI tool to interact with the blockchain and execute operations seamlessly.