Deployed 264424d to update-agenda-link with MkDocs 1.6.1 and mike 1.1.2

update-agenda-link/index.html

@@ -444,7 +444,7 @@ <h2 id="tides-specification">TIDES specification<a class="headerlink" href="#tid
 </ul>
 <h3 id="data-package">Data Package<a class="headerlink" href="#data-package" title="Permanent link"> ¶</a></h3>
 <p>Directories with TIDES data must contain metadata in a <a href="datapackage/"><code>datapackage.json</code></a> file in a format compliant with the <a href="datapackage/"><code>tides-datapackage-profile</code></a> of a <a href="https://specs.frictionlessdata.io/data-package/"><code>frictionless data package</code></a>.  </p>
-<p><a href="http://github.com/TIDES-transit/TIDES/tree/update-agenda-link/samples/template/TIDES/datapackage.json"><code>/samples/template/datapackage.json</code></a> has a template datapackage which can be used.</p>
+<p><a href="http://github.com/TIDES-transit/TIDES/tree/HEAD/samples/template/TIDES/datapackage.json"><code>/samples/template/datapackage.json</code></a> has a template datapackage which can be used.</p>
 <h2 id="sample-data">Sample Data<a class="headerlink" href="#sample-data" title="Permanent link"> ¶</a></h2>
 <p><a href="./samples">Sample data</a> can be found in the <code>/samples</code> directory, with one directory for each sample.</p>
 <h3 id="template">Template<a class="headerlink" href="#template" title="Permanent link"> ¶</a></h3>

update-agenda-link/samples/index.html

@@ -411,11 +411,11 @@ <h3 id="adding-examples">Adding Examples<a class="headerlink" href="#adding-exam
 <li><em>Include a README.md</em> in the base folder of your example with an overview so that it can be included in the documentation.</li>
 </ol>
 <h3 id="data-package">Data Package<a class="headerlink" href="#data-package" title="Permanent link"> ¶</a></h3>
-<p>TIDES sample data must include a <a href="../datapackage/"><code>datapackage.json</code></a> in the format specified by the <a href="http://github.com/TIDES-transit/TIDES/tree/update-agenda-link/spec/tides-datapackage-profile.json"><code>tides-data-package</code> json schema</a> (an extension of the <a href="https://specs.frictionlessdata.io/data-package/">frictionless data package</a>).  </p>
+<p>TIDES sample data must include a <a href="../datapackage/"><code>datapackage.json</code></a> in the format specified by the <a href="http://github.com/TIDES-transit/TIDES/tree/HEAD/spec/tides-datapackage-profile.json"><code>tides-data-package</code> json schema</a> (an extension of the <a href="https://specs.frictionlessdata.io/data-package/">frictionless data package</a>).  </p>
 <p>See:</p>
 <ul>
 <li><a href="../datapackage/">Full documentation on the <code>tides-data-package</code></a></li>
-<li><a href="http://github.com/TIDES-transit/TIDES/tree/update-agenda-link/samples/template/TIDES/datapackage.json">Example <code>tides-data-package</code> file</a></li>
+<li><a href="http://github.com/TIDES-transit/TIDES/tree/HEAD/samples/template/TIDES/datapackage.json">Example <code>tides-data-package</code> file</a></li>
 </ul>
 <h3 id="data-validation">Data validation<a class="headerlink" href="#data-validation" title="Permanent link"> ¶</a></h3>
 <p>Data with a valid <a href="#data-package"><code>datapackage.json</code></a> can be easily validated using the <a href="https://framework.frictionlessdata.io/">frictionless framework</a>, which can be installed and invoked as follows:</p>

update-agenda-link/tables/index.html

@@ -1077,7 +1077,7 @@ <h3 id="station-activities">Station Activities<a class="headerlink" href="#stati
 <h3 id="stop-visits">Stop Visits<a class="headerlink" href="#stop-visits" title="Permanent link"> ¶</a></h3>
 <p><em>stop_visits.schema.json</em></p>
 <p>Summarized boarding, alighting, arrival, departure, and other events (kneel engaged, ramp deployed, etc.) by trip and stop for each service date.</p>
-<p>Primary key: {<code>trip_id_performed</code>, <code>service_date</code>, <code>trip_stop_sequence</code>}</p>
+<p>Primary key: {<code>service_date</code>, <code>trip_id_performed</code>, <code>trip_stop_sequence</code>}</p>
 <table>
 <thead>
 <tr>
@@ -1311,7 +1311,7 @@ <h3 id="stop-visits">Stop Visits<a class="headerlink" href="#stop-visits" title=
 <h3 id="trips-performed">Trips Performed<a class="headerlink" href="#trips-performed" title="Permanent link"> ¶</a></h3>
 <p><em>trips_performed.schema.json</em></p>
 <p>Trips performed for each service date.</p>
-<p>Primary key: {<code>trip_id_performed</code>, <code>service_date</code>}</p>
+<p>Primary key: {<code>service_date</code>, <code>trip_id_performed</code>}</p>
 <table>
 <thead>
 <tr>
@@ -1641,7 +1641,7 @@ <h3 id="train-cars">Train Cars<a class="headerlink" href="#train-cars" title="Pe
 <h3 id="vehicle-train-cars">Vehicle Train Cars<a class="headerlink" href="#vehicle-train-cars" title="Permanent link"> ¶</a></h3>
 <p><em>vehicle_train_cars.schema.json</em></p>
 <p>Relationships between assets and vehicles.</p>
-<p>Primary key: {<code>train_car_id</code>, <code>vehicle_id</code>}</p>
+<p>Primary key: {<code>vehicle_id</code>, <code>train_car_id</code>}</p>
 <table>
 <thead>
 <tr>