From 17a9ba6bda3501dd3864d3385c6fde23036283b8 Mon Sep 17 00:00:00 2001
From: purifyyourhome <44551716+purifyyourhome@users.noreply.github.com>
Date: Fri, 18 Jan 2019 18:42:14 -0500
Subject: [PATCH] Added part about SSH's capabilities and uses (#31256)

Added part to indicate SSH's capabilities, and separated a sentence into two to indicate how developers often use SSH.
---
 guide/english/ssh/managing-multiple-ssh-keys/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/guide/english/ssh/managing-multiple-ssh-keys/index.md b/guide/english/ssh/managing-multiple-ssh-keys/index.md
index 2e82b4c7c3..87b68599e6 100644
--- a/guide/english/ssh/managing-multiple-ssh-keys/index.md
+++ b/guide/english/ssh/managing-multiple-ssh-keys/index.md
@@ -3,7 +3,7 @@ title: Managing multiple SSH keys
 ---
 # Managing multiple SSH keys
 
-It is safe to say that most developers in the Web sphere have at some point encountered SSH. SSH is one of the most used protocols for safe data exchange. You use SSH for connecting to remote servers, which also includes managing your code using git and syncing with remote repositories.
+It is safe to say that most developers in the Web sphere have at some point encountered SSH. SSH is one of the most used protocols for safe data exchange. You can use SSH for connecting to remote servers, issuing commands and managing files. For developers, often this includes managing your code using git and syncing with remote repositories.
 
 Even though it is considered a good practice to have one private-public key pair per device, sometimes you need to use multiple keys and/or you have unorthodox key names. You might be using one SSH key-pair for working on your company's internal projects but you might be using a different key for accessing some corporate client's servers. You might even be using a different key for accessing your own private server.