From ed7c66e06802f3fb2b31bc04f4d34405c75e1347 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Fran=C3=A7ois=20LASSERRE?=
 <198672+ChoiZ@users.noreply.github.com>
Date: Tue, 25 May 2021 09:59:35 +0200
Subject: [PATCH] Update vultr.markdown (#17958)

Fix current_bandwidth_used by current_bandwidth_gb
---
 source/_integrations/vultr.markdown | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/source/_integrations/vultr.markdown b/source/_integrations/vultr.markdown
index 5ace94fea8c..ae3aa17a6d9 100644
--- a/source/_integrations/vultr.markdown
+++ b/source/_integrations/vultr.markdown
@@ -128,13 +128,13 @@ monitored_conditions:
   detault: All conditions
   type: list
   keys:
-    current_bandwidth_used:
+    current_bandwidth_gb:
       description: The current (invoice period) bandwidth usage in Gigabytes (GB).
     pending_charges:
       description: The current (invoice period) charges that have built up for this subscription. Value is in US Dollars (US$).
 {% endconfiguration %}
 
-Full `configuration.yaml` using `{}` to format condition name (produces `sensor.server_current_bandwidth_used` and `sensor.server_pending_charges`):
+Full `configuration.yaml` using `{}` to format condition name (produces `sensor.server_current_bandwidth_gb` and `sensor.server_pending_charges`):
 
 ```yaml
 sensor:
@@ -142,7 +142,7 @@ sensor:
     name: Server {}
     subscription: 123456
     monitored_conditions:
-      - current_bandwidth_used
+      - current_bandwidth_gb
       - pending_charges
 ```