review: Correct typos in comments related to itinerary normalization

t2gran · t2gran · commit a9c6fc9ffca6 · 2025-10-29T15:39:32.000+01:00
diff --git a/application/src/main/java/org/opentripplanner/model/plan/Itinerary.java b/application/src/main/java/org/opentripplanner/model/plan/Itinerary.java
@@ -94,8 +94,8 @@ public class Itinerary implements ItinerarySortKey {
   Itinerary(ItineraryBuilder builder) {
     this.legs = List.copyOf(builder.legs);
 
-    // Normalize (round to seconds) to make sure insignificant small diffrenses does not
-    // have an efect when comparing itineraries in the filter-chain and in paging
+    // Normalize (round to seconds) to make sure insignificant small differences do not
+    // have an effect when comparing itineraries in the filter-chain and in paging
     this.generalizedCost = builder.calculateGeneralizedCostWithoutPenalty().normalize();
     this.generalizedCost2 = builder.generalizedCost2;
 
diff --git a/application/src/main/java/org/opentripplanner/model/plan/paging/cursor/PageCursorSerializer.java b/application/src/main/java/org/opentripplanner/model/plan/paging/cursor/PageCursorSerializer.java
@@ -53,9 +53,9 @@ public static String encode(PageCursor cursor) {
       .withEnum(SORT_ORDER_FIELD, cursor.originalSortOrder());
 
     if (cursor.containsItineraryPageCut()) {
-      // Note! For this to work properly we needt to preserve the same presission for time
-      // and cost, that we use for comparing itnineraries in the filter-chain. This is enforced
-      // when creating a itinerary - cost and times are normilized to seconds resolution.
+      // Note! For this to work properly we need to preserve the same precision for time
+      // and cost, that we use for comparing itineraries in the filter-chain. This is enforced
+      // when creating an itinerary - cost and times are normalized to seconds resolution.
       var cut = cursor.itineraryPageCut();
       tokenBuilder
         .withBoolean(CUT_ON_STREET_FIELD, cut.isStreetOnly())
