diff --git a/_datasets/septa-sms-transit.md b/_datasets/septa-sms-transit.md
index 69db25ab..14110f8e 100644
--- a/_datasets/septa-sms-transit.md
+++ b/_datasets/septa-sms-transit.md
@@ -20,7 +20,7 @@ notes: 'SEPTA SMS Transit enables users to request scheduled trip information vi
Finally, the SMS data can be accessed from an API. The data returned by the API
is currently text format, separated. The API can be accessed in the format:
- [https://www3.septa.org/sms/var1/var2/var3/var4/var5](https://www3.septa.org/sms/var1/var2/var3/var4/var5)
+ https://www3.septa.org/sms/var1/var2/var3/var4/var5
\[var1\] = stop id
\[var2\] = route id OR i/o for inbound/outbound
@@ -42,27 +42,27 @@ notes: 'SEPTA SMS Transit enables users to request scheduled trip information vi
but all travel is in one direction:
- [https://www3.septa.org/sms/20645/](https://www3.septa.org/sms/20645/)
+ https://www3.septa.org/sms/20645/
Returns the next 4 scheduled trolleys at 22nd St. Station. Note the results shows
trolleys regardless or route. To grep just a single route, for a multi-route, uni-directional stop, add another var:
- [https://www3.septa.org/sms/20645/13/](https://www3.septa.org/sms/20645/13/)
+ https://www3.septa.org/sms/20645/13/
Returns only the Route 13 trolleys at 22nd St. Station