Fix more markdown-in-html blocks

Author: PeterJCLaw

programming/sr/power/index.md

@@ -98,7 +98,7 @@ humans can only hear between [20Hz and 20000Hz][pitch-range].
 The `Note` enum provides notes in [scientific pitch notation][pitch-notation]
 between `C6` and `C8`. You can play other tones by providing a frequency.
 
-<div class="info">
+<div class="info" markdown="1">
   Calling `buzz` is non-blocking, which means it doesn't actually wait
   for the piezo to stop buzzing before continuing with your code. If you
   want to wait for the buzzing to stop, add a `sleep` afterwards!

programming/sr/ruggeduinos/index.md

@@ -34,10 +34,10 @@ you could do this instead:
 R.ruggeduinos["752303138333517171B1"].something...
 ~~~~~
 
-<div class="warning">
-    When you have more than one Ruggeduino board connected to your kit,
-    you must use `R.ruggeduinos` and index by serial number. This is so
-    that the kit knows which Ruggeduino you want to control.
+<div class="warning" markdown="1">
+  When you have more than one Ruggeduino board connected to your kit,
+  you must use `R.ruggeduinos` and index by serial number. This is so
+  that the kit knows which Ruggeduino you want to control.
 </div>
 
 

programming/sr/servos/index.md

@@ -32,10 +32,10 @@ If you have more than one Servo Board attached, you need to specify which one yo
 R.servo_boards["srABC1"].something...
 ~~~~~
 
-<div class="warning">
-    When you have more than one servo board connected to your kit,
-    you must use `R.servo_boards` and index by serial number. This is so
-    that the kit knows which servo board you want to control.
+<div class="warning" markdown="1">
+  When you have more than one servo board connected to your kit,
+  you must use `R.servo_boards` and index by serial number. This is so
+  that the kit knows which servo board you want to control.
 </div>
 
 Setting servo positions

tutorials/basic_motor_control.md

@@ -131,11 +131,11 @@ You're familiar with the first few lines; in fact, the only lines you may not be
 For a comprehensive reference to the `motor` object, see the `sr.robot3` module's [`motor`](/docs/programming/sr/motors/) page.
 But, to summarise:
 
-<div class="info">
-    `R.motor_board.motors[0].power = x` will set the power of the motor connected to output 0 (the `motors[0]` part)
-    on the first [motor board](/docs/kit/motor_board) (the `motor_board` part)
-    plugged in to a USB hub to `x`, where `x` is a value between `-1` and `1`,
-    inclusive &mdash; in other words: `-1` &le; `x` &le; `1`.
+<div class="info" markdown="1">
+  `R.motor_board.motors[0].power = x` will set the power of the motor connected to output 0 (the `motors[0]` part)
+  on the first [motor board](/docs/kit/motor_board) (the `motor_board` part)
+  plugged in to a USB hub to `x`, where `x` is a value between `-1` and `1`,
+  inclusive &mdash; in other words: `-1` &le; `x` &le; `1`.
 </div>
 
 So, `R.motor_board.motors[0].power = 0.5` sets the target power of the motor connected to output 0 on the first [motor board](/docs/kit/motor_board)
@@ -146,10 +146,10 @@ As you would expect, then, `R.motor_board.motors[0].power = -0.5` will put the t
 So, if you put the above code on your robot,
  you should be able to see a motor spin forwards, stop, spin backwards, stop, and then repeat...
 
-<div class="info">
-    If you find that the motor doesn't turn when you run the above code,
-     check that you've got all the cables connected to the right places,
-     in particular note that the motor board has _two_ outputs.
+<div class="info" markdown="1">
+  If you find that the motor doesn't turn when you run the above code,
+  check that you've got all the cables connected to the right places,
+  in particular note that the motor board has _two_ outputs.
 </div>
 
 ### Changing the Speed