fix spelling (#4069)

sqlx-postgres/src/any.rs

@@ -136,8 +136,8 @@ impl AnyConnectionBackend for PgConnection {
     ) -> BoxFuture<'c, sqlx_core::Result<AnyStatement>> {
         Box::pin(async move {
             let statement = Executor::prepare_with(self, sql, &[]).await?;
-            let colunn_names = statement.metadata.column_names.clone();
-            AnyStatement::try_from_statement(statement, colunn_names)
+            let column_names = statement.metadata.column_names.clone();
+            AnyStatement::try_from_statement(statement, column_names)
         })
     }
 

sqlx-postgres/src/message/sasl.rs

@@ -41,7 +41,7 @@ impl FrontendMessage for SaslInitialResponse<'_> {
 
         let response_len = i32::try_from(self.response.len()).map_err(|_| {
             err_protocol!(
-                "SASL Initial Response length too long for protcol: {}",
+                "SASL Initial Response length too long for protocol: {}",
                 self.response.len()
             )
         })?;

sqlx-postgres/src/migrate.rs

@@ -231,7 +231,7 @@ CREATE TABLE IF NOT EXISTS {table_name} (
             if migration.no_tx {
                 execute_migration(self, table_name, migration).await?;
             } else {
-                // Use a single transaction for the actual migration script and the essential bookeeping so we never
+                // Use a single transaction for the actual migration script and the essential bookkeeping so we never
                 // execute migrations twice. See https://github.com/launchbadge/sqlx/issues/1966.
                 // The `execution_time` however can only be measured for the whole transaction. This value _only_ exists for
                 // data lineage and debugging reasons, so it is not super important if it is lost. So we initialize it to -1

sqlx-postgres/src/options/pgpass.rs

@@ -173,8 +173,8 @@ fn find_next_field<'a>(line: &mut &'a str) -> Option<Cow<'a, str>> {
     let mut escaped_string = None;
     let mut last_added = 0;
 
-    let char_indicies = line.char_indices();
-    for (idx, c) in char_indicies {
+    let char_indices = line.char_indices();
+    for (idx, c) in char_indices {
         if c == ':' && !escaping {
             let (field, rest) = line.split_at(idx);
             *line = &rest[1..];

sqlx-postgres/src/types/geometry/polygon.rs

@@ -15,7 +15,7 @@ const BYTE_WIDTH: usize = mem::size_of::<f64>();
 /// Description: Polygon (similar to closed polygon)
 /// Representation: `((x1,y1),...)`
 ///
-/// Polygons are represented by lists of points (the vertexes of the polygon). Polygons are very similar to closed paths; the essential semantic difference is that a polygon is considered to include the area within it, while a path is not.
+/// Polygons are represented by lists of points (the vertices of the polygon). Polygons are very similar to closed paths; the essential semantic difference is that a polygon is considered to include the area within it, while a path is not.
 /// An important implementation difference between polygons and paths is that the stored representation of a polygon includes its smallest bounding box. This speeds up certain search operations, although computing the bounding box adds overhead while constructing new polygons.
 /// Values of type polygon are specified using any of the following syntaxes:
 ///