more code blocks

Author: markingmyname

docs/database-engine/service-broker/handling-poison-messages.md

@@ -36,13 +36,11 @@ Consider the following questions when you decide how the application handles a p
 
 ## Example: Detecting a Poison Message
 
-
-
 This Transact-SQL example shows a simple, stateless service that includes logic for handling poison messages. Before the stored procedure receives a message, the procedure saves the transaction. When the procedure cannot process a message, the procedure rolls the transaction back to the save point. The partial rollback returns the message to the queue while continuing to hold a lock on the conversation group for the message. Because the program continues to hold the conversation group lock, the program can update a table that maintains a list of failed messages without risk that another queue reader might process the message.
 
 The following example defines the activation stored procedure for the application:
 
-```
+```sql
     CREATE PROCEDURE ProcessExpenseReport
     AS
     BEGIN
@@ -116,7 +114,7 @@ The following example defines the activation stored procedure for the applicatio
 
 The stored procedure TrackMessage tracks the number of times that a message has failed. When the message has not failed before, the procedure inserts a new counter for the message into the table ExpenseServiceFailedMessages. Otherwise, the procedure checks the counter for the number of times that the message failed. The procedure increments the counter when the counter is less than a predefined number. When the counter is greater than the predefined number, the procedure ends the conversation with an error and removes the counter for the conversation from the table.
 
-```
+```sql
     CREATE PROCEDURE TrackMessage
     @conversationHandle uniqueidentifier
     AS
@@ -154,7 +152,7 @@ The stored procedure TrackMessage tracks the number of times that a message has
 
 The definition of table ExpenseServiceFailedMessages simply contains a conversation_handle column and a count column, as shown in the following sample:
 
-```
+```sql
     CREATE TABLE ExpenseServiceFailedMessages (
       conversation_handle uniqueidentifier PRIMARY KEY,
       count smallint
@@ -163,7 +161,7 @@ The definition of table ExpenseServiceFailedMessages simply contains a conversat
 
 The procedure ClearMessageTracking deletes the counter for a conversation from the table ExpenseServiceFailedMessages, as shown in the following sample:
 
-```
+```sql
     CREATE PROCEDURE ClearMessageTracking
       @conversationHandle uniqueidentifier
     AS
@@ -196,5 +194,4 @@ If you believe that the processing you perform on the message might cause a tran
 
 #### Other Resources
 
-[Understanding Database Engine Errors](../../relational-databases/errors-events/understanding-database-engine-errors.md)
-
+[Understanding Database Engine Errors](../../relational-databases/errors-events/understanding-database-engine-errors.md)