Normalize lab docs and keep reusable TNS alias

scenarios/05-legacy-app-ai-extension/README.md

@@ -22,7 +22,7 @@ Before Oracle Deep Data Security, an AI agent connected to the same legacy schem
 Run commands from the repository root:
 
 ```powershell
-cd C:\Users\rodrigo\Documents\Codex\oracle-deep-data-security-lab
+cd <repo-root>
 ```
 
 Connect to the database with SQLcl or SQL*Plus:

scenarios/05-legacy-app-ai-extension/WORKSHOP.md

@@ -29,13 +29,16 @@ Before DDS, the AI agent can reuse broad legacy privileges and combine customer,
 ## Before You Begin
 
 ```bash
-cd ~/DEEP-DATA-SECURITY/oracle-deep-data-security-lab
-export TNS_ADMIN=~/DEEP-DATA-SECURITY/wallet-ddslab
+cd <repo-root>
+export TNS_ADMIN=<wallet-directory>
 sql admin@ddslab_tunnel
 ```
 
 SQLcl note: after running `@file.sql`, do not type `/`.
 
+
+Connection alias note: ddslab_tunnel is the TNS alias configured in the wallet `tnsnames.ora` for this lab. If your wallet uses another alias, replace ddslab_tunnel with your own service alias.
+
 ## Lab 1 - Prepare The Environment
 
 ### Task 1.1 - Reset The Scenario