Merge pull request #16 from InteractiveAdvertisingBureau/wittjill-pat…

…ch-1

Update 2.6.md

2.6.md

@@ -749,7 +749,7 @@ There are also several subordinate objects that provide detailed data to potenti
   <tr>
     <td><code>bcat</code></td>
     <td>string array</td>
-    <td>Blocked advertiser categories using the specified category taxonomy. <br>The taxonomy to be used is defined by the <code>cattax</code> field. If no <code>cattax</code> field is supplied IAB Content Category Taxonomy 1.0 is assumed.</td>
+    <td>Blocked advertiser categories using the specified category taxonomy. <br>The taxonomy to be used is defined by the <code>cattax</code> field. If no <code>cattax</code> field is supplied IAB Content Taxonomy 1.0 is assumed.</td>
   </tr>
   <tr>
     <td><code>cattax</code></td>
@@ -3159,7 +3159,7 @@ Each of the ad serving methods has its own advantages that may be of varying imp
 
 ## 4.4 - Substitution Macros <a name="substitutionmacros"></a>
 
-The win notice and billing notice URLs and their format are defined by the bidder. For the exchange to convey certain information to the bidder (e.g., the clearing price), several substitution macros can be inserted into these URLs. Prior to calling a win or billing notice URL, the exchange will search the specified URL for any of the defined macros and replace them with the appropriate data.
+The win notice and billing notice URLs and their format are defined by the bidder. For the exchange to convey certain information to the bidder (e.g., the clearing price), several substitution macros can be inserted into these URLs. Prior to calling a win or billing notice URL, the exchange will search the specified URL for any of the defined macros and replace them with the appropriate data.<br>
 Note that the substitution is simple in the sense that wherever a legal macro is found, it will be replaced without regard for syntax correctness. Furthermore, if the source value is an optional parameter that was not specified, the macro will simply be removed (i.e., replaced with a zero-length string).
 
 These same substitution macros can also be placed in the ad markup. The exchange will perform the same data substitutions as in the aforementioned notice URLs. This occurs irrespective of whether the markup is returned on the win notice or passed in the `bid.adm` attribute of the bid response. A use case for macros in the ad markup might be when a bidder prefers to receive its win notification from the device itself. To accomplish this, the bidder would include a tracking pixel in the ad markup, the URL for which would include any of the available macros.
@@ -3225,9 +3225,9 @@ Note that OpenRTB compliance exchanges must support all macros for which data is
 
 Prior to substitution, macro data values can be encoded for security purposes using various obfuscation or encryption algorithms. This may be of particular interest for use cases where price information is carried beyond the exchange, through the publisher, and into the device browser via a tracking pixel in the markup.
 
-To specify that a particular macro is to be encoded, the suffix “:X” should be appended to the macro name, where X is a string that indicates the algorithm to be used. Algorithms choices are not defined by this specification and must be mutually agreed upon between parties. As an example, suppose that the price macro is to be encoded using Base64 and that its code is “B64”. The macro would then be written as follows:
+To specify that a particular macro is to be encoded, the suffix “`:X`” should be appended to the macro name, where X is a string that indicates the algorithm to be used. Algorithms choices are not defined by this specification and must be mutually agreed upon between parties. As an example, suppose that the price macro is to be encoded using Base64 and that its code is “`B64`”. The macro would then be written as follows:
 
-${AUCTION PRICE:B64}
+`${AUCTION PRICE:B64}`
 
 ### 4.4.1 - Notes on the macro ${AUCTION_MIN_TO_WIN} <a name="notesonmacro"></a>
 
@@ -3239,12 +3239,13 @@ Except where the value "AUDIT" applies, as above, the macro is replaced by:
   - As dictated by exchange privacy controls, e.g., if price data is not shared to bidders that did not meet the desired floor, or if the exchange supports a publisher or winning bidder election not to share price data with the other bidders.
 
 - The minimum price required to tie with the winning bid, when your bid lost to another in the auction.
-- The minimum price required to tie with the next-closest bid, or the floor if there was only one bid, when your bid won the auction
+- The minimum price required to tie with the next-closest bid, or the floor if there was only one bid, when your bid won the auction.
 
 Note, the exchange in question may not be the final decision-maker. It may propagate two or more bids into a second auction. In that case, still only one auction bid is the "winner" and the macro is replaced for all bids as above.
 
 In the following examples, assume an auction with a floor price of $0.85, and that each row is a competing bid. Note the exchange may also choose to replace the macros with the empty string for the reasons above.
 
+For a first-price auction:<br>
 
 <table>
   <tr>
@@ -3277,7 +3278,7 @@ In the following examples, assume an auction with a floor price of $0.85, and th
 </table>
 
 
-For a second-price auction (where, for the sake of the illustration, the clearing price is the second-best price plus $0.01):
+For a second-price auction (where, for the sake of the illustration, the clearing price is the second-best price plus $0.01):<br>
 
 <table>
   <tr>
@@ -3544,7 +3545,7 @@ This example builds the first and adds parameters to describe support for an exp
 
 ### 6.2.3 - Example 3 – Mobile <a name="example3mobile"></a>
 
-This example uses a device object to reflect a mobile device, and an app object to reflect a request from a mobile application .
+This example uses a device object to reflect a mobile device, and an app object to reflect a request from a mobile application.
 
 ```javascript
 {