fix: MD037/no-space-in-emphasis (#2422)

fix: MD037/no-space-in-emphasis

meetings/2014/LDM-2014-10-01.md

@@ -38,7 +38,7 @@ _Resolution: Option4_. This is the most helpful to developers. You might wonder
 
 __Piecewise initialization of structs__. In the code above, do we allow `z.z1 = 15` to assign to the _field_ of a readonly struct autoprop?
 _Option1:_ Yes by threating access to "z" for purposes of definite assignment as an access of the underlying field.
-_Option2: _ No because in `z.z1` the read of `z` happens via the accessor as per the principle above, and thus returns an rvalue, and hence assignment to `z.z1` can't work. Instead you will have to write `z = new Z(...)`.
+_Option2:_ No because in `z.z1` the read of `z` happens via the accessor as per the principle above, and thus returns an rvalue, and hence assignment to `z.z1` can't work. Instead you will have to write `z = new Z(...)`.
 _Resolution: Option2_. If we went with Option1, then readonly autoprops would end up being more expressive than settable autoprops which would be odd! Note that in VB you can still write `_z.z1 = 15` if you do want piecewise assignment.
 
 __Virtual__. What should happen if the readonly autoprop is virtual, and its getter is overridden in a derived class?