From 2fcbdfdf3aa0850d2df2fdc57e94c37ff1f9191c Mon Sep 17 00:00:00 2001
From: Mike Hillyer <mike@kumomta.com>
Date: Wed, 10 May 2023 15:56:23 +0000
Subject: [PATCH] Automated doc formatting fix

---
 docs/userguide/configuration/trafficshaping.md | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/docs/userguide/configuration/trafficshaping.md b/docs/userguide/configuration/trafficshaping.md
index cca51d47..7abc72f9 100644
--- a/docs/userguide/configuration/trafficshaping.md
+++ b/docs/userguide/configuration/trafficshaping.md
@@ -106,14 +106,23 @@ Because the shaping.toml file is part of the install repository, it should not b
 
 ```lua
 -- load the community shaping.toml + local settings
-kumo.on('get_egress_path_config', shaping:setup({'/opt/kumomta/etc/shaping.json'}))
+kumo.on(
+  'get_egress_path_config',
+  shaping:setup { '/opt/kumomta/etc/shaping.json' }
+)
 ```
 
 You can load multiple override files too if you wish, by adding each file name to that table:
 
 ```lua
 -- load the community shaping.toml + local settings
-kumo.on('get_egress_path_config', shaping:setup({'/opt/kumomta/etc/shaping.toml', '/opt/kumomta/etc/shaping-generated.json'}))
+kumo.on(
+  'get_egress_path_config',
+  shaping:setup {
+    '/opt/kumomta/etc/shaping.toml',
+    '/opt/kumomta/etc/shaping-generated.json',
+  }
+)
 ```
 
 When creating an override file, any settings that overlap with an existing domain definition will append any existing settings in the `shaping.toml` file, replacing any directly overlapping options.