diff --git a/chapters/jsonChapters.md b/chapters/jsonChapters.md
index e50d6e5..3d1db15 100644
--- a/chapters/jsonChapters.md
+++ b/chapters/jsonChapters.md
@@ -100,7 +100,7 @@ Here is what a very basic chapters file may look like:
 ```
 
 In this simple form, the chapter objects are treated as sequential just based on their index as a function of being
-ordered in ascending fashing based on their `startTime`.  In a very simple example such as this nothing is present except the `startTime`,
+ordered in ascending fashion based on their `startTime`.  In a very simple example such as this nothing is present except the `startTime`,
 `title`, and a few bits of optional meta-data.
 
 <br><br>
@@ -171,4 +171,4 @@ chapter list, but allows for different artwork to be shown:
 
 Clearly, when pulling in web based data there is the chance that this functionality could be used for tracking.  As a safeguard against that, apps
 using chapters are encouraged to prompt the user to acknowledge whether they trust the podcast in question before displaying the content.  Trusted
-podcasts can then be remembered for the future.
\ No newline at end of file
+podcasts can then be remembered for the future.