remove excess trailing newlines across all pages

bosh · bosh · commit 2f9ee994f73c · 2025-06-27T00:24:16.000-07:00
diff --git a/docs/code/BCP_Protocol/ball_end.md b/docs/code/BCP_Protocol/ball_end.md
@@ -11,4 +11,3 @@ None
 ## Response
 
 None
-
diff --git a/docs/code/BCP_Protocol/index.md b/docs/code/BCP_Protocol/index.md
@@ -93,5 +93,3 @@ The following BCP commands have been defined (and implemented) in MPF:
 * [reset_complete](reset_complete.md)
 * [switch](switch.md)
 * [trigger](trigger.md)
-
-
diff --git a/docs/code/Writing_Tests/RunUnitTests.md b/docs/code/Writing_Tests/RunUnitTests.md
@@ -41,4 +41,3 @@ Notes about the MPF-MC tests:
 * These tests create a window on the screen and then just re-use the same window for all tests (to save time). So don't worry if it looks like the window content is scaled weird or blurry or doesn't fill the entire window.
 * Many of these tests are used to test internal workings of the media controller itself, so there will be lots of time when the pop up window is blank or appears frozen since the tests are testing non-visual things.
 * The animation and transition tests include testing functionality to stop, restart, pause, and skip frames. So if things look “jerky” in the tests, don't worry, that doesn't mean your computer is slow, it's just how the tests work! :)
-
diff --git a/docs/code/Writing_Tests/WritingCustomTestsForYourMachine.md b/docs/code/Writing_Tests/WritingCustomTestsForYourMachine.md
@@ -124,5 +124,3 @@ If you get some kind of loading error or config error, make sure you're running
 If you get a message about 0 tests run, make sure you have that empty __init__.py in your tests folder.
 
 And if you get some weird error that you can't figure out, then post a message to the MPF Google Group.
-
-
diff --git a/docs/code/Writing_Tests/index.md b/docs/code/Writing_Tests/index.md
@@ -8,5 +8,3 @@ You can run built-in tests to test MPF itself or extend them if you think you fo
 
 * [How to run MPF unittests](RunUnitTests.md)
 * [Writing Custom Tests for your Machine](WritingCustomTestsForYourMachine.md)
-
-
diff --git a/docs/code/introduction/index.md b/docs/code/introduction/index.md
@@ -11,6 +11,3 @@ Follow either the examples for the [machine wide](machine_code.md) extension or
 As long as you only write smaller extensions you don't have to setup a full Python development environment. Of course you can and the more complex your development gets the more handy it might be. The [setup guide](setup.md) you only have to follow if you really want to develop MPF itself and not only to write an extension for your game.
 
 Last but not least of course the [API Reference](../api_reference/index.md) is very important for you.
-
-
-
diff --git a/docs/code/introduction/variables_in_code.md b/docs/code/introduction/variables_in_code.md
@@ -39,4 +39,3 @@ self.machine.variables.configure_machine_var("my_variable", persist=True, expire
 # set a variable
 self.machine.variables.set_machine_var("my_variable", 17)
 ```
-
diff --git a/docs/config/variable_player.md b/docs/config/variable_player.md
@@ -272,4 +272,3 @@ changes.
 * [Machine Variables Reference](../machine_vars/index.md)
 * [Scoring](../game_logic/scoring/index.md)
 * [Persisting the State of a Logic Block in a Player Variable](../game_logic/logic_blocks/persisting_state_in_a_player_variable.md)
-
diff --git a/docs/events/combo_switch_both.md b/docs/events/combo_switch_both.md
@@ -4,7 +4,6 @@ title: (combo_switch_name)_both
 
 # (combo_switch_name)\_both
 
-
 --8<-- "event.md"
 
 Event is posted by [combo_switches:](../config/combo_switches.md)
@@ -19,4 +18,3 @@ The event name can be changed by using the `events_when_both:`
 attribute.
 
 --8<-- "event_no_keywords_notice.md"
-
diff --git a/docs/events/combo_switch_switches_2.md b/docs/events/combo_switch_switches_2.md
@@ -4,7 +4,6 @@ title: (combo_switch_name)_switches_2
 
 # (combo_switch_name)\_switches_2
 
-
 --8<-- "event.md"
 
 Event is posted by [combo_switches:](../config/combo_switches.md)
@@ -19,4 +18,3 @@ The event name can be changed by using the `events_when_switches_2:`
 attribute.
 
 --8<-- "event_no_keywords_notice.md"
-
diff --git a/docs/events/multiball_multiball_shoot_again_ended.md b/docs/events/multiball_multiball_shoot_again_ended.md
@@ -4,12 +4,10 @@ title: multiball_(name)_shoot_again_ended
 
 # multiball_(name)\_shoot_again_ended
 
-
 --8<-- "event.md"
 
 Event is posted by [multiballs:](../config/multiballs.md)
 
 Shoot again for multiball called (name) has ended.
 
 --8<-- "event_no_keywords_notice.md"
-
diff --git a/docs/events/queue_events/index.md b/docs/events/queue_events/index.md
@@ -12,7 +12,6 @@ See:
 * [queue_event_player:](../../config/queue_event_player.md)
 * [queue_relay_player:](../../config/queue_relay_player.md)
 
-
 ## Events:
 
 * Machine Events
@@ -48,4 +47,3 @@ See:
 * Match Mode Events
     * [match_has_match](../match_has_match.md) *Queue Event*
     * [match_no_match](../match_no_match.md) *Queue Event*
-
diff --git a/docs/game_logic/ball_search/index.md b/docs/game_logic/ball_search/index.md
@@ -4,7 +4,6 @@ title: Ball Search
 
 # Ball Search
 
-
 Related Config File Sections:
 
 * [ball_devices:](../../config/ball_devices.md)
@@ -52,4 +51,3 @@ until the balls drain, etc.)
 * [ball_search_stopped](../../events/ball_search_stopped.md)
 * [flipper_cradle](../../events/flipper_cradle.md)
 * [flipper_cradle_release](../../events/flipper_cradle_release.md)
-
diff --git a/docs/gmc/reference/mpf-gmc.md b/docs/gmc/reference/mpf-gmc.md
@@ -182,4 +182,3 @@ Examples:
 
     pluralize("Shot%s Remaining", 3)
     # > "Shots Remaining"
-
diff --git a/docs/gmc/reference/slide_player.md b/docs/gmc/reference/slide_player.md
@@ -209,4 +209,3 @@ name of a slide_frame where you want this slide to be displayed.
 One or more sub-entries. Each in the format of `string` : `string`
 
 Tokens can be passed to the slide with additional information that might affect the slide's content or behavior. Token values are parsed by the GMC slide when calculating variable values, and can be passed to custom methods on the slide.
-
diff --git a/docs/hardware/opp/oppcombo/index.md b/docs/hardware/opp/oppcombo/index.md
@@ -86,5 +86,3 @@ With those boards, I digitized a 1975 Gottlieb Fast Draw, which was presented to
 on June 1rst-2nd, 2024, South of France, where it ran 375 plays without any software problem.
 
 ![image](../../images/pontacq.jpg)
-
-
diff --git a/docs/install/linux/raspberry.md b/docs/install/linux/raspberry.md
@@ -164,6 +164,3 @@ mpf both -X
 You can step left and right through the slides to see animations and videos. You can also test audio here by listening for sounds during slide transitions.
 
 Now that MPF is working on the Raspberry Pi, there are steps to take to tweak the device itself and harden it for use in the machine. Those are A) not fully known and B) outside the scope of this page, but as information becomes available, it can be added. 
-
-
-
diff --git a/docs/logs/index.md b/docs/logs/index.md
@@ -32,4 +32,3 @@ MPF tries to give IDs to errors that happen a lot so you can look them up here,
 ### Warning Logs:
 
 * [Log-SwitchController-1](Log-SwitchController-1.md)
-
diff --git a/docs/mechs/plungers/index.md b/docs/mechs/plungers/index.md
@@ -4,7 +4,6 @@ title: Plungers & Ball Launch Devices
 
 # Plungers & Ball Launch Devices
 
-
 Related Config File Sections:
 
 * [ball_devices:](../../config/ball_devices.md)
@@ -120,4 +119,3 @@ If you have this type of coil-powered plunger, follow the
 * [balldevice_(name)\_ball_eject_failed](../../events/balldevice_ball_device_ball_eject_failed.md)
 * [balldevice_(name)\_ball_eject_success](../../events/balldevice_ball_device_ball_eject_success.md)
 * [balldevice_(name)\_ejecting_ball](../../events/balldevice_ball_device_ejecting_ball.md)
-

Original file line number	Diff line number	Diff line change
`@@ -11,4 +11,3 @@ None`
`11`	`11`	`## Response`
`12`	`12`
`13`	`13`	`None`
`14`		`-`