Replace .NET Framework usage (#11592)

Article applies to both .NET Framework and .NET Core. Have replaced ".NET Framework" with just ".NET"

Author: JamesNK

docs/standard/io/pipe-operations.md

@@ -1,5 +1,5 @@
 ---
-title: "Pipe Operations in the .NET Framework"
+title: "Pipe Operations in .NET"
 ms.date: "03/30/2017"
 ms.technology: dotnet-standard
 helpviewer_keywords: 
@@ -11,22 +11,22 @@ ms.assetid: 7b964ebd-7a4f-4d28-8194-7841f9e4c702
 author: "mairaw"
 ms.author: "mairaw"
 ---
-# Pipe Operations in the .NET Framework
+# Pipe Operations in .NET
 Pipes provide a means for interprocess communication. There are two types of pipes:  
 
 -   Anonymous pipes.  
 
      Anonymous pipes provide interprocess communication on a local computer. Anonymous pipes require less overhead than named pipes but offer limited services. Anonymous pipes are one-way and cannot be used over a network. They support only a single server instance. Anonymous pipes are useful for communication between threads, or between parent and child processes where the pipe handles can be easily passed to the child process when it is created.  
 
-     In the .NET Framework, you implement anonymous pipes by using the <xref:System.IO.Pipes.AnonymousPipeServerStream> and <xref:System.IO.Pipes.AnonymousPipeClientStream> classes.  
+     In .NET, you implement anonymous pipes by using the <xref:System.IO.Pipes.AnonymousPipeServerStream> and <xref:System.IO.Pipes.AnonymousPipeClientStream> classes.  
 
      See [How to: Use Anonymous Pipes for Local Interprocess Communication](../../../docs/standard/io/how-to-use-anonymous-pipes-for-local-interprocess-communication.md).  
 
 -   Named pipes.  
 
      Named pipes provide interprocess communication between a pipe server and one or more pipe clients. Named pipes can be one-way or duplex. They support message-based communication and allow multiple clients to connect simultaneously to the server process using the same pipe name. Named pipes also support impersonation, which enables connecting processes to use their own permissions on remote servers.  
 
-     In the .NET Framework, you implement named pipes by using the <xref:System.IO.Pipes.NamedPipeServerStream> and <xref:System.IO.Pipes.NamedPipeClientStream> classes.  
+     In .NET, you implement named pipes by using the <xref:System.IO.Pipes.NamedPipeServerStream> and <xref:System.IO.Pipes.NamedPipeClientStream> classes.  
 
      See [How to: Use Named Pipes for Network Interprocess Communication](../../../docs/standard/io/how-to-use-named-pipes-for-network-interprocess-communication.md).