Light freshness - SQL - Service Broker 6

Author: gitName

docs/database-engine/service-broker/completing-a-conversation-in-a-single-database.md

@@ -46,9 +46,9 @@ This tutorial is divided into three lessons:
 
 | Lesson | Description |
 | --- | --- |
-| [Lesson 1: Creating the Conversation Objects](lesson-1-creating-the-conversation-objects.md) | In this lesson, you create the message types, contract, services, and queues that are required to support a basic Service Broker conversation. |
-| [Lesson 2: Beginning a Conversation and Transmitting Messages](lesson-2-beginning-a-conversation-and-transmitting-messages.md) | In this lesson, you complete a basic conversation by starting the conversation and transmitting a request message from the initiator to the target. You'll then transmit a reply message back to the initiator and end the conversation. |
-| [Lesson 3: Dropping the Conversation Objects](lesson-3-dropping-the-conversation-objects.md) | In this lesson, you drop the objects that were created to support the conversation. |
+| [Lesson 1: Create the conversation objects](lesson-1-creating-the-conversation-objects.md) | In this lesson, you create the message types, contract, services, and queues that are required to support a basic Service Broker conversation. |
+| [Lesson 2: Begin a conversation and transmit messages](lesson-2-beginning-a-conversation-and-transmitting-messages.md) | In this lesson, you complete a basic conversation by starting the conversation and transmitting a request message from the initiator to the target. You then transmit a reply message back to the initiator and end the conversation. |
+| Lesson 3: Drop the conversation objects](lesson-3-dropping-the-conversation-objects.md) | In this lesson, you drop the objects that were created to support the conversation. |
 
 ## Requirements
 

docs/database-engine/service-broker/how-to-deactivate-service-broker-message-delivery-in-databases-transact-sql.md

@@ -14,7 +14,7 @@ ms.topic: how-to
 
 [!INCLUDE [sql-asdbmi](../../includes/applies-to-version/sql-asdbmi.md)]
 
-When message delivery isn't active, messages remain in the transmission queue. To determine whether Service Broker is active for a database, check the **is_broker_enabled** column of the `sys.databases` catalog view.
+When message delivery isn't active, messages remain in the transmission queue. To determine whether Service Broker is active for a database, check the `is_broker_enabled` column of the `sys.databases` catalog view.
 
 > [!NOTE]  
 > Deactivating Service Broker prevents messages from being sent from or delivered to the database. However, this doesn't prevent messages from arriving in the instance. To prevent messages from arriving in the instance, you must remove or stop the Service Broker endpoint.

docs/database-engine/service-broker/implementing-internal-activation.md

@@ -1,10 +1,10 @@
 ---
-title: Implementing Internal Activation
+title: Implement Internal Activation
 description: "This tutorial is intended for users who are new to Service Broker, but are familiar with database concepts and Transact-SQL statements."
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: mikeray, maghan
-ms.date: 03/07/2025
+ms.date: 09/03/2025
 ms.service: sql
 ms.subservice: configuration
 ms.topic: how-to
@@ -65,16 +65,16 @@ To complete this tutorial, you should be familiar with the Transact-SQL language
 
 Your system must have the following installed:
 
-- Any supported edition of SQL Server.
+- Any supported edition of SQL Server
 
-- [SQL Server Management Studio](/ssms/).
+- [SQL Server Management Studio](/ssms/)
 
-- A supported internet browser.
+- A supported internet browser
 
-- The [!INCLUDE [sssampledbobject-md](../../includes/sssampledbobject-md.md)] sample database, which you can download from the [Microsoft SQL Server Samples and Community Projects](https://go.microsoft.com/fwlink/?LinkID=85384) home page.
+- The [!INCLUDE [sssampledbobject-md](../../includes/sssampledbobject-md.md)] sample database, which you can download from the [Microsoft SQL Server Samples and Community Projects](https://go.microsoft.com/fwlink/?LinkID=85384) home page
 
 ## Related content
 
-- [Completing a Conversation in a Single Database](completing-a-conversation-in-a-single-database.md)
-- [Completing a Conversation Between Databases](completing-a-conversation-between-databases.md)
-- [Completing a Conversation Between Instances](completing-a-conversation-between-instances.md)
+- [Complete a conversation in a single database](completing-a-conversation-in-a-single-database.md)
+- [Complete a conversation between databases](completing-a-conversation-between-databases.md)
+- [Complete a conversation between instances](completing-a-conversation-between-instances.md)

docs/database-engine/service-broker/internal-activation-context.md

@@ -4,7 +4,7 @@ description: Learn about the execution context for a stored procedure that is st
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: mikeray, maghan
-ms.date: 07/17/2025
+ms.date: 09/03/2025
 ms.service: sql
 ms.subservice: configuration
 ms.topic: conceptual
@@ -20,15 +20,15 @@ This article describes the execution context for a stored procedure that is star
 
 A queue configured for activation must also specify the user that the activation stored procedure runs as. SQL Server impersonates this user before starting the stored procedure.
 
-When the stored procedure also specifies an EXECUTE AS clause, two impersonations occur. SQL Server first impersonates the user specified for the queue and executes the stored procedure. When the stored procedure executes, the procedure impersonates the user specified in the EXECUTE AS clause of the procedure.
+When the stored procedure also specifies an `EXECUTE AS` clause, two impersonations occur. SQL Server first impersonates the user specified for the queue and executes the stored procedure. When the stored procedure executes, the procedure impersonates the user specified in the `EXECUTE AS` clause of the procedure.
 
-The user specified for a remote service binding is generally a different user from the user specified for activation. The permissions required for each user also differ. The remote service binding user doesn't need permission to read from the queue or execute stored procedures in the database, while the user specified for activation doesn't need permission to send messages to the service. For more information on user permissions, see [Identity and Access Control (Service Broker)](identity-and-access-control.md) and [Service Broker Dialog Security](service-broker-dialog-security.md).
+The user specified for a remote service binding is generally a different user from the user specified for activation. The permissions required for each user also differ. The remote service binding user doesn't need permission to read from the queue or execute stored procedures in the database, while the user specified for activation doesn't need permission to send messages to the service. For more information on user permissions, see [Identity and access control (Service Broker)](identity-and-access-control.md) and [Service Broker dialog security](service-broker-dialog-security.md).
 
 ## Session settings
 
 Service Broker executes internally activated service programs on a background session distinct from the connection that created the message. The options set for this session are the default options for the database.
 
-Within a session started by Service Broker, SQL Server writes the output of PRINT and RAISERROR statements to the SQL Server error log. Service Broker doesn't provide parameters to an activated stored procedure. Service Broker doesn't consider return values from an activated stored procedure and doesn't process result sets from an activated stored procedure.
+Within a session started by Service Broker, SQL Server writes the output of `PRINT` and `RAISERROR` statements to the SQL Server error log. Service Broker doesn't provide parameters to an activated stored procedure. Service Broker doesn't consider return values from an activated stored procedure and doesn't process result sets from an activated stored procedure.
 
 ## Transaction context
 

docs/database-engine/service-broker/lesson-1-creating-the-base-conversation-objects.md

@@ -1,10 +1,10 @@
 ---
-title: "Lesson 1: Creating the Base Conversation Objects"
+title: "Lesson 1: Create the Base Conversation Objects"
 description: "In this lesson, you learn to build all the objects that enable a database to support a conversation in the database"
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: mikeray, maghan
-ms.date: 03/07/2025
+ms.date: 09/03/2025
 ms.service: sql
 ms.subservice: configuration
 ms.topic: how-to
@@ -51,17 +51,18 @@ GO
 
 ### Create the contract
 
-Copy and paste the following code into a Query Editor window. Then, run it to create the contract for the conversation. The contract specifies that conversations that use it must send messages of the `//AWDB/InternalAct/RequestMessage` type from the initiator to the target, and messages of the `//AWDB/InternalAct/ReplyMessage` type from the target to the initiator.
+Copy and paste the following code into a Query Editor window. Then, run it to create the contract for the conversation. The contract specifies that conversations that use it must send messages of the **//AWDB/InternalAct/RequestMessage** type from the initiator to the target, and messages of the **//AWDB/InternalAct/ReplyMessage** type from the target to the initiator.
 
 ```sql
 CREATE CONTRACT [//AWDB/InternalAct/SampleContract]
-    ([//AWDB/InternalAct/RequestMessage] SENT BY INITIATOR, [//AWDB/InternalAct/ReplyMessage] SENT BY TARGET);
+    ([//AWDB/InternalAct/RequestMessage] SENT BY INITIATOR,
+    [//AWDB/InternalAct/ReplyMessage] SENT BY TARGET);
 GO
 ```
 
 ### Create the target queue and service
 
-Copy and paste the following code into a Query Editor window. Then, run it to create the queue and service that is used for the target. Because queues are referenced from the same database in a manner similar to tables and views, queue names are formatted like table or view names. The `CREATE SERVICE` statement associates the service with the `TargetQueueIntAct`. Therefore, all messages that are sent to the service are received into the `TargetQueueIntAct`. The `CREATE SERVICE` also specifies that only conversations that use the `//AWDB/InternalAct/SampleContract` created earlier can use the service as a target service.
+Copy and paste the following code into a Query Editor window, then run it to create the queue and service that's used for the target. Because queues are referenced from the same database in a manner similar to tables and views, queue names are formatted like table or view names. The `CREATE SERVICE` statement associates the service with the **TargetQueueIntAct**. Therefore, all messages that are sent to the service are received into the **TargetQueueIntAct**. The `CREATE SERVICE` also specifies that only conversations that use the **//AWDB/InternalAct/SampleContract** created earlier can use the service as a target service.
 
 ```sql
 CREATE QUEUE TargetQueueIntAct;
@@ -74,7 +75,7 @@ GO
 
 ### Create the initiator queue and service
 
-Copy and paste the following code into a Query Editor window. Then, run it to create the queue and service that is used for the initiator. Because no contract name is specified, no other services can use this service as a target service.
+Copy and paste the following code into a Query Editor window, then run it to create the queue and service that's used for the initiator. Because no contract name is specified, no other services can use this service as a target service.
 
 ```sql
 CREATE QUEUE InitiatorQueueIntAct;
@@ -89,4 +90,4 @@ GO
 You successfully configured [!INCLUDE [sssampledbobject-md](../../includes/sssampledbobject-md.md)] to support a conversation between the `//AWDB/InternalAct/InitiatorService` and the `//AWDB/InternalAct/TargetService`.
 
 > [!div class="nextstepaction"]
-> [Lesson 2: Creating an Internal Activation Procedure](lesson-2-creating-an-internal-activation-procedure.md)
+> [Lesson 2: Create an internal activation procedure](lesson-2-creating-an-internal-activation-procedure.md)