Kestrel named pipes

Author: Rick-Anderson

aspnetcore/fundamentals/servers/kestrel/endpoints.md

@@ -581,16 +581,11 @@ The following example configures an endpoint for HTTP/1.1, HTTP/2, and HTTP/3 co
 
 :::code language="csharp" source="~/fundamentals/servers/kestrel/samples/6.x/KestrelSample/Snippets/Program.cs" id="snippet_ConfigureKestrelProtocols":::
 
-## See also
-
-* <xref:fundamentals/servers/kestrel>
-* <xref:fundamentals/servers/kestrel/options>
-
 :::moniker-end
 
 :::moniker range=">= aspnetcore-9.0"
 
-### Customize Kestrel named pipe endpoints
+## Customize Kestrel named pipe endpoints
 
 Kestrel's named pipe support includes advanced customization options. The [CreateNamedPipeServerStream](/dotnet/api/microsoft.aspnetcore.server.kestrel.transport.namedpipes.namedpipetransportoptions.createnamedpipeserverstream) property on the named pipe options allows pipes to be customized per-endpoint.
 
@@ -601,4 +596,13 @@ An example of where this is useful is a Kestrel app that requires two pipe endpo
 
 :::moniker-end
 
+:::moniker range=">= aspnetcore-8.0"
+
+## See also
+
+* <xref:fundamentals/servers/kestrel>
+* <xref:fundamentals/servers/kestrel/options>
+
+:::moniker-end
+
 [!INCLUDE [endpoints5-7](~/fundamentals/servers/kestrel/endpoints/includes/endpoints5-7.md)]