Apply suggestions from code review

ttorble · web-flow · commit ec0d41e2d710 · 2022-04-03T10:11:25.000+01:00
diff --git a/docs/database-engine/service-broker/conversation-groups.md b/docs/database-engine/service-broker/conversation-groups.md
@@ -46,13 +46,13 @@ Service Broker manages the lifetime of the conversation group. You do not need t
 
 - Service Broker receives the first message on a new conversation started by another service. In this case, Service Broker uses the name of the service and the broker instance identifier (if one is present) to do the following:
 
-1. Locate the appropriate queue.
+   1. Locate the appropriate queue.
 
-2. Create a new conversation group and associate the conversation group with the queue.
+   2. Create a new conversation group and associate the conversation group with the queue.
 
-3. Create a new conversation handle and add the conversation handle to the new conversation group.
+   3. Create a new conversation handle and add the conversation handle to the new conversation group.
 
-4. Place the incoming message on the queue.
+   4. Place the incoming message on the queue.
 
 Service Broker adds the conversation group identifier to the metadata for the conversation that created the conversation group. Whenever Service Broker receives a message for any conversation associated with the conversation group, Service Broker adds the conversation group identifier to that message before entering the message in the queue.
 
diff --git a/docs/database-engine/service-broker/how-to-activate-service-broker-networking-transact-sql.md b/docs/database-engine/service-broker/how-to-activate-service-broker-networking-transact-sql.md
@@ -14,8 +14,12 @@ ms.date: "03/30/2022"
 
 [!INCLUDE [sql-asdbmi](../../includes/applies-to-version/sql-asdbmi.md)]
 
-Service Broker does not send or receive messages over the network by default. To activate Service Broker networking in an instance, create an endpoint for Service Broker.> [!NOTE]  
-> Creating a Service Broker endpoint causes SQL Server to accept TCP/IP connections on the port specified. Service Broker transport security allows you to require authorization for connections to the port. If the computer that runs SQL Server has a firewall enabled, the firewall configuration on that computer must allow both incoming connections for the port specified in the endpoint. For more information on Service Broker transport security, see [Service Broker Transport Security](service-broker-transport-security.md).### To activate Service Broker networking
+Service Broker does not send or receive messages over the network by default. To activate Service Broker networking in an instance, create an endpoint for Service Broker.
+
+> [!NOTE]  
+> Creating a Service Broker endpoint causes SQL Server to accept TCP/IP connections on the port specified. Service Broker transport security allows you to require authorization for connections to the port. If the computer that runs SQL Server has a firewall enabled, the firewall configuration on that computer must allow both incoming connections for the port specified in the endpoint. For more information on Service Broker transport security, see [Service Broker Transport Security](service-broker-transport-security.md).
+
+### To activate Service Broker networking
 
 - Create a Service Broker endpoint, specifying the port number and the authentication level.
 
diff --git a/docs/database-engine/service-broker/how-to-configure-initiating-services-for-anonymous-dialog-security-transact-sql.md b/docs/database-engine/service-broker/how-to-configure-initiating-services-for-anonymous-dialog-security-transact-sql.md
@@ -14,7 +14,9 @@ ms.date: "03/30/2022"
 
 [!INCLUDE [sql-asdbmi](../../includes/applies-to-version/sql-asdbmi.md)]
 
-SQL Server uses dialog security for any conversation to a service for which a remote service binding exists. If the database that hosts the target service does not contain a user that corresponds to the user that created the dialog, the dialog uses anonymous security.> [!NOTE]  
+SQL Server uses dialog security for any conversation to a service for which a remote service binding exists. If the database that hosts the target service does not contain a user that corresponds to the user that created the dialog, the dialog uses anonymous security.
+
+> [!NOTE]  
 > Only install certificates from trusted sources.
 
 ## To make sure that an initiating service uses dialog security
diff --git a/docs/database-engine/service-broker/performance.md b/docs/database-engine/service-broker/performance.md
@@ -41,6 +41,8 @@ Next, end conversations when the task completes. Service Broker maintains state
 
 Finally, keep transactions short. For example, if the conversation pattern for the service involves a large number of messages on the same conversation group, limiting the number of messages processed in each transaction may improve overall throughput.
 
-## See also[Conversation Group Locks](conversation-group-locks.md)
+## See also
+
+[Conversation Group Locks](conversation-group-locks.md)
 
 [Message Retention](message-retention.md)
diff --git a/docs/database-engine/service-broker/service-broker-dialog-security.md b/docs/database-engine/service-broker/service-broker-dialog-security.md
@@ -81,7 +81,7 @@ When Service Broker establishes a dialog between two databases, the initiating s
 The most flexible way to do this is to create a certificate and remote service binding. For more information about creating a certificate, see [CREATE CERTIFICATE (Transact-SQL)](../../t-sql/statements/create-certificate-transact-sql.md). For more information about creating a remote service binding see, [CREATE REMOTE SERVICE BINDING (Transact-SQL)](../../t-sql/statements/create-remote-service-binding-transact-sql.md).
 
 > [!NOTE]
-> If the security context is not set up correctly, messages sent on the dialog will stay in the sys.transmission_queue on the initiating service with the following error message in the transmission_status column: **The server principal '%.*ls' is not able to access the database '%.*ls' under the current security context.**
+> If the security context is not set up correctly, messages sent on the dialog will stay in the sys.transmission_queue on the initiating service with the following error message in the transmission_status column: **The server principal `'%.*ls'` is not able to access the database `'%.*ls'` under the current security context.**
 
 ## See also
 
