Index: sources/view/hd/adjustment/posttreatment/VPostTreatmentAdjustTreatmentLog.cpp
===================================================================
diff -u -r4b7b6f9506d7c7ad4f611b8c417ed37d5f9a48ac -rf9e747f0f28df1cc6a33179f0bc78bfc03d486fc
--- sources/view/hd/adjustment/posttreatment/VPostTreatmentAdjustTreatmentLog.cpp	(.../VPostTreatmentAdjustTreatmentLog.cpp)	(revision 4b7b6f9506d7c7ad4f611b8c417ed37d5f9a48ac)
+++ sources/view/hd/adjustment/posttreatment/VPostTreatmentAdjustTreatmentLog.cpp	(.../VPostTreatmentAdjustTreatmentLog.cpp)	(revision f9e747f0f28df1cc6a33179f0bc78bfc03d486fc)
@@ -79,7 +79,7 @@
     _TreatmentLog.initModel     ( vData, _patientID.trimmed(), isHeparinOff);
     if ( vData.mAccepted ) {
         //TODO  Commented out for now
-        // It is needed to display NONE for the heparin items if the heparin set to off on Create Treatment Prameters screen.
+        // It is needed to display NONE for the heparin items if the heparin set to off on Create Treatment Parameters screen.
         // The problem is the data comes from the _TreatmentLog model
         // But if that model changes to have the NONE values, then the CloudSync or Cloud may reject the TxLog.
         // When the Cloud is updated we can as well update the entire flow.