Fix lowercase all files 2026 03 02 (#659)

Author: fredericsimard

…/en/assets/TimeVariableFares-OffPeak.png …/en/assets/timevariablefares-offpeak.pngdocs/en/assets/TimeVariableFares-OffPeak.png renamed to docs/en/assets/timevariablefares-offpeak.png docs/en/assets/TimeVariableFares-OffPeak.png renamed to docs/en/assets/timevariablefares-offpeak.png

@@ -59,4 +59,4 @@ GTFS is primarily concerned with passenger information. That is, the spec should
 When adding features to the specification, we want to avoid making changes that will make existing feeds invalid. We don't want to create more work for existing feed publishers until they want to add capabilities to their feeds. Also, whenever possible, we want existing parsers to be able to continue to read the older parts of newer feeds.
 
 #### Speculative features are discouraged
-Every new feature adds complexity to the creation and reading of feeds. Therefore, we want to take care to only add features that we know to be useful. Ideally, any proposal will have been tested by generating data for a real transit system that uses the new feature and writing software to read and display it. Note that the GTFS readily allows for extensions to the format through the addition of extra columns and files that are ignored by the official parsers & validators, so proposals can be easily prototyped and tested on existing feeds.
+Every new feature adds complexity to the creation and reading of feeds. Therefore, we want to take care to only add features that we know to be useful. Ideally, any proposal will have been tested by generating data for a real transit system that uses the new feature and writing software to read and display it. Note that the GTFS readily allows for extensions to the format through the addition of extra columns and files that are ignored by the official parsers & validators, so proposals can be easily prototyped and tested on existing feeds.