Light freshness - SQL - Service Broker 7

Author: gitName

docs/database-engine/service-broker/administration.md

@@ -20,12 +20,12 @@ This section describes the tasks that are involved in administering a database t
 
 | Article | Description |
 | --- | --- |
-| [Managing Service Broker Applications](managing-service-broker-applications.md) | Describes the tasks that are required to install, maintain, and uninstall Service Broker applications. |
-| [Managing Service Broker Identities](managing-service-broker-identities.md) | Describes how Service Broker identities protect against message misdirection. |
-| [Managing Queues and Messages](managing-queues-and-messages.md) | Describes how an administrator works with queues and messages. |
-| [Managing Forwarding (Service Broker)](managing-forwarding.md) | Describes administrative considerations to manage a database that provides Service Broker message forwarding. |
-| [Managing Security (Service Broker)](managing-security.md) | Describes administrative considerations to manage the security for a Service Broker application. |
-| [Managing Routing](managing-routing.md) | Describes considerations to manage routing. |
+| [Manage Service Broker applications](managing-service-broker-applications.md) | Describes the tasks that are required to install, maintain, and uninstall Service Broker applications. |
+| [Manage Service Broker identities](managing-service-broker-identities.md) | Describes how Service Broker identities protect against message misdirection. |
+| [Manage queues and messages](managing-queues-and-messages.md) | Describes how an administrator works with queues and messages. |
+| [Manage forwarding (Service Broker)](managing-forwarding.md) | Describes administrative considerations to manage a database that provides Service Broker message forwarding. |
+| [Manage security (Service Broker)](managing-security.md) | Describes administrative considerations to manage the security for a Service Broker application. |
+| [Manage routing](managing-routing.md) | Describes considerations to manage routing. |
 
 ## Related content
 

docs/database-engine/service-broker/backing-up-and-restoring-service-broker-applications.md

@@ -18,7 +18,7 @@ Backup and restore procedures for a Service Broker service are integrated with t
 
 The `msdb` database contains routes for incoming messages. Therefore, these routes aren't backed up with the database that contains the service. Service Broker endpoints and configuration for transport security are stored in the `master` database, so these objects also aren't backed up with the database that contains the service.
 
-Service Broker routing relies on a unique identifier in each database to correctly deliver messages. When restoring a backup that is intended to replace the original database, ensure that this identifier isn't changed. When restoring a copy of a database to a different location, take care to change this identifier. For more information on Service Broker database identities, see [Managing Service Broker Identities](managing-service-broker-identities.md).
+Service Broker routing relies on a unique identifier in each database to correctly deliver messages. When restoring a backup that is intended to replace the original database, ensure that this identifier isn't changed. When restoring a copy of a database to a different location, take care to change this identifier. For more information on Service Broker database identities, see [Manage Service Broker identities](managing-service-broker-identities.md).
 
 ## Related content
 

docs/database-engine/service-broker/broker-system-messages.md

@@ -59,7 +59,7 @@ Dialog timer messages are empty messages. A receive operation receives the dialo
 
 ## Related content
 
-- [How to: Retrieve Information from a Service Broker Error Message (Transact SQL)](how-to-retrieve-information-from-a-service-broker-error-message-transact-sql.md)
+- [How to: Retrieve information from a Service Broker error message (Transact SQL)](how-to-retrieve-information-from-a-service-broker-error-message-transact-sql.md)
 - [BEGIN CONVERSATION TIMER (Transact-SQL)](../../t-sql/statements/begin-conversation-timer-transact-sql.md)
 - [BEGIN DIALOG CONVERSATION (Transact-SQL)](../../t-sql/statements/begin-dialog-conversation-transact-sql.md)
 - [CREATE CONTRACT (Transact-SQL)](../../t-sql/statements/create-contract-transact-sql.md)

docs/database-engine/service-broker/building-applications-with-service-broker.md

@@ -26,7 +26,7 @@ For information on creating applications with Service Broker, see [Benefits of p
 
 The following illustration shows the interaction in an application that uses Service Broker:
 
-:::image type="content" source="media/broker03.gif" alt-text="Diagram of the relationship and flow of messages in conversations.":::
+:::image type="content" source="media/building-applications-with-service-broker/broker-message-flow.png" alt-text="Diagram of the relationship and flow of messages in conversations.":::
 
 As shown in the illustration, the `SubmitExpense`, `AcceptDenyExpense`, and `ReimbursementIssued` message types are created first. The `ProcessExpenses` contract is created based on these message types and provides a schema for having a conversation to complete an expense reimbursement task. The `ProcessExpenses` contract governs all conversations between the `ProcessExpense` service and the `SubmitExpense` service. The `ProcessExpenses` contract and the message types that it uses must exist in the databases of all services that have conversations based on this contract.
 

docs/database-engine/service-broker/certificates-and-service-broker.md

@@ -27,9 +27,9 @@ SQL Server uses certificates to verify a remote database's identity and to ident
 
 To verify a remote server's identity, SQL Server must receive information that can be decrypted with the public key in a certificate owned by a local database principal. If SQL Server can successfully decrypt the information, it means that the remote database contains the private key that corresponds to the public key in the local certificate. Once SQL Server verifies a remote database's identity, the remote database can act with the permissions of the local database principal.
 
-For transport security, each database must trust the other database. Transport security can use either certificates or Windows Authentication. For more information on transport security, see [Service Broker Transport Security](service-broker-transport-security.md).
+For transport security, each database must trust the other database. Transport security can use either certificates or Windows Authentication. For more information on transport security, see [Service Broker transport security](service-broker-transport-security.md).
 
-For dialog security, the initiator of the dialog must trust the target, and must be able to verify the identity of the target. However, the target might allow connections from initiators that don't provide identifying information. In this case, the initiators use the **public** role in the database that hosts the target service. Dialog security always uses certificates. For more information on dialog security, see [Service Broker Dialog Security](service-broker-dialog-security.md).
+For dialog security, the initiator of the dialog must trust the target, and must be able to verify the identity of the target. However, the target might allow connections from initiators that don't provide identifying information. In this case, the initiators use the **public** role in the database that hosts the target service. Dialog security always uses certificates. For more information on dialog security, see [Service Broker dialog security](service-broker-dialog-security.md).
 
 SQL Server doesn't provide automated methods for configuration of Service Broker security by means of certificates.
 
@@ -53,6 +53,6 @@ In order for SQL Server to use a certificate to begin a conversation, the certif
 
 - [CREATE CERTIFICATE (Transact-SQL)](../../t-sql/statements/create-certificate-transact-sql.md)
 - [Encryption hierarchy](../../relational-databases/security/encryption/encryption-hierarchy.md)
-- [Service Broker Communication Protocols](service-broker-communication-protocols.md)
-- [Remote Service Bindings](remote-service-bindings.md)
+- [Service Broker communication protocols](service-broker-communication-protocols.md)
+- [Remote service bindings](remote-service-bindings.md)
 - [Certificates for dialog security](certificates-for-dialog-security.md)

docs/database-engine/service-broker/certificates-for-dialog-security.md

@@ -61,4 +61,4 @@ When Service Broker itself generates a message in response to an incoming messag
 - [ALTER CERTIFICATE (Transact-SQL)](../../t-sql/statements/alter-certificate-transact-sql.md)
 - [DROP CERTIFICATE (Transact-SQL)](../../t-sql/statements/drop-certificate-transact-sql.md)
 - [Certificates and Service Broker](certificates-and-service-broker.md)
-- [Remote Service Bindings](remote-service-bindings.md)
+- [Remote service bindings](remote-service-bindings.md)

docs/database-engine/service-broker/completing-a-conversation-between-databases.md

@@ -36,10 +36,10 @@ This tutorial is divided into four lessons:
 
 | Lesson | Description |
 | --- | --- |
-| [Lesson 1: Creating the Databases](lesson-1-creating-the-databases.md) | In this lesson, you create the databases and enable the `TRUSTWORTHY` option in the initiator database. |
-| [Lesson 2: Creating the Target Conversation Objects](lesson-2-creating-the-target-conversation-objects.md) | In this lesson, you create the message types, contract, services, and queues in the target database. |
-| [Lesson 3: Creating the Initiator Conversation Objects](lesson-3-creating-the-initiator-conversation-objects.md) | In this lesson, you create the message types, contract, services, and queues in the initiator database. |
-| [Lesson 4: Beginning a Conversation and Transmitting Messages](lesson-4-beginning-a-conversation-and-transmitting-messages.md) | In this lesson, you complete a basic conversation by beginning the conversation and transmitting a request message from the initiator to the target. Then, you transmit a reply message back to the initiator and end the conversation. |
+| [Lesson 1: Create the databases](lesson-1-creating-the-databases.md) | In this lesson, you create the databases and enable the `TRUSTWORTHY` option in the initiator database. |
+| [Lesson 2: Create the target conversation objects](lesson-2-creating-the-target-conversation-objects.md) | In this lesson, you create the message types, contract, services, and queues in the target database. |
+| [Lesson 3: Create the initiator conversation objects](lesson-3-creating-the-initiator-conversation-objects.md) | In this lesson, you create the message types, contract, services, and queues in the initiator database. |
+| [Lesson 4: Begin a conversation and transmit messages](lesson-4-beginning-a-conversation-and-transmitting-messages.md) | In this lesson, you complete a basic conversation by beginning the conversation and transmitting a request message from the initiator to the target. Then, you transmit a reply message back to the initiator and end the conversation. |
 
 ## Requirements
 

docs/database-engine/service-broker/completing-a-conversation-between-instances.md

@@ -34,12 +34,12 @@ This tutorial is divided into six lessons:
 
 | Lesson | Description |
 | --- | --- |
-| [Lesson 1: Creating the Target Database](lesson-1-creating-the-target-database.md) | In this lesson, you create the target database and all the objects that don't have dependencies on the initiator database. This includes the endpoint, master key, certificate, users, message types, contract, service, and queue. |
-| [Lesson 2: Creating the Initiator Database](lesson-2-creating-the-initiator-database.md) | In this lesson, you create the initiator database and its endpoint, master key, certificate, users, routes, remote service bindings, message types, contract, service, and queue. |
-| [Lesson 3: Completing the Target Conversation Objects](lesson-3-completing-the-target-conversation-objects.md) | In this lesson, you create the target objects that have dependencies on the initiator database. This includes certificates, users, routes, and remote service bindings. |
-| [Lesson 4: Beginning the Conversation](lesson-4-beginning-the-conversation.md) | In this lesson, you start the conversation and send a request message from the initiator to the target. |
-| [Lesson 5: Receiving a Request and Sending a Reply](lesson-5-receiving-a-request-and-sending-a-reply.md) | In this lesson, you receive the request message at the target service and send a reply message back to the initiator. |
-| [Lesson 6: Receiving the Reply and Ending the Conversation](lesson-6-receiving-the-reply-and-ending-the-conversation.md) | In this lesson, you receive the reply message at the initiator service and end the conversation. |
+| [Lesson 1: Create the target database](lesson-1-creating-the-target-database.md) | In this lesson, you create the target database and all the objects that don't have dependencies on the initiator database. This includes the endpoint, master key, certificate, users, message types, contract, service, and queue. |
+| [Lesson 2: Create the initiator database](lesson-2-creating-the-initiator-database.md) | In this lesson, you create the initiator database and its endpoint, master key, certificate, users, routes, remote service bindings, message types, contract, service, and queue. |
+| [Lesson 3: Complete the target conversation objects](lesson-3-completing-the-target-conversation-objects.md) | In this lesson, you create the target objects that have dependencies on the initiator database. This includes certificates, users, routes, and remote service bindings. |
+| [Lesson 4: Begin the conversation](lesson-4-beginning-the-conversation.md) | In this lesson, you start the conversation and send a request message from the initiator to the target. |
+| [Lesson 5: Receive a request and send a reply](lesson-5-receiving-a-request-and-sending-a-reply.md) | In this lesson, you receive the request message at the target service and send a reply message back to the initiator. |
+| [Lesson 6: Receive the reply and end the conversation](lesson-6-receiving-the-reply-and-ending-the-conversation.md) | In this lesson, you receive the reply message at the initiator service and end the conversation. |
 
 ## Requirements
 

docs/database-engine/service-broker/contracts.md

@@ -28,5 +28,5 @@ For example, a contract can have message types **SubmitRequest**, **ProcessReque
 
 - [CREATE CONTRACT (Transact-SQL)](../../t-sql/statements/create-contract-transact-sql.md)
 - [DROP CONTRACT (Transact-SQL)](../../t-sql/statements/drop-contract-transact-sql.md)
-- [Message Types](message-types.md)
+- [Message types](message-types.md)
 - [Create Service Broker contracts](creating-service-broker-contracts.md)

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

@@ -27,4 +27,4 @@ All Service Broker applications communicate through conversations. Conversations
 
 ## Related content
 
-- [Logical Architecture \(Service Broker\)](logical-architecture.md)
+- [Logical architecture (Service Broker)](logical-architecture.md)