From cadfe72a817de11d4a085afe19b932230b5e992b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Adriana=20Ceri=C4=87?=
 <62163307+AdrianaCeric@users.noreply.github.com>
Date: Wed, 13 Dec 2023 17:24:17 -0500
Subject: [PATCH] docs: fix grammar

---
 docs/user/editor/fares.md     | 8 +++++---
 docs/user/editor/routes.md    | 2 +-
 docs/user/editor/schedules.md | 1 +
 docs/user/editor/stops.md     | 2 +-
 4 files changed, 8 insertions(+), 5 deletions(-)

diff --git a/docs/user/editor/fares.md b/docs/user/editor/fares.md
index 1c545e5cb..358cde39e 100644
--- a/docs/user/editor/fares.md
+++ b/docs/user/editor/fares.md
@@ -1,5 +1,7 @@
 # Fares
 
+## Fares Overview
+
 ### Fare attributes
 
 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
 
 To begin editing fares, click the fare ticket button on the lefthand navigation bar (outlined in red).
 
-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).
+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).
 
 ![fare-tab](https://datatools-builds.s3.amazonaws.com/docs/fares/fare-tab.png)
 
 ### Edit fare attributes
-In the `Attributes` tab, required and optional information about the fare can be inputted, like `fare_id`, `price` and `currency_type`.
+In the `Attributes` tab, required and optional information about the fare can be entered, like `fare_id`, `price` and `currency_type`.
 
 **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.**
 
 ### Edit fare rules
 
-To define fare rules, you must first create fare zones, which is explained in the next section.
+To define fare rules, you must first create fare zones, which are explained in the next section.
 
 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:
 
diff --git a/docs/user/editor/routes.md b/docs/user/editor/routes.md
index 3b7f981ef..204fbb500 100644
--- a/docs/user/editor/routes.md
+++ b/docs/user/editor/routes.md
@@ -38,7 +38,7 @@ The following fields are optional:
 - **Route branding URL:** A link to a webpage with route branding information
 - **Route branding asset:** A route image
 
-Once all the required fields, and any of the desired optional fields, are filled in click `Save`.
+Once all the required fields and any of the desired optional fields are filled in, click `Save`.
 
 **Note:** as with all newly created items (except patterns), the new route will not be saved until the save icon (💾) is clicked.
 
diff --git a/docs/user/editor/schedules.md b/docs/user/editor/schedules.md
index d48aa1e70..8d6c92b8c 100644
--- a/docs/user/editor/schedules.md
+++ b/docs/user/editor/schedules.md
@@ -1,5 +1,6 @@
 # Schedules/Calendars
 
+## Schedule and Calendar Overview
 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:
 
 ![calendar-tab](https://datatools-builds.s3.amazonaws.com/docs/schedules/calendar-tab.png)
diff --git a/docs/user/editor/stops.md b/docs/user/editor/stops.md
index 2f0f2dc3f..fda0561b0 100644
--- a/docs/user/editor/stops.md
+++ b/docs/user/editor/stops.md
@@ -30,7 +30,7 @@ Optionally, additional parameters can be included such as:
 - **Zone ID (`zone_id`):** The fare zone for a stop.
 - **Stop Timezone (`stop_timezone`):** Timezone of the stop.
 - **Level ID (`level_id`):** Level of the location.
-- **Platform Code (`platform_code`):** Code that identifies the platform for a stop. For stations with multiple platforms.
+- **Platform Code (`platform_code`):** Code that identifies the platform for a stop. Used with stations that have multiple platforms.
 - **Parent Station (`parent_station`):** Defines the hierarchy of stops in `stops.txt`.
 - **Wheelchair Boarding (`wheelchair_boarding`):** A value (0, 1, or 2) that identifies whether wheelchair boardings are possible at the stop.