From e69bc7adbfb57c8d252565c1c84d3efbbe64d4cd Mon Sep 17 00:00:00 2001
From: Carl Tashian <carl@smallstep.com>
Date: Thu, 4 Jun 2026 16:03:43 -0700
Subject: [PATCH] Andrew's feedback

---
 certificate-manager/acme/README.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/certificate-manager/acme/README.mdx b/certificate-manager/acme/README.mdx
index be28d74d..47244d18 100644
--- a/certificate-manager/acme/README.mdx
+++ b/certificate-manager/acme/README.mdx
@@ -24,7 +24,7 @@ including enterprise use cases.
 
 <Alert severity="info">
   <div>
-    <strong>ACME vs. ACME device attestation.</strong> Standard ACME issues certificates to servers and workloads, proving control of a domain or IP address through the <code>http-01</code>, <code>dns-01</code>, or <code>tls-alpn-01</code> challenges. <a href="https://smallstep.com/platform/acme-device-attestation/">ACME device attestation (ACME DA)</a> extends the same protocol to issue hardware-bound certificates for <em>device</em> identity, using the <code>device-attest-01</code> challenge to verify a device's built-in security module. Reach for ACME DA when you're identifying devices rather than servers.
+    <strong>ACME vs. ACME device attestation.</strong> Standard ACME issues certificates to servers and workloads, proving control of a domain or IP address through the <code>http-01</code>, <code>dns-01</code>, or <code>tls-alpn-01</code> challenges. <a href="https://smallstep.com/platform/acme-device-attestation/">ACME device attestation (ACME DA)</a> extends the same protocol to issue hardware-bound certificates for <em>device</em> identity, using the <code>device-attest-01</code> challenge to verify a device's built-in security module. Reach for ACME DA when you're identifying devices rather than hostnames and IPs.
   </div>
 </Alert>