Skip to content

Commit 0fb1157

Browse files
committed
Don't use backticks for WebView2 Runtime
1 parent cb5e506 commit 0fb1157

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

specs/BrowserProcessExited.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# Background
2-
We have heard asks for a WebView2 API to easily track the `WebView2 Runtime`'s
2+
We have heard asks for a WebView2 API to easily track the WebView2 Runtime's
33
browser process exit. Manually waiting for the process to exit requires
44
additional work on the host app, so we are proposing the `BrowserProcessExited`
55
event. The `ProcessFailed` already lets app developers handle unexpected browser
@@ -11,10 +11,10 @@ document we describe the new API. We'd appreciate your feedback.
1111

1212
# Description
1313
The `BrowserProcessExited` event allows developers to subscribe event handlers
14-
to be run when the `WebView2 Runtime`'s browser process associated to a
14+
to be run when the WebView2 Runtime's browser process associated to a
1515
`CoreWebView2Environment` terminates. Key scenarios are cleanup of the use data
16-
folder used by the `WebView2 Runtime`, which is locked while the runtime's
17-
browser process is active, and moving to a new `WebView2 Runtime` version after
16+
folder used by the WebView2 Runtime, which is locked while the runtime's
17+
browser process is active, and moving to a new WebView2 Runtime version after
1818
a `NewBrowserVersionAvailable` event.
1919

2020
This event is raised for both expected and unexpected browser process
@@ -261,7 +261,7 @@ namespace Microsoft.Web.WebView2.Core
261261
// ...
262262
263263
/// `BrowserProcessExited` is raised when the browser process of the
264-
/// `WebView2 Runtime` associated to this `CoreWebView2Environment`
264+
/// WebView2 Runtime associated to this `CoreWebView2Environment`
265265
/// terminates due to an error or normal shutdown (e.g., when all its
266266
/// WebViews are closed), after all resources (including the user data
267267
/// folder) used by the browser process (and related processes) have
@@ -299,7 +299,7 @@ namespace Microsoft.Web.WebView2.Core
299299

300300
# Appendix
301301
We expect that for the two scenarios this API is designed for, namely cleanup of
302-
the user data folder and upgrading the `WebView2 Runtime`, an app adding a
302+
the user data folder and upgrading the WebView2 Runtime, an app adding a
303303
handler for `BrowserProcessExited` will only be interested in the next single
304304
time the browser process exits (even if there could be more browser processes
305305
being created and exiting throughout the lifetime of a

0 commit comments

Comments
 (0)