From edd5739e90ee3ce6e0ed167d278b4e0f7bf4608d Mon Sep 17 00:00:00 2001 From: James Turnbull Date: Fri, 25 Nov 2016 13:29:55 -0500 Subject: [PATCH] Final dc pass --- website/source/docs/agent/http/catalog.html.markdown | 8 ++++---- website/source/docs/agent/http/session.html.markdown | 6 +++--- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/website/source/docs/agent/http/catalog.html.markdown b/website/source/docs/agent/http/catalog.html.markdown index cbfd66e16..efb80b3b9 100644 --- a/website/source/docs/agent/http/catalog.html.markdown +++ b/website/source/docs/agent/http/catalog.html.markdown @@ -184,7 +184,7 @@ used as a simple check to see if any Consul servers are routable. This endpoint is hit with a `GET` and returns the nodes registered in a given DC. By default, the datacenter of the agent is queried; -however, the dc can be provided using the `?dc=` query parameter. +however, the `dc` can be provided using the `?dc=` query parameter. Adding the optional `?near=` parameter with a node name will sort the node list in ascending order based on the estimated round trip @@ -220,7 +220,7 @@ This endpoint supports blocking queries and all consistency modes. This endpoint is hit with a `GET` and returns the services registered in a given DC. By default, the datacenter of the agent is queried; -however, the dc can be provided using the `?dc=` query parameter. +however, the `dc` can be provided using the `?dc=` query parameter. It returns a JSON body like this: @@ -244,7 +244,7 @@ This endpoint supports blocking queries and all consistency modes. This endpoint is hit with a `GET` and returns the nodes providing a service in a given DC. By default, the datacenter of the agent is queried; -however, the dc can be provided using the `?dc=` query parameter. +however, the `dc` can be provided using the `?dc=` query parameter. The service being queried must be provided on the path. By default all nodes in that service are returned. However, the list can be filtered @@ -300,7 +300,7 @@ The returned fields are as follows: This endpoint is hit with a `GET` and returns the node's registered services. By default, the datacenter of the agent is queried; -however, the dc can be provided using the `?dc=` query parameter. +however, the `dc` can be provided using the `?dc=` query parameter. The node being queried must be provided on the path. It returns a JSON body like this: diff --git a/website/source/docs/agent/http/session.html.markdown b/website/source/docs/agent/http/session.html.markdown index 00e859ba1..8b82bdda6 100644 --- a/website/source/docs/agent/http/session.html.markdown +++ b/website/source/docs/agent/http/session.html.markdown @@ -95,7 +95,7 @@ The return code is 200 on success. This endpoint is hit with a `GET` and returns the requested session information within a given datacenter. By default, the datacenter of the agent is queried; -however, the dc can be provided using the `?dc=` query parameter. +however, the `dc` can be provided using the `?dc=` query parameter. The session being queried must be provided on the path. It returns a JSON body like this: @@ -121,7 +121,7 @@ This endpoint supports blocking queries and all consistency modes. This endpoint is hit with a `GET` and returns the active sessions for a given node and datacenter. By default, the datacenter of the agent is queried; -however, the dc can be provided using the `?dc=` query parameter. +however, the `dc` can be provided using the `?dc=` query parameter. The node being queried must be provided on the path. @@ -148,7 +148,7 @@ This endpoint supports blocking queries and all consistency modes. This endpoint is hit with a `GET` and returns the active sessions for a given datacenter. By default, the datacenter of the agent is queried; -however, the dc can be provided using the `?dc=` query parameter. +however, the `dc` can be provided using the `?dc=` query parameter. It returns a JSON body like this: