Merge pull request #21091 from HamzaSallakh/dev

change the is satisfied and to expression examples

docs/en/framework/architecture/domain-driven-design/specifications.md

@@ -81,7 +81,7 @@ namespace MyProject
 {
     public class CustomerService : ITransientDependency
     {
-        public async Task BuyAlcohol(Customer customer)
+        public async Task BookRoom(Customer customer)
         {
             if (!new Age18PlusCustomerSpecification().IsSatisfiedBy(customer))
             {
@@ -120,7 +120,7 @@ namespace MyProject
             _customerRepository = customerRepository;
         }
 
-        public async Task<List<Customer>> GetCustomersCanBuyAlcohol()
+        public async Task<List<Customer>> GetCustomersCanBookRoom()
         {
             var queryable = await _customerRepository.GetQueryableAsync();
             var query = queryable.Where(
@@ -254,4 +254,4 @@ Some benefits of using specifications:
 ### When To Not Use?
 
 - **Non business expressions**: Do not use specifications for non business-related expressions and operations.
-- **Reporting**: If you are just creating a report, do not create specifications, but directly use `IQueryable` & LINQ expressions. You can even use plain SQL, views or another tool for reporting. DDD does not necessarily care about reporting, so the way you query the underlying data store can be important from a performance perspective.
+- **Reporting**: If you are just creating a report, do not create specifications, but directly use `IQueryable` & LINQ expressions. You can even use plain SQL, views or another tool for reporting. DDD does not necessarily care about reporting, so the way you query the underlying data store can be important from a performance perspective.