Improved modes cross linking

Author: schnuerle

modes/car-share.md

@@ -36,6 +36,8 @@ The short name identifier for Car Share used across MDS is `car-share`.
 
 ## Trip Properties
 
+_See more available trip and fare attributes for any mode used in the [trips object](/data-types.md#trips)._
+
 ### Journey ID
 
 The `journey_id` field shall have a consistent value in overlapping trips for a single reservation period, e.g. trips taken by a customer between ignition states over the duration of their reservation. A reservation is the duration the customer has continuous exclusive access to the vehicle whether parked or in motion. Journeys may be point-to-point or multi-segment.
@@ -92,11 +94,9 @@ The `trip_attributes` array **may** have the following key value pairs:
 
 - `hail_type` (enumerated, required): `phone_dispatch`, `phone`, `text`, `app`
 - `app_name` (text, optional): name of the app used to reserve the trip which could be provider's app or 3rd party app
-- `permit_licence_number` (string, optional) - The permit licence number of the organization that dispatched the vehicle
+- `permit_license_number` (string, optional) - The permit license number of the organization that dispatched the vehicle
 - `driver_id` (string, optional): Universal identifier of a specific driver, static across operators, like a driver's license number, for company employees in `reservation` or `empty` trip types, not `private` trips. Could also be used as a lookup in an agency's internal driver system.
 
-_See more available trip attributes for any mode in the [trips endpoint](/provider#trips)._
-
 [Top][toc]
 
 ### Fare Attributes
@@ -114,12 +114,12 @@ The `fare_attributes` array **may** have the following key value pairs:
 - `taxes` (currency, optional) - amount of taxes paid for the ride
 - `surcharge` (currency, optional) - any surcharge pricing
 
-_See more available fare attributes for any mode in the [trips endpoint](/provider#trips)._
-
 [Top][toc]
 
 ## Vehicle Properties
 
+_See more available vehicle attributes and accessibility options for any mode used in the [vehicles object](/data-types.md#vehicles)._
+
 ### Vehicle Attributes
 
 The `vehicle_attributes` array **may** have the following key value pairs:
@@ -137,9 +137,7 @@ The `vehicle_attributes` array **may** have the following key value pairs:
 - `park_access` (boolean, optional) - access pass to a national/regional/municipal park system
 - `toll_transponder` (boolean, optional) - toll transponder for national/regional toll system
 - `phone_charger` (boolean, optional) - a place to charge your phone
-- `sunshade` (boolean, optional) - sunshade avaialable (i.e. for windshield)
-
-_See more available vehicle attributes for any mode in the [vehicles endpoint](/provider#vehicles)._
+- `sunshade` (boolean, optional) - sunshade available (i.e. for windshield)
 
 [Top][toc]
 

modes/delivery-robots.md

@@ -1,14 +1,14 @@
 # Mobility Data Specification: **Delivery Robots**
 
-<img src="https://i.imgur.com/f8iMepu.png" width="120" align="right" alt="MDS Modes - Delivey Robots" border="0">
+<img src="https://i.imgur.com/f8iMepu.png" width="120" align="right" alt="MDS Modes - Delivery Robots" border="0">
 
-**Delivey Robots** refers to autonomous and remotely driven goods delivery devices. There can be one or multiple orders on different trips at the same time. The state machine tracks the trip states of the orders separately from the vehicle state.  
+**Delivery Robots** refers to autonomous and remotely driven goods delivery devices. There can be one or multiple orders on different trips at the same time. The state machine tracks the trip states of the orders separately from the vehicle state.  
 
 See the [modes overview](/modes) for how the mode specific information below applies across MDS.
 
 ## Robots Vs Other Delivery Types
 
-Autonomous and remotely piloted delivery robots do not require a driver, whereas other forms of deliveries may, e.g. in a commerical or private car, truck, bike, etc. For this MDS release, this mode is limited to deliveries where a human driver is not on board the vehicle doing the delivery, and human passengers are not being transported. 
+Autonomous and remotely piloted delivery robots do not require a driver, whereas other forms of deliveries may, e.g. in a commercial or private car, truck, bike, etc. For this MDS release, this mode is limited to deliveries where a human driver is not on board the vehicle doing the delivery, and human passengers are not being transported. 
 
 ## Table of Contents
 
@@ -40,6 +40,8 @@ The short name identifier for deliveries used across MDS is `delivery-robots`.
 
 ## Trip Properties
 
+_See more available trip and fare attributes for any mode used in the [trips object](/data-types.md#trips)._
+
 ### Journey ID
 
 The `journey_id` field shall have a consistent value in overlapping trips. Journeys may be point-to-point, multi-segment, or multi-segment overlapping.
@@ -94,16 +96,14 @@ The `trip_type` field **must** have one of the following enumerated values:
 
 The `trip_attributes` array **may** have the following key value pairs:
 
-- `driver_type` (ennum, required): type of driver operating the device: `human`, `semi-autonomous`, `autonomous`
-- `driver_id` (UUID, optional): consistent unique identifier of the privary driver. Could be based on software version or an internal human driver id.
+- `driver_type` (enum, required): type of driver operating the device: `human`, `semi-autonomous`, `autonomous`
+- `driver_id` (UUID, optional): consistent unique identifier of the primary driver. Could be based on software version or an internal human driver id.
 - `app_name` (text, optional): name of the app used to reserve the trip which could be provider's app or 3rd party app
 - `request_time` (timestamp, optional): when the customer requested the trip
 - `has_payload` (boolean, optional): is there any payload for any delivery included in the device at trip start. 1 = loaded, 0 = empty
-- `range` (interger, optional): estimated range in meters based on energy levels in device at trip start
+- `range` (integer, optional): estimated range in meters based on energy levels in device at trip start
 - `identification_required` (boolean, optional): does the cargo require providing customer identification before trip start or upon delivery?
 
-_See more available trip attributes for any mode in the [trips endpoint](/provider#trips)._
-
 [Top][toc]
 
 ### Fare Attributes
@@ -113,12 +113,12 @@ The `fare_attributes` array **may** have the following key value pairs:
 - `payment_type` (enumerated, optional): `cash`, `mobile`, `voucher`, `paratransit`, `no payment`, `test`
 - `price` (currency, optional): Total price of the order
 
-_See more available fare attributes for any mode in the [trips endpoint](/provider#trips)._
-
 [Top][toc]
 
 ## Vehicle Properties
 
+_See more available vehicle attributes and accessibility options for any mode used in the [vehicles object](/data-types.md#vehicles)._
+
 ### Vehicle Attributes
 
 The `vehicle_attributes` array **may** have the following key value pairs:
@@ -138,8 +138,6 @@ The `vehicle_attributes` array **may** have the following key value pairs:
 - `top_speed` (integer, optional): theoretical top speed in meters per second of the device
 - `storage_capacity` (integer, optional): cubic centimeters of cargo space available not including any cargo
 
-_See more available vehicle attributes for any mode in the [vehicles endpoint](/provider#vehicles)._
-
 [Top][toc]
 
 ### Accessibility Options
@@ -289,7 +287,7 @@ When there is only one trip ongoing, `trip_state == vehicle_state`
 
 In cases where there are multiple trips ongoing, please follow the trip state model pseudocode for determining what the vehicle state should be:
 ```
-t = for the one vehicle, all on-going trips which are 'delivey' or undefined trips (we do not take into account 'roaming', 'return' or 'advertising' trips)
+t = for the one vehicle, all on-going trips which are 'delivery' or undefined trips (we do not take into account 'roaming', 'return' or 'advertising' trips)
 v = vehicle state
 if t.any(state == ‘stopped’):
     v = ‘stopped’ 

modes/micromobility.md

@@ -36,6 +36,8 @@ The short name identifier for Micromobility used across MDS is `micromobility`.
 
 ## Trip Properties
 
+_See more available trip and fare attributes for any mode used in the [trips object](/data-types.md#trips)._
+
 ### Journey ID
 
 The `journey_id` field is not used in this mode. Trips are point-to-point.
@@ -68,30 +70,26 @@ The `trip_type` field **may** have one of the following values:
 
 The `trip_attributes` array is not used in this mode.
 
-_See more available trip attributes for any mode in the [trips endpoint](/provider#trips)._
-
 [Top][toc]
 
 ### Fare Attributes
 
 The `fare_attributes` array is not used in this mode.
 
-_See more available fare attributes for any mode in the [trips endpoint](/provider#trips)._
-
 [Top][toc]
 
 ## Vehicle Properties
 
 ### Vehicle Attributes
 
+_See more available vehicle attributes and accessibility options for any mode used in the [vehicles object](/data-types.md#vehicles)._
+
 The `vehicle_attributes` array **may** have the following key value pairs:
 
 - `year` (integer, optional)
 - `make` (string, optional)
 - `model` (string, optional)
 
-_See more available vehicle attributes for any mode in the [vehicles endpoint](/provider#vehicles)._
-
 [Top][toc]
 
 ### Accessibility Options

modes/passenger-services.md

@@ -40,6 +40,8 @@ The short name identifier for Passenger Services used across MDS is `passenger-s
 
 ## Trip Properties
 
+_See more available trip and fare attributes for any mode used in the [trips object](/data-types.md#trips)._
+
 ### Journey ID
 
 The `journey_id` field shall have a consistent value in overlapping trips, e.g. "pooled" or "shared" rides with different start and/or end locations. Journeys may be point-to-point, multi-segment, or multi-segment overlapping.
@@ -107,8 +109,6 @@ The `trip_attributes` array **may** have the following key value pairs:
 - `wheelchair_transported` (boolean, optional) - was a wheelchair transported as part of this trip?
 - `cancellation_reason` (String, Conditionally Required): The reason why a *driver* cancelled a reservation. (required if a driver cancelled a trip, and a `driver_cancellation` event_type was part of the trip) 
 
-_See more available trip attributes for any mode in the [trips endpoint](/provider#trips)._
-
 [Top][toc]
 
 ### Fare Attributes
@@ -130,12 +130,12 @@ The `fare_attributes` array **may** have the following key value pairs:
 - `driver_trip_pay` (currency, optional) - The payment the driver received for the trip 
 - `rate_code_id` (enumerated, optional) - one of `meter_fare`, `shared`, `out_of_town`, `disabled`, `upfront_pricing`, `promo_rate`
 
-_See more available fare attributes for any mode in the [trips endpoint](/provider#trips)._
-
 [Top][toc]
 
 ## Vehicle Properties
 
+_See more available vehicle attributes and accessibility options for any mode used in the [vehicles object](/data-types.md#vehicles)._
+
 ### Vehicle Attributes
 
 The `vehicle_attributes` array **may** have the following key value pairs:
@@ -149,8 +149,6 @@ The `vehicle_attributes` array **may** have the following key value pairs:
 - `license_plate` (string, optional) - the registered vehicle license/number/registration plate identifier on the vehicle
 - `inspection_date` (date YYYY-MM-DD, optional) - the date of the last inspection of the vehicle
 
-_See more available vehicle attributes for any mode in the [vehicles endpoint](/provider#vehicles)._
-
 [Top][toc]
 
 ### Accessibility Options