Skip to content

Commit e5db55e

Browse files
authored
Update concurrency.md (#4378)
Fixed a spelling error.
1 parent dbbe2d7 commit e5db55e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

entity-framework/core/saving/concurrency.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ Regardless of how your concurrency token is set up, to implement optimistic conc
137137

138138
One option is to simply inform the user that the update failed due to conflicting changes; the user can then load the new data and try again. Or if your application is performing an automated update, it can simply loop and retry immediately, after re-querying the data.
139139

140-
A more sophisticated way to resolve concurrency conflilcts is to *merge* the pending changes with the new values in the database. The precise details of which values get merged depend on the application, and the process may be directed by a user interface, where both sets of values are displayed.
140+
A more sophisticated way to resolve concurrency conflicts is to *merge* the pending changes with the new values in the database. The precise details of which values get merged depend on the application, and the process may be directed by a user interface, where both sets of values are displayed.
141141

142142
There are three sets of values available to help resolve a concurrency conflict:
143143

0 commit comments

Comments
 (0)