summaryrefslogtreecommitdiff
path: root/providers/implementations/keymgmt/kdf_legacy_kmgmt.c
diff options
context:
space:
mode:
Diffstat (limited to 'providers/implementations/keymgmt/kdf_legacy_kmgmt.c')
-rw-r--r--providers/implementations/keymgmt/kdf_legacy_kmgmt.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/providers/implementations/keymgmt/kdf_legacy_kmgmt.c b/providers/implementations/keymgmt/kdf_legacy_kmgmt.c
index 0b301c333b..73e6974208 100644
--- a/providers/implementations/keymgmt/kdf_legacy_kmgmt.c
+++ b/providers/implementations/keymgmt/kdf_legacy_kmgmt.c
@@ -69,7 +69,7 @@ int ossl_kdf_data_up_ref(KDF_DATA *kdfdata)
/* This is effectively doing a new operation on the KDF_DATA and should be
* adequately guarded again modules' error states. However, both current
- * calls here are guarded propery in exchange/kdf_exch.c. Thus, it
+ * calls here are guarded properly in exchange/kdf_exch.c. Thus, it
* could be removed here. The concern is that something in the future
* might call this function without adequate guards. It's a cheap call,
* it seems best to leave it even though it is currently redundant.