Fix heading capitalization

Author: emirmx

content/en/docs/refguide/runtime/optimistic-locking.md

@@ -30,15 +30,15 @@ Optimistic locking can be enabled per Mendix application using the `Runtime` tab
 
 {{< figure src="/attachments/refguide/runtime/optimistic-locking/runtime-settings-dialog.png" >}}
 
-After optimistic locking is enabled, whenever a commit is executed, the Mendix runtime will automatically ensure that the object that is committed was not already changed by another party after the committer read the object.
+After optimistic locking is enabled, whenever a commit is executed, the Mendix runtime will automatically ensure that the object that is committed was not already changed by another party after the committer retrieved the object.
 
 ### New Projects and Migration
 
 In case an existing app already had the `MxObjectVersion` attribute, when optimistic locking is enabled a duplicate attribute will be reported in the Modeler. This must be fixed by renaming the existing attribute to another name. The system attribute cannot be renamed.
 
 ### Behavior
 
-Here we describe how various runtime actions are influenced by optimistic locking:
+The following runtime actions are influenced by optimistic locking:
 
 #### Create Object
 
@@ -50,7 +50,7 @@ When the `MxObjectVersion` attribute in the object being committed is different
 
 #### Delete Object
 
-When the `MxObjectVersion` attribute in the object being deleted is different from the value in the database, throw a `ConcurrentModificationRuntimeException`. Otherwise, proceed with the delete. If the object was already deleted, no error occurs, as is the case without optimistic locking.
+When the `MxObjectVersion` attribute in the object being deleted is different from the value in the database, throw a `ConcurrentModificationRuntimeException`. Otherwise, proceed with the delete. If the object was already deleted, no error occurs.
 
 ## Performance Impact
 
@@ -93,11 +93,11 @@ If the optimistic locking error is propagated to the client, then an error dialo
 
 {{< figure src="/attachments/refguide/runtime/optimistic-locking/optimistic-locking-error-dialog.png" >}}
 
-To handle the optimistic locking error one of the following strategies can be used:
+To handle the optimistic locking error one of the following approaches can be used:
 
 ### Single `Save` Button
 
-In this case user can refresh the whole page losing all changes.
+In this case the user can refresh the whole page, but this causes all their changes to be lost.
 
 ### `Save` Button With a Separate `Refresh` Button