GitBook: [master] 11 pages modified

Author: rekrishn

SUMMARY.md

@@ -27,11 +27,9 @@
     * [Libraries](publishing/web/libraries.md)
     * [Self-hosting Libraries](publishing/web/self-hosting-libraries.md)
 * [Client-side Information](client-side-information/README.md)
-  * [Mobile](client-side-information/mobile.md)
-  * [Web](client-side-information/web/README.md)
-    * [Asynchronous Deployment](client-side-information/web/asynchronous-deployment.md)
-    * [Deploy JavaScript tags to opt in to Launch](client-side-information/web/deploy-javascript-tags-to-opt-in-to-launch.md)
-    * [Launch Object Reference](client-side-information/web/launch-object-reference.md)
+  * [Asynchronous Deployment](client-side-information/asynchronous-deployment.md)
+  * [Deploy JavaScript tags to opt in to Launch](client-side-information/deploy-javascript-tags-to-opt-in-to-launch.md)
+  * [Launch Object Reference](client-side-information/launch-object-reference.md)
 * [Administration](administration/README.md)
   * [Companies and Properties](administration/companies-and-properties.md)
   * [User Permissions](administration/user-permissions.md)

client-side-information/README.md

@@ -2,11 +2,11 @@
 
 This section contains information that is useful when managing client-side operations of Launch.
 
-* [**Launch Object Reference**](web/launch-object-reference.md)
+* [**Launch Object Reference**](launch-object-reference.md)
 
   This reference documents the \_satellite object and the things you can do with it.
 
-* [**Asynchronous Deployment of Experience Cloud JavaScript**](web/asynchronous-deployment.md)
+* [**Asynchronous Deployment of Experience Cloud JavaScript**](asynchronous-deployment.md)
 
   Performance and non-blocking deployment of the JavaScript libraries required by our products is increasingly important to Adobe Experience Cloud users. Tools like [Google PageSpeed](https://developers.google.com/speed/pagespeed/insights/) recommend that users change they way they deploy The Adobe libraries on their site. This article explains how to use the Adobe JavaScript libraries in an asynchronous fashion.
 

client-side-information/asynchronous-deployment.md

@@ -32,9 +32,9 @@ Although the goal is to display content to visitors faster, and asynchronously l
 
 ### Timing
 
-As described above, in synchronous deployments, page rendering pauses while the Launch library is loaded and executed.  This means that events that happen after the library is loaded \(Page Bottom, DOM Ready, Window Loaded, etc\) always reliably happen after the `_satellite` object is available.
+As described above, in synchronous deployments, page rendering pauses while the Launch library is loaded and executed. This means that events that happen after the library is loaded \(Page Bottom, DOM Ready, Window Loaded, etc\) always reliably happen after the `_satellite` object is available.
 
-In asynchronous deployments, the page rendering does not pause for the library to be loaded.  This means that the sequence of events is less reliable and can even vary from one browser to another and even one page load to another depending on a number of factors \(cached libraries, bandwidth, etc\).
+In asynchronous deployments, the page rendering does not pause for the library to be loaded. This means that the sequence of events is less reliable and can even vary from one browser to another and even one page load to another depending on a number of factors \(cached libraries, bandwidth, etc\).
 
 If you see things occuring out of order - or occuring in different order inconsistently - it is likely that you have some timing issues to work through.
 
@@ -46,7 +46,7 @@ Another consideration is that Launch has always provided a Page Bottom event typ
 
 ## Loading the Launch embed code asynchronously
 
-Launch provides a toggle to turn on asynchronous loading when creating an embed code when you configure an [environment](../publishing/environments.md). You can also configure asynchronous loading yourself:
+Launch provides a toggle to turn on asynchronous loading when creating an embed code when you configure an [environment](../publishing/web/environments.md). You can also configure asynchronous loading yourself:
 
 1. Add an async attribute to the `<script>` tag to load the script asynchronously.
 

client-side-information/deploy-javascript-tags-to-opt-in-to-launch.md

@@ -1,8 +1,8 @@
 # Deploy JavaScript tags to opt in to Launch
 
-The combination of the European Union [General Data Protection Regulation \(GDPR\)](https://gdpr-info.eu/art-7-gdpr/) and [ePrivacy](https://medium.com/mydata/consent-lost-gdpr-and-found-eprivacy-e85cf881ffb) legislation requires companies to be able to manage consent for their users.  Adobe customers may require visitors to opt-in before Adobe solutions execute for any given visitor. Visitors should have the ability to manage their opt-in and opt-out status.
+The combination of the European Union [General Data Protection Regulation \(GDPR\)](https://gdpr-info.eu/art-7-gdpr/) and [ePrivacy](https://medium.com/mydata/consent-lost-gdpr-and-found-eprivacy-e85cf881ffb) legislation requires companies to be able to manage consent for their users. Adobe customers may require visitors to opt-in before Adobe solutions execute for any given visitor. Visitors should have the ability to manage their opt-in and opt-out status.
 
-Adobe Experience Cloud customers require a variety of implementations of these requirements. Some use  enterprise-level consent managers and others build their own.
+Adobe Experience Cloud customers require a variety of implementations of these requirements. Some use enterprise-level consent managers and others build their own.
 
 For Launch, extension developers use extensions and the rule builder to define opt-in and opt-out solutions.
 
@@ -16,12 +16,12 @@ Integrations with consent managers \(such as OneTrust\) can set and track the co
 
 ## Analytics
 
-In the Link Tracking section of the Analytics extension's configuration settings, make sure the following are _not_ selected: 
+In the Link Tracking section of the Analytics extension's configuration settings, make sure the following are _not_ selected:
 
 * Track download links
 * Track outbound links
 
-When these settings are not selected, Launch does not fire Adobe Analytics automatically. Analytics fires only if you specifically tell it to in a rule action. Use the rule conditions to determine when and what to fire. For example, to use cookies to determine opt-in status, set a data element to read that cookie and use it as a condition in the rule to determine when to fire the Send Beacon action. 
+When these settings are not selected, Launch does not fire Adobe Analytics automatically. Analytics fires only if you specifically tell it to in a rule action. Use the rule conditions to determine when and what to fire. For example, to use cookies to determine opt-in status, set a data element to read that cookie and use it as a condition in the rule to determine when to fire the Send Beacon action.
 
 Integrations with consent managers \(such as OneTrust\) can set and track the consent cookies for customers, which can then be used in the rule builder.