Merge pull request #672 from bosh/whitespace_cleanup

remove empty lines with multiple spaces

Author: bosh

docs/code/introduction/variables_in_code.md

@@ -23,7 +23,6 @@ player["my_variable"] = 17
 ```
 
 
-
 ## Machine Variables in Code
 
 You can use machine variables by calling into the MPF machine.

docs/events/queue_events/index.md

@@ -27,20 +27,20 @@ See:
 * Game Events
     * [game_starting](../game_starting.md) *Queue Event*
     * [game_ending](../game_ending.md) *Queue Event*
-  
+
 * Player Events
     * [player_adding](../player_adding.md) *Queue Event*
     * [player_turn_starting](../player_turn_starting.md) *Queue Event*
     * [player_turn_ending](../player_turn_ending.md) *Queue Event*
-  
+
 * Ball Events
     * [ball_starting](../ball_starting.md) *Queue Event*
     * [ball_ending](../ball_ending.md) *Queue Event*
-  
+
 * Mode Events
     * [mode_(name)_starting](../mode_name_starting.md) *Queue Event*
     * [mode_(name)_stopping](../mode_name_stopping.md) *Queue Event*
-    
+
 * Ball Device Events
     * [balldevice_(name)\_ball_eject_attempt](../balldevice_ball_device_ball_eject_attempt.md) *Queue Event*
 

docs/game_logic/multiballs/multiball_with_traditional_ball_lock.md

@@ -49,7 +49,7 @@ In either scenario, both the `multiball_locks` and the `multiballs` config setti
     balls to be locked and replaced from the trough, but the third ball not 
     to be replaced from the trough (because multiball is starting and all three 
     locked balls will come out as part of that), then set `balls_to_replace: 2`. 
-    
+
     If for some reason the multiball doesn't start automatically on ball 3 
     entering, the game will get stuck with no balls on the playfield!
 

docs/gmc/reference/gmc-cfg.md

@@ -9,7 +9,7 @@ The *gmc.cfg* configuration file in your Godot project root contains options for
 !!! note
 
     Currently the Godot engine will remove comments from this file when it chooses to rewrite it.
-    
+
 ### Local Overrides
 
 Any configuration options in *gmc.cfg* can be overridden with a local file *gmc.local.cfg* in the Godot User Data folder. This allows you to commit the primary configuration to version control while still having platform-specific configurations (e.g. MPF executable path and logging levels) on each machine.

docs/hardware/opp/cobrapin/cobrapin_serial_segment_displays.md

@@ -218,7 +218,7 @@ neoseg_displays:
     light_template:
       type: w
       subtype: led
-      
+
 segment_displays:
   neoSegTop:
     number: 1
@@ -230,13 +230,13 @@ segment_displays:
       light_groups:
         - neoSeg_0
       type: 14segment
-      
+
 show_player:
   player_score{player_num==1}: #of course for more than 1 player you need to have multiple entries
     p1_score:
       show_tokens:
         txt: "{(players[0].score):d}"
-        
+
 shows:
   p1_score:
   - duration: -1

docs/running/commands/index.md

@@ -18,11 +18,8 @@ See the specific command reference pages to determine which command line
 options you will need for your particular use cases.
 
 
-
 ### Commands for starting your game
 
-
-
 To start the MPF game engine as well as the media controller, you can use:
 
 ``` shell

docs/tutorials/legacy_mc/2_creating_a_new_machine.md

@@ -130,7 +130,6 @@ not `config.yaml.txt`. Find the option in the "View" menu of Explorer.
 
 ## 4. Add #config_version=6 to the top of your config file
 
-
 The first thing you need to do when you create any new config file for
 MPF is to add an entry on the very top line that tells MPF what
 "version" of the MPF config spec you're using for the file you're
@@ -184,7 +183,6 @@ When all your changes are staged, make a new commit with a message describing wh
 
 Now your changes are safe and if you ever need to come back to this point (or share your code with someone else), it's ready!
 
-
 ## 6. Run your game!
 
 Believe it our not, it's time to run your game! Simply open a console

includes/common_ground_warning.md

@@ -6,15 +6,15 @@
     them, burn down your house or kill you. We are serious, floating grounds
     are dangerous. If you are not an electrical engineer read the
     [guide about voltages and power](https://missionpinball.org/latest/hardware/voltages_and_power).
-    
+
     In a nutshell: You need to connect your logic ground (5V/12V) and your
     high voltage ground (48V or 80V). A
     [power entry or power filter board](https://missionpinball.org/latest/hardware/voltages_and_power) is a convenient solution to solve this (and more) issues.
-    
+
     Always turn all PSUs off when connecting power or you might fry all
     boards at once. This is generally a good idea but even more important
     when connecting more than one power supply to a board.
-    
+
     IF YOU DID NOT UNDERSTAND WHAT THIS WARNING MEANS STOP NOW AND TRY TO
     UNDERSTAND IT. OTHERWISE YOUR HARDWARE WILL LIKELY BURST INTO FLAMES AND
     YOU NEED TO WAIT A FEW DAYS FOR A REPLACEMENT OR EVEN WORSE IT MIGHT