improves formatting

docs/total-service-request-delay.md

@@ -14,7 +14,7 @@ network_delay = time delay from first byte leaving source to final byte arriving
 
 If we ignore the OSI L6 protocol (e.g. HTTP, FTP, Tsunami) then we are modelling a chunk of data moving along a wire. The network delay is then:
 
-```math
+```
 network_delay = latency + (time difference from start of the data to the end of the data)
 ```
 
@@ -26,7 +26,7 @@ latency = distance / speed
 
 For optical fibre (or even an eletric wire), the speed naively would be the speed of light. In fact, the speed is slower than this (in optical fibre this is because of the internal refraction that occurs, which is different for different wavelengths). According to http://www.m2optics.com/blog/bid/70587/Calculating-Optical-Fiber-Latency the delay (1/speed) is approximately 5 microseconds / km
 
-```math
+```
 if 
     distance is in m
     delay is in s/m
@@ -43,7 +43,7 @@ Normally we would just measure the latency of a link. Most real-life connections
 
 The time difference from start of the data to the end of the data (or "data delay" for want of a better term) is dependent on the bandwidth of the network and the amount of data.
 
-```math
+```
 if
     data_size is in Bytes
     bandwidth is in Mb/s
@@ -54,7 +54,7 @@ then
 
 The data_size naively is the size of the data you want to send over the network (call this the "file_size"). However, the data is split into packets and each packet has a header on it so the amount of data going over the network is actually more than the amount sent.
 
-```math
+```
 let 
     packet_size = packet_header_size + packet_payload_size
 then
@@ -65,7 +65,7 @@ or
 
 ### Total delay
 
-```math
+```
 delay = latency + data_delay
     = (distance * 5 / 1E9) + {[(packet_size / packet_size - packet_header_size) * file_size] * 8 / bandwidth * 1E6}
 ```