From 9565c170c4cd828d887b941f87acfc6e3ea59cfb Mon Sep 17 00:00:00 2001 From: John Asmuth Date: Sat, 22 Nov 2014 13:53:45 -0500 Subject: [PATCH] fix typo --- docs/getting-started-guides/logging.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/getting-started-guides/logging.md b/docs/getting-started-guides/logging.md index fe4bf7fcf9..b65733ef9b 100644 --- a/docs/getting-started-guides/logging.md +++ b/docs/getting-started-guides/logging.md @@ -14,10 +14,10 @@ This will instantiate a [Fluentd](http://www.fluentd.org/) instance on each node collect all the Dcoker container log files. The collected logs will be targetted at an [Elasticsearch](http://www.elasticsearch.org/) instance assumed to be running on the local node and accepting log information on port 9200. This can be accomplished -by writing a pod specification and service sepecificaiton to define an +by writing a pod specification and service specificaiton to define an Elasticsearch service (more informaiton to follow shortly in the contrib directory). ### Logging with Fluentd and Google Compute Platform To enable logging of Docker contains in a cluster using Google Compute -Platfrom set the shell environment variable ``FLUENTD_GCP`` to ``true``. \ No newline at end of file +Platfrom set the shell environment variable ``FLUENTD_GCP`` to ``true``.