From 92adad62e38550ba5c192d6778652e91fe5478d4 Mon Sep 17 00:00:00 2001 From: alenros Date: Fri, 21 Dec 2018 03:39:02 +0200 Subject: [PATCH] Cleanup doc comment grammar and some debugging leftovers (#6065) --- .../Services/WebAssemblyUriHelper.cs | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/src/Components/blazor/src/Microsoft.AspNetCore.Blazor/Services/WebAssemblyUriHelper.cs b/src/Components/blazor/src/Microsoft.AspNetCore.Blazor/Services/WebAssemblyUriHelper.cs index 01c50778e5..c0c29fdfb0 100644 --- a/src/Components/blazor/src/Microsoft.AspNetCore.Blazor/Services/WebAssemblyUriHelper.cs +++ b/src/Components/blazor/src/Microsoft.AspNetCore.Blazor/Services/WebAssemblyUriHelper.cs @@ -26,8 +26,8 @@ namespace Microsoft.AspNetCore.Blazor.Services } /// - /// Called to initialize BaseURI and current URI before those values the first time. - /// Override this method to dynamically calculate the those values. + /// Called to initialize BaseURI and current URI before those values are used the first time. + /// Override this method to dynamically calculate those values. /// protected override void InitializeState() { @@ -36,14 +36,12 @@ namespace Microsoft.AspNetCore.Blazor.Services typeof(WebAssemblyUriHelper).Assembly.GetName().Name, nameof(NotifyLocationChanged)); - // As described in other comment block above, BrowserUriHelper is only for - // client -side (Mono) use, so it's OK to rely on synchrony here. + // As described in the comment block above, BrowserUriHelper is only for + // client-side (Mono) use, so it's OK to rely on synchronicity here. var baseUri = ((IJSInProcessRuntime)JSRuntime.Current).Invoke(Interop.GetBaseUri); var uri = ((IJSInProcessRuntime)JSRuntime.Current).Invoke(Interop.GetLocationHref); SetAbsoluteBaseUri(baseUri); SetAbsoluteUri(uri); - - Console.WriteLine("Initialized"); } ///