Update CHANGES.md; spelling

CHANGES.md

@@ -14,6 +14,7 @@
   - Add pre-built bindings for GDAL 3.10 ([#573](https://github.com/georust/gdal/pull/573))
   - Add methods `alternative_name`, `is_nullable`, `is_unique`, `default_value` to `Field` ([#561](https://github.com/georust/gdal/pull/561))
   - Add `Defn::geometry_type` ([#562](https://github.com/georust/gdal/pull/562))
+  - Add `Dataset::maybe_start_transaction` which always succeeds to use transaction when possible for speed reasons -- no rollback ([#584](https://github.com/georust/gdal/pull/584))
 
 ### Fixed
 

src/vector/transaction.rs

@@ -181,9 +181,9 @@ impl Dataset {
 
 /// Represents maybe a transaction on a dataset for speed reasons.
 ///
-/// It can be committed by calling [`commit`](MaybeTransaction::commit), but unline [`Transaction`] it can not be rolled back. The transaction part is to make the process speedy when possible. If the [`Dataset`] does not support transaction, it does nothing.
+/// It can be committed by calling [`commit`](MaybeTransaction::commit), but unlike [`Transaction`] it can not be rolled back. The transaction part is to make the process speedy when possible. If the [`Dataset`] does not support transaction, it does nothing.
 ///
-/// If the transaction is not explicitly committed when it is dropped, it is implicitely committed, but you will not know if it fails.
+/// If the transaction is not explicitly committed when it is dropped, it is implicitly committed, but you will not know if it fails.
 ///
 /// The transaction holds a mutable borrow on the `Dataset` that it was created from, so during the
 /// lifetime of the transaction you will need to access the dataset by dereferencing the