Skip to content

Commit cadfe72

Browse files
committed
docs: fix grammar
1 parent eddec9a commit cadfe72

File tree

4 files changed

+8
-5
lines changed

4 files changed

+8
-5
lines changed

โ€Ždocs/user/editor/fares.mdโ€Ž

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Fares
22

3+
## Fares Overview
4+
35
### Fare attributes
46

57
Fare attributes describe the basic information about a fare including the price, currency type and transfer information. See the [GTFS specification fare attribute reference](https://gtfs.org/schedule/reference/#fare_attributestxt) for more information.
@@ -12,18 +14,18 @@ Fare rules describe how much riders pay to use a transit system, based on factor
1214

1315
To begin editing fares, click the fare ticket button on the lefthand navigation bar (outlined in red).
1416

15-
Choose a fare from the list to begin editing. To create a new fare, click `+ New fare`, or, if this is the first fare being created for this feed, select `+ Create first fare` (highlighted in yellow).
17+
Choose a fare from the list to begin editing. To create a new fare, click `+ New fare`, or, if this is the first fare being created for this feed, click `+ Create first fare` (highlighted in yellow).
1618

1719
![fare-tab](https://datatools-builds.s3.amazonaws.com/docs/fares/fare-tab.png)
1820

1921
### Edit fare attributes
20-
In the `Attributes` tab, required and optional information about the fare can be inputted, like `fare_id`, `price` and `currency_type`.
22+
In the `Attributes` tab, required and optional information about the fare can be entered, like `fare_id`, `price` and `currency_type`.
2123

2224
**Note: Be sure to click the save button (๐Ÿ’พ) after changes to fare attributes or fare rules are made. Clicking save after adding attributes will allow you to edit fare rules.**
2325

2426
### Edit fare rules
2527

26-
To define fare rules, you must first create fare zones, which is explained in the next section.
28+
To define fare rules, you must first create fare zones, which are explained in the next section.
2729

2830
To edit fare rules, you must first create and save a fare with attributes. After choosing a fare, click the `Rules` tab and define one or more rules for this fare using the following types:
2931

โ€Ždocs/user/editor/routes.mdโ€Ž

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ The following fields are optional:
3838
- **Route branding URL:** A link to a webpage with route branding information
3939
- **Route branding asset:** A route image
4040

41-
Once all the required fields, and any of the desired optional fields, are filled in click `Save`.
41+
Once all the required fields and any of the desired optional fields are filled in, click `Save`.
4242

4343
**Note:** as with all newly created items (except patterns), the new route will not be saved until the save icon (๐Ÿ’พ) is clicked.
4444

โ€Ždocs/user/editor/schedules.mdโ€Ž

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
# Schedules/Calendars
22

3+
## Schedule and Calendar Overview
34
The schedule editor allows for the creation of trips/frequencies for any combination of route, pattern, and/or calendar. To manage or edit schedules or exceptions, navigate to the `Calendar` tab located in the left-hand menu:
45

56
![calendar-tab](https://datatools-builds.s3.amazonaws.com/docs/schedules/calendar-tab.png)

โ€Ždocs/user/editor/stops.mdโ€Ž

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Optionally, additional parameters can be included such as:
3030
- **Zone ID (`zone_id`):** The fare zone for a stop.
3131
- **Stop Timezone (`stop_timezone`):** Timezone of the stop.
3232
- **Level ID (`level_id`):** Level of the location.
33-
- **Platform Code (`platform_code`):** Code that identifies the platform for a stop. For stations with multiple platforms.
33+
- **Platform Code (`platform_code`):** Code that identifies the platform for a stop. Used with stations that have multiple platforms.
3434
- **Parent Station (`parent_station`):** Defines the hierarchy of stops in `stops.txt`.
3535
- **Wheelchair Boarding (`wheelchair_boarding`):** A value (0, 1, or 2) that identifies whether wheelchair boardings are possible at the stop.
3636

0 commit comments

Comments
ย (0)