GITBOOK-gitbook-chronotrains-23: No subject

gitbook/tools/chronotrains/README.md

@@ -107,31 +107,35 @@ While Ukraine is marked as available on the map, it may be incomplete. Make sure
 
 Chronotrains.com includes a caveat [that the travel times are based on estimates only provided by Deutsche Bahn data](https://www.chronotrains.com/en/8) (Under FAQs). Actual arrival times may not always match. Therefore it is important to use this platform for estimates. 
 
-3. **Local Transit Exclusion**
+3. **Adding Connections (“Edges”) Between “Closed Stations” Based on Assumed Walking Speed**
 
-According to the tool provider [here](https://github.com/benjamintd/chronotrains), "Because local transit is not included for most cities, there are no journeys available between different stations that can actually be connected by bus, bike, or on foot."
+According to its [GitHub page](https://github.com/benjamintd/chronotrains), “closed stations” and “assumed speed” are defined as follows:
 
-Tool does not show options involving connections by local transit methods such as buses, bikes, or walking. Specifically, it would not display a journey where:
+**Close stations:** If two stations are close to each other (less than 10 km/6.2 mi apart),  the system will add a connection between them, and that connection is then reflected on the map. 
 
-a. The train stops at point B and does not go directly to point D. 
+**Assumed speed:** The system also assumes that you can walk/travel between these stations at a speed of 9/km/h (5.59 mph) - which is described as [“faster than walking but slower than biking.”](https://github.com/benjamintd/chronotrains) 
 
-b. You could take a bus or bike from point B to point C. 
+It is important to note that this speed can be variable from person to person and that this is an average estimate. So when looking at the data on Chronotrains, keep these limitations in mind. 
 
-c. From point C, you could catch another train to reach point D. 
+4. **Local Transit Exclusion**
 
-These types of multi-modal journeys, which involve switching from a train to a bus or bike and then back to a train, are not included in the dataset.
+According to the tool provider [here](https://github.com/benjamintd/chronotrains), "Because local transit is not included for most cities, there are no journeys available between different stations that can actually be connected by bus, bike, or on foot."
 
-4. **Adding Connections (“Edges”) Between “Closed Stations” Based on Assumed Walking Speed**
+The tool does not show options involving connections by local transit methods such as buses, bikes, or walking.
 
-According to its [GitHub page](https://github.com/benjamintd/chronotrains), “closed stations” and “assumed speed” are defined as follows:
+Specifically, as mentioned above, _if two locations are more than 10 km/6.2 mi apart_, it will not display a journey/connection. For instance, if a user wants to go from Point B to Point D.
 
-**Close stations:** If two stations are close to each other (less than 10 km/6.2 mi apart),  the system will add a connection between them, and that connection is then reflected on the map. 
+a. The train stops at point B and does not go directly to point D. 
 
-**Assumed speed:** The system also assumes that you can walk/travel between these stations at a speed of 9/km/h (5.59 mph) - which is described as [“faster than walking but slower than biking.”](https://github.com/benjamintd/chronotrains) 
+b. You could take a bus or bike from point B to point C. 
 
-It is important to note that this speed can be variable from person to person and that this is an average estimate. So when looking at the data on Chronotrains, keep these limitations in mind. 
+c. From point C, you could catch another train to reach point D.
 
-5. **Assumed Interchange Time**
+If the distance between Point B and Point C (where the user intends to get a connecting train) is more than 10 km/6.2 mi apart, then it will not appear on the map.
+
+These types of multi-modal journeys, which involve switching from a train to a bus or bike and then back to a train, are not included in the dataset.
+
+4. **Assumed Interchange Time**
 
 According to its [GitHub page](https://github.com/benjamintd/chronotrains), when switching from one train to another, the system assumes it takes 20 minutes. Since this can be variable depending on the person, the data should be taken as an estimate and needs to be cross-checked with other train schedules. 
 
@@ -163,8 +167,6 @@ Chronotrains data should be treated as an estimate or an investigative lead that
 
 If less frequently traveled routes are underrepresented, the overall dataset might not accurately reflect precise travel estimates. However, this does not drastically compromise the overall quality and reliability of Chronotrains' data. These travel estimates can still be valuable, particularly when coupled with mitigation strategies such as regularly verifying data from multiple reliable sources, including real-time updates and local transit information.
 
-
-
 ## Guides and articles
 
 A description and demo for the tool, including an interview with the tool provider: [https://www.youtube.com/watch?v=3ODcetbkq7U](https://www.youtube.com/watch?v=3ODcetbkq7U)