diff --git a/aqua-examples/aqua-ceramic-integration/README.md b/aqua-examples/aqua-ceramic-integration/README.md
index e91c166..26c02eb 100644
--- a/aqua-examples/aqua-ceramic-integration/README.md
+++ b/aqua-examples/aqua-ceramic-integration/README.md
@@ -12,7 +12,7 @@ In this example, we develop an adapter for the Ceramic [CLI API](https://develop
 
 Our adapter service mounts the Ceramic CLI with the [MountedBinaryResult](https://doc.fluence.dev/docs/knowledge_aquamarine/marine/marine-rs-sdk#mountedbinaryresult) interface requiring the availability of [Ceramic tools](https://developers.ceramic.network/build/cli/installation/) as a sidecar. In addition, a limited Ceramic HTTP API implementation is also available using the Marine [curl adapter](https://doc.fluence.dev/docs/tutorials_tutorials/curl-as-a-service). Since the HTTP API is limited and won't let users create streams, it is offered primarily for educational purposes, although it may be useful in scenarios where a ceramic daemon deployment is not feasible.
 
-**Please note that Ceramic binary access is currently only available at Fluence's `stage` network environment (`aqua env stage`) with path `/usr/bin/ceramic`.**
+**Please note that Ceramic binary access is currently only available at Fluence's `stage` network environment (`aqua config default_peers stage`) with path `/usr/bin/ceramic`.**
 
 ToDos:
 
diff --git a/aqua-examples/echo-greeter/Readme.md b/aqua-examples/echo-greeter/Readme.md
index 37bb07b..68ef0b9 100644
--- a/aqua-examples/echo-greeter/Readme.md
+++ b/aqua-examples/echo-greeter/Readme.md
@@ -97,10 +97,10 @@ result: String("Bye, yah")
  elapsed time: 49.64µs
 ```
 
-Looks like all is working as planned and we're ready to deploy our services to the Fluence testnet. To deploy a service, we need the peer id of our desired host node, which we can get with `aqua env`:
+Looks like all is working as planned and we're ready to deploy our services to the Fluence testnet. To deploy a service, we need the peer id of our desired host node, which we can get with `aqua config default_peers`:
 
 ```text
-% aqua env
+% aqua config default_peers
 /dns4/kras-00.fluence.dev/tcp/19990/wss/p2p/12D3KooWSD5PToNiLQwKDXsu8JSysCwUt8BVUJEqCHcDe7P5h45e
 /dns4/kras-00.fluence.dev/tcp/19001/wss/p2p/12D3KooWR4cv1a8tv7pps4HH6wePNaK6gf1Hww5wcCMzeWxyNw51
 /dns4/kras-01.fluence.dev/tcp/19001/wss/p2p/12D3KooWKnEqMfYo9zvfHmqTLpLdiHXPe4SVqUWcWHDJdFGrSmcA
diff --git a/aqua-examples/price-oracle/README.md b/aqua-examples/price-oracle/README.md
index 5e4d61a..1db8851 100644
--- a/aqua-examples/price-oracle/README.md
+++ b/aqua-examples/price-oracle/README.md
@@ -155,7 +155,7 @@ which gives you the updated Wasm modules in the `artifacts` directory.
 The next step is to deploy the two services to one or more peers and we use the `aqua` cli tool to get this done. First, we need to now what peers are available and we can get an enumeration from:
 
 ```bash
-aqua env
+aqua config default_peers
 ```
 
 *Please note that multiple service instances have been already deployed and the (peer id, service id) tuples can be found in [data]("./data/deployed_services.json) json file. While your more than welcome to deploy your services, you don't have to in order to use them.*