From 87d45ff0ef2abeb2d5be3d48aa7a4d3e278bf87d Mon Sep 17 00:00:00 2001
From: Santori Helix <74464484+santorihelix@users.noreply.github.com>
Date: Wed, 18 Nov 2020 20:52:26 +0000
Subject: [PATCH] Update split-ssh.md

---
 docs/configuration/split-ssh.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/configuration/split-ssh.md b/docs/configuration/split-ssh.md
index 56e7934..2636482 100644
--- a/docs/configuration/split-ssh.md
+++ b/docs/configuration/split-ssh.md
@@ -331,7 +331,7 @@ Theoretically, you can use any AppVM but to increase security it is advised to c
 
 ## Test Your Configuration
 
-1. Shutdown your vaultVM.
+1. Shutdown KeePassXC on your vault VM.
 
 2. Try fetching your identities on the SSH Client VM. 
 
@@ -343,9 +343,9 @@ Theoretically, you can use any AppVM but to increase security it is advised to c
 
     ![operation execution](https://aws1.discourse-cdn.com/free1/uploads/qubes_os/original/1X/adcd0c408226c24950d2c876a38d2fecad8aacea.png)
 
-Check if it returns `error fetching identities: communication with agent failed`
+Check if it returns `The agent has no identities.`
 
-4. Start your vaultVM and unlock your KeePassXC database.
+4. Launch KeePassXC and unlock your database.
 
 5. Try fetching your identities on the SSH Client VM.