readme: Make whitespace more consistent (#41)

README.md

@@ -268,7 +268,6 @@ Measuring own (and third-party) JavaScript bytes is crucial as JavaScript is the
 - [What's in the Google PageSpeed score](https://medium.com/expedia-group-tech/whats-in-the-google-pagespeed-score-a5fc93f91e91)
 - [How Google Pagespeed works](https://calibreapp.com/blog/how-pagespeed-works/)
 
-
 ### User Timing
 
 The User Timing API allows the developer to create application specific timestamps that are part of the browser's performance timeline. e.g. you can create a user timing mark to measure when your JS has loaded for a specific component on the page.
@@ -283,7 +282,6 @@ Surface any backend server timing metrics (e.g. database latency, etc.) in the d
 
 - [Docs - Server Timing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Server-Timing)
 
-
 ### Frame rate
 
  The frame rate is the **frequency at which the browser can display frames**. A frame represents the amount of work a browser does in one event loop iteration such as processing DOM events, resizing, scrolling, rendering, CSS animations, etc. A frame rate of 60 fps (frames per second) is a common target for a good responsive user experience. This means the browser should process a frame in about 16.7 ms.
@@ -307,4 +305,3 @@ Surface any backend server timing metrics (e.g. database latency, etc.) in the d
 [![CC0](http://mirrors.creativecommons.org/presskit/buttons/88x31/svg/cc-zero.svg)](https://creativecommons.org/publicdomain/zero/1.0/)
 
 To the extent possible under law, Csaba Palfi has waived all copyright and related or neighboring rights to this work.
-