From f1d6eef5be00ca7668ed41e87c86eb533ecdf57c Mon Sep 17 00:00:00 2001 From: Dan Frost Date: Wed, 26 Nov 2014 11:55:42 +0000 Subject: [PATCH] docs: intro/checks: minor fixes --- website/source/intro/getting-started/checks.html.markdown | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/website/source/intro/getting-started/checks.html.markdown b/website/source/intro/getting-started/checks.html.markdown index a072c2a647..e4f8210b11 100644 --- a/website/source/intro/getting-started/checks.html.markdown +++ b/website/source/intro/getting-started/checks.html.markdown @@ -19,9 +19,8 @@ two node cluster running. ## Defining Checks Similarly to a service, a check can be registered either by providing a -[check definition](/docs/agent/checks.html) -, or by making the appropriate calls to the -[HTTP API](/docs/agent/http.html). +[check definition](/docs/agent/checks.html), or by making the +appropriate calls to the [HTTP API](/docs/agent/http.html). We will use the check definition, because just like services, definitions are the most common way to setup checks.