From 2653e19da72cda750d759ceac501710ab842b471 Mon Sep 17 00:00:00 2001 From: Anthony van Winkle Date: Wed, 24 Jul 2024 15:49:19 -0700 Subject: [PATCH] Warning admonition still making a code block for some reason --- docs/config/segment_displays.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/config/segment_displays.md b/docs/config/segment_displays.md index e7e46fc625..b832d284a6 100644 --- a/docs/config/segment_displays.md +++ b/docs/config/segment_displays.md @@ -105,14 +105,14 @@ persist player variables (e.g. score) without having to continually push updates !!! warning "Can cause memory bloat" - Using the "stack" method for updates will create a new event subscriber for each entry, so misusing the segment_display_player and sending manual updates will cause - hundreds or thousands of subscribers to be created, which can cause lag and memory issues. + Using the "stack" method for updates will create a new event subscriber for each entry, so misusing the segment_display_player and sending manual updates will cause + hundreds or thousands of subscribers to be created, which can cause lag and memory issues. - In a future release of MPF **"replace" will become the default setting** because it is more aligned with how most people implement their segment_display_player. + In a future release of MPF **"replace" will become the default setting** because it is more aligned with how most people implement their segment_display_player. - If you know what you're doing and want to use "stack", you should set it explicitly in your config to prevent errors when the default changes to "replace". + If you know what you're doing and want to use "stack", you should set it explicitly in your config to prevent errors when the default changes to "replace". - If you are unsure or don't know which to use, use "replace". + If you are unsure or don't know which to use, use "replace". ### use_dots_for_commas: