Use consistent formatting in pulseInLong() description

Code markdown was used on some instances of the words HIGH and LOW and not on others. A search of the rest of the reference pages shows them to be quite inconsistent in formatting but code markdown is used in the majority of instances and I feel that's the correct usage.

Author: per1234

Language/Functions/Advanced IO/pulseInLong.adoc

@@ -19,7 +19,7 @@ subCategories: [ "Advanced I/O" ]
 === Description
 `pulseInLong()` is an alternative to link:../pulsein[pulseIn()] which is better at handling long pulse and interrupt affected scenarios.
 
-Reads a pulse (either HIGH or LOW) on a pin. For example, if value is HIGH, `pulseInLong()` waits for the pin to go from `LOW` to `HIGH`, starts timing, then waits for the pin to go `LOW` and stops timing. Returns the length of the pulse in microseconds or gives up and returns 0 if no complete pulse was received within the timeout.
+Reads a pulse (either `HIGH` or `LOW`) on a pin. For example, if `value` is `HIGH`, `pulseInLong()` waits for the pin to go from `LOW` to `HIGH`, starts timing, then waits for the pin to go `LOW` and stops timing. Returns the length of the pulse in microseconds or gives up and returns 0 if no complete pulse was received within the timeout.
 
 The timing of this function has been determined empirically and will probably show errors in shorter pulses. Works on pulses from 10 microseconds to 3 minutes in length. This routine can be used only if interrupts are activated. Furthermore the highest resolution is obtained with large intervals.
 [%hardbreaks]