From 8908ce3e3c39b833d230d6e2cbf21e1b5e3cbf29 Mon Sep 17 00:00:00 2001
From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com>
Date: Mon, 3 Jun 2024 16:36:46 +0000
Subject: [PATCH] backport of commit dd3314864d798739d36c38f471c7c8643e774c15

---
 website/content/docs/concepts/domain-model/targets.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/content/docs/concepts/domain-model/targets.mdx b/website/content/docs/concepts/domain-model/targets.mdx
index cc0a7117d0..e56f702c09 100644
--- a/website/content/docs/concepts/domain-model/targets.mdx
+++ b/website/content/docs/concepts/domain-model/targets.mdx
@@ -114,8 +114,8 @@ SSH targets use injected application credentials to authenticate an SSH session
 Injected credentials allow users to securely connect to remost hosts using SSH, while never being in the possession of a valid credential for that target host.
 The injected credentials can be a username/password or username/private key credential from Vault [credential libraries][] or they can be static [credentials][] or an SSH certificate from Vault SSH credential libraries.
 
-You cannot establish an SSH connection to a target using brokered credentials.
-If you do not configure injected credentials to make the SSH connection, any attempts to connect to the SSH target result in an error.
+SSH targets require you to configure injected credentials in order to create a session.
+If you attempt to create a session against an SSH target without configuring injected credentials, it results in an error.
 However, you can use brokered credentials with SSH targets for purposes other than establishing the initial SSH connection.
 
 SSH targets have the following additional attributes: