From d19c5ffa0d2e0fab5c52f738c76d2114ddea2725 Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Sat, 22 Oct 2016 12:07:24 -0700 Subject: fix spelling errors caught by lintian Gbp-Pq: Name fix-spelling-errors-caught-by-lintian.patch --- keysafe.1 | 2 +- keysafe.hs | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/keysafe.1 b/keysafe.1 index c278bb1..c22d337 100644 --- a/keysafe.1 +++ b/keysafe.1 @@ -29,7 +29,7 @@ to decrypt. This makes it hard for an attacker to crack your password, because each guess they make costs them. .PP Keysafe is designed so that it should take millions of dollars of computer -time to crack any fairly good password. With a truely good +time to crack any fairly good password. With a truly good password, such as four random words, the cracking cost should be many trillions of dollars. Keysafe checks your password strength (using the zxcvbn library), and shows an estimate of the cost to crack your password, diff --git a/keysafe.hs b/keysafe.hs index 1e64226..996c0a7 100644 --- a/keysafe.hs +++ b/keysafe.hs @@ -144,7 +144,7 @@ backup cmdline ui tunables distinguisher (secretkeysource, secretkey) = do if queued then do willautostart <- isAutoStartFileInstalled - showInfo ui "Backup queued" $ "Some data was not sucessfully uploaded to servers, and has been queued for later upload." + showInfo ui "Backup queued" $ "Some data was not successfully uploaded to servers, and has been queued for later upload." ++ if willautostart then "" else " Run keysafe --uploadqueued at a later point to finish the backup." else showInfo ui "Backup success" "Your secret key was successfully encrypted and backed up." StoreFailure s -> showError ui ("There was a problem storing your encrypted secret key: " ++ s) -- cgit v1.2.3