From 2cba8ecbd5537e4210ee0e5c2f3fe41a414285d0 Mon Sep 17 00:00:00 2001 From: zuccs Date: Tue, 2 Jun 2020 19:54:05 +1000 Subject: [PATCH] Fix Pi-hole brand capitalisation (#13647) --- source/_integrations/pi_hole.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/_integrations/pi_hole.markdown b/source/_integrations/pi_hole.markdown index 3b836409b43..8bd055ec130 100644 --- a/source/_integrations/pi_hole.markdown +++ b/source/_integrations/pi_hole.markdown @@ -35,7 +35,7 @@ name: description: > The name for this Pi-hole. This name will be a part of the sensors created, e.g., `name: My Awesome Pi-hole` would result in sensor names beginning with `sensor.my_awesome_pi_hole_`. - **Note:** If you configure multiple Pi-Holes, each one *must* have a unique name. + **Note:** If you configure multiple Pi-holes, each one *must* have a unique name. required: false type: string default: Pi-hole @@ -45,13 +45,13 @@ location: type: string default: admin ssl: - description: "If `true`, use SSL/TLS to connect to the Pi-Hole system." + description: "If `true`, use SSL/TLS to connect to the Pi-hole system." required: false type: boolean default: false verify_ssl: description: > - Verify the SSL/TLS certificate of the system. If your Pi-Hole instance uses a self-signed certificate, you should specify `false`. + Verify the SSL/TLS certificate of the system. If your Pi-hole instance uses a self-signed certificate, you should specify `false`. required: false type: boolean default: true @@ -77,7 +77,7 @@ Multiple Pi-holes: pi_hole: - host: '192.168.0.2' - host: '192.168.0.3' - name: 'Secondary Pi-Hole' + name: 'Secondary Pi-hole' ``` Pi-hole with a self-signed certificate: