diff options
| -rw-r--r-- | pskc/policy.py | 2 | ||||
| -rw-r--r-- | tests/test_rfc6030.doctest | 2 | ||||
| -rw-r--r-- | tests/test_write.doctest | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/pskc/policy.py b/pskc/policy.py index b72aca3..a66e983 100644 --- a/pskc/policy.py +++ b/pskc/policy.py @@ -24,7 +24,7 @@ import warnings def _make_aware(d): - """Make tge specified datetime timezone aware.""" + """Make the specified datetime timezone aware.""" import dateutil.tz if not d.tzinfo: return d.replace(tzinfo=dateutil.tz.tzlocal()) 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') |