From 93f6a8f70bc0a98ef982879d44d67bbfed735a2c Mon Sep 17 00:00:00 2001
From: awokd <34515595+awokd@users.noreply.github.com>
Date: Sun, 14 Nov 2021 16:10:25 +0000
Subject: [PATCH] Update split-ssh.md

Grammar tweak
---
 docs/configuration/split-ssh.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/configuration/split-ssh.md b/docs/configuration/split-ssh.md
index 8ba786d..c7fd98e 100644
--- a/docs/configuration/split-ssh.md
+++ b/docs/configuration/split-ssh.md
@@ -377,7 +377,7 @@ If you're getting an error (e.g. `error fetching identities: communication with
 * It is possible for a malicious VM to hold onto an ssh-agent connection for more than one use. 
 Therefore, if you authorize usage once, assume that a malicious VM could then use it many more times. 
 In this case, though, the SSH Agent will continue to protect your private keys; only usage of it would be available to the malicious VM until it is shut down.
-* It is still to be fully verified if solve the problem of allowing the user to know what is requested before the operation gets approved is properly solved by either:
+* The two actions below should allow the user to know what is requested before the operation gets approved, but has not been fully verified:
   * configuring the vault to use `ssh-add -c` as described above
   * configuring KeepassXC to "Require user confirmation when this key is used"