From ba56b550aa00943e94785adde8a8e44dba38fc9e Mon Sep 17 00:00:00 2001
From: pierwill <19642016+pierwill@users.noreply.github.com>
Date: Tue, 22 Oct 2019 10:40:28 -0700
Subject: [PATCH] Update telegraf config for TLS docs

---
 content/v2.0/security/enable-https.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/content/v2.0/security/enable-https.md b/content/v2.0/security/enable-https.md
index 0b59d637a..1aa4e25f3 100644
--- a/content/v2.0/security/enable-https.md
+++ b/content/v2.0/security/enable-https.md
@@ -125,13 +125,13 @@ That's it! You've successfully set up HTTPS with InfluxDB.
 
 ## Connect Telegraf to a secured InfluxDB instance
 
-Connecting [Telegraf](/telegraf/latest/) to an InfluxDB instance that's using
-HTTPS requires some additional steps.
+To connect [Telegraf](/telegraf/latest/) to an InfluxDB 2.0 instance with TLS enabled,
+update the following `influxdb_v2` output settings in your Telegraf configuration file:
 
-In the Telegraf configuration file (`/etc/telegraf/telegraf.conf`), edit the `urls`
-setting to indicate `https` instead of `http`.
-(Change `localhost` to the relevant domain name if necessary.)
-If you're using a self-signed certificate, uncomment the `insecure_skip_verify` setting and set it to `true`.
+- Update urls to use https instead of http.
+- If using a self-signed certificate, uncomment and set `insecure_skip_verify` to true.
+
+### Example configuration
 
 ```toml
 ###############################################################################
@@ -144,7 +144,7 @@ If you're using a self-signed certificate, uncomment the `insecure_skip_verify`
   ##
   ## Multiple URLs can be specified for a single cluster, only ONE of the
   ## urls will be written to each interval.
-  urls = ["http://127.0.0.1:9999"]
+  urls = ["https://127.0.0.1:9999"]
 
   [...]