Use standard terminology to describe the personalization string
NIST and many other sources call it a "personalization string", and
certainly not "device-specific identifiers" which is actually somewhat
misleading since this is just one of many things that might go into a
personalization string.
diff --git a/include/mbedtls/ctr_drbg.h b/include/mbedtls/ctr_drbg.h
index 3d17628..3599e95 100644
--- a/include/mbedtls/ctr_drbg.h
+++ b/include/mbedtls/ctr_drbg.h
@@ -203,7 +203,7 @@
* \p f_entropy is always called with a buffer size equal to the entropy
* length described in the documentation of mbedtls_ctr_drbg_set_entropy_len().
*
- * Personalization data can be provided in addition to the more generic
+ * You can provide a personalization string in addition to the
* entropy source, to make this instantiation as unique as possible.
*
* \note The _seed_material_ value passed to the derivation
@@ -231,11 +231,10 @@
* \p p_entropy context, the buffer to fill, and the
* length of the buffer.
* \param p_entropy The entropy context to pass to \p f_entropy.
- * \param custom Personalization data, that is device-specific
- * identifiers. This can be \c NULL, in which case the
- * personalization data is empty regardless of the value
- * of \p len.
- * \param len The length of the personalization data.
+ * \param custom The personalization string.
+ * This can be \c NULL, in which case the personalization
+ * string is empty regardless of the value of \p len.
+ * \param len The length of the personalization string.
* This must be at most
* #MBEDTLS_CTR_DRBG_MAX_SEED_INPUT / 2.
*