From b60e5791306af1922530e78c3e072ba04ad53655 Mon Sep 17 00:00:00 2001 From: Michael Hoffman Date: Wed, 2 Oct 2024 06:21:54 -0700 Subject: [PATCH] break up "by but by" sentence --- microsoft-edge/webview2/concepts/windowed-vs-visual-hosting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/microsoft-edge/webview2/concepts/windowed-vs-visual-hosting.md b/microsoft-edge/webview2/concepts/windowed-vs-visual-hosting.md index 5863316bbb..1631a26940 100644 --- a/microsoft-edge/webview2/concepts/windowed-vs-visual-hosting.md +++ b/microsoft-edge/webview2/concepts/windowed-vs-visual-hosting.md @@ -74,7 +74,7 @@ For a list of APIs that can be used when configuring WebView2 for Windowed hosti ## Window to Visual hosting: For a similar experience as Windowed hosting, with added benefits and tradeoff -_Window-to-Visual hosting_ means that the WebView2 content is outputted to a Visual that is hosted in an HWND, rather than outputting content to a window directly or to a Visual directly. By hosting content in an HWND, Window to Visual hosting is easy to use, like Windowed hosting, but by displaying content by using a Visual, Window-to-Visual hosting avoids some DPI and input issues that can result when using Windowed hosting. +_Window-to-Visual hosting_ means that the WebView2 content is outputted to a Visual that is hosted in an HWND, rather than outputting content to a window directly or to a Visual directly. By hosting content in an HWND, Window to Visual hosting is easy to use, in the same ways as Windowed hosting. But by displaying content by using a Visual, Window-to-Visual hosting avoids some DPI and input issues that can result when using Windowed hosting. Window to Visual hosting doesn't require you to use the WebView2 Visual hosting APIs.