diff --git a/episodes/00-sql-introduction.md b/episodes/00-sql-introduction.md
index aae78860..b76c015a 100644
--- a/episodes/00-sql-introduction.md
+++ b/episodes/00-sql-introduction.md
@@ -147,7 +147,7 @@ screen under Database Structure tab. Here you will see a list under "Tables." Ea
 we were exploring earlier. To see the contents of any table, right-click on it, and
 then click the "Browse Table" from the menu, or select the "Browse Data" tab next to the "Database Structure" tab and select the wanted table from the dropdown named "Table". This will
 give us a view that we're used to - a copy of the table. Hopefully this
-helps to show that a database is, in some sense, just a collection of tables,
+helps to show that a database is, in some sense, only a collection of tables,
 where there's some value in the tables that allows them to be connected to each
 other (the "related" part of "relational database").
 
diff --git a/episodes/03-sql-joins.md b/episodes/03-sql-joins.md
index 73918ee6..bebb19df 100644
--- a/episodes/03-sql-joins.md
+++ b/episodes/03-sql-joins.md
@@ -154,7 +154,7 @@ SELECT COUNT(*) FROM surveys;
 This is because, by default, SQL only returns records where the joining value
 is present in the joined columns of both tables (i.e. it takes the *intersection*
 of the two join columns). This joining behaviour is known as an `INNER JOIN`.
-In fact the `JOIN` keyword is simply shorthand for `INNER JOIN` and the two
+In fact the `JOIN` keyword is shorthand for `INNER JOIN` and the two
 terms can be used interchangeably as they will produce the same result.
 
 We can also tell the computer that we wish to keep all the records in the first