From fa29fee4b6a1353c565fdc5067e5ba08e2c0229f Mon Sep 17 00:00:00 2001 From: Paul Banks Date: Fri, 13 Jul 2018 23:09:34 +0100 Subject: [PATCH] Typos --- website/source/docs/connect/native/go.html.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/source/docs/connect/native/go.html.md b/website/source/docs/connect/native/go.html.md index e2e4535835..ad59caca3c 100644 --- a/website/source/docs/connect/native/go.html.md +++ b/website/source/docs/connect/native/go.html.md @@ -168,17 +168,17 @@ discovery mechanism for the target. **It's not actually resolved via DNS** but used as a logical identifier for a Consul service discovery mechanism. It has the following specific limitations: - * The sheme must be `https://`. + * The scheme must be `https://`. * It must be a Consul DNS name in one of the following forms: * `.service[.].consul` to discover a healthy service instance for a given service. - * `.query[.].consul` to discover an instance via + * `.query[.].consul` to discover an instance via [Prepared Query](/api/query.html). * The top-level domain _must_ be `.consul` even if your cluster has a custom `domain` configured for it's DNS interface. This might be relaxed in the future. * Tag filters for services are not currently supported (i.e. - `tag1.web.service.consul`) however the same behaviour can be acheived using a + `tag1.web.service.consul`) however the same behaviour can be achieved using a prepared query. * External DNS names, raw IP addresses and so on will cause an error and should be fetched using a separate `HTTPClient`.