Proofread .md files -- fixed contractions, grammar, incorrect symbol …

…interpretation

Consent String SDK/README.md

@@ -24,5 +24,4 @@ These implementations are not supported by the IAB.
 
 - [Go](https://github.com/prebid/go-gdpr) (prebid/go-gdpr)
 - [Go](https://github.com/LiveRamp/iabconsent) (LiveRamp/iabconsent)
-- [Rust](https://github.com/cirla/gdpr_consent) (cirla/gdpr_consent)
-
+- [Rust](https://github.com/cirla/gdpr_consent) (cirla/gdpr_consent)

In-App Reference/Android/readme.md

@@ -1,7 +1,6 @@
 # Implementation Guide for Android App Publishers
 
-* Drag and drop the classes from the `cmpconsenttool` package to your project. You will have to update the copied classes `package` name to point to yours,
- update the `import` where needed and add the `CMPConsentToolActivity` to your `AndroidManifest.xml`
+* Drag and drop the classes from the `cmpconsenttool` package to your project. You will have to update the copied classes `package` name to point to yours, update the `import` where needed and add the `CMPConsentToolActivity` to your `AndroidManifest.xml`
 * Configure the consent tool by providing a set of properties encapsulated in the `CMPSettings` object. Where:
 
 	* `SubjectToGdpr`: Enum that indicates
@@ -12,7 +11,7 @@
 	* `consentString`: If this property is given, it enforces reinitialization with the given string, configured based on the `consentToolURL`. This property is optional.
 
 ```
-CMPSettings cmpSettings = new CMPSettings(SubjectToGdpr.CMPGDPREnabled, “https://consentWebPage”, null);
+CMPSettings cmpSettings = new CMPSettings(SubjectToGdpr.CMPGDPREnabled, "https://consentWebPage", null);
 ```
 
 * In order to start the `CMPConsentToolActivity`, you can call the following method:	`CMPConsentToolActivity.openCmpConsentToolView(cmpSettings, context, onCloseCallback);`
@@ -29,7 +28,7 @@ CMPSettings cmpSettings = new CMPSettings(SubjectToGdpr.CMPGDPREnabled, “https
         * `CMPGDPRDisabled`- value 0, not subject to GDPR
         * `CMPGDPREnabled` - value 1, subject to GDPR
         * `CMPGDPRUnknown` - value -1, unset
-    * CMPPresent: Boolean which indicates if a CMP implementing the `iAB` specification is present in the application. (stored in SharedPreferences under key `IABConsent_CMPPresent`)
+    * CMPPresent: Boolean which indicates if a CMP implementing the `IAB` specification is present in the application. (stored in SharedPreferences under key `IABConsent_CMPPresent`)
     * consentString: The consent string as a websafe base64-encoded string. (stored in SharedPreferences under key `IABConsent_ConsentString`)
     * purposes: String of purposes created from a subset of the decoded consentString converted to binary. (stored in SharedPreferences under key `IABConsent_ParsedPurposeConsents`)
     * vendors: String of vendors created from a subset of the decoded consentString converted to binary. (stored in SharedPreferences under key `IABConsent_ParsedVendorConsents`)

In-App Reference/Mobile In-App Reference Implementation/README.md

@@ -23,7 +23,7 @@ This produces a production build of the `cmp` script and the docs application:
 
 ## Documentation
 
-Instructions to install the CMP as well as API docs and examples are available in the `docs` 
+Instructions to install the CMP as well as the API docs and examples are available in the `docs` 
 application included with the repo.
 
 ```sh
@@ -34,6 +34,7 @@ The documentation can be viewed at:
 `http://localhost:5000/docs/`
 
 ## Development
+
 You can start a development server that will monitor changes to all CMP and docs files with:
 ```sh
 npm run dev
@@ -46,4 +47,4 @@ Development server can be accessed at:
 
 ```sh
 npm test
-```
+```

In-App Reference/iOS/readme.md

@@ -2,7 +2,7 @@
 # CMP Wrapper Implementation Guide for iOS App Publishers
 
 
-* Configure the consent tool by providing a `cosentToolURL` to `CMPConsentToolViewController`.
+* Configure the consent tool by providing a `consentToolURL` to `CMPConsentToolViewController`.
 	* `consentToolURL`: `NSURL` 
 		* It is used to create and load the request into the `WKWebView` – it is the request for the consent webpage. This property is mandatory.
 		* `cmpPresent`:`BOOL`
@@ -47,7 +47,7 @@ int purposeId = <purpose id>;
 BOOL purposeConsent = [consentToolViewController.consentToolAPI isPurposeConsentGivenFor:purposeId];
 ````
 
-* To access vendor consent for given vendorId `isVendorConsentGivenFor:` can be used. Return type is YES if consent is given else returns NO.
+* To access vendor consent for given vendorId `isVendorConsentGivenFor:` can be used. Return type is YES if consent is given, else returns NO.
 ````
 int vendorId = <vendor id>;
 BOOL vendorConsent = [consentToolViewController.consentToolAPI isVendorConsentGivenFor:vendorId];

Mobile In-App Consent APIs v1.0 Final.md

@@ -30,7 +30,7 @@
 
 # Introduction <a name="Introduction"></a>
 
-In February 2017, the IAB Europe assembled parties representing both the supply and demand sides of the digital advertising ecosystem, to work collectively on guidance and solutions to the requirements of the General Data Protection Regulation (GDPR).  That working group is known as the GDPR Implementation Working Group (GIG).  One of the sub-groups within the GIG was tasked with developing guidance on consent as a legal basis for processing personal data. Out of that effort, an additional working group was formed to develop a technical solution to the challenge of obtaining and disseminating consumer consent to the various parties relying on it as a legal basis of processing personal data.
+In February 2017, the IAB Europe assembled parties representing both the supply and demand sides of the digital advertising ecosystem, to work collectively on guidance and solutions to the requirements of the General Data Protection Regulation (GDPR). That working group is known as the GDPR Implementation Working Group (GIG). One of the sub-groups within the GIG was tasked with developing guidance on consent as a legal basis for processing personal data. Out of that effort, an additional working group was formed to develop a technical solution to the challenge of obtaining and disseminating consumer consent to the various parties relying on it as a legal basis of processing personal data.
 
 This mobile in-app specification is dependent on the following Transparency and Consent Framework;
 - [CMP JS API v1.1](https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework/blob/master/CMP%20JS%20API%20v1.1%20Final.md)
@@ -39,8 +39,8 @@ This mobile in-app specification is dependent on the following Transparency and
 
 ## About the Transparency & Consent Framework <a name="About-the-Framework"></a>
 
-The scope of the technical working group?s initiative increased to include a technical industry solution to allow website operators to:
-1.  Control the vendors they wish to allow to access their users? browsers (for setting and reading cookies) and process their personal data and disclose these choices to other parties in the online advertising ecosystem
+The scope of the technical working group's initiative increased to include a technical industry solution to allow website operators to:
+1. Control the vendors they wish to allow to access their users' browsers (for setting and reading cookies) and process their personal data and disclose these choices to other parties in the online advertising ecosystem
 2. Seek user consent under the ePrivacy Directive (for setting cookies or similar technical applications that access information on a device) and/or the GDPR in line with applicable legal requirements and signal the consent status through the online advertising ecosystem
 
 In summary, have one place to go to:
@@ -71,9 +71,9 @@ For purposes of this documentation, the following terms have the following defin
 
 * " **_CMP_** " or Consent Management Platform means a company that can read the to transmit information about which vendors and which purposes a user has consented to with vendors. The back end storage and retrieval components of a CMP is optional and also is not necessarily to be provided by the same company that surfaces the front end consent collection aspects of the CMP via a user interface to a user (although it can be the same).	
 
-* " **_Purposes_** " mean the purposes for which a controller enabled by an online publisher is using personal data collected from,or received by a third party about an end user.
+* " **_Purposes_** " mean the purposes for which a controller enabled by an online publisher is using personal data collected from, or received by a third party about an end user.
 
-* " **_Vendor_** " means a third party that a publisher is using, directly or indirectly, in connection with surfacing content to its end users that either (1) accesses an end user?s device or browser; and/or (2) collects or receives personal data about the publisher?s end users. As such, a vendor need not be a controller.
+* " **_Vendor_** " means a third party that a publisher is using, directly or indirectly, in connection with surfacing content to its end users that either (1) accesses an end user's device or browser; and/or (2) collects or receives personal data about the publisher's end users. As such, a vendor need not be a controller.
 
 ## Scope of the document and definitions <a name="Scope"></a>
 
@@ -91,7 +91,7 @@ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLI
 
 ## Disclaimer <a name="Disclaimer"></a>
 
-THE STANDARDS, THE SPECIFICATIONS, THE MEASUREMENT GUIDELINES, AND ANY OTHER MATERIALS OR SERVICES PROVIDED TO OR USED BY YOU HEREUNDER (THE "PRODUCTS AND SERVICES") ARE PROVIDED "AS IS" AND "AS AVAILABLE," AND IAB TECHNOLOGY LABORATORY, INC. ("TECH LAB") MAKES NO WARRANTY WITH RESPECT TO THE SAME AND HEREBY DISCLAIMS ANY AND ALL EXPRESS, IMPLIED, OR STATUTORY WARRANTIES, INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AVAILABILITY, ERROR-FREE OR UNINTERRUPTED OPERATION, AND ANY WARRANTIES ARISING FROM A COURSE OF DEALING, COURSE OF PERFORMANCE, OR USAGE OF TRADE.  TO THE EXTENT THAT TECH LAB MAY NOT AS A MATTER OF APPLICABLE LAW DISCLAIM ANY IMPLIED WARRANTY, THE SCOPE AND DURATION OF SUCH WARRANTY WILL BE THE MINIMUM PERMITTED UNDER SUCH LAW.  THE PRODUCTS AND SERVICES DO NOT CONSTITUTE BUSINESS OR LEGAL ADVICE.  TECH LAB DOES NOT WARRANT THAT THE PRODUCTS AND SERVICES PROVIDED TO OR USED BY YOU HEREUNDER SHALL CAUSE YOU AND/OR YOUR PRODUCTS OR SERVICES TO BE IN COMPLIANCE WITH ANY APPLICABLE LAWS, REGULATIONS, OR SELF-REGULATORY FRAMEWORKS, AND YOU ARE SOLELY RESPONSIBLE FOR COMPLIANCE WITH THE SAME.
+THE STANDARDS, THE SPECIFICATIONS, THE MEASUREMENT GUIDELINES, AND ANY OTHER MATERIALS OR SERVICES PROVIDED TO OR USED BY YOU HEREUNDER (THE "PRODUCTS AND SERVICES") ARE PROVIDED "AS IS" AND "AS AVAILABLE," AND IAB TECHNOLOGY LABORATORY, INC. ("TECH LAB") MAKES NO WARRANTY WITH RESPECT TO THE SAME AND HEREBY DISCLAIMS ANY AND ALL EXPRESS, IMPLIED, OR STATUTORY WARRANTIES, INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AVAILABILITY, ERROR-FREE OR UNINTERRUPTED OPERATION, AND ANY WARRANTIES ARISING FROM A COURSE OF DEALING, COURSE OF PERFORMANCE, OR USAGE OF TRADE. TO THE EXTENT THAT TECH LAB MAY NOT AS A MATTER OF APPLICABLE LAW DISCLAIM ANY IMPLIED WARRANTY, THE SCOPE AND DURATION OF SUCH WARRANTY WILL BE THE MINIMUM PERMITTED UNDER SUCH LAW. THE PRODUCTS AND SERVICES DO NOT CONSTITUTE BUSINESS OR LEGAL ADVICE.  TECH LAB DOES NOT WARRANT THAT THE PRODUCTS AND SERVICES PROVIDED TO OR USED BY YOU HEREUNDER SHALL CAUSE YOU AND/OR YOUR PRODUCTS OR SERVICES TO BE IN COMPLIANCE WITH ANY APPLICABLE LAWS, REGULATIONS, OR SELF-REGULATORY FRAMEWORKS, AND YOU ARE SOLELY RESPONSIBLE FOR COMPLIANCE WITH THE SAME.
 
 ## About IAB Tech Lab  <a name="About-Tech-Lab"></a>
 
@@ -161,12 +161,12 @@ Here is the list of the preferences created by the CMP:
 0 - (not subject to GDPR), 
 Nil - undetermined (default before initialization)</td>
     <td>Aligns with IAB OpenRTB GDPR Advisory. 
-Decided to be String, to have the uninitialized status. </td>
+Decided to be String, to have the uninitialized status.</td>
   </tr>
   <tr>
     <td>IABConsent_ConsentString</td>
     <td>Consent string as defined in "Cookie and vendor list format specification"</td>
-    <td>Aligns with IAB OpenRTB GDPR Advisory </td>
+    <td>Aligns with IAB OpenRTB GDPR Advisory</td>
   </tr>
   <tr>
     <td>IABConsent_ParsedPurposeConsents</td>
@@ -298,12 +298,12 @@ The preferred way to make this happen in current AdServers are macros for perfor
     <td>{gdpr}
 </td>
     <td>1 (subject to GDPR), 0 (not subject to GDPR), unset (unknown)</td>
-    <td>Aligns with IAB OpenRTB GDPR Advisory </td>
+    <td>Aligns with IAB OpenRTB GDPR Advisory</td>
   </tr>
   <tr>
     <td>{gdpr_consent}</td>
     <td>Consent string</td>
-    <td>Aligns with IAB OpenRTB GDPR Advisory </td>
+    <td>Aligns with IAB OpenRTB GDPR Advisory</td>
   </tr>
 </table>
 
@@ -348,7 +348,7 @@ At app start, before the user can access the app the GDPR consent UI should be s
 
 **Revoke / change consent:**
 
-A UI access (either in app or through settings/app (iOS)) that allows the user to revoke/change the consent using the same UI that the user was asked to provide consent in to begin with
+A UI access (either in app or through settings/app (iOS)) that allows the user to revoke/change the consent using the same UI that the user was asked to provide consent in to begin with.
 
 **Selecting purposes and access vendorlist:**
 

README.md

@@ -2,13 +2,13 @@
 
 
 # GDPR Transparency and Consent Framework
-Hosted in this repository are the technical specifications for IAB Europe Transparency and Consent Framework that will help the digital advertising industry interpret and comply with EU rules on data protection and privacy - notably the General Data Protection Regulation (GDPR) that comes into effect on May 25, 2018. 
+Hosted in this repository are the technical specifications for the IAB Europe Transparency and Consent Framework that will help the digital advertising industry interpret, and comply with EU rules on data protection and privacy - notably the General Data Protection Regulation (GDPR) that comes into effect on May 25, 2018. 
 
 #### IAB Europe Transparency and Consent Framework 
 
-In November 2017, IAB Europe and a cross-section of the publishing and advertising industry, announced a new Transparency & Consent Framework to help publishers, advertisers and technology companies comply with key elements of GDPR. The Framework will give the publishing and advertising industries a common language with which to communicate consumer consent for the delivery of relevant online advertising and content. IAB Tech Lab is charged with the technical governance of these specifications. 
+In November 2017, IAB Europe and a cross-section of the publishing, and advertising industry announced a new Transparency & Consent Framework to help publishers, advertisers, and technology companies comply with key elements of GDPR. The Framework will give the publishing, and advertising industries a common language with which to communicate consumer consent for the delivery of relevant online advertising and content. IAB Tech Lab is charged with the technical governance of these specifications. 
 
-Specifications published here support the Framework, including the following v1.1 final specifications ready for industry adoption: 
+Specifications published here support the Framework, including the following v1.1 final specifications that are ready for industry adoption: 
 * Consent Management Provider JavaScript API v1.1 Final (referred to as CMP JS API v1.1) 
 * Consent string and vendor list formats v1.1 Final
 * Mobile In-App CMP API v1.0
@@ -17,7 +17,7 @@ Specifications published here support the Framework, including the following v1.
 Upcoming final release of:
 * pubvendors.json v1.0
 
-Please submit any general feedback to [email protected] and any technical feedback to [email protected]. 
+Please submit any general feedback to [email protected], and any technical feedback to [email protected]. 
 
 #### About IAB Tech Lab  
 
@@ -39,4 +39,4 @@ GDPR Technical Working Group members provide contributions to this repository. P
 
 #### Disclaimer
 
-THE STANDARDS, THE SPECIFICATIONS, THE MEASUREMENT GUIDELINES, AND ANY OTHER MATERIALS OR SERVICES PROVIDED TO OR USED BY YOU HEREUNDER (THE “PRODUCTS AND SERVICES”) ARE PROVIDED “AS IS” AND “AS AVAILABLE,” AND IAB TECHNOLOGY LABORATORY, INC. (“TECH LAB”) MAKES NO WARRANTY WITH RESPECT TO THE SAME AND HEREBY DISCLAIMS ANY AND ALL EXPRESS, IMPLIED, OR STATUTORY WARRANTIES, INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AVAILABILITY, ERROR-FREE OR UNINTERRUPTED OPERATION, AND ANY WARRANTIES ARISING FROM A COURSE OF DEALING, COURSE OF PERFORMANCE, OR USAGE OF TRADE. TO THE EXTENT THAT TECH LAB MAY NOT AS A MATTER OF APPLICABLE LAW DISCLAIM ANY IMPLIED WARRANTY, THE SCOPE AND DURATION OF SUCH WARRANTY WILL BE THE MINIMUM PERMITTED UNDER SUCH LAW. THE PRODUCTS AND SERVICES DO NOT CONSTITUTE BUSINESS OR LEGAL ADVICE. TECH LAB DOES NOT WARRANT THAT THE PRODUCTS AND SERVICES PROVIDED TO OR USED BY YOU HEREUNDER SHALL CAUSE YOU AND/OR YOUR PRODUCTS OR SERVICES TO BE IN COMPLIANCE WITH ANY APPLICABLE LAWS, REGULATIONS, OR SELF-REGULATORY FRAMEWORKS, AND YOU ARE SOLELY RESPONSIBLE FOR COMPLIANCE WITH THE SAME, INCLUDING, BUT NOT LIMITED TO, DATA PROTECTION LAWS, SUCH AS THE PERSONAL INFORMATION PROTECTION AND ELECTRONIC DOCUMENTS ACT (CANADA), THE DATA PROTECTION DIRECTIVE (EU), THE E-PRIVACY DIRECTIVE (EU), THE GENERAL DATA PROTECTION REGULATION (EU), AND THE E-PRIVACY REGULATION (EU) AS AND WHEN THEY BECOME EFFECTIVE.
+THE STANDARDS, THE SPECIFICATIONS, THE MEASUREMENT GUIDELINES, AND ANY OTHER MATERIALS OR SERVICES PROVIDED TO OR USED BY YOU HEREUNDER (THE "PRODUCTS AND SERVICES") ARE PROVIDED "AS IS" AND "AS AVAILABLE," AND IAB TECHNOLOGY LABORATORY, INC. ("TECH LAB") MAKES NO WARRANTY WITH RESPECT TO THE SAME AND HEREBY DISCLAIMS ANY AND ALL EXPRESS, IMPLIED, OR STATUTORY WARRANTIES, INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AVAILABILITY, ERROR-FREE OR UNINTERRUPTED OPERATION, AND ANY WARRANTIES ARISING FROM A COURSE OF DEALING, COURSE OF PERFORMANCE, OR USAGE OF TRADE. TO THE EXTENT THAT TECH LAB MAY NOT AS A MATTER OF APPLICABLE LAW DISCLAIM ANY IMPLIED WARRANTY, THE SCOPE AND DURATION OF SUCH WARRANTY WILL BE THE MINIMUM PERMITTED UNDER SUCH LAW. THE PRODUCTS AND SERVICES DO NOT CONSTITUTE BUSINESS OR LEGAL ADVICE. TECH LAB DOES NOT WARRANT THAT THE PRODUCTS AND SERVICES PROVIDED TO OR USED BY YOU HEREUNDER SHALL CAUSE YOU AND/OR YOUR PRODUCTS OR SERVICES TO BE IN COMPLIANCE WITH ANY APPLICABLE LAWS, REGULATIONS, OR SELF-REGULATORY FRAMEWORKS, AND YOU ARE SOLELY RESPONSIBLE FOR COMPLIANCE WITH THE SAME, INCLUDING, BUT NOT LIMITED TO, DATA PROTECTION LAWS, SUCH AS THE PERSONAL INFORMATION PROTECTION AND ELECTRONIC DOCUMENTS ACT (CANADA), THE DATA PROTECTION DIRECTIVE (EU), THE E-PRIVACY DIRECTIVE (EU), THE GENERAL DATA PROTECTION REGULATION (EU), AND THE E-PRIVACY REGULATION (EU) AS AND WHEN THEY BECOME EFFECTIVE.