Arthur de Jong

Open Source / Free Software developer

summaryrefslogtreecommitdiffstats
path: root/tests
diff options
context:
space:
mode:
Diffstat (limited to 'tests')
-rw-r--r--tests/test_rfc6030.doctest2
-rw-r--r--tests/test_write.doctest2
2 files changed, 2 insertions, 2 deletions
diff --git a/tests/test_rfc6030.doctest b/tests/test_rfc6030.doctest
index df5193b..c02c851 100644
--- a/tests/test_rfc6030.doctest
+++ b/tests/test_rfc6030.doctest
@@ -217,7 +217,7 @@ True
This tests a PSKC file that uses asymmetric encryption as seen in figure 8 of
-RFC 6030. Note thet python-pskc does not yet support asymmetric encryption so
+RFC 6030. Note that python-pskc does not yet support asymmetric encryption so
this test is really limited.
>>> pskc = PSKC('tests/rfc6030/figure8.pskcxml')
diff --git a/tests/test_write.doctest b/tests/test_write.doctest
index c1ea198..04d1c9e 100644
--- a/tests/test_write.doctest
+++ b/tests/test_write.doctest
@@ -659,7 +659,7 @@ set on one key end up being applied to both keys.
If we specify a global IV it will be used for all encrypted values but will
be not be written as a global IV in the PSKC file because RFC 6030 does not
-specify this (and re-using an IV is a bad idea).
+specify this (and reusing an IV is a bad idea).
>>> pskc = PSKC()
>>> key = pskc.add_key(secret='1234')