diff --git a/src/pages/signatures/getting-started/document-lifecycle.mdx b/src/pages/signatures/getting-started/document-lifecycle.mdx
index ccd49630..0d9eb6d6 100644
--- a/src/pages/signatures/getting-started/document-lifecycle.mdx
+++ b/src/pages/signatures/getting-started/document-lifecycle.mdx
@@ -10,7 +10,7 @@ subtitle: Learn how Idura Signatures handles your documents securely and safely.
 
 - **Signature order is created:** When you create a signature order with `createSignatureOrder`, you send along document blobs with it. Upon receiving the order, we validate and encrypt it, then store it on Azure servers.
 - **Signatory signs:** Whenever a signatory needs to sign a document, we download and decrypt it to show it to the user.
-  Once the user signs, we embed the signatory evidence (usually eID claims returned by Idura Verify) inside the PDF and seal it with Idura's AATL certificate.
+  Once the user signs, we embed the signatory evidence (usually eID claims returned by Idura Verify) inside the PDF and seal it with Idura's EUTL certificate.
   After sealing the PDF, we encrypt it again and store it on Azure servers, ready for the next person to sign.
 - **Signature order is closed:** Upon closing a signature order, we apply a final document timestamp to the PDF to ensure that the data inside is valid for multiple years.
   You should always request document blobs as part of the close response, as this is the last time they will be available. After closing the order, the documents will be deleted from Idura's servers.