Deployed bad81fce89 to dev-2.x in en with MkDocs 1.6.1 and mike 1.2.0.dev0

Author: OTP Bot

en/dev-2.x/Changelog/index.html

@@ -2546,7 +2546,8 @@ <h2 id="270-snapshot-under-development">2.7.0-SNAPSHOT (under development)</h2>
 <li>Don't use elevation data directly for ways with cutting=*, location=underground or indoor=yes tags in the default mapper <a href="https://github.com/opentripplanner/OpenTripPlanner/pull/6093">#6093</a></li>
 <li>Un-deprecate GTFS API's <code>planConnection</code>, deprecate <code>plan</code> <a href="https://github.com/opentripplanner/OpenTripPlanner/pull/6110">#6110</a></li>
 <li>Support for routing to Station centroid instead of child stops <a href="https://github.com/opentripplanner/OpenTripPlanner/pull/6047">#6047</a></li>
-<li>Add via to the Transmodel trip query and make a proper Raptor implementation for it <a href="https://github.com/opentripplanner/OpenTripPlanner/pull/6084">#6084</a>
+<li>Add via to the Transmodel trip query and make a proper Raptor implementation for it <a href="https://github.com/opentripplanner/OpenTripPlanner/pull/6084">#6084</a></li>
+<li>Fix GTFS-Flex duration offset and factor parsing when only one of them is set <a href="https://github.com/opentripplanner/OpenTripPlanner/pull/6138">#6138</a>
 <a href="AUTOMATIC_CHANGELOG_PLACEHOLDER_DO_NOT_REMOVE"></a></li>
 </ul>
 <h2 id="260-2024-09-18">2.6.0 (2024-09-18)</h2>

en/dev-2.x/Developers-Guide/index.html

@@ -1523,15 +1523,6 @@
     </span>
   </a>
 
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#code-comments" class="md-nav__link">
-    <span class="md-ellipsis">
-      Code Comments
-    </span>
-  </a>
-  
 </li>
 
           <li class="md-nav__item">
@@ -2354,14 +2345,6 @@ <h3 id="unit-tests-using-real-osm-data">Unit tests using real OSM data</h3>
    in <a href="../Preparing-OSM/">Preparing OSM</a></p>
 </li>
 </ol>
-<h3 id="code-comments">Code Comments</h3>
-<p>As a matter of <a href="http://github.com/opentripplanner/OpenTripPlanner/issues/93">policy</a>, all new
-methods, classes, and fields should include comments explaining what they are for and any other
-pertinent information. For Java code, the comments should use the
-<a href="http://java.sun.com/j2se/javadoc/writingdoccomments">JavaDoc conventions</a>. It is best to provide
-comments that not only explain <em>what</em> you did but also <em>why you did it</em> while providing some
-context. Please avoid including trivial Javadoc or the empty Javadoc stubs added by IDEs, such as
-<code>@param</code> annotations with no description.</p>
 <h3 id="itinerary-and-api-snapshot-tests">Itinerary and API Snapshot Tests</h3>
 <p>To test the itinerary generation, and the API there are snapshot test which save the result of the
 requests as <code>*.snap</code> JSON-like files. These are stored in git so that it is possible to compare to