MicrosoftDocs · mikehoffms · Apr 9, 2024 · Apr 10, 2024 · Apr 11, 2024 · Apr 11, 2024
diff --git a/microsoft-edge/developer/index.yml b/microsoft-edge/developer/index.yml
@@ -163,7 +163,7 @@ landingContent:
  url: ../webview2/get-started/get-started.md
  - linkListType: download
  links:
- - text: Sample Code
+ - text: WebView2 sample apps
  url: ../webview2/code-samples-links.md
  - linkListType: whats-new
  links:

diff --git a/microsoft-edge/index.yml b/microsoft-edge/index.yml
@@ -287,7 +287,7 @@ conceptualContent:
  url: ./webview2/get-started/get-started.md
  itemType: get-started
 
- - text: Sample Code
+ - text: WebView2 sample apps
  url: ./webview2/code-samples-links.md
  itemType: download
 

diff --git a/microsoft-edge/toc.yml b/microsoft-edge/toc.yml
diff --git a/microsoft-edge/webview2/code-samples-links.md b/microsoft-edge/webview2/code-samples-links.md
@@ -1,5 +1,5 @@
 ---
-title: Sample apps
+title: WebView2 sample apps
 description: Sample apps for WebView2, for various frameworks or platforms including WinUI 2 (UWP), WinUI 3 (Windows App SDK), WPF, WPF with Chrome DevTools Protocol extension, WinForms, Win32/C++, and Win32 with Visual Composition.
 author: MSEdgeTeam
 ms.author: msedgedevrel
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: webview
 ms.date: 08/29/2022
 ---
-# Sample apps
+# WebView2 sample apps
 
 
 <!-- ====================================================================== -->
@@ -52,3 +52,4 @@ For some frameworks or platforms, the samples repo contains both a completed Get
 ## See also
 
 * [WebView2Samples repo](https://github.com/MicrosoftEdge/WebView2Samples#readme)
+* [WebView2 deployment samples](./samples/deployment-samples.md)
diff --git a/microsoft-edge/webview2/concepts/frames.md b/microsoft-edge/webview2/concepts/frames.md
@@ -491,7 +491,7 @@ The following features, listed in [Overview of WebView2 features and APIs](./ove
 <!-- ====================================================================== -->
 ## See also
 
-* [Call native-side code from web-side code](../how-to/hostobject.md)
+* [Interop of native and web code](../how-to/hostobject.md)
 * [Navigation events for WebView2 apps](./navigation-events.md) - valid for frames as well as webpages.
 
 **External pages:**

diff --git a/microsoft-edge/webview2/concepts/navigation-events.md b/microsoft-edge/webview2/concepts/navigation-events.md
@@ -84,7 +84,7 @@ For example code showing how to handle navigation events, see:
 * [Step 8 - Navigation events](../get-started/winforms.md#step-8---navigation-events) in _Get started with WebView2 in WinForms apps_.
 * [Step 13 - Navigation events](../get-started/win32.md#step-13---navigation-events) in _Get started with WebView2 in Win32 apps_.
 
-The WebView2 [Sample apps](../code-samples-links.md) also demonstrate handling navigation events.
+The [WebView2 sample apps](../code-samples-links.md) also demonstrate handling navigation events.
 
 
 <!-- ====================================================================== -->

diff --git a/microsoft-edge/webview2/concepts/overview-features-apis.md b/microsoft-edge/webview2/concepts/overview-features-apis.md
@@ -96,7 +96,7 @@ Common use cases for web/native interop:
 * Run a dedicated JavaScript file on the web side of an application.
 
 See also:
-* [Interop of native-side and web-side code](../how-to/communicate-btwn-web-native.md)
+* [Interop of native and web code](../how-to/communicate-btwn-web-native.md)
 * [Call web-side code from native-side code](../how-to/javascript.md)
 * [Call native-side code from web-side code](../how-to/hostobject.md)
 * [Call native-side WinRT code from web-side code](../how-to/winrt-from-js.md)
@@ -1701,7 +1701,7 @@ These APIs load, stop loading, and reload content to WebView2. The content that
 * Content from a constructed network request.
 
 See also:
-* [Working with local content in WebView2 apps](./working-with-local-content.md)
+* [Use local content in WebView2 apps](./working-with-local-content.md)
 
 ##### [.NET/C#](#tab/dotnetcsharp)
 

diff --git a/microsoft-edge/webview2/concepts/process-related-events.md b/microsoft-edge/webview2/concepts/process-related-events.md
@@ -1,5 +1,5 @@
 ---
-title: Handling process-related events in WebView2
+title: Handle process-related events in WebView2
 description: Process-related events in WebView2 and how apps can handle them for recovery and improved reliability.
 author: MSEdgeTeam
 ms.author: msedgedevrel
@@ -8,9 +8,9 @@ ms.service: microsoft-edge
 ms.subservice: webview
 ms.date: 07/13/2023
 ---
-# Handling process-related events in WebView2
+# Handle process-related events in WebView2
 
-WebView2 uses multiple processes to support the WebView2 controls in your application. Because these processes can exit during use, WebView2 provides the `CoreWebView2.ProcessFailed` and `CoreWebView2Environment.BrowserProcessExited` events for your application to react to different scenarios. Use this document to learn how to use these events to react when these scenarios occur.
+WebView2 uses multiple processes to support the WebView2 controls in your application. Because these processes can exit during use, WebView2 provides the `CoreWebView2.ProcessFailed` and `CoreWebView2Environment.BrowserProcessExited` events. Have your app use these events as follows, to react when these scenarios occur.
 
 To improve the reliability of your WebView2 application, it is recommended that your app handles at least the following events:
 * [The main browser process has exited unexpectedly](#the-main-browser-process-has-exited-unexpectedly).

diff --git a/microsoft-edge/webview2/concepts/working-with-local-content.md b/microsoft-edge/webview2/concepts/working-with-local-content.md
@@ -1,5 +1,5 @@
 ---
-title: Working with local content in WebView2 apps
+title: Use local content in WebView2 apps
 description: Ways to work with local content in WebView2 apps, including navigating to a file URL, navigating to a string, virtual host name mapping, or the WebResourceRequested event.
 author: MSEdgeTeam
 ms.author: msedgedevrel
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: webview
 ms.date: 04/10/2024
 ---
-# Working with local content in WebView2 apps
+# Use local content in WebView2 apps
 
 In addition to loading remote content, content can also be loaded locally into WebView2. There are several approaches that can be used to load local content into a WebView2 control, including: 
 * Navigating to a file URL.

diff --git a/microsoft-edge/webview2/get-started/get-started.md b/microsoft-edge/webview2/get-started/get-started.md
@@ -26,5 +26,5 @@ These articles cover how to set up your development tools and create an initial
 ## See also
 
 * [Microsoft Edge WebView2](https://developer.microsoft.com/microsoft-edge/webview2) - initial introduction to WebView2, at `developer.microsoft.com`.
-* [Sample apps](../code-samples-links.md) - framework-specific sample apps that showcase more of the WebView2 APIs than the Getting Started tutorials.
+* [WebView2 sample apps](../code-samples-links.md) - framework-specific sample apps that showcase more of the WebView2 APIs than the Getting Started tutorials.
 * [WebView2Samples repo](https://github.com/MicrosoftEdge/WebView2Samples#readme) - contains completed Visual Studio projects that result from following the steps in these Getting Started tutorials, as well as sample apps and deployment samples.
diff --git a/microsoft-edge/webview2/get-started/win32.md b/microsoft-edge/webview2/get-started/win32.md
@@ -573,6 +573,6 @@ Congratulations, you've built a Win32 app that hosts and uses the WebView2 contr
 <!-- ====================================================================== -->
 ## See also
 
-* [Sample Code for WebView2](../code-samples-links.md)
+* [WebView2 sample apps](../code-samples-links.md)
 * [Windows Runtime C++ Template Library (WRL)](/cpp/cppcx/wrl/windows-runtime-cpp-template-library-wrl?view=vs-2019&preserve-view=true)
 * [Windows Implementation Libraries (WIL)](https://github.com/Microsoft/wil) GitHub repo.
diff --git a/microsoft-edge/webview2/get-started/winui.md b/microsoft-edge/webview2/get-started/winui.md
@@ -465,7 +465,7 @@ See [WinAppSDK supports custom WebView2 environments](#winappsdk-supports-custom
 * [WebView2 API Reference](../webview2-api-reference.md)
 * [Introduction to Microsoft Edge WebView2](../index.md) - overview of features.
 * [Manage user data folders](../concepts/user-data-folder.md)
-* [Sample Code for WebView2](../code-samples-links.md) - a guide to the `WebView2Samples` repo.
+* [WebView2 sample apps](../code-samples-links.md) - a guide to the `WebView2Samples` repo.
 * [Development best practices for WebView2 appsDevelopment best practices](../concepts/developer-guide.md)
 
 developer.microsoft.com:

diff --git a/microsoft-edge/webview2/get-started/winui2.md b/microsoft-edge/webview2/get-started/winui2.md
@@ -474,7 +474,7 @@ The following classes aren't accessible in WinUI 2:
 * [WebView2 API Reference](../webview2-api-reference.md)
 * [WinUI 2 (UWP) sample app](../samples/webview2_sample_uwp.md) - steps to download, update, build, and run the WinUI 2 WebView2 sample.
 * [Manage user data folders](../concepts/user-data-folder.md)
-* [Sample Code for WebView2](../code-samples-links.md) - a guide to the `WebView2Samples` repo.
+* [WebView2 sample apps](../code-samples-links.md) - a guide to the `WebView2Samples` repo.
 * [Development best practices for WebView2 apps](../concepts/developer-guide.md)
 
 GitHub:

diff --git a/microsoft-edge/webview2/get-started/wpf.md b/microsoft-edge/webview2/get-started/wpf.md
@@ -561,7 +561,7 @@ developer.microsoft.com:
 Local pages:
 * [WPF sample app](../samples/webview2wpfbrowser.md)
 * [Manage user data folders](../concepts/user-data-folder.md)
-* [Sample Code for WebView2](../code-samples-links.md) - a guide to the `WebView2Samples` repo.
+* [WebView2 sample apps](../code-samples-links.md) - a guide to the `WebView2Samples` repo.
 * [Development best practices for WebView2 apps](../concepts/developer-guide.md)
 
 GitHub:

diff --git a/microsoft-edge/webview2/how-to/communicate-btwn-web-native.md b/microsoft-edge/webview2/how-to/communicate-btwn-web-native.md
@@ -1,5 +1,5 @@
 ---
-title: Interop of native-side and web-side code
+title: Interop of native and web code
 description: Embed web content into native applications using WebView2.
 author: MSEdgeTeam
 ms.author: msedgedevrel
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: webview
 ms.date: 2/24/2022
 ---
-# Interop of native-side and web-side code
+# Interop of native and web code
 
 The Microsoft Edge WebView2 control lets you embed web content into native applications. You can use WebView2 in different ways, depending on what you need to accomplish. This article describes how to communicate using simple messages, JavaScript code, and native objects.
 
@@ -23,7 +23,7 @@ Some common use cases include:
 
 This tutorial steps through the Sample App code to demonstrate some of the communication capabilities in WebView2. Clone the [WebView2Samples repo](https://github.com/MicrosoftEdge/WebView2Samples), open a `.sln` file in Visual Studio, build the project, and run (debug) to follow along with the steps in this article.
 
-For detailed steps about cloning the repo, see [WebView2 samples](../code-samples-links.md).
+For detailed steps about cloning the repo, see [WebView2 sample apps](../code-samples-links.md).
 
 
 <!-- ====================================================================== -->

diff --git a/microsoft-edge/webview2/how-to/customize-ui.md b/microsoft-edge/webview2/how-to/customize-ui.md
@@ -1,14 +1,14 @@
 ---
-title: Customizing the UI in WebView2 apps
-description: Customizing the UI in WebView2 apps. Add custom right-click menus (context menus) to a WebView2 app, or add and remove items from the default WebView2 context menus.
+title: Customize the UI in WebView2 apps
+description: How to add custom right-click menus (context menus) to a WebView2 app, or add and remove items from the default WebView2 context menus.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: conceptual
 ms.service: microsoft-edge
 ms.subservice: webview
 ms.date: 02/08/2022
 ---
-# Customizing the UI in WebView2 apps
+# Customize the UI in WebView2 apps
 
 <!-- presently omitted from TOC -->
 

diff --git a/microsoft-edge/webview2/samples/deployment-samples.md b/microsoft-edge/webview2/samples/deployment-samples.md
@@ -1,5 +1,5 @@
 ---
-title: Deployment samples
+title: WebView2 deployment samples
 description: Deployment samples for WebView2.
 author: MSEdgeTeam
 ms.author: msedgedevrel
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: webview
 ms.date: 07/11/2022
 ---
-# Deployment samples
+# WebView2 deployment samples
 
 These samples demonstrate how to deploy the Evergreen WebView2 Runtime with your app that uses the WebView2 control.
 
@@ -24,3 +24,4 @@ These samples demonstrate how to deploy the Evergreen WebView2 Runtime with your
 
 * [Deploying the Evergreen WebView2 Runtime](../concepts/distribution.md#deploying-the-evergreen-webview2-runtime) in _Distribute your app and the WebView2 Runtime_.
 * [WebView2Samples repo](https://github.com/MicrosoftEdge/WebView2Samples#readme)
+* [WebView2 sample apps](../code-samples-links.md)
diff --git a/microsoft-edge/webview2/samples/webview2apissample.md b/microsoft-edge/webview2/samples/webview2apissample.md
@@ -168,7 +168,7 @@ Next, you'll update the WebView2 SDK and then re-build the project.
 
 If you want to quickly see which version of the WebView2 SDK is installed in the repo's copy of the **WebView2APISample** app at GitHub, see [packages.config](https://github.com/MicrosoftEdge/WebView2Samples/blob/main/SampleApps/WebView2APISample/packages.config).
 
-The repo version of this sample has a prerelease version of the WebView2 SDK installed. Below, you'll update it to the latest prerelease version of the WebView2 SDK, or confirm that the latest SDK is installed. Using a prerelease SDK gives you access to the latest functionality.
+The repo version of this sample has a Prerelease version of the WebView2 SDK installed. Below, you'll update it to the latest Prerelease version of the WebView2 SDK, or confirm that the latest SDK is installed. Using a Prerelease SDK gives you access to the latest functionality.
 
 Examine and possibly update the installed NuGet packages, as follows: