Draft button should change to Edit button on node Display

Thanks for the report, I see what you mean, and assume you are talking about the default workflow when in a published state. A draft button doesn’t necessarily mean a button that doesn’t do anything, meaningful though I agree it normally would be. Transitions can be named whatever you want. If we were to consider this change we’d want to consider removing buttons that save into an unpublished state that also does not become the default revision. That change might make sense in many cases, but I can imagine flows where it wouldn’t. Say a request to unpublish button, which then moves the content to an editor with final say over what gets unpublished. I think your likely best bet for this would be to do a form alter to remove the offending button and add an edit button if that matches your need.

Using form alter hook rename it as per the requirement. But changing the draft button to edit means when node is in publish state or any other state and user need to be edit node then it will create lack of certainty to edit that node.

I don’t recommend adding an “Edit” button or replacing the “Draft” button with an “Edit” button. If a user is allowed to edit the content, they probably already see an “Edit” button in the usual place.

Usually, workflow buttons are used for things like approvals. In these cases, the person approving the content should see the final version, not the edit form. These users often cannot edit the content at all — and even if they can, editing is not the action they are meant to take with the workflow buttons.

That said, your situation might be different. If you really need to add the “Edit” button there, you can do it using a form alter.

One thing that could be possible here, might be to offer config for transitions to exclude from workflow buttons in the display mode. That would require some thought as to how to present that in an intuitive way.