diff --git a/draft-ietf-suit-firmware-encryption.md b/draft-ietf-suit-firmware-encryption.md
index 75e0a19..db601dd 100644
--- a/draft-ietf-suit-firmware-encryption.md
+++ b/draft-ietf-suit-firmware-encryption.md
@@ -1427,11 +1427,11 @@ distribution, utilizing two primary methods: AES Key Wrap (AES-KW) and
Ephemeral-Static Diffie-Hellman (ES-DH). The key properties associated
with their deployment are summarized in {{cek-distribution}}.
-| Number of
Long-Term
Keys | Number of
Content
Encryption
Keys (CEKs) | Use Case | Recommended? |
-|----------------------------------|-----------------------------------------------------------------------|----------------------------------------------|----------------------|
-| Same key
for all
devices | Single
CEK per
payload
shared
with all
devies | Legacy
Usage | No, bad
practice |
-| One key
per device | Single
CEK per
payload
shared
with all
devies | Efficient
Payload
Distribution | Yes |
-| One Key
per device | One CEK
per payload
encryption
transaction
per device | Point-to-
Point Payload
Distribution | Yes |
+| Number of
Long-Term
Keys | Number of Content
Encryption Keys (CEKs) | Use Case | Recommended? |
+|----------------------------------|---------------------------------------------------------------|----------------------------------------------|----------------------|
+| Same key
for all
devices | Single CEK per
payload shared
with all devies | Legacy Usage | No, bad
practice |
+| One key
per device | Single CEK per
payload shared
with all devies | Efficient
Payload
Distribution | Yes |
+| One Key
per device | One CEK per payload
encryption transaction
per device | Point-to-
Point Payload
Distribution | Yes |
{: #cek-distribution title="Content Key Distribution: Comparison"}
The use of firmware encryption in battery-powered IoT devices introduces the