diff --git a/README.md b/README.md
index 3bf4cca9d679c974742a8029c277508c0904072a..5e18027be92e49b5905b1cf976d221bf32cc3332 100644
--- a/README.md
+++ b/README.md
@@ -77,13 +77,16 @@ pedestal_event_generator = event_source._pedestal_event_generator(telescope='M1'
 Monitoring data are saved in `run['data'].monitoring_data` and can also accessed event-wise via the `event.mon` container. Even if they can be accessed event-wise, they are saved only once per run, i.e., identical for all events in a run. If monitoring data is taken several times during a run, the `run['data'].monitoring_data`/`event.mon` sub-containers contain arrays of the quantities taken at the different times together with an array of the time stamps. So far, we have
 - Dead pixel information (MARS `RunHeaders.MBadPixelsCam.fArray.fInfo` tree), once per sub-run in `run['data'].monitoring_data['MX']['badpixelinfo']` (with X=1 or X=2) or `event.mon.tel[tel_id].pixel_status`
 - Pedestal information from MARS `Pedestals` tree to calculate hot pixels:
-	- `run['data'].monitoring_data['MX']['PedestalFundamental']`
-	- `run['data'].monitoring_data['MX']['PedestalFromExtractor']`
-	- `run['data'].monitoring_data['MX']['PedestalFromExtractorRndm']`
+     - `run['data'].monitoring_data['MX']['PedestalFundamental']`
+     - `run['data'].monitoring_data['MX']['PedestalFromExtractor']`
+     - `run['data'].monitoring_data['MX']['PedestalFromExtractorRndm']`
+  
   or everyting also in `event.mon.tel[tel_id].pedestal`
+
 Dead pixel and pedestal information are read by `magic-cta-pipe` `MAGIC_Badpixels.py` class.
 
 #### Changelog
 
 - v0.1: Initial version
 - v0.2.0: Unification of data and MC reading
+- v0.2.1: Monitoring data (Dead pixel and pedestal information)
\ No newline at end of file