From 9cd166c5c91fb63cc32693ef565e9657b7a05aae Mon Sep 17 00:00:00 2001 From: Tim Preston Date: Thu, 14 May 2020 13:35:57 +1000 Subject: [PATCH] Fix typo --- ...ip-connection-sql-server-database-that-resolves-localhost.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/includes/migration-guide/runtime/data/attempting-tcpip-connection-sql-server-database-that-resolves-localhost.md b/includes/migration-guide/runtime/data/attempting-tcpip-connection-sql-server-database-that-resolves-localhost.md index d4a3f194a63b3..011fcdc6bc53c 100644 --- a/includes/migration-guide/runtime/data/attempting-tcpip-connection-sql-server-database-that-resolves-localhost.md +++ b/includes/migration-guide/runtime/data/attempting-tcpip-connection-sql-server-database-that-resolves-localhost.md @@ -3,7 +3,7 @@ | | | |---|---| |Details|In the .NET Framework 4.6 and 4.6.1, attempting a TCP/IP connection to a SQL Server database that resolves to localhost fails with the error, "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"| -|Suggestion|This issue has been addressed and the previous behavior restored in the .NET Framework 4.6.2. To connect to a SQL Server databsae that resolves to localhost, upgrade to the .NET Framework 4.6.2.| +|Suggestion|This issue has been addressed and the previous behavior restored in the .NET Framework 4.6.2. To connect to a SQL Server database that resolves to localhost, upgrade to the .NET Framework 4.6.2.| |Scope|Minor| |Version|4.6| |Type|Runtime|