review: Update src/main/java/org/opentripplanner/model/transfer/Trans…

…ferPoint.java

Co-authored-by: Hannes Junnila <[email protected]>

src/main/java/org/opentripplanner/model/transfer/TransferPoint.java

@@ -15,32 +15,32 @@
  *     <p>This is the least specific type, and is overridden if a more specific type exist.
  *   </li>
  *   <li>
- *     {@link StationTransferPoint} This apply to all trip stopping at a stop part of the given
+ *     {@link StationTransferPoint} This applies to all trips stopping at a stop part of the given
  *     station.
  *     <p>The specificity-ranking is above {@link StationTransferPoint}s and less than
  *     {@link RouteStationTransferPoint}.
  *   </li>
  *   <li>
  *     A {@link RouteStationTransferPoint} is a from/to point for a Route at the given stop. This
- *     only exist in GTFS, not in the Nordic NeTex profile.
+ *     only exists in GTFS, not in the Nordic NeTex profile.
  *
  *     <p>The specificity-ranking is above {@link StopTransferPoint}s and less than
  *     {@link RouteStopTransferPoint}.
  *   </li>
  *   <li>
  *     A {@link RouteStopTransferPoint} is a from/to point for a Route at the given station. This
- *     only exist in GTFS, not in the Nordic NeTex profile.
+ *     only exists in GTFS, not in the Nordic NeTex profile.
  *
  *     <p>The specificity-ranking is above {@link RouteStationTransferPoint}s and less than
  *     {@link TripTransferPoint}.
  *   </li>
  *   <li>
  *     {@link TripTransferPoint} A transfer from/to a Trip at the given stop position(not stop).
  *     The GTFS Transfers may specify a transfer from/to a trip and stop/station. But in OTP we
- *     map the stop to a stop position in pattern. The OTP model {@link TripTransferPoint} do NOT
+ *     map the stop to a stop position in pattern. The OTP model {@link TripTransferPoint} does NOT
  *     reference the stop/station, but the {@code stopPositionInPattern} instead. There is two
  *     reasons for this. In NeTEx the an interchange is from a trip and stop-point, so this model
- *     fits better with NeTEx. The second reson is that real-time updates could invalidate the
+ *     fits better with NeTEx. The second reason is that real-time updates could invalidate the
  *     trip-transfer-point, since the stop could change to another platform(common for railway
  *     stations). To account for this the RT-update would need to patch the trip-transfer-point.
  *     We simplify the RT-updates by converting the stop to a stop-position-in-pattern.