Fix em-dash usage

Author: Rob-Barefoot

learn-pr/wwl-azure/guided-project-build-basic-website-endpoint-with-functions/includes/1-introduction.md

@@ -4,7 +4,7 @@ Azure Functions is a serverless compute service that lets you run code in respon
 
 ## Scenario
 
-Your team needs a lightweight endpoint for a contact page without maintaining servers. You create a Function App, deploy an HTTP-triggered function using Cloud Shell, and then test, secure, and monitor the endpoint — all in one session.
+Your team needs a lightweight endpoint for a contact page without maintaining servers. You create a Function App, deploy an HTTP-triggered function using Cloud Shell, and then test, secure, and monitor the endpoint—all in one session.
 
 - Exercise 1 - Create a Function App with the serverless Flex Consumption plan.
 - Exercise 2 - Deploy an HTTP-trigger function from Cloud Shell.

learn-pr/wwl-azure/guided-project-build-basic-website-endpoint-with-functions/includes/2-exercise-create-function-app.md

@@ -48,7 +48,7 @@ Set up the Function App with serverless hosting. The Flex Consumption plan ensur
 > **Validation step:** Verify you selected all required settings before deployment: resource group, runtime stack (Node.js), region, and Flex Consumption hosting plan.
 
 > [!NOTE]
-> Each exercise includes validation steps like this one. Track your results as you go — you'll review them all in the validation unit at the end of this module.
+> Each exercise includes validation steps like this one. Track your results as you go—you'll review them all in the validation unit at the end of this module.
 
 ## Task 3: Verify the deployment
 

learn-pr/wwl-azure/guided-project-build-basic-website-endpoint-with-functions/includes/4-exercise-test-endpoint-logs.md

@@ -43,13 +43,13 @@ Confirm the deployed function appears in the Azure portal alongside the Function
 
 ## Task 3: Enable Application Insights
 
-When you created the Function App, you skipped past the Monitoring tab and accepted the defaults. Now that you want to track invocations, you need to enable Application Insights. This is a common pattern in Azure — you can add monitoring after the fact without recreating your resources.
+When you created the Function App, you skipped past the Monitoring tab and accepted the defaults. Now that you want to track invocations, you need to enable Application Insights. This is a common pattern in Azure—you can add monitoring after the fact without recreating your resources.
 
 1.  Select **GetStatus** from the function list.
 2.  In the top menu, select **Invocations**.
 3.  The page displays a message that Application Insights is not configured. Select the **Configure Application Insights** button.
 4.  On the Application Insights configuration page, select **Turn on Application Insights**.
-5.  Before selecting **Apply**, note the **Log Analytics Workspace** name and location shown on the page. Write down the last four characters of the workspace name and the location — you need this information during cleanup.
+5.  Before selecting **Apply**, note the **Log Analytics Workspace** name and location shown on the page. Write down the last four characters of the workspace name and the location—you need this information during cleanup.
 6.  Select **Apply**. When the **Apply monitoring settings** dialog appears noting the site will be restarted, select **Yes**. Wait for the configuration to complete.
 7.  Refresh the portal page (press **F5**) so the portal picks up the new Application Insights configuration.
 

learn-pr/wwl-azure/guided-project-build-basic-website-endpoint-with-functions/includes/6-clean-up-resources.md

@@ -27,7 +27,7 @@ When you enabled Application Insights, Azure created a Log Analytics workspace i
     - If the resource group contains other resources, delete only the Log Analytics workspace that matches your noted name. Select the workspace, select **Delete**, and confirm.
 
 > [!WARNING]
-> Do not delete a Log Analytics workspace used by other services in your subscription — doing so would break monitoring for those services.
+> Do not delete a Log Analytics workspace used by other services in your subscription—doing so would break monitoring for those services.
 
 ### Clean up Cloud Shell files