diff options
author | Sean Whitton <spwhitton@spwhitton.name> | 2016-10-22 12:07:24 -0700 |
---|---|---|
committer | Sean Whitton <spwhitton@spwhitton.name> | 2016-10-22 13:45:13 -0700 |
commit | d19c5ffa0d2e0fab5c52f738c76d2114ddea2725 (patch) | |
tree | 74be4e1f80910e35c56b138bfaf89b313615a465 | |
parent | 14ab8020228fa44acfeb124edf944e011b99dcc4 (diff) | |
download | keysafe-d19c5ffa0d2e0fab5c52f738c76d2114ddea2725.tar.gz |
fix spelling errors caught by lintian
Gbp-Pq: Name fix-spelling-errors-caught-by-lintian.patch
-rw-r--r-- | keysafe.1 | 2 | ||||
-rw-r--r-- | keysafe.hs | 2 |
2 files changed, 2 insertions, 2 deletions
@@ -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, @@ -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) |