Here is a rough summary of what users could do. Feel free to change the wording and improve this paragraph further! : )

• Review the list of existing certificates
  • From theActions menu, you can then delete that certificate

This would be incorrect. The "Actions" menu is from the cert management page, where users can choose to delete a certificate object from N1 Console. However, the contexts here are that users can remove a deployed certificate file from an instance or a CSG. If users want to remove a cert deployment from a specific instance or CSG, they should only be able to do that through the config editor (where users edit NGINX configuration for an instance or a CSG). It would also be helpful to clarify that when users click on the delete icon from the config editor, they would delete the deployed certificate or key file fromspecific file paths.

• Navigate to [Manage Config Sync Groups]({{< relref "/nginx-one/how-to/config-sync-groups/manage-config-sync-groups" >}})
  • You can then delete the certificate from the Config Sync Group of your choice.

https://frontdoor-test-docs.nginx.com/previews/docs/291/nginx-one/how-to/nginx-configs/manage-config-sync-groups/
In addition, I wasn't able to find any instructions on how users could delete the certificate from a Config Sync Group in this page, so this could be confusing to the reader.

I'm thinking that deleting a certificate file is a special case for deleting an aux file. Since we have a page that documents how to add a file, should we also add a new page that documents how to remove a file? That might be easier in comparison to trying to fit all the details into a small section in the cert management doc.
https://frontdoor-test-docs.nginx.com/previews/docs/291/nginx-one/how-to/nginx-configs/add-file/
https://frontdoor-test-docs.nginx.com/previews/docs/291/nginx-one/how-to/config-sync-groups/add-file-csg/

I'm realizing that our coverage of "Edit Configuration" for instances and CSGs are haphazard. I'm going to address@sylwang 's comments, and later, address#427 to "unify" the messaging.

@sylwang see:https://github.com/nginx/documentation/pull/291/files#diff-2445ce44d5814d8ceb795a09fa3672417a9d86c176326cf9ecbc3036b8fc5702R170-R178

Thank you for opening a new PR to address this. The new changes look good!

Hi@mjang, just checking in, what are your thoughts on this part of the doc?

I'd like to avoid references to "Data Plane", as we'll soon incorporateNGF data planes in N1C.

In any case, I think this is superseded byhttps://github.com/nginx/documentation/pull/291/files#diff-2445ce44d5814d8ceb795a09fa3672417a9d86c176326cf9ecbc3036b8fc5702R170-R178

The only case when it would lead to publication failures for the instance or CSG associated with a certificate, is when users choose to delete a deployed certificate. Let's remove this warning from this section and add it to the section "Deleted a deployed certificate".

The warning

{{< warning >}} Be cautious if you want to delete certificates that are being used in the NGINX configuration of an instance or a Config Sync Group. Deleting deployed certificates can lead to publication failure in affected NGINX instances or Config Sync Groups. {{< /warning >}}

should be added for this section.