Merge pull request #609 from bosh/page_retitles

Page retitles

Author: bosh

README.md

@@ -1,4 +1,3 @@
-
 # Mission Pinball website & documentation
 
 This repo contains all the source code for [MissionPinball.org](https://missionpinball.org), which also includes all user documentation.

docs/code/BCP_Protocol/ball_end.md

@@ -1,5 +1,4 @@
-
-## ball_end (BCP command)
+# ball_end (BCP command)
 
 Indicates the ball has ended. Note that this does not necessarily mean that the next player's turn will start, as this player may have an extra ball which means they'll shoot again.
 
@@ -12,4 +11,3 @@ None
 ## Response
 
 None
-

docs/code/BCP_Protocol/ball_start.md

@@ -1,4 +1,3 @@
-
 # ball_start (BCP command)
 
 Indicates a new ball has started. It passes the player number (1, 2, etc.) and the ball number as parameters. This command will be sent every time a ball starts, even if the same player is shooting again after an extra ball.

docs/code/BCP_Protocol/device.md

@@ -1,4 +1,3 @@
-
 # device (BCP command)
 
 ## Origin

docs/code/BCP_Protocol/error.md

@@ -1,4 +1,3 @@
-
 # error (BCP command)
 This is a command used to convey error messages back to the origin of a command.
 

docs/code/BCP_Protocol/goodbye.md

@@ -1,4 +1,3 @@
-
 # goodbye (BCP command)
 Lets one side tell the other than it's shutting down.
 

docs/code/BCP_Protocol/hello.md

@@ -1,4 +1,3 @@
-
 # hello (BCP command)
 This is the initial handshake command upon first connection. It sends the BCP protocol version that the origin controller speaks.
 

docs/code/BCP_Protocol/index.md

@@ -1,4 +1,3 @@
-
 # BCP Protocol Specification
 
 This document describes the Backbox Control Protocol, (or “BCP”), a simple, fast protocol for communications between an implementation of a pinball game controller and a multimedia controller.
@@ -94,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)
-
-

docs/code/BCP_Protocol/machine_variable.md

@@ -1,4 +1,3 @@
-
 # machine_variable (BCP command)
 This is a generic "catch all" which sends machine variables to the media controller any time they change. Machine variables are like player variables, except they're maintained machine-wide instead of per-player or per-game. Since the pin controller will most likely track hundreds of variables (with many being internal things that the media controller doesn't care about), it's recommended that the pin controller has a way to filter which machine variables are sent to the media controller.
 

docs/code/BCP_Protocol/mode_list.md

@@ -1,4 +1,3 @@
-
 # mode_list (BCP command)
 This message informs the media controller about which modes are currently running. It is sent whenever a mode starts or stops, but only to clients currently [monitoring](monitor_start.md) the `mode` category.