summaryrefslogtreecommitdiffhomepage
path: root/keysafe.1
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2016-10-22 12:07:24 -0700
committerSean Whitton <spwhitton@spwhitton.name>2016-10-22 13:45:13 -0700
commitd19c5ffa0d2e0fab5c52f738c76d2114ddea2725 (patch)
tree74be4e1f80910e35c56b138bfaf89b313615a465 /keysafe.1
parent14ab8020228fa44acfeb124edf944e011b99dcc4 (diff)
downloadkeysafe-d19c5ffa0d2e0fab5c52f738c76d2114ddea2725.tar.gz
fix spelling errors caught by lintian
Gbp-Pq: Name fix-spelling-errors-caught-by-lintian.patch
Diffstat (limited to 'keysafe.1')
-rw-r--r--keysafe.12
1 files changed, 1 insertions, 1 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,