Fixing compile errors due to unprintable ASCII character.

Source/OrientationLib/OrientationMath/OrientationTransforms.hpp

@@ -358,7 +358,7 @@ class OrientationTransforms
       T out = OMHelperType::multiply(ro, ro, 3);
       K ttl = OMHelperType::sum(out);
       ttl = sqrt(ttl);
-      if (fabs(ttl - 1.0L) > eps)
+      if (fabs(ttl - 1.0) > eps)
       {
         res.msg = "rotations:ro_check:: Rodrigues-Frank axis vector not normalized";
         res.result = -2;

Source/OrientationLib/Test/OrientationTransformsTest.cpp

@@ -649,7 +649,6 @@ void StartTest()
       {
         //  RunTestCase<float>(entry, 16);
         RunTestCase<double>(entry, 16);
-
       }
     }
   }

Source/Plugins/OrientationAnalysis/Documentation/OrientationAnalysisFilters/ConvertOrientations.md

@@ -32,9 +32,9 @@ If the angles fall outside of this range the **original** Euler Input data **WIL
 | Cubochoric                 | 3 | 5 | **Not Yet Implemented** |
 
 
-#### Precision Notes ###
+## Precision Notes ##
 
-While every effort has been made to ensure the correctness of each transformation algorithm certain situations may arise where the initial precision of the input data is not large enough for the algorithm to calculate an answer that is intuitive. The user should be acutely aware of their input data and if their data may cause these situations to occur. Combinations of Euler angles close to 0, 180 and 360 can cause these issues to be hit. For instance an Euler angle of [180, 56, 360] is symmetrically the same as [180, 56, 0] and due to calculation errors and round off errors converting that Euler angle between representations may not give the numerical answer the user was anticipating but will give a symmetrically equivalent angle.
+While every effort has been made to ensure the correctness of each transformation algorithm, certain situations may arise where the initial precision of the input data is not large enough for the algorithm to calculate an answer that is intuitive. The user should be acutely aware of their input data and if their data may cause these situations to occur. Combinations of Euler angles close to 0, 180 and 360 can cause these issues to be hit. For instance an Euler angle of [180, 56, 360] is symmetrically the same as [180, 56, 0] and due to calculation errors and round off errors converting that Euler angle between representations may not give the numerical answer the user was anticipating but will give a symmetrically equivalent angle.
 
 ## Parameters ##