GITBOOK-gitbook-chronotrains-21: No subject

gitbook/tools/chronotrains/README.md

@@ -147,9 +147,13 @@ Chronotrains is best used in conjunction with other tools and other sources of i
 
 As mentioned above, Chronotrains uses data based on pre-scheduled train times and not real-time tracking. It includes this caveat under its FAQs section. As mentioned under the “Limitations” section, data are based on the user’s assumed walking speed and assumed duration for changing between trains. These variables can modify the estimates that the map shows. It is, therefore, important to disclose these limitations when using it as a tool for your investigations. 
 
-**Algorithmic Bias:**
+**Accuracy:**
+
+Chronotrains data should be treated as an estimate or an investigative lead that needs further verification. While Chronotrains uses established train schedule data, it's important to consider if there could be any bias within that data itself. For instance, if certain routes are less frequently traveled or have less up-to-date scheduling information, this could skew the results generated by Chronotrains. 
+
+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.
+
 
-While Chronotrains uses established train schedule data, it's important to consider if there could be any bias within that data itself. For instance, if certain routes are less frequently traveled or have less up-to-date scheduling information, this could skew the results generated by Chronotrains.
 
 ## Guides and articles