Extra TW review

Author: NicoletaComan

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

@@ -24,23 +24,23 @@ For example, if one user commits changes for `AttributeA` and `AttributeB` and a
 
 ## Behavior of App with Optimistic Locking Enabled
 
-The Mendix runtime implements optimistic locking by tracking the version of all objects using the attribute `MxObjectVersion` with type `Long`. Although the `MxObjectVersion` attribute is not write-protected, setting this value will **not** result in it being saved to the database. Its current value will be compared with the value for the same object in the database.
+The Mendix runtime implements optimistic locking by tracking the version of all objects using the attribute `MxObjectVersion` with type `Long`. Although the `MxObjectVersion` attribute is not write-protected, setting this value does not result in it being saved to the database. Its current value is compared with the value for the same object in the database.
 
 ### How to Enable and Use Optimistic Locking
 
-You can enable optimistic locking for your Mendix application in the `Runtime` tab in the App settings dialog:
+You can enable optimistic locking for your Mendix application in the `Runtime` tab in the **App Settings** dialog:
 
 {{< 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 retrieved the object.
+After optimistic locking is enabled, whenever a commit is executed, the Mendix runtime automatically ensures that the object that is committed was not already changed by another party after the committer retrieved the object.
 
 ### New Projects and Migration
 
-If an existing app already has the `MxObjectVersion` attribute, a duplicate attribute will be reported in Studio Pro when optimistic locking is enabled. This must be fixed by renaming the existing attribute to another name. The system attribute cannot be renamed.
+If an existing app already has the `MxObjectVersion` attribute, a duplicate attribute is reported in Studio Pro when optimistic locking is enabled. This must be fixed by renaming the existing attribute. The system attribute cannot be renamed.
 
 ### Behavior
 
-The following runtime actions are influenced by optimistic locking:
+The following runtime actions are influenced by optimistic locking.
 
 #### Create Object
 
@@ -52,7 +52,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, the runtime throw a `ConcurrentModificationRuntimeException`. Otherwise, it proceeds with the delete. If the object has already been deleted, no error occurs.
+When the `MxObjectVersion` attribute in the object being deleted is different from the value in the database, the runtime throws a `ConcurrentModificationRuntimeException`. Otherwise, it proceeds with the delete. If the object has already been deleted, no error occurs.
 
 ## Performance Impact
 
@@ -73,7 +73,7 @@ com.mendix.systemwideinterfaces.connectionbus.data.ConcurrentModificationRuntime
 Object of type 'MyFirstModule.MyEntity' with guid '3940649673949185' cannot be updated, as it is modified by someone else at MyFirstModule.MyMicroflow (Change : 'Change 'MyEntity'')
 ```
 
-The above error shows that there was a `ConcurrentModificationRuntimeException` during execution of the change action `Change 'MyEntity'` of the microflow `MyFirstModule.MyMicroflow`. The object had the id `3940649673949185` and was of type `MyFirstModule.MyEntity`.
+This error shows that there was a `ConcurrentModificationRuntimeException` while executing the `Change 'MyEntity'` change action of the `MyFirstModule.MyMicroflow` microflow. The object had the `3940649673949185` ID and was of type `MyFirstModule.MyEntity`.
 
 If committing an object causes an optimistic locking error, trying to commit the same object without reloading always results in an optimistic locking error.
 
@@ -82,10 +82,10 @@ If the changes are still deemed valid, you can retry the action causing the opti
 1. Change the error handling for that action to either `Custom with Rollback` or `Custom without Rollback`, and do the following steps in the error flow.
 2. If `$latestError/ErrorType` is `com.mendix.systemwideinterfaces.connectionbus.data.ConcurrentModificationRuntimeException`.
 3. Retrieve a fresh copy of the object from the database.
-4. Apply the original changes onto the retrieved copy.
+4. Apply the original changes to the retrieved copy.
 5. Perform the operation again.
 
-You can see an example implementation in the image below. The change action has error handling `Custom without Rollback`. If an optimistic locking error is detected, the latest version of the object is retrieved from the database, changes are applied again, and the change action is retried.
+You can see an example implementation in the following image. The change action has error handling `Custom without Rollback`. If an optimistic locking error is detected, the latest version of the object is retrieved from the database, changes are applied again, and the change action is retried.
 
 {{< figure src="/attachments/refguide/runtime/optimistic-locking/retry-example.png" >}}
 
@@ -97,7 +97,7 @@ You can handle optimistic locking errors in Java actions using similar steps to
 
 ## Handling Optimistic Locking Errors in the Client
 
-If the optimistic locking error is propagated to the client, then you will see the following error: "The data you're trying to save has already been modified by another user. Please refresh the page and try again."
+If the optimistic locking error is propagated to the client, the following error is displayed: "The data you're trying to save has already been modified by another user. Please refresh the page and try again."
 
 {{< figure src="/attachments/refguide/runtime/optimistic-locking/optimistic-locking-error-dialog.png" >}}