Apply suggestion from @Sharra-writes

Sharra-writes · web-flow · commit 9aa4442339fe · 2026-04-14T09:27:30.000-07:00
diff --git a/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -167,7 +167,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
 > ### Troubleshooting SSH agent conflicts in Windows
 >
-> In Windows environments, the native Windows OpenSSH implementation and the one included with Git for Windows (based on MSYS2/Bash) can coexist.
+> In Windows environments, the native Windows OpenSSH implementation and the one included with [Git for Windows](https://gitforwindows.org/) (based on MSYS2/Bash) can coexist.
 >
 > If you configure and save your passphrases in the Windows agent using PowerShell, Git may still prompt you for your passphrase during operations like `git push`. This can happen when Git for Windows uses its bundled `ssh.exe` (from MSYS2) instead of the Windows system OpenSSH client, and therefore can't talk to the Windows `ssh-agent` service.
 >

Original file line number	Diff line number	Diff line change
`@@ -167,7 +167,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav`
`167`	`167`
`168`	`168`	`> ### Troubleshooting SSH agent conflicts in Windows`
`169`	`169`	`>`
`170`		`-> In Windows environments, the native Windows OpenSSH implementation and the one included with Git for Windows (based on MSYS2/Bash) can coexist.`
	`170`	`+> In Windows environments, the native Windows OpenSSH implementation and the one included with [Git for Windows](https://gitforwindows.org/) (based on MSYS2/Bash) can coexist.`
`171`	`171`	`>`
`172`	`172`	> If you configure and save your passphrases in the Windows agent using PowerShell, Git may still prompt you for your passphrase during operations like `git push`. This can happen when Git for Windows uses its bundled `ssh.exe` (from MSYS2) instead of the Windows system OpenSSH client, and therefore can't talk to the Windows `ssh-agent` service.
`173`	`173`	`>`