Replace <br/> with <br>

This is an effort to have more consistent markup, also related to
ongoing work with adding local anchors to comments:
Danielovich/PloehComments#5

If anyone's wondering why I don't just make a search-and-replace, I want
to visually verify that these changes don't mess anything up - at least
for a few posts.

If you're a front-end developer and find this ridiculous, then please
have patience with me. I rarely deal with such issues these days, and I
haven't kept up with web page rendering or HTML standards.

_posts/2018-09-17-typing-is-not-a-programming-bottleneck.html

@@ -234,8 +234,8 @@ <h2 id="comments-header">
 	<div class="comment" id="4bfb1d54e38449c7bc5d30e171d01179">
 		<div class="comment-author"><a href="http://honestillusion.com">James Curran</a></div>
 		<div class="comment-content">
-		While I accept most of what you say, you are overlooking one key point: Better typists are better typists.  Speed of typing (and volume of code produced) is the only statistic you look at.  But what about <em>quality</em>?  <br/>
-		Watch a bad typist code.  (It's easier with coding-heavy tutorial videos).  It usually go as: type four or five characters, backspace, make a correction, type another six characters, backspace, make another fix, type a few more character, etc. <br/>
+		While I accept most of what you say, you are overlooking one key point: Better typists are better typists.  Speed of typing (and volume of code produced) is the only statistic you look at.  But what about <em>quality</em>?  <br>
+		Watch a bad typist code.  (It's easier with coding-heavy tutorial videos).  It usually go as: type four or five characters, backspace, make a correction, type another six characters, backspace, make another fix, type a few more character, etc. <br>
 		They rarely get more than 10 keystrokes out before have to stop and go back.   This reeks havoc with your cognitive flow, and makes it much harder to get into the "groove" of coding.  Once you can type fluidly, you can concetrate on the code itself, rather than the mechanics of entering it.
 		</div>
 		<div class="comment-date">2018-09-19 02:02 UTC</div>	
@@ -247,9 +247,9 @@ <h2 id="comments-header">
 	    Lines of code has nothing to do with productivity. As professionals I think we all know this. <br />
 	    Moreover, in many cases, too much verbosity might only lead to more defects (unless you're a strong advocate of TDD et similia)<br />
 	    That said, one thing that I really liked about your article is the version of the Builder pattern you've implemented in the Reservation class. 
-	    I love immutability in my classes and I often use the Builder pattern implemented as a inner class, just to be able to access the private cTor. <br/>
+	    I love immutability in my classes and I often use the Builder pattern implemented as a inner class, just to be able to access the private cTor. <br>
 	    One thing that I don't like with your approach is that in case you have a bit parameter list in your cTor (as you do in the example), the consumers are forced to create a "dummy" instance and then call the WithXXX() methods on it when possible.
-	    I guess it could be solved adding a static readonly Empty property on the Reservation class that can be used as a starting point. <br/>
+	    I guess it could be solved adding a static readonly Empty property on the Reservation class that can be used as a starting point. <br>
 	    Anyways thank you for sharing this!
 	    </div>
 	    <div class="comment-date">2018-09-19 11:02 UTC</div>