Update content/en/post/2024-12-20-acme-profiles.md

Co-authored-by: J.C. Jones <[email protected]>

content/en/post/2024-12-20-acme-profiles.md

@@ -66,7 +66,7 @@ If the new-order request is accepted, then the selected profile name will be ref
 
 If you are an ACME client author, we encourage you to introduce support for this new field in your client. Start by taking a look at the [draft specification in the IETF ACME Working Group](https://datatracker.ietf.org/doc/draft-aaron-acme-profiles/). A simple implementation might allow the user to configure a static profile name and include that name in all new-order requests. For a better user experience, check the configured name against the list of profiles advertised in the directory, to ensure that changes to the available profiles don't result in invalid new-order requests. For clients with a user interface, such as a control panel or interactive command line interface, an implementation could fetch the list of profiles and their descriptions to prompt the user to select one on first run. It could also use a notification mechanism to inform the user of changes to the list of available profiles. We'd also love to hear from you about your experience implementing and deploying this new extension.
 
-If you are a site operator or ACME client user, we encourage you to keep an eye on your ACME client of choice to see when they adopt this new feature, and update your client when they do. We also encourage you to try out the "modern" profile in Staging, and let us know what you think of the changes we've made to the certificates issued under that profile.
+If you are a site operator or ACME client user, we encourage you to keep an eye on your ACME client of choice to see when they adopt this new feature, and update your client when they do. We also encourage you to try out the modern "tlsserver" profile in Staging, and let us know what you think of the changes we've made to the certificates issued under that profile.
 
 ### What's next?