How to reproduce the problem
The user is editing a content.
The content is automatically locked to avoid anyone to edit it at the same time
The user decide to cancel the modification by clicking on the icon to "cancel & quit"
The content is displayed

Actual behavior
The content stay locked.

Reason of this behavior
This behavior was made because the decision to edit a content is important and is due to a real need. Then the user decide to cancel but may need to edit it afterwards, for example he need to do some pre-requised that he forgot (like to upload a picture) or to ask a some one for information... but he wants to keep the lock on it.

Waiting behavior
The basic use case is:

• edit, then cancel without lock because the user is going to forgot to lock
  How it can be solve?
• A configuration point to decide by default to lock the content?
• an icon to lock the content before editing, so to be unlock the user need to unlock
• an icon to "cancel and unlock" and another one to "cancel and keep locked"
• ...