Fix a few typos

libsqlite3-sys/build.rs

@@ -5,7 +5,7 @@ use std::path::Path;
 /// `cfg!(windows)`, since the latter does not properly handle cross-compilation
 ///
 /// Note that there is no way to know at compile-time which system we'll be
-/// targetting, and this test must be made at run-time (of the build script) See
+/// targeting, and this test must be made at run-time (of the build script) See
 /// https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-build-scripts
 fn win_target() -> bool {
     env::var("CARGO_CFG_WINDOWS").is_ok()
@@ -668,7 +668,7 @@ mod loadable_extension {
         // (2) `#define sqlite3_xyz sqlite3_api->abc` => `pub unsafe fn
         // sqlite3_xyz(args) -> ty {...}` for each `abc` field:
         for field in sqlite3_api_routines.fields {
-            let ident = field.ident.expect("unamed field");
+            let ident = field.ident.expect("unnamed field");
             let span = ident.span();
             let name = ident.to_string();
             if name == "vmprintf" || name == "xvsnprintf" || name == "str_vappendf" {

src/params.rs

@@ -41,7 +41,7 @@ use sealed::Sealed;
 /// - Using the [`rusqlite::params!`](crate::params!) macro, e.g.
 ///   `thing.query(rusqlite::params![1, "foo", bar])`. This is mostly useful for
 ///   heterogeneous lists where the number of parameters greater than 16, or
-///   homogenous lists of parameters where the number of parameters exceeds 32.
+///   homogeneous lists of parameters where the number of parameters exceeds 32.
 ///
 /// - For small homogeneous lists of parameters, they can either be passed as:
 ///
@@ -194,7 +194,7 @@ pub trait Params: Sealed {
 //
 // This sadly prevents `impl<T: ToSql, const N: usize> Params for [T; N]`, which
 // forces people to use `params![...]` or `rusqlite::params_from_iter` for long
-// homogenous lists of parameters. This is not that big of a deal, but is
+// homogeneous lists of parameters. This is not that big of a deal, but is
 // unfortunate, especially because I mostly did it because I wanted a simple
 // syntax for no-params that didnt require importing -- the empty tuple fits
 // that nicely, but I didn't think of it until much later.

src/statement.rs

@@ -1353,7 +1353,7 @@ mod test {
     fn test_error_offset() -> Result<()> {
         use crate::ffi::ErrorCode;
         let db = Connection::open_in_memory()?;
-        let r = db.execute_batch("SELECT CURRENT_TIMESTANP;");
+        let r = db.execute_batch("SELECT INVALID_FUNCTION;");
         match r.unwrap_err() {
             Error::SqlInputError { error, offset, .. } => {
                 assert_eq!(error.code, ErrorCode::Unknown);