fix errors

Author: markingmyname

docs/database-engine/service-broker/conversation-priorities.md

@@ -98,6 +98,7 @@ Service Broker assigns the conversation endpoint the priority level from the con
 
    :::column-end:::
 :::row-end:::
+
 :::row:::
    :::column span="1":::
    Priority Contract
@@ -112,6 +113,7 @@ Service Broker assigns the conversation endpoint the priority level from the con
 
    :::column-end:::
 :::row-end:::
+
 :::row:::
    :::column span="1":::
    Priority Contract
@@ -126,6 +128,7 @@ Service Broker assigns the conversation endpoint the priority level from the con
 
    :::column-end:::
 :::row-end:::
+
 :::row:::
    :::column span="1":::
    Priority Contract
@@ -140,6 +143,7 @@ Service Broker assigns the conversation endpoint the priority level from the con
 
    :::column-end:::
 :::row-end:::
+
 :::row:::
    :::column span="1":::
    ANY
@@ -154,6 +158,7 @@ Service Broker assigns the conversation endpoint the priority level from the con
 
    :::column-end:::
 :::row-end:::
+
 :::row:::
    :::column span="1":::
    ANY
@@ -168,6 +173,7 @@ Service Broker assigns the conversation endpoint the priority level from the con
 
    :::column-end:::
 :::row-end:::
+
 :::row:::
    :::column span="1":::
    ANY
@@ -182,20 +188,23 @@ Service Broker assigns the conversation endpoint the priority level from the con
 
    :::column-end:::
 :::row-end:::
+
 :::row:::
-   :::column span="1":::
-   ANY
+  :::column span="1":::
+  ANY
 
-   :::column-end:::
-   :::column span="1":::
-   ANY
+  :::column-end:::
+  :::column span="1":::
+  ANY
 
-   :::column-end:::
-   :::column span="1":::
-   ANY
+  :::column-end:::
+  :::column span="1":::
+  ANY
 
-   :::column-end:::
-:::row-end:::Service Broker first looks for a priority whose specified contract, local service, and remote service matches those used by the conversation endpoint. If one is not found, Service Broker then looks for a priority with a contract and local service that matches those used by the endpoint, and where the remote service was specified as ANY. This continues for all the variations listed in the precedence table. If no match is found, the endpoint is assigned the default priority of 5.
+  :::column-end:::
+:::row-end:::
+
+Service Broker first looks for a priority whose specified contract, local service, and remote service matches those used by the conversation endpoint. If one is not found, Service Broker then looks for a priority with a contract and local service that matches those used by the endpoint, and where the remote service was specified as ANY. This continues for all the variations listed in the precedence table. If no match is found, the endpoint is assigned the default priority of 5.
 
 The Service Broker communication protocols do not transmit priority levels between conversation endpoints. Service Broker independently assigns a priority level to each endpoint. To have Service Broker assign priority levels to both the initiator and target conversation endpoints, you must ensure that both endpoints are covered by conversation priorities. If the initiator and target conversation endpoints are in separate databases, you must create conversation priorities in each database. If the initiator and target endpoints are in the same database:
 
@@ -255,9 +264,9 @@ This script specifies the priority level for the initiator conversation endpoint
 
 This script specifies the priority level for the target conversation endpoint and its associated operations:
 
-  - The RECEIVE of the **RequestMessage** from the **TargetQueue**.
+- The RECEIVE of the **RequestMessage** from the **TargetQueue**.
 
-  - The SEND of the **ReplyMessage** from the **TargetService** to the **InitiatorQueue**.
+- The SEND of the **ReplyMessage** from the **TargetService** to the **InitiatorQueue**.
 
 <!-- end list -->
 ```sql
@@ -319,6 +328,7 @@ Messages and message fragments may be sent out of priority order:
 While individual messages or message fragments may be sent out of priority order, the effects should be small when considered across many message sends.
 
 ## See also
+
 - [ALTER BROKER PRIORITY (Transact-SQL)](../../t-sql/statements/alter-broker-priority-transact-sql.md)
 - [ALTER DATABASE SET options (Transact-SQL)](../../t-sql/statements/alter-database-transact-sql-set-options.md)
 - [BEGIN DIALOG CONVERSATION (Transact-SQL)](../../t-sql/statements/begin-dialog-conversation-transact-sql.md)

docs/database-engine/service-broker/determining-the-dialog-security-type.md

@@ -58,6 +58,7 @@ The following table lists the type of dialog security for each valid combination
 
    :::column-end:::
 :::row-end:::
+
 :::row:::
    :::column span="1":::
    Service owner has a certificate
@@ -80,6 +81,7 @@ The following table lists the type of dialog security for each valid combination
 
    :::column-end:::
 :::row-end:::
+
 :::row:::
    :::column span="1":::
    Service owner does not have a certificate
@@ -99,9 +101,9 @@ The following table lists the type of dialog security for each valid combination
    :::column-end:::
    :::column span="1":::
    Dialog fails
-
-   :::column-end:::
+:::column-end:::
 :::row-end:::
+
 :::row:::
    :::column span="1":::
    Service owner does not have a certificate
@@ -123,17 +125,19 @@ The following table lists the type of dialog security for each valid combination
    Dialog fails
 
    :::column-end:::
-:::row-end:::  - Dialog fails  
-    SQL Server does not have the information required to provide the requested security. Service Broker ends the conversation and puts an error message on the queue for the initiating service.
+:::row-end:::
+
+- Dialog fails  
+  SQL Server does not have the information required to provide the requested security. Service Broker ends the conversation and puts an error message on the queue for the initiating service.
 
-  - No dialog security  
-    SQL Server does not provide dialog security for the dialog. Operations on behalf of the initiating service run as **public** in the target database. Messages are not encrypted for this dialog. Notice, however, that transport security may encrypt the message on the network.
+- No dialog security  
+  SQL Server does not provide dialog security for the dialog. Operations on behalf of the initiating service run as **public** in the target database. Messages are not encrypted for this dialog. Notice, however, that transport security may encrypt the message on the network.
 
-  - Anonymous security  
-    SQL Server uses anonymous security. Messages outside of the instance are encrypted for this dialog. Because the target service cannot verify the identity of the initiating service, operations on behalf of the initiating service run as **public** in the target database.
+- Anonymous security  
+  SQL Server uses anonymous security. Messages outside of the instance are encrypted for this dialog. Because the target service cannot verify the identity of the initiating service, operations on behalf of the initiating service run as **public** in the target database.
 
-  - Full security  
-    SQL Server uses full security. Messages outside of the instance are encrypted for this dialog. Operations on behalf of the initiating service run as the designated user in the target database.
+- Full security  
+  SQL Server uses full security. Messages outside of the instance are encrypted for this dialog. Operations on behalf of the initiating service run as the designated user in the target database.
 
 ## See also