From 02bbcb68f1f8bcfb3ae01d1eb8b0ff87c85ec7b2 Mon Sep 17 00:00:00 2001
From: Meir017 <meirblachman@gmail.com>
Date: Fri, 24 Nov 2017 08:41:55 +0200
Subject: [PATCH] fixed docs on SocketNodeInstance

namespace was incorrect
---
 .../SocketNodeInstance.cs                                    | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/src/Microsoft.AspNetCore.NodeServices.Sockets/SocketNodeInstance.cs b/src/Microsoft.AspNetCore.NodeServices.Sockets/SocketNodeInstance.cs
index 1e6afd1..7559ae2 100644
--- a/src/Microsoft.AspNetCore.NodeServices.Sockets/SocketNodeInstance.cs
+++ b/src/Microsoft.AspNetCore.NodeServices.Sockets/SocketNodeInstance.cs
@@ -14,8 +14,7 @@ namespace Microsoft.AspNetCore.NodeServices.Sockets
     /// <summary>
     /// A specialisation of the OutOfProcessNodeInstance base class that uses a lightweight binary streaming protocol
     /// to perform RPC invocations. The physical transport is Named Pipes on Windows, or Domain Sockets on Linux/Mac.
-    /// For details on the binary streaming protocol, see
-    /// Microsoft.AspNetCore.NodeServices.HostingModels.VirtualConnections.VirtualConnectionClient.
+    /// For details on the binary streaming protocol, see <see cref="Microsoft.AspNetCore.NodeServices.Sockets.VirtualConnections.VirtualConnectionClient" />
     /// The advantage versus using HTTP for RPC is that this is faster (not surprisingly - there's much less overhead
     /// because we don't need most of the functionality of HTTP.
     ///
@@ -238,4 +237,4 @@ namespace Microsoft.AspNetCore.NodeServices.Sockets
         }
 #pragma warning restore 649
     }
-}
\ No newline at end of file
+}