Correct two typos (#345)

docs/src/index.md

@@ -346,7 +346,7 @@ we say that a `MatrixTable` iterates our own custom row type, `MatrixRow`. `Matr
 `Tables.AbstractRow`, which provides interface implementations for several useful behaviors (indexing,
 iteration, property-access, etc.); essentially it makes our custom `MatrixRow` type more convenient to work with.
 
-Implementing the `Tables.AbstractRow` interface is straightfoward, and very similar to our implementation
+Implementing the `Tables.AbstractRow` interface is straightforward, and very similar to our implementation
 of `Tables.AbstractColumns` previously (i.e. the same methods for `getcolumn` and `columnnames`).
 
 And that's it. Our `MatrixTable` type is now a fully fledged, valid Tables.jl source and can be used throughout

src/Tables.jl

@@ -439,7 +439,7 @@ as well as provide a convenient "structural" type for code generation.
 
 To get a table's schema, one can call `Tables.schema` on the result of `Tables.rows` or `Tables.columns`,
 but also note that a table may return `nothing`, indicating that its column names and/or column element types
-are unknown (usually not inferrable). This is similar to the `Base.EltypeUnknown()` trait for iterators
+are unknown (usually not inferable). This is similar to the `Base.EltypeUnknown()` trait for iterators
 when `Base.IteratorEltype` is called. Users should account for the `Tables.schema(tbl) => nothing` case
 by using the properties of the results of `Tables.rows(x)` and `Tables.columns(x)` directly.