Update content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md

Sharra-writes · Copilot · web-flow · commit df8d5956c127 · 2026-04-14T09:44:13.000-07:00
Co-authored-by: Copilot &lt;175728472+Copilot@users.noreply.github.com&gt;
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
@@ -176,7 +176,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 > ```powershell
 > git config --global core.sshCommand "C:/Windows/System32/OpenSSH/ssh.exe"
 > ```
-> 
+>
 > You may need to specify which `ssh-keygen` binary Git should use to avoid conflicts with the binary bundled with Git for Windows. To define which binary is used, run the following command:
 > 
 > ```powershell

Original file line number	Diff line number	Diff line change
`@@ -176,7 +176,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav`
`176`	`176`	> ```powershell
`177`	`177`	`> git config --global core.sshCommand "C:/Windows/System32/OpenSSH/ssh.exe"`
`178`	`178`	> ```
`179`		`->`
	`179`	`+>`
`180`	`180`	> You may need to specify which `ssh-keygen` binary Git should use to avoid conflicts with the binary bundled with Git for Windows. To define which binary is used, run the following command:
`181`	`181`	`>`
`182`	`182`	> ```powershell