Small fixes and updates

Instructions/Labs/LAB[PL-400]_Lab06_Client_Scripting.md

@@ -162,28 +162,26 @@ In this task, you will upload the JavaScript file as a web resource.You will als
 
 1. Create web resource.
 
-   - Select **+ New**.
+    - Select **+ New**.
 
-   - Select **More** and then select **Web resource**.
+    - Select **More** and then select **Web resource**.
 
     ![Add web resource - screenshot](../images/L06/mod-01-client-scripting-12.png)
 
-   - Enter `Permit Form Scripts` for **Display name**.
-
-   - Enter `PermitFormScripts.js` for **Name**.
-
-   - Select **JavaScript (JS)** for **Type**.
+    - Select **Choose file**.
+
+    - Browse to the **ContosoClientScripts** folder and then to the **FormScripts** folder.
 
-   - Select **Choose file**.
-
-     ![New web resource form - screenshot](../images/L06/new-web-resource.png)
+    - Select the **PermitFormFunctions.js** file and select **Open**.
 
-   - Browse to the **ContosoClientScripts** folder and then to the **FormScripts** folder.
+     ![Select file - screenshot](../images/L06/mod-01-client-scripting-14.png)
 
-   - Select the **PermitFormFunctions.js** file and select **Open**.
+   - Enter `Permit Form Scripts` for **Display name**.
 
-     ![Select file - screenshot](../images/L06/mod-01-client-scripting-14.png)
+   - Enter `PermitFormScripts.js` for **Name**.
 
+     ![New web resource form - screenshot](../images/L06/new-web-resource.png)
+
    - Select **Save**.
 
 1. Add the JavaScript library to the Permit main form.
@@ -730,7 +728,6 @@ In this task, you will create a custom API that will be called to lock the permi
       - `Canceled Inspections Count` for *Display name*.
       - `Canceled Inspections Count` for *Description*.
    - Select **Integer** for *Type*.
-   - Select **Save & Close**.
 
      ![Process arguments - screenshot](../images/L06/mod-01-client-scripting-80.png)
 
@@ -758,6 +755,7 @@ In this task, you will create the logic to invoke that will call the custom API.
 
       ```javascript
       _lockPermitRequest : function (permitID, reason) {
+         "use strict";
 
       },
       ```
@@ -804,6 +802,7 @@ In this task, you will create the logic to invoke that will call the custom API.
 
       ```javascript
       lockPermit: function (primaryControl) {
+         "use strict";
 
       },
       ```

Instructions/Labs/LAB[PL-400]_Lab07_PCF.md

@@ -696,7 +696,7 @@ In this task, you will use the **css** resource you configured to change the col
 
      ![Add existing custom control - screenshot](../images/L07/mod-02-pcf-1-79.png)
 
-   - Select **contoso_contoso_timelinecontrol**.
+   - Select **contoso_contoso.timelinecontrol**.
 
      ![Select control - screenshot](../images/L07/mod-02-pcf-1-80.png)
 

Instructions/Labs/LAB[PL-400]_Lab08_Plugins.md

@@ -663,7 +663,7 @@ Complete source code files for this lab can be found in the  C:\Labfiles\L08\Res
 
    - Provide **Name** as `Test Permit Two`.
 
-   - Select **New Construction** for Permit Type, **One Microsoft Way** for Build Site, and **Jon Doe** for **Contact**.
+   - Select **New Construction** for Permit Type, **One Microsoft Way** for Build Site, and **John Doe** for **Contact**.
 
    - Select today's date for the Start Date.
 

Instructions/Labs/LAB[PL-400]_Lab09_Azure.md

@@ -10,7 +10,7 @@ lab:
 
 This lab focuses on both inbound and outbound integration with Azure. In this lab you will:
 
-1) Use the event publishing capability of Microsoft Dataverse. When a permit results in changing the size of the build site, an external taxing authority needs to be notified so they can evaluate if additional taxing is required. You will configure Microsoft Dataverse to publish permits with size changes using the Webhook. To simulate the taxing authority receiving the information you will create a simple Azure function to receive the post.
+1. Use the event publishing capability of Microsoft Dataverse. When a permit results in changing the size of the build site, an external taxing authority needs to be notified so they can evaluate if additional taxing is required. You will configure Microsoft Dataverse to publish permits with size changes using the Webhook. To simulate the taxing authority receiving the information you will create a simple Azure function to receive the post.
 
 1. Build a custom connector that can be used from Power Apps and Power Automate. Custom connectors describe existing APIs and allow them to be used easily. In this lab, you will build an API that has common calculations used by inspectors so that they can be used by applications. After building the API, you will create a custom connector definition to make it available to Power Apps and Power Automate.
 
@@ -224,6 +224,8 @@ As part of configuring the event publishing, you will complete the following:
 
    - Select the **PL400** for resource group.
 
+   - Ensure the **Region** is set to **East US 2**.
+
    - Enter `pl400sa` followed by a unique number for Storage account name.
 
      > Note: Storage account name must be unique across Azure.
@@ -264,14 +266,14 @@ As part of configuring the event publishing, you will complete the following:
 
    - Select the **PL400** for resource group.
 
-   - Enter `pl400wh` followed by your initials and a unique number for Function App name.
-
-     > Note: Function app name must be unique across Azure. Wait until you see a green tick to confirm the name is unique.
+   - Enter `pl400wh` for Function App name.
 
    - Select **.NET** for Runtime stack
 
    - Select **8 (LTS), in-process model** for Version
 
+   - Ensure the **Region** is set to **East US 2**.
+
    - Select **Next : Storage**.
 
    - Select the storage account you created in the previous task.
@@ -320,15 +322,15 @@ As part of configuring the event publishing, you will complete the following:
 
    - Select **Run**.
 
-   - You should see **Hello, Azure** in the output.
+   - You should see the following output.
 
      ![Function output - screenshot](../images/L09/Mod_01_Web_Hook_image10.png)
 
    - Close the test pane.
 
 1. Edit the function
 
-   - Replace the entire Task method with the method below.
+   - Replace the entire **Run** method with the method below.
 
      ```csharp
      public static async void Run(HttpRequest req, ILogger log)
@@ -413,7 +415,7 @@ As part of configuring the event publishing, you will complete the following:
 
    - Select **Login**.
 
-   - Select the Dev One environment and select **Login**.
+   - Select the **Dev One** environment and select **Login**.
 
 1. Register webhook.
 
@@ -1014,6 +1016,19 @@ As part of configuring the custom connector, you will complete the following
 
       ![Reposition button - screenshot](../images/L09/Mod_2_Custom_Connector_image54.png)
 
+1. Add another button.
+   - Select **+ Insert** tab.
+
+   - Select Button 
+
+   - Select **Tree view** tab.
+
+   - Rename button to `Back Button`
+
+   - Change the **Text** value of the button to `"Back"`.
+
+   - Change the **OnSelect** value to `Back()`.
+
 1. Add the result label to the screen
 
    - Select **+ Insert** tab.
@@ -1100,12 +1115,8 @@ As part of configuring the custom connector, you will complete the following
 
    - The CPM Calc screen should load.
 
-     ![Calculator page - screenshot](../images/L09/Mod_2_Custom_Connector_image63.png)
-
    - Enter values into the four fields and select **Submit**. You can notice the loading dots on top of the screen, which confirms that the request has been initiated.
 
-     ![Submit form - screenshot](../images/L09/Mod_2_Custom_Connector_image64.png)
-
    - The **Result Label** should show the calculated result from the Custom Connector.
 
      ![Calculation result - screenshot](../images/L09/Mod_2_Custom_Connector_image65.png)