Skip to content

Commit 08a319b

Browse files
committed
Make process distinction more explicit
1 parent a6315ad commit 08a319b

1 file changed

Lines changed: 10 additions & 8 deletions

File tree

specs/BrowserProcessExited.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -314,10 +314,11 @@ interface ICoreWebView2Environment3 : ICoreWebView2Environment2
314314

315315
/// Add an event handler for the `BrowserProcessExited` event.
316316
/// The `BrowserProcessExited` event is raised when the collection of WebView2
317-
/// Runtime processes associated to this environment terminate due to a
318-
/// browser process error or normal shutdown (for example, when all associated
319-
/// WebViews are closed), after all resources (including the user data folder)
320-
/// have been released.
317+
/// Runtime processes for the browser process of this environment terminate
318+
/// due to browser process failure or normal shutdown (for example, when all
319+
/// associated WebViews are closed), after all resources have been released
320+
/// (including the user data folder). To learn about what these processes are,
321+
/// go to [Process model](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/process-model).
321322
///
322323
/// A handler added with this method is called until removed with
323324
/// `remove_BrowserProcessExited`, even if a new browser process is bound to
@@ -403,10 +404,11 @@ namespace Microsoft.Web.WebView2.Core
403404
// ...
404405
405406
/// `BrowserProcessExited` is raised when the collection of WebView2
406-
/// Runtime processes associated to this `CoreWebView2Environment` terminate due to a
407-
/// browser process error or normal shutdown (for example, when all associated
408-
/// WebViews are closed), after all resources (including the user data folder)
409-
/// have been released.
407+
/// Runtime processes for the browser process of this `CoreWebView2Environment`
408+
/// terminate due to browser process failure or normal shutdown (for example,
409+
/// when all associated WebViews are closed), after all resources have been
410+
/// released (including the user data folder). To learn about what these processes
411+
/// are, go to [Process model](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/process-model).
410412
///
411413
/// Multiple app processes can share a browser process by creating their webviews
412414
/// from a `CoreWebView2Environment` with the same user data folder. When the entire

0 commit comments

Comments
 (0)