diff --git a/website/content/docs/configuration/target-aliases/transparent-sessions.mdx b/website/content/docs/configuration/target-aliases/transparent-sessions.mdx
index 920092bbce..e50518ae99 100644
--- a/website/content/docs/configuration/target-aliases/transparent-sessions.mdx
+++ b/website/content/docs/configuration/target-aliases/transparent-sessions.mdx
@@ -15,7 +15,7 @@ description: >-
 
 Before you configure transparent sessions, you must:
 
-- Ensure that the Boundary CLI and Boundary Desktop are not installed in the environment in which you want to run the transparent sessions beta.
+- If you have previous versions of the Boundary Desktop or CLI client in your local environment, ensure that they are fully uninstalled before you install with the latest Boundary installer.
 - Download the appropriate Boundary installer for your Windows or MacOS environment from the [Install Boundary](/boundary/install#installer) page or the [releases](https://releases.hashicorp.com/boundary-installer) page.
 - Ensure that both IPv4 and IPv6 protocols are enabled for your environment. The [Client Agent](/boundary/docs/api-clients/client-agent) requires both protocols to start and perform DNS lookups.
 
@@ -96,4 +96,4 @@ With transparent sessions, you use the target alias as the address to establish
 $ ssh my.alias.name
 ```
 
-Boundary starts the session as usual, and brokers or injects any credentials you have configured.
\ No newline at end of file
+Boundary starts the session as usual, and brokers or injects any credentials you have configured.