v0.2.55..v0.2.56 changeset NetworkMatch.cpp

diff --git a/hoot-core/src/main/cpp/hoot/core/conflate/network/NetworkMatch.cpp b/hoot-core/src/main/cpp/hoot/core/conflate/network/NetworkMatch.cpp
index 9bb9b04..8007e62 100644
--- a/hoot-core/src/main/cpp/hoot/core/conflate/network/NetworkMatch.cpp
+++ b/hoot-core/src/main/cpp/hoot/core/conflate/network/NetworkMatch.cpp
@@ -41,11 +41,6 @@ namespace hoot
 
 HOOT_FACTORY_REGISTER(Match, NetworkMatch)
 
-NetworkMatch::NetworkMatch() :
-Match()
-{
-}
-
 NetworkMatch::NetworkMatch(const ConstNetworkDetailsPtr& details, ConstEdgeMatchPtr edgeMatch,
   double score, ConstMatchThresholdPtr mt, double scoringFunctionMax,
   double scoringFunctionCurveMidpointX, double scoringFunctionCurveSteepness) :
@@ -100,8 +95,8 @@ void NetworkMatch::_discoverWayPairs(ConstOsmMapPtr map, ConstEdgeMatchPtr edgeM
   // Unfortunately, this can be a very coarse estimate. Something like Frechet distance may
   // improve this matching. - see #3158
 
-  // Its not why we would allow node/way match pairs here, but forcing way/way match pairs does
-  // lead to worse snapping at some road intersections as was found while working on #3386.
+  // Its not obvious why we would allow node/way match pairs here, but forcing way/way match pairs
+  // does lead to worse snapping at some road intersections as was found while working on #3386.
   // NetworkMatchCreator does have a candidate check for highways, so its also not completely
   // clear when nodes would be getting into the mix here.