From 244e9c7caa7fbfdb6022b847387ffacd6aec71ad Mon Sep 17 00:00:00 2001 From: Piyush Chaudhari Date: Mon, 25 Sep 2017 21:23:12 +0530 Subject: [PATCH] #352- Unit Of Work : modified readme. --- unit-of-work/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/unit-of-work/README.md b/unit-of-work/README.md index c67c1bc02..20788279d 100644 --- a/unit-of-work/README.md +++ b/unit-of-work/README.md @@ -22,8 +22,8 @@ When a business transaction is completed all the these updates are sent as one Use the Unit Of Work pattern when * The client is asking to optimize the time taken for database transactions. -* When you want to boost the performance to get database records. -* You want reduce number of database calls. +* To send changes to database as a unit of work which ensures atomicity of the transaction. +* You want to reduce number of database calls. ## Credits