diff --git a/content/rke/latest/en/config-options/secrets-encryption/_index.md b/content/rke/latest/en/config-options/secrets-encryption/_index.md
index 5801592df0a..f2a17364746 100644
--- a/content/rke/latest/en/config-options/secrets-encryption/_index.md
+++ b/content/rke/latest/en/config-options/secrets-encryption/_index.md
@@ -56,7 +56,7 @@ services:
 ```
 Once enabled, RKE will perform the following [actions](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#encrypting-your-data) to enable at-rest data encryption:
 
-- Generate a new random 32-bit encryption key
+- Generate a new random 32-byte encryption key
 - Generate an encryption provider configuration file using the new key The default [provider](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#providers) used is `aescbc`
 - Deploy the provider configuration file to all nodes with `controlplane` role
 - Update the `kube-apiserver` container arguments to point to the provider configuration file.
@@ -105,7 +105,7 @@ OPTIONS:
 ```
 This command will perform the following actions:
 
-- Generate a new random 32-bit encryption key
+- Generate a new random 32-byte encryption key
 - Generate a new provider configuration with the new key as the first provider and the second key as the second provider. When the secrets are rewritten, the first key will be used to encrypt the data on the write operation, while the second key (the old key) will be used to decrypt the stored data during the the read operation
 - Deploy the new provider configuration to all `controlplane` nodes and restart the `kube-apiserver`
 - Rewrite all secrets. This process will re-encrypt all the secrets with the new key.