From bb6a1bd40a37b5b11da2adf5085dfee1d906d427 Mon Sep 17 00:00:00 2001
From: Luke Latham <1622880+guardrex@users.noreply.github.com>
Date: Thu, 28 May 2020 10:26:05 -0500
Subject: [PATCH] 'inspectUri' clarification in Blazor debug topic (#18537)

---
 aspnetcore/blazor/debug.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/aspnetcore/blazor/debug.md b/aspnetcore/blazor/debug.md
index 4ae17b0402..3bd168ca07 100644
--- a/aspnetcore/blazor/debug.md
+++ b/aspnetcore/blazor/debug.md
@@ -5,7 +5,7 @@ description: Learn how to debug Blazor apps.
 monikerRange: '>= aspnetcore-3.1'
 ms.author: riande
 ms.custom: mvc
-ms.date: 05/19/2020
+ms.date: 05/28/2020
 no-loc: [Blazor, "Identity", "Let's Encrypt", Razor, SignalR]
 uid: blazor/debug
 ---
@@ -13,7 +13,7 @@ uid: blazor/debug
 
 [Daniel Roth](https://github.com/danroth27)
 
-Blazor WebAssembly apps can be debugged using the browser dev tools in Chromium-based browsers (Edge/Chrome).  Alternatively you can debug your app using Visual Studio or Visual Studio Code.
+Blazor WebAssembly apps can be debugged using the browser dev tools in Chromium-based browsers (Edge/Chrome). Alternatively, you can debug your app using Visual Studio or Visual Studio Code.
 
 Available scenarios include:
 
@@ -55,6 +55,8 @@ The `inspectUri` property:
 * Enables the IDE to detect that the app is a Blazor WebAssembly app.
 * Instructs the script debugging infrastructure to connect to the browser through Blazor's debugging proxy.
 
+The placeholder values for the WebSockets protocol (`wsProtocol`), host (`url.hostname`), port (`url.port`), and inspector URI on the launched browser (`browserInspectUri`) are provided by the framework.
+
 ## Visual Studio
 
 To debug a Blazor WebAssembly app in Visual Studio: