From 3a32907d1af00e6da9659fa89fc2e88426e14649 Mon Sep 17 00:00:00 2001 From: maliming Date: Fri, 10 Jul 2026 13:15:24 +0800 Subject: [PATCH] Fix subject-verb agreement in unit-of-work docs --- .../framework/architecture/domain-driven-design/unit-of-work.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/framework/architecture/domain-driven-design/unit-of-work.md b/docs/en/framework/architecture/domain-driven-design/unit-of-work.md index cfe851b249..0f50be8f66 100644 --- a/docs/en/framework/architecture/domain-driven-design/unit-of-work.md +++ b/docs/en/framework/architecture/domain-driven-design/unit-of-work.md @@ -38,7 +38,7 @@ All of these are automatically handled by the ABP. While the section above explains the UOW as it is database transaction, actually a UOW doesn't have to be transactional. By default; -* **HTTP GET** and **HTTP QUERY** requests don't start a transactional UOW. They still starts a UOW, but **doesn't create a database transaction**. +* **HTTP GET** and **HTTP QUERY** requests don't start a transactional UOW. They still start a UOW, but **don't create a database transaction**. * All other HTTP request types start a UOW with a database transaction, if database level transactions are supported by the underlying database provider. This is because they are safe HTTP methods that don't (and shouldn't) make any change in the database. You can change this behavior using the options explained below.