react to feedback

Author: Rick-Anderson

aspnetcore/diagnostics/asp0028.md

@@ -17,7 +17,11 @@ uid: diagnostics/asp0028
 
 ## Cause
 
+[IPv6Any](/dotnet/api/system.net.ipaddress.ipv6any) is preferred to [Any](/dotnet/api/system.net.ipaddress.any) because `Any` can be slower than `IPv6Any`. In some cases, `Any` may not work at all. `Any` can be slower due to the [underlying System types implementation](https://github.com/dotnet/runtime/issues/82404). Servers that support `IPv6` my report the `ASP0028` diagnostic message.
+
+<!--
 [IPv6Any](/dotnet/api/system.net.ipaddress.ipv6any) is preferred to [Any](/dotnet/api/system.net.ipaddress.any) because `Any` is less performant than `IPv6Any`. In some cases, `Any` may not work at all. `Any` has performance problems due to the [underlying System types implementation](https://github.com/dotnet/runtime/issues/82404).
+-->
 
 `127.0.0.1` is the IPv4 loopback address. `::1` is the IPv6 loopback address. `Any` is the wildcard address for IPv4. `IPv6Any` is the wildcard address for IPv6.
 
@@ -43,21 +47,23 @@ The recommended way to configure Kestrel to listen for incoming connections on a
 
 For the problematic code, replace `Any` with `IPv6Any`:
 
+Use the [ListenAnyIP](https://source.dot.net/#Microsoft.AspNetCore.Server.Kestrel.Core/KestrelServerOptions.cs,1c84a7db2c1f6892) method without specifying any arguments:
+
 ```diff
 .UseKestrel().ConfigureKestrel(options =>
 { 
 -   options.Listen(IPAddress.Any, ...);
-+   options.Listen(IPAddress.IPv6Any, ...);
++   options.ListenAnyIP(...);
 })
 ```
 
-Alternatively, use the [ListenAnyIP](https://source.dot.net/#Microsoft.AspNetCore.Server.Kestrel.Core/KestrelServerOptions.cs,1c84a7db2c1f6892) method without specifying any arguments:
+Alternatively, use the `IPv6Any` method:
 
 ```diff
 .UseKestrel().ConfigureKestrel(options =>
 { 
 -   options.Listen(IPAddress.Any, ...);
-+   options.ListenAnyIP(...);
++   options.Listen(IPAddress.IPv6Any, ...);
 })
 ```