Index: resources/settings/Service.conf
===================================================================
diff -u -r56ad953ae404fcf6956bd4f76b7a54b12d0285d3 -r371ebfbad6c230e8415c12f85935910fbca46612
--- resources/settings/Service.conf	(.../Service.conf)	(revision 56ad953ae404fcf6956bd4f76b7a54b12d0285d3)
+++ resources/settings/Service.conf	(.../Service.conf)	(revision 371ebfbad6c230e8415c12f85935910fbca46612)
@@ -1,3 +1,4 @@
+# FIXME :
 # this is the service password
 # later needs to be encoded to something with the algorithm which is used for all other encryption like CANBus messages 
 # and will be encrypted on the application
Index: sources/view/hd/data/VHDOperationModeData.cpp
===================================================================
diff -u -re28183bddebf7383c1bd113e7b8ef4ea11f494fb -r371ebfbad6c230e8415c12f85935910fbca46612
--- sources/view/hd/data/VHDOperationModeData.cpp	(.../VHDOperationModeData.cpp)	(revision e28183bddebf7383c1bd113e7b8ef4ea11f494fb)
+++ sources/view/hd/data/VHDOperationModeData.cpp	(.../VHDOperationModeData.cpp)	(revision 371ebfbad6c230e8415c12f85935910fbca46612)
@@ -46,12 +46,12 @@
     // Go to home is kind of tricky and needs to be managed here in the backend.
     // It seems we need more states.
     // It can be handled in the QML but two things will happen that none of which are good.
-    // Problem : The issue is for example FW may changed the opMode state to TPAR <=> STAN but during that, subMode is not changing.
+    // Problem : The issue is for example FW may change the opMode state to TPAR <=> STAN but during that, subMode is not changing.
     // and when it comes back to the opMode STAN again only opMode is changing which is not enough,
     // because we still need to know when we are in STAN what subMode of STAN we need to be in
-    // and because that doesn't change QML, since FW change opMode STAN <=> TPAR then UI is doing nothing.
+    // and because that does not change QML, since FW change opMode STAN <=> TPAR then UI is doing nothing.
     // The solutions on QML side are:
-    // 1 - On each standby change STAN <=> TPAR which is not good because if in STAN we need to go to the anything other than Start/waitTreatment.
+    // 1 - On each standby change STAN <=> TPAR which is not good because if in STAN we need to go to anything other than Start/waitTreatment.
     // Issue : But then the home screen would jump.
     // 2 - And we can also check that if subMode is Start/WaitTreatment go to home in QML.
     // 3 - Make the sub PROPERTY as TRIGGER and if standby is true trigger them.