Merge pull request #588 from bosh/more_anchors

Cleaning up more anchors

Author: bosh

docs/config/multiballs.md

@@ -122,9 +122,8 @@ Single value, type: `time string (ms) or template`
 [Instructions for entering templates](instructions/dynamic_values.md)). Default: `0`
 
 The time before the add-a-ball ball save ends (in MPF time string
-format) that will cause the [multiball](../index.md)_\(name\)_hurry_up event to be
-posted. Use this to change the script for the light or trigger other
-effect.
+format) that will cause the [multiball_(name)\_hurry_up](../events/multiball_multiball_hurry_up.md) event to be
+posted. Use this to change the script for the light or trigger other effect.
 
 ### add_a_ball_shoot_again:
 
@@ -149,21 +148,21 @@ number of balls it should add into play. Adjusting this setting is
 useful when you have multiple (or stacked) multiballs and you want to
 control how the combined counts work.
 
-*total*
+#### *total*:
 
-:   Means the `ball_count:` setting will provide a target for the total
-    number of balls that should be in play when this multiball starts.
-    So if this multiball has a `ball_count: 3`, and it starts when 2
-    balls are live on the playfield, then this multiball will only add 1
-    more ball to bring the total to 3.
+Means the `ball_count:` setting will provide a target for the total
+number of balls that should be in play when this multiball starts.
+So if this multiball has a `ball_count: 3`, and it starts when 2
+balls are live on the playfield, then this multiball will only add 1
+more ball to bring the total to 3.
 
-*add*
+#### *add*:
 
-:   Means that the `ball_count:` setting will specify the number of
-    balls that are added into play on top of whatever number of balls
-    are already in play. So if this multiball is set to `ball_count: 2`
-    and there are already 2 balls in play, then this multiball will add
-    2 more balls for a total of 4 balls live.
+Means that the `ball_count:` setting will specify the number of
+balls that are added into play on top of whatever number of balls
+are already in play. So if this multiball is set to `ball_count: 2`
+and there are already 2 balls in play, then this multiball will add
+2 more balls for a total of 4 balls live.
 
 ### ball_locks:
 
@@ -217,7 +216,7 @@ Single value, type: `time string (ms) or template`
 [Instructions for entering templates](instructions/dynamic_values.md)). Default: `0`
 
 The time before the ball save ends (in MPF time string format) that will
-cause the [multiball](../index.md)_\(name\)_hurry_up event to be posted. Use this
+cause the [multiball_(name)\_hurry_up](../events/multiball_multiball_hurry_up.md) event to be posted. Use this
 to change the script for the light or trigger other effect.
 
 ### replace_balls_in_play:

docs/config/show_player.md

@@ -46,39 +46,37 @@ your config. (If you don't include them, the default will be used).
 Single value, type: one of the following options: play, stop, pause,
 resume, advance, step_back, update, queue. Default: `play`
 
-`play`
+#### `play`:
 
-:   Starts playing the show. This is the default action which will
-    happen if you don't include an `action:` setting.
+Starts playing the show. This is the default action which will
+happen if you don't include an `action:` setting.
 
-`stop`
+#### `stop`:
 
-:   Stops the show. Removes and "undoes" anything the show did, and
-    posts the show stop events.
+Stops the show. Removes and "undoes" anything the show did, and
+posts the show stop events.
 
-`pause`
+#### `pause`:
 
-:   Pauses the show by holding it at the current step. Posts the show
-    pause events.
+Pauses the show by holding it at the current step. Posts the show pause events.
 
-`resume`
+#### `resume`:
 
-:   Resumes a previously paused show.
+Resumes a previously paused show.
 
-`advance`
+#### `advance`:
 
-:   Manually advances a show to the next step. Posts the show advance
-    events.
+Manually advances a show to the next step. Posts the show advance events.
 
-`step_back`
+#### `step_back`
 
-:   Manually moves the show back to the previous step. Posts the show
-    step_back events.
+Manually moves the show back to the previous step. Posts the show
+step_back events.
 
-`update`
+#### `update`:
 
-:   Not yet implemented. In the future it will be used to change a
-    setting of a running show, like changing the playback speed.
+Not yet implemented. In the future it will be used to change a
+setting of a running show, like changing the playback speed.
 
 ### block_queue:
 

docs/config/slide_player.md

@@ -42,25 +42,24 @@ your config. (If you don't include them, the default will be used).
 Single value, type: one of the following options: play, remove. Default:
 `play`
 
-`play`
+#### `play`:
 
-:   Makes the slide active. Note that the actual slide shown on a
-    display will be whichever active slide has the highest priority, so
-    depending on what other slides are active, this action might not
-    technically show the slide.
+Makes the slide active. Note that the actual slide shown on a
+display will be whichever active slide has the highest priority, so
+depending on what other slides are active, this action might not
+technically show the slide.
 
-    Also note that if a transition is specified (either in the slide
-    definition or the `transition:` section here, then than transition
-    will be used when showing this slide.
+Also note that if a transition is specified (either in the slide
+definition or the `transition:` section here, then than transition
+will be used when showing this slide.
 
-`remove`
+#### `remove`:
 
-:   Removes the slide from the list of active slides. If this slide is
-    the highest priority slide that's currently showing, then the
-    next-highest priority slide will be shown in its place.
+Removes the slide from the list of active slides. If this slide is
+the highest priority slide that's currently showing, then the
+next-highest priority slide will be shown in its place.
 
-    If a `transition_out:` setting is used, then that transition will be
-    used here.
+If a `transition_out:` setting is used, then that transition will be used here.
 
 For example, to remove *slide1* when the event *remove_slide_1* is
 posted:

docs/config/timer_control_events.md

@@ -60,77 +60,76 @@ change_tick_interval, reset_tick_interval.
 Take a look at the various types of actions you can perform on timers
 with control events:
 
-`add`
+#### `add`:
 
-:   Adds the time (specified in the `value:` setting) to the timer. If
-    the value would be higher than the timer's `max_value:` setting,
-    then the value is set to the max value. Posts the
-    *timer_\(name\)_time_added* event.
+Adds the time (specified in the `value:` setting) to the timer. If
+the value would be higher than the timer's `max_value:` setting,
+then the value is set to the max value. Posts the
+*timer_\(name\)_time_added* event.
 
-    This action does not change the timer's running state.
+This action does not change the timer's running state.
 
-    The timer is checked for done after the value has been added. (So,
-    for example, if you have a timer that's set to count up, and the
-    timer finishes at 10, and the timer is currently at 6, and you add
-    value of 5, then the timer will be complete.
+The timer is checked for done after the value has been added. (So,
+for example, if you have a timer that's set to count up, and the
+timer finishes at 10, and the timer is currently at 6, and you add
+value of 5, then the timer will be complete.
 
-`subtract`
+#### `subtract`:
 
-:   Subtracts time (specified in the `value:` setting) from the timer.
-    Posts the *timer_\(name\)_time_subtracted* event and checks to see
-    if the timer is complete.
+Subtracts time (specified in the `value:` setting) from the timer.
+Posts the *timer_\(name\)_time_subtracted* event and checks to see
+if the timer is complete.
 
-`jump`
+#### `jump`:
 
-:   "Jumps" the timer to a specific new value (specified in the
-    `value:` setting) and checks to see if the timer is complete.
+"Jumps" the timer to a specific new value (specified in the
+`value:` setting) and checks to see if the timer is complete.
 
-`start`
+#### `start`:
 
-:   Starts the timer if it's not running. Does nothing if the timer is
-    already running. Posts the *timer_\(name\)_started* event.
+Starts the timer if it's not running. Does nothing if the timer is
+already running. Posts the *timer_\(name\)_started* event.
 
-`stop`
+#### `stop`:
 
-:   Stops the timer and posts the *timer_\(name\)_stopped* event.
-    Removes any outstanding "pause" delays.
+Stops the timer and posts the *timer_\(name\)_stopped* event.
+Removes any outstanding "pause" delays.
 
-`reset`
+#### `reset`:
 
-:   Changes the timers current value back to the `start_value:`. Nothing
-    else is touched, so if the timer is running, it stays running, etc.
+Changes the timers current value back to the `start_value:`. Nothing
+else is touched, so if the timer is running, it stays running, etc.
 
-`restart`
+#### `restart`:
 
-:   Acts as a combination of reset, then start.
+Acts as a combination of reset, then start.
 
-`pause`
+#### `pause`:
 
-:   Pauses the timer for a given `value:` time (in seconds). Note that
-    the timer pause value is real world seconds and does not take the
-    timers tick interval into consideration. If the pause value is 0,
-    the timer is paused indefinitely. Posts the
-    *timer_\(name\)_paused* event.
+Pauses the timer for a given `value:` time (in seconds). Note that
+the timer pause value is real world seconds and does not take the
+timers tick interval into consideration. If the pause value is 0,
+the timer is paused indefinitely. Posts the
+*timer_\(name\)_paused* event.
 
-`set_tick_interval`
+#### `set_tick_interval`:
 
-:   Sets the tick interval to a new value (specified in the `value:`
-    setting).
+Sets the tick interval to a new value (specified in the `value:` setting).
 
-`change_tick_interval`
+#### `change_tick_interval`:
 
-:   Changes the tick interval by multiplying the current tick interval
-    by the new one specified in the `value:` setting. In other words, if
-    you want to make the tick interval 10% faster, than set this to
-    `value: 1.1`. If you want to make it 50% slower, set this to
-    `value: 0.5`, etc.
+Changes the tick interval by multiplying the current tick interval
+by the new one specified in the `value:` setting. In other words, if
+you want to make the tick interval 10% faster, than set this to
+`value: 1.1`. If you want to make it 50% slower, set this to
+`value: 0.5`, etc.
 
-`reset_tick_interval`
+#### `reset_tick_interval`:
 
-:   (added in MPF 0.33)
+(added in MPF 0.33)
 
-    Resets the timer's tick interval back to the original from the
-    `tick_interval:` setting.
+Resets the timer's tick interval back to the original from the
+`tick_interval:` setting.
 
 ### event:
 

docs/config/widget_player.md

@@ -82,18 +82,17 @@ your config. (If you don't include them, the default will be used).
 Single value, type: one of the following options: add, remove, update.
 Default: `add`
 
-`add`
+#### `add`:
 
-:   The widget or widget group is added to the slide or display target.
+The widget or widget group is added to the slide or display target.
 
-`remove`
+#### `remove`:
 
-:   The widget or widget group is removed from the slide or display
-    target.
+The widget or widget group is removed from the slide or display target.
 
-`update`
+#### `update`:
 
-:   One or more of the widget or widget group's properties is updated.
+One or more of the widget or widget group's properties is updated.
 
 ### key: