From 5db237446e359f1fb1df4863a084dac999bb4bad Mon Sep 17 00:00:00 2001
From: Michael <35783820+mib1185@users.noreply.github.com>
Date: Tue, 10 Sep 2024 19:08:03 +0200
Subject: [PATCH] Fix table in iperf3 (#34663)

---
 source/_integrations/iperf3.markdown | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/source/_integrations/iperf3.markdown b/source/_integrations/iperf3.markdown
index 57b779c3684..330adc4c408 100644
--- a/source/_integrations/iperf3.markdown
+++ b/source/_integrations/iperf3.markdown
@@ -118,7 +118,8 @@ You can use the `sensor.iperf3_update` action to trigger a manual speed test for
 Once loaded, the `iperf3` integration will expose an action (`iperf3.speedtest`) that can be called to run a speed test on demand. This can be useful if you have enabled manual mode.
 
 | Data attribute | Description |
-| `host` | String that point at a configured `host` from `configuration.yaml`. Otherwise, tests will be run against all configured hosts.
+| --- | --- |
+| `host` | String that point at a configured `host` from `configuration.yaml`. Otherwise, tests will be run against all configured hosts. |
 
 Example action data: