chore: fix typos and small things (#19)

00 - Start Here.qmd

@@ -10,6 +10,7 @@ For convenience they're also linked below 👇
 
 
 Let's kick things off by loading some PyPI package data into a local PostgreSQL database!
+We will do this using DuckDB, yes you can do that! 
 
 ```{python}
 !duckdb < load.sql

01 - Getting Started.qmd

@@ -10,7 +10,7 @@ See the [README](https://github.com/ibis-project/ibis-tutorial#setup) for up-to-
 
 ## Download some data
 
-There are other ways to get example data, but we'll start by downloading the penguins dataset
+There are other ways to get example data, but we'll start by downloading the penguins dataset.
 $^1$.
 
 ```{python}
@@ -110,7 +110,7 @@ the important point is that Ibis is deferred.
 
 ## Interactive Mode
 
-Remmeber when we said Ibis is deferred? Sometimes you want eager execution so
+Remember when we said Ibis is deferred? Sometimes you want eager execution so
 you can explore a dataset.  For most of this tutorial, we'll turn on
 `interactive` mode, where Ibis will eagerly execute as much of the query as it
 needs to in order to show you the first 10 rows of the result.
@@ -243,7 +243,7 @@ penguins.drop("sex", penguins.year)
 Everything we've seen so far has been subtractive -- removing rows or columns.
 What about _adding_ columns?
 
-That's what `mutate` is for!  You can create a new column -- either as a
+That's what `mutate` is for! You can create a new column -- either as a
 function of other existing columns (for example, converting units):
 
 ```{python}
@@ -355,7 +355,7 @@ ibis.to_sql(penguins_imperial_select)
 
 In practice, small differences in the generated SQL don't make a difference.
 Any modern SQL execution engine will optimize variations to the same set of
-operations and there will be no measureable performance difference.
+operations and there will be no measurable performance difference.
 
 ## Order By
 

02 - Ibis and the Python Ecosystem.qmd

@@ -118,7 +118,7 @@ and returns an aggregate value constructed from columns in that table. The
 the need to create an intermediate python variable.
 
 Another way of spelling this (one some might consider nicer syntax) is through
-usage of ibis's `_` API. This is a "magical" object that constructs "deferred
+the usage of ibis's `_` API. This is a "magical" object that constructs "deferred
 expressions". Everywhere you see `_` in the expression you should read "the
 current table (`self`) in the method being called".
 
@@ -297,7 +297,10 @@ Depending on the library, this may work through a few mechanisms:
 
 ---
 
-For example, here we demonstrate passing an `ibis.Table` to the `altair` plotting library. Notice that you don't have to manually call any of the `to_*` methods yourself! This is because `altair` supports anything that implements the `__dataframe__` protocol as input, which means it can accept an `ibis.Table` directly.
+For example, here we demonstrate passing an `ibis.Table` to the `altair` plotting
+library. Notice that you don't have to manually call any of the `to_*` methods
+yourself! This is because `altair` supports anything that implements the `__dataframe__`
+protocol as input, which means it can accept an `ibis.Table` directly.
 
 ```{python}
 import altair as alt