From 3c3e3509edb2085cbba59e4821d25fbbd61e024a Mon Sep 17 00:00:00 2001
From: abSauce <45953059+abSauce@users.noreply.github.com>
Date: Mon, 9 Dec 2024 14:52:24 -0600
Subject: [PATCH] Update Sauce Connect metrics API environment variable to SC 5
 variable

Changed SC_API_ADDRESS to SAUCE_API_ADDRESS as suggested below.

https://docs.saucelabs.com/dev/cli/sauce-connect-5/run/#api-address
---
 .../sauce-connect-5/operation/readiness-checks.md               | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/secure-connections/sauce-connect-5/operation/readiness-checks.md b/docs/secure-connections/sauce-connect-5/operation/readiness-checks.md
index 4610fda68e..2154e878c5 100644
--- a/docs/secure-connections/sauce-connect-5/operation/readiness-checks.md
+++ b/docs/secure-connections/sauce-connect-5/operation/readiness-checks.md
@@ -94,7 +94,7 @@ to wait for the sc container to be healthy before starting the test container.
 Sauce Connect provides a local [API server](/secure-connections/sauce-connect-5/operation/api-server) that contains readiness and liveness endpoints. 
 The readiness endpoint `/readyz` returns a 200 response code when Sauce Connect Proxy is ready, and 503 otherwise.
 
-To use the API server, you need to start Sauce Connect with the `--api-address` option or set the `SC_API_ADDRESS` environment variable.
+To use the API server, you need to start Sauce Connect with the `--api-address` option or set the `SAUCE_API_ADDRESS` environment variable.
 
 ```bash
 sc --api-address :8032 …