Fix content.

dotnet · Dec 2, 2024 · e0efe31 · e0efe31
1 parent b8ff4e4
commit e0efe31
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 7 deletions.
diff --git a/docs/user-interface/controls/blazorwebview.md b/docs/user-interface/controls/blazorwebview.md
@@ -235,14 +235,14 @@ AppContext.SetSwitch("BlazorWebView.AndroidFireAndForgetAsync", false);
 
 If your app is configured to block on dispose via this switch, <xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> performs async-over-sync disposal, which means that it blocks the thread until the async disposal is complete. However, this can cause deadlocks if the disposal needs to run code on the same thread (because the thread is blocked while waiting).
 
-## Host content using the legacy behavior on iOS and Mac Catalyst
+## Host content using the legacy behavior
 
-On iOS and Mac Catalyst 18, the default behavior for hosting content in a <xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> has changed to `localhost`. The internal `0.0.0.1` address used to host content no longer works and results in the <xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> not loading any content and rendering as an empty rectangle.
+The default behavior for hosting content in a <xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> has changed to `0.0.0.1`. The internal `0.0.0.0` address used to host content no longer works and results in the <xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> not loading any content and rendering as an empty rectangle.
 
-To opt into using the `0.0.0.1` address, add the following code to the `CreateMauiApp` method in *MauiProgram.cs*:
+To opt into using the `0.0.0.0` address, add the following code to the `CreateMauiApp` method in *MauiProgram.cs*:
 
 ```csharp
-// Set this switch to use the LEGACY behavior of always using 0.0.0.1 to host BlazorWebView
+// Set this switch to use the LEGACY behavior of always using 0.0.0.0 to host BlazorWebView
 AppContext.SetSwitch("BlazorWebView.AppHostAddressAlways0000", true);
 ```
 

diff --git a/docs/whats-new/dotnet-9.md b/docs/whats-new/dotnet-9.md
@@ -145,12 +145,12 @@ The binding mode for `IsVisible` and `IsEnabled` on a <xref:Microsoft.Maui.Contr
 
 ### BlazorWebView
 
-On iOS and Mac Catalyst 18, .NET MAUI 9 changes the default behavior for hosting content in a <xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> to `localhost`. The internal `0.0.0.1` address used to host content no longer works and results in the <xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> not loading any content and rendering as an empty rectangle.
+The default behavior for hosting content in a <xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> has changed to `0.0.0.1`. The internal `0.0.0.0` address used to host content no longer works and results in the <xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> not loading any content and rendering as an empty rectangle.
 
-To opt into using the `0.0.0.1` address, add the following code to the `CreateMauiApp` method in *MauiProgram.cs*:
+To opt into using the `0.0.0.0` address, add the following code to the `CreateMauiApp` method in *MauiProgram.cs*:
 
 ```csharp
-// Set this switch to use the LEGACY behavior of always using 0.0.0.1 to host BlazorWebView
+// Set this switch to use the LEGACY behavior of always using 0.0.0.0 to host BlazorWebView
 AppContext.SetSwitch("BlazorWebView.AppHostAddressAlways0000", true);
 ```