Merge pull request #1740 from MicrosoftDocs/master

Pushing changes live

Author: KumarVivek

powerapps-docs/developer/common-data-service/walkthrough-registering-configuring-simplespa-application-adal-js.md

@@ -179,7 +179,7 @@ Finally, you can click on **Logout** button to logout.
        retrievingAccountsMessage.textContent = "Retrieving 10 accounts from " + organizationURI + "/api/data/v9.1/accounts";  
        message.appendChild(retrievingAccountsMessage)  
   
-       // Function to perform operation is passed as a parameter to the aquireToken method  
+       // Function to perform operation is passed as a parameter to the acquireToken method  
        authContext.acquireToken(organizationURI, retrieveAccounts)  
   
       }  

powerapps-docs/developer/common-data-service/webapi/enhanced-quick-start.md

@@ -185,7 +185,7 @@ These helpers are also used in the [SampleHelper.cs](https://github.com/Microsof
     > [!NOTE]
     > Do not add this within the `SampleHelpers` class itself.
 
-    This class ensures that the access token is refreshed each time an operation is performed. Each access token will expire after about an hour. This class implements a <xref:System.Net.Http.DelegatingHandler> that will work with the Azure Active Directory Authentication Library (ADAL) authentication context to call the `AquireToken` method everytime an operation is performed so you don't need to explicitly manage token expiration.
+    This class ensures that the access token is refreshed each time an operation is performed. Each access token will expire after about an hour. This class implements a <xref:System.Net.Http.DelegatingHandler> that will work with the Azure Active Directory Authentication Library (ADAL) authentication context to call the `AcquireToken` method everytime an operation is performed so you don't need to explicitly manage token expiration.
 
     ```csharp
     /// <summary>

powerapps-docs/developer/component-framework/import-custom-controls.md

@@ -22,7 +22,7 @@ Follow the steps below to create and import a solution file:
    > The `publisherName` and `cutomizationPrefix` values must be unique to your environment.
  
 2. Once the new solution project is created, you need to refer to the ___location where the created control is located. You can add the reference by using the command
-`pac solution add-reference --<path of your PowerApps component framework project on disk>`
+`pac solution add-reference --path <path of your PowerApps component framework project on disk>`
 3. To generate a zip file from your solution project, you will need to `cd` into your solution project directory and build the project using the command `msbuild/t:restore` and `msbuild`
 
     > [!NOTE]
@@ -62,4 +62,4 @@ If you would like to remove a custom component from a solution, follow the steps
 
 [Add Controls to entities or fields](add-custom-controls-to-a-field-or-entity.md)<br/>
 [PowerApps component framework API Reference](reference/index.md)<br/>
-[PowerApps component framework Overview](overview.md)
+[PowerApps component framework Overview](overview.md)

powerapps-docs/maker/canvas-apps/performance-tips.md

@@ -7,7 +7,7 @@ ms.service: powerapps
 ms.topic: conceptual
 ms.custom: canvas
 ms.reviewer: anneta
-ms.date: 08/31/2018
+ms.date: 06/17/2019
 ms.author: yingchin
 search.audienceType: 
   - maker
@@ -84,10 +84,11 @@ Contact information doesn’t change frequently, and neither do default values a
 technique with the **Defaults** and **User** functions also. 
 
 ## Avoid controls dependency between screens
-If a control’s value depends on the value of a control on a different screen, manage the data by using a variable, a collection, or a data-source reference.
+To improve performance, the screens of an app are loaded into memory only as they are needed. This optimization can be hampered if, for example, screen 1 is loaded and one of its formulas uses a property of a control from screen 2. Now screen 2 must be loaded to fulfill the dependency before screen 1 can be displayed. Imagine screen 2 has a dependency on screen 3, which has another dependency on screen 4, and so on. This dependency chain can cause many screens to be loaded.
 
-## Use global variables
-To pass the app’s state from one screen to another, create or modify a global variable value by using the [**Set**](functions/function-set.md) function instead of by using the **Navigate** and **UpdateContext)** functions.
+For this reason avoid formula dependencies between screens. In some cases you can use a global variable or collection to share information between screens.
+
+There is an exception. In the previous example imagine that the only way to display screen 1 is by navigating from screen 2. Then screen 2 would have already been loaded in memory when screen 1 was to be loaded. No additional work is needed to fulfill the dependency for screen 2 and therefore there's no performance impact.
 
 ## Use delegation
 Where possible, use functions that delegate data processing to the data source instead of retrieving data to the local device for processing. If an app must process data locally, the operation requires much more processing power, memory, and network bandwidth, especially if the data set is large.