From c32d63fc9396258bb1c6df5fd052a5cd61d5c5fb Mon Sep 17 00:00:00 2001 From: Aman Chopra Date: Thu, 28 Aug 2025 16:06:02 +0530 Subject: [PATCH] updated the notes --- docs/hyperexecute-bidi-testing.md | 2 +- docs/network-whitelisting-and-tunnel-guide.md | 4 +++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/hyperexecute-bidi-testing.md b/docs/hyperexecute-bidi-testing.md index 266f30ff8..4a958fddb 100644 --- a/docs/hyperexecute-bidi-testing.md +++ b/docs/hyperexecute-bidi-testing.md @@ -113,7 +113,7 @@ From the project root directory, execute the below CLI command in your terminal:
- {`./hyperexecute --user ${ YOUR_LAMBDATEST_USERNAME()} --key ${ YOUR_LAMBDATEST_ACCESS_KEY()} --config hyperexecute.yaml`} + {`./hyperexecute --user ${ YOUR_LAMBDATEST_USERNAME()} --key ${ YOUR_LAMBDATEST_ACCESS_KEY()} --config yaml/hyperexecute-linux.yaml`}
diff --git a/docs/network-whitelisting-and-tunnel-guide.md b/docs/network-whitelisting-and-tunnel-guide.md index 7347524f1..d5feca54d 100644 --- a/docs/network-whitelisting-and-tunnel-guide.md +++ b/docs/network-whitelisting-and-tunnel-guide.md @@ -45,7 +45,9 @@ import TabItem from '@theme/TabItem'; > When testing private or restricted environments on LambdaTest, your team may need to configure network access controls. Depending on how your applications are hosted and secured, LambdaTest supports multiple approaches **Inbound Whitelisting, Dedicated Proxy, Outbound Whitelisting, STUN/TURN Whitelisting, and Tunnel configurations (including Site-to-Site tunnels)**. -This guide helps you decide which option to use for your infrastructure setup. +> These are Inbound and Outbound with respect to user's network. + +This guide helps you decide which option to use for your infrastructure setup. ## 1. When Inbound Whitelisting Has to Be Done (Shared IP) Inbound IP whitelisting allows LambdaTest cloud browsers and devices to directly access your IP-restricted web applications without using a tunnel.