diff --git a/hugo/content/manual/troubleshooting/hardware/EL5042.md b/hugo/content/manual/troubleshooting/hardware/EL5042.md
index 1400c16b3..ed396cbfd 100644
--- a/hugo/content/manual/troubleshooting/hardware/EL5042.md
+++ b/hugo/content/manual/troubleshooting/hardware/EL5042.md
@@ -28,8 +28,8 @@ Always start troubleshooting by checking the error, warning and ready bits and r
 
 #### Bad electrical connection
 
-The serial communication performed by two RS422 channels, one for the clock and one for data. These channels can easily be measured with a scope:
- * The clock should output periodic "bursts" with clock pulses with a short break in between. The bursts should appear in the same rate as the ethercat frame rate. And the frequency of the clock pulses should correspond with the setting in your startup script (normally 250kHz..10Mhz depending on configuration)
+The serial communication is hanled by two RS422 channels, one for the clock and one for data. These channels can be measured with a scope:
+ * The clock should output periodic "bursts" with clock pulses with a short break in between. The bursts should appear in the same rate as the ethercat frame rate (EC_RATE, default 1kHz). And the frequency of the clock pulses should correspond with the setting in your startup script (normally 250kHz..10Mhz depending on configuration)
  * The data channel should return bits in sync with the clock pulses.
  
 Lack of clock or data pulses could be caused by (in order of probability):
@@ -48,13 +48,13 @@ Never apply a higher voltage than the specified operating voltage for the encode
 
 The EL5042 can supply 5V or 9V. The default setting is 5V and in order to change the setting to 9V a special sequence need to be executed (see EL5042 manual).
 
-After ensureing that the encoder is correctly supplied, it's a good ide to measure the power consumption of the encoder and compare with the specified consumption. If the power consumption does not match, the encoder might be broken or a faulty cabling.
+After ensuring that the encoder is correctly supplied, the verify the power consumption of the encoder and compare with the specified consumption. If the power consumption does not match, the encoder might be broken or a faulty cabling.
 
 #### Long cable lengths
 
 Long cable lengths can affect both power supply levels and the serial data channels.
 
-_Power supply:_
+**Power supply:**
 
 Longer cables will normally also result in a higher voltage drops. Especaillay for 5V encoders this can be an issue. Make sure that the voltage are within the specified range by measuring the voltage level close to the encoder.
 
@@ -63,7 +63,7 @@ If the voltage is to low (mainly for 5V encoders):
 2. Can cable impedance be reduced (higher area)
 3. Add a separate (5V) power supply with possabilities to adjust the voltage level to a slightly higher voltage. Make sure the voltage is not too high at the encoder end.
 
-_Serial communication:_
+**Serial communication:**
 The serial communication is also affected by the cable legth. For long cable lengths a reduction of the clock rate can be needed. The clock rate can be reduced by setting the CLK_FRQ_KHZ macro in the call to applyComponent.cmd (set clock freq. to 500kHz):
 
 ```bash