Corrected formating and spelling errors.

Author: HeinzBaumann

TCFv2/IAB Tech Lab - Consent string and vendor list formats v2.md

@@ -334,7 +334,7 @@ In order to strengthen the TCF as a standard within the industry it was decided
 
 ### Why was the disclosed vendor section made mandatory in TCF 2.3?<a name="mandatory_in_2_3"></a>
 
-To solved the abiguity issue for vendors declaring special purpose(s) we have re-introduced the disclose vendors section to declare which vendors have been disclosed through the CMP. This way there is no abiguity regarding a vendor only declaring special purposes being disclosed or not. If a vendor who declares special purpose(s) is listed in the disclosed vendor list this means that the vendor has been disclosed to the user and can operate under the declared special purpose(s).
+To resolve the ambiguity regarding vendors that declare special purpose(s), we have reintroduced the <b>Disclosed Vendors</b> section. This section allows CMPs to explicitly declare which vendors have been disclosed to the user. As a result, there is no longer any uncertainty about whether a vendor that only declares special purposes has been disclosed. If a vendor declaring special purpose(s) appears in the disclosed vendors list, it means that the vendor has been presented to the user and is permitted to operate under the declared special purpose(s).
 
 ## Creating a TC String
 

TCFv2/TCF-Implementation-Guidelines.md

@@ -93,7 +93,7 @@ If you have not yet read tech specs or policy, you can access these documents he
 All definitions in the implementation guidelines should reflect definitions provided in the Policy. 
 
 ## What changed in v2.3?<a name="changesV2_3"></a>
-The TCF v2.3 update introduces a change to resolve the ambiguity for vendors that declare special purposes. It makes the Disclosed Vendor segment mandatory for CMPs to declare the vendors they have disclosed to the user.
+The TCF v2.3 update introduces a change to resolve the ambiguity for vendors that declare special purposes. It makes the <b>Disclosed Vendor</b> segment mandatory for CMPs to declare the vendors they have disclosed to the user.
 
 ## What changed in v2.2?<a name="changesV2_2"></a>
 The TCF v2.2 update further strengthens the TCF as a standard in the industry: revised purpose names and descriptions, introduced retention periods for all purposes, removed legitimate interest for purposes 3 to 6, the introduction of data categories used in conjunction with the purposes, support for legitimate interest claim urls, adding support for localized policy urls, deprecation of the __tcfapi command "getTCData" and introducing a more robust vendor compliance program.