Renaming to EnableEndpointDiscovery

Author: ealsur

articles/cosmos-db/nosql/migrate-dotnet-v3.md

@@ -215,7 +215,7 @@ Some settings in `ConnectionPolicy` have been renamed or replaced by `CosmosClie
 
 | .NET v2 SDK | .NET v3 SDK |
 |-------------|-------------|
-|`EnableEndpointDiscovery`|`LimitToEndpoint` - The value is now inverted, if `EnableEndpointRediscovery` was being set to `true`, `LimitToEndpoint` should be set to `false`. Before using this setting, you need to understand [how it affects the client](troubleshoot-sdk-availability.md).|
+|`EnableEndpointDiscovery`|`LimitToEndpoint` - The value is now inverted, if `EnableEndpointDiscovery` was being set to `true`, `LimitToEndpoint` should be set to `false`. Before using this setting, you need to understand [how it affects the client](troubleshoot-sdk-availability.md).|
 |`ConnectionProtocol`|Removed. Protocol is tied to the Mode, either it's Gateway (HTTPS) or Direct (TCP). Direct mode with HTTPS protocol is no longer supported on V3 SDK and the recommendation is to use TCP protocol. |
 |`MediaRequestTimeout`|Removed. Attachments are no longer supported.|
 |`SetCurrentLocation`|`CosmosClientOptions.ApplicationRegion` can be used to achieve the same effect.|