Add journey images

Author: schnuerle

modes/car-share.md

@@ -42,23 +42,11 @@ _See more available trip and fare attributes for any mode used in the [trips obj
 
 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.
 
-Example 1: customer makes a reservation and company delivers vehicle to customer, then one trip point-to-point by customer, ending reservation at destination
-```
-<-                 Journey                ->
-<-  Trip: reservation -><-  Trip: private ->
-```
-
-Example 2: Customer reservation for multiple days with trips for errands, gas, entertainment, etc
-```
-<-                                           Journey                                         ->
-<- Trip: private -><- Trip: private -><- Trip: private -><- Trip: private -><- Trip: private ->
-```
-
-Example 3: one trip point-to-point with an employee moving the vehicle to a new location for maintenance
-```
-<-    Journey  ->
-<- Trip: empty ->
-```
+- **Example 1**: customer makes a reservation and company delivers vehicle to customer, then one trip point-to-point by customer, ending reservation at destination
+- **Example 2**: Customer reservation for multiple days with trips for errands, gas, entertainment, etc
+- **Example 3**: one trip point-to-point with an employee moving the vehicle to a new location for maintenance
+
+![Journey Diagram](https://i.imgur.com/FHxQLps.png)
 
 [Top][toc]
 

modes/delivery-robots.md

@@ -46,27 +46,17 @@ _See more available trip and fare attributes for any mode used in the [trips obj
 
 The `journey_id` field shall have a consistent value in overlapping trips. Journeys may be point-to-point, multi-segment, or multi-segment overlapping.
 
-Example 1: delivery to a single location, then return
-```
-<-                  Journey               ->
-<- Trip: delivery -><-    Trip: return    ->
-```
+- **Example 1**: delivery to a single location, then return
+- **Example 2**: three overlapping delivery trips in the same journey
 
-Example 2: three overlapping delivery trips in the same journey
-```
-<-                                 Journey                                  ->
-<- Trip: delivery ->
-                    <- Trip: delivery ->
-                                        <- Trip: delivery -><- Trip: return ->
-```
+![Journey Diagram](https://i.imgur.com/Mx8jVQq.png)
 
 [Top][toc]
 
 ### Journey Attributes
 
 The `journey_attributes` array is not used in this mode.
 
-- ...
 
 [Top][toc]
 

modes/passenger-services.md

@@ -46,19 +46,10 @@ _See more available trip and fare attributes for any mode used in the [trips obj
 
 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.
 
-Example 1: one private trip with reservation, then return to depot
-```
-<-                            Journey                           ->
-<- Trip: reservation -><-    Trip: private    -><- Trip: empty  ->
-```
+- **Example 1**: one private trip with reservation, then return to depot
+- **Example 2**: three shared trips, some overlapping
 
-Example 2: three shared trips, some overlapping
-```
-<-                            Journey                           ->
-<- Trip: reservation -><- Trip: shared ->
-            <- Trip: reservation -><- Trip: shared ->
-                         <- Trip: reservation -><- Trip: shared ->
-```
+![Journey Diagram](https://i.imgur.com/ciNnDKC.png)
 
 [Top][toc]