More on the journal, plus escalator hater in a large font

papers/JOURNAL_fmea_sw_hw/sw_hw_fmea.tex

@@ -682,17 +682,21 @@ use it in another one without complication.
 Later languages implemented object orientation
 which grouped functions and data together into modules called classes, where
 even the internal local variables of a class could be hidden from the 
-programmer using the class. For instance the internal workings of a binary~tree or linked~list do no need to be 
-accessed if you simply want to use a class in your program to store data: in this case
-the programmer would pick a ready written and well de-bugged data store class and simply use it.
+programmer using the class. 
+%
+For instance the internal workings of a binary~tree or linked~list do no need to be 
+accessed if one simply wants to use a class to store data: in this case
+the programmer would pick a ready written and well de-bugged data storage class and simply use it.
 %
 Software expanded in complexity faster than electronics,
-and to cope with this software languages developed modularity (function call trees, classes and finally distributed processing mechanisms).
+and to cope with this software languages developed modularity
+(function call trees, classes and finally distributed processing mechanisms).
 %
 FMEA has, by necessity, started to include some modular features but none yet
 have defined mechanisms for ensuring that all component failure modes
 are traceable from component to system level. % in the analysis of the module(s) that incorporate it.
-
+%
+That is to say the process is not rigorous.