Merge pull request #569 from bosh/patch22

Image fix followups

docs/hardware/opp/cobrapin/index.md

@@ -138,7 +138,7 @@ voltage power or without the coils plugged in. Using these LEDs, you can
 verify that each output is being driven correctly, in the picture below
 coil 1-0-1 is being driven at this very moment.
 
-![image](../../Cobra_Coils_LED_Switch.jpg)
+![image](../../images/Cobra_Coils_LED_Switch.jpg)
 
 To run the above test, there is no need for a high voltage power supply
 neither for any coil. Only the mirco controllers need to be powered up.

docs/mc/slides/multiplayer_display.md

@@ -79,11 +79,11 @@ score normally is.
 
 ![image](../images/multiplayer_player_2.png)
 
-The _[multi_player_ball_started](../../index.md) event happens when a player's turn
+The _[multi_player_ball_started](../../events/multi_player_ball_started.md)_ event happens when a player's turn
 starts and there are multiple players in the game, so this will show our
 multiplayer slide at the beginning of every ball.
 
-The _[multiplayer_game](../../index.md) event happens as soon as a second player is
+The _[multiplayer_game](../../events/multiplayer_game.md)_ event happens as soon as a second player is
 added, so we use it to swap the slides if player_2 joins after player_1
 has already started their turn.
 

docs/mechs/coils/index.md

@@ -22,7 +22,7 @@ pulse times, PWM values, whether they can be enabled (held on), etc.
 You don't typically work with coils directly, rather, you tend to add
 them to other devices once they've been defined (flippers, autofires,
 ball devices, diverters, etc). You can configure
-[/tutorial/3_get_flipping](dual_wound_coils.md) on top of coils.
+[dual_wound_coils:](../../config/dual_wound_coils.md) on top of coils.
 
 That said, it is possible to perform actions on coils directly, such as
 pulsing, enabling, or disabling them. You can do this via the
@@ -35,11 +35,12 @@ file or via the `coils:` section of a
 ### Connecting Coils
 
 If you coil has more than two terminals please have a look at
-[/tutorial/3_get_flipping](dual_wound_coils.md) because you got a
-dual-wound coil-If your coil has two terminals it is a single wound
+[dual_wound_coils](dual_wound_coils.md) because you have a
+dual-wound coil. If your coil has only two terminals it is a single wound
 coil.
 
 [TODO: Add a picture a single wound coil with diode](../../about/help.md)
+
 [TODO: Add a electrical drawing a single wound coil with diode](../../about/help.md)
 
 In general, polarity does not matter for a coil. However, there might be
@@ -90,10 +91,8 @@ means slightly less powerful.
 If you want to compare the strength of different coils you can get the
 number of windings and their resistance from one of the following pages:
 
-* [Pinball Medic Coil
-    Chart](https://www.pinballmedic.net/coilchart.html)
-* [Flippers.com Coil
-    Resistance](https://flippers.com/coil-resistance.html)
+* [Pinball Medic Coil Chart](https://www.pinballmedic.net/coilchart.html)
+* [Flippers.com Coil Resistance](https://flippers.com/coil-resistance.html)
 
 Get windings `N` and resistance `R` from the chart. To get the current
 you can use `I = U/R`. Depending on your power supply `U` is either 48
@@ -135,14 +134,13 @@ coils:
     default_hold_power: .2
 ```
 
-See [/tutorial/3_get_flipping](dual_wound_coils.md) for more details.
+See [Dual-wound Coils](dual_wound_coils.md) for more details.
 
 ## Related How To guides
 
 * [Tutorial step 3: Get flipping!](../../tutorial/3_get_flipping.md)
-
-[pulse_power](pulse_power.md)
-[hold_power](hold_power.md)
-[recycle](recycle.md)
-[dual_wound_coils](dual_wound_coils.md)
-[dual_vs_single_wound](dual_vs_single_wound.md)
+* [Adjust Coil Strength (Pulse Times)](pulse_power.md)
+* [Adjust Coil Hold Power](hold_power.md)
+* [Recycle/"Cool Down" Time](recycle.md)
+* [Dual-wound Coils](dual_wound_coils.md)
+* [Dual-wound vs Single-wound Coils](dual_vs_single_wound.md)

docs/mechs/lights/flashers.md

@@ -88,11 +88,9 @@ The color of this string. If you set it to brightness values all color channels
 
 See the documentation of your platform on how to configure GIs.
 
-Platform related How To
-
-* [P/P3-Roc leds](../../hardware/multimorphic/leds.md)
-* [P/P3-Roc matrix light](../../hardware/multimorphic/lights.md)
-* [FAST leds](../../hardware/fast/leds.md)
-* [FAST matrix light](../../hardware/fast/lights.md)
-* [OPP leds](../../hardware/opp/leds.md)
-* [OPP matrix light](../../hardware/opp/lights.md)----
+* [P/P3-Roc - leds](../../hardware/multimorphic/leds.md)
+* [P/P3-Roc - matrix light](../../hardware/multimorphic/lights.md)
+* [FAST - leds](../../hardware/fast/leds.md)
+* [FAST - matrix light](../../hardware/fast/lights.md)
+* [OPP - leds](../../hardware/opp/leds.md)
+* [OPP - matrix light](../../hardware/opp/lights.md)

docs/mechs/lights/gis.md

@@ -114,15 +114,9 @@ For
 
 See the documentation of your platform on how to configure GIs.
 
-Platform related How To
-
-* [P/P3-Roc leds](../../hardware/multimorphic/leds.md)
-* [P/P3-Roc matrix light](../../hardware/multimorphic/lights.md)
-* [FAST leds](../../hardware/fast/leds.md)
-* [FAST matrix light](../../hardware/fast/lights.md)
-* [OPP leds](../../hardware/opp/leds.md)
-* [OPP matrix light](../../hardware/opp/lights.md)----
-
-## Related Events
-
-None
+* [P/P3-Roc - leds](../../hardware/multimorphic/leds.md)
+* [P/P3-Roc - matrix light](../../hardware/multimorphic/lights.md)
+* [FAST - leds](../../hardware/fast/leds.md)
+* [FAST - matrix light](../../hardware/fast/lights.md)
+* [OPP - leds](../../hardware/opp/leds.md)
+* [OPP - matrix light](../../hardware/opp/lights.md)

docs/mechs/lights/index.md

@@ -243,8 +243,8 @@ Pay attention to the event `single_led_green` to understand how to address a sin
 ## Monitorable Properties
 For dynamic values and conditional events, the prefix for lights is `device.lights.(name)`.
 
-* brightness: The numeric value of the brightness of this light, from 0-255.
-* color: The current color.
+* *brightness*: The numeric value of the brightness of this light, from 0-255.
+* *color*: The current color.
 
 ## Related How To guides
 

docs/mechs/targets/drop_targets/drop_target_bank.md

@@ -66,8 +66,8 @@ For
 
 ## Related How To guides
 
-* [Welcome to The Mission Pinball Framework!](../../../index.md)
-* [/events/drop_target_bank_drop_target_bank_mixed](fixing_drop_target_reset_issues.md)
+* [Drop Targets](index.md)
+* [Fixing Drop Target Reset Issues](fixing_drop_target_reset_issues.md)
 
 ## Related Events