From 3380706b5c66ca3307917dced66d63a11e429ca9 Mon Sep 17 00:00:00 2001 From: Matthias Hanel Date: Mon, 3 Feb 2020 19:16:59 -0500 Subject: [PATCH] Fix description Signed-off-by: Matthias Hanel --- developing-with-nats/connecting/specific_server.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developing-with-nats/connecting/specific_server.md b/developing-with-nats/connecting/specific_server.md index 5d49cda..ee6ea2b 100644 --- a/developing-with-nats/connecting/specific_server.md +++ b/developing-with-nats/connecting/specific_server.md @@ -2,7 +2,7 @@ The NATS client libraries can take a full URL, `nats://demo.nats.io:4222`, to specify a specific server host and port to connect to. -Libraries are removing the requirement for an explicit protocol and may allow `nats://demo.nats.io:4222` or just `demo.nats.io:4222`. Check with your specific client library's documentation to see what URL formats are supported. +Libraries are removing the requirement for an explicit protocol and may allow `demo.nats.io:4222` or just `demo.nats.io`. In the later example the default port 4222 will be used. Check with your specific client library's documentation to see what URL formats are supported. For example, to connect to the demo server with a URL you can use: