Updated links for Native to point to GitHub

Thanks robhazan!!!!!

Author: hillslatt

2.6.md

@@ -763,14 +763,14 @@ The presence of a `Audio` as a subordinate of the `Imp` object indicates that th
 
 This object represents a native type impression. Native ad units are intended to blend seamlessly into the surrounding content (e.g., a sponsored Twitter or Facebook post). As such, the response must be well-structured to afford the publisher fine-grained control over rendering.
 
-The Native Subcommittee has developed a companion specification to OpenRTB called the <a href="https://iabtechlab.com/standards/openrtb-native/">Dynamic Native Ads API</a>. It defines the request parameters and response markup structure of native ad units. This object provides the means of transporting request parameters as an opaque string so that the specific parameters can evolve separately under the auspices of the Dynamic Native Ads API. Similarly, the ad markup served will be structured according to that specification.
+The Native Subcommittee has developed a companion specification to OpenRTB called the [Dynamic Native Ads API](https://github.com/InteractiveAdvertisingBureau/Native-Ads). It defines the request parameters and response markup structure of native ad units. This object provides the means of transporting request parameters as an opaque string so that the specific parameters can evolve separately under the auspices of the Dynamic Native Ads API. Similarly, the ad markup served will be structured according to that specification.
 
 The presence of a `Native` as a subordinate of the `Imp` object indicates that this impression is offered as a native type impression. At the publisher’s discretion, that same impression may also be offered as `Banner`, `Video`, and/or `Audio` by also including as `Imp` subordinates objects of those types. However, any given bid for the impression must conform to one of the offered types.
 
 
 | Attribute | Type | Description |
 | --- | --- | --- |
-| `request` | string; required | Request payload complying with the [Native Ad Specification](https://iabtechlab.com/standards/openrtb-native/). The root node of the payload, "native", was dropped in the Native Ads Specification 1.1.<br>For Native 1.0, this is a JSON-encoded string consisting of a unnamed root object, with a single subordinate object named 'native', which is the Native Markup Request object, section 4.1 of OpenRTB Native 1.0 specification.<br>For Native 1.1 and higher, this is a JSON-encoded string consisting of an unnamed root object which is itself the Native Markup Request Object, section 4.1 of OpenRTB Native 1.1+ . |
+| `request` | string; required | Request payload complying with the [Native Ad Specification](https://github.com/InteractiveAdvertisingBureau/Native-Ads). The root node of the payload, "native", was dropped in the Native Ads Specification 1.1.<br>For Native 1.0, this is a JSON-encoded string consisting of a unnamed root object, with a single subordinate object named 'native', which is the Native Markup Request object, section 4.1 of OpenRTB Native 1.0 specification.<br>For Native 1.1 and higher, this is a JSON-encoded string consisting of an unnamed root object which is itself the Native Markup Request Object, section 4.1 of OpenRTB Native 1.1+ . |
 | `ver` | string; recommended | Version of the Dynamic Native Ads API to which `request` complies; highly recommended for efficient parsing. |
 | `api` | integer array | List of supported API frameworks for this impression. Refer to [List: API Frameworks](https://github.com/InteractiveAdvertisingBureau/AdCOM/blob/master/AdCOM%20v1.0%20FINAL.md#list--api-frameworks-) in AdCOM. If an API is not explicitly listed, it is assumed not to be supported. |
 | `battr` | integer array | Blocked creative attributes. Refer to [List: Creative Attributes](https://github.com/InteractiveAdvertisingBureau/AdCOM/blob/master/AdCOM%20v1.0%20FINAL.md#list--creative-attributes-) in AdCOM. |
@@ -1918,7 +1918,7 @@ Following is a basic example of a bid request for a banner ad with a direct deal
 
 ### 6.2.6 - Example 6 – Native Ad <a name="example6nativead"></a>
 
-For details on Native Ad implementation including examples, please review the OpenRTB Native Ads API Specification: https://iabtechlab.com/standards/openrtb-native/
+For details on Native Ad implementation including examples, please review the OpenRTB Native Ads API Specification: https://github.com/InteractiveAdvertisingBureau/Native-Ads
 
 
 ## 6.3 - Bid Responses <a name="6.5bidresponses"></a>