Merge branch 'main' into enh-codespell

.gitattributes

@@ -0,0 +1 @@
+*.ipynb linguist-detectable=false

.mailmap

@@ -0,0 +1,2 @@
+Sebastián Galkin <code@amisdelabc.com>
+Sebastián Galkin <paraseba@gmail.com>

README.md

@@ -22,7 +22,7 @@ that enhance performance, collaboration, and safety in a cloud-computing context
   library
 - Documentation for the [Icechunk Rust Crate](https://icechunk.io/icechunk-rust)
 - The [Contributor Guide](https://icechunk.io/contributing)
-- The [Icechunk Spec](https://icechunk.io/icechunk-python/spec)
+- The [Icechunk Spec](https://icechunk.io/spec)
 
 ## Icechunk Overview
 
@@ -96,7 +96,7 @@ Readers can only see and use committed snapshots.
 
 ### Branches and Tags
 
-Additionally, snapshots occur in a specific linear (i.e. serializable) order within  **branch**.
+Additionally, snapshots occur in a specific linear (i.e. serializable) order within a **branch**.
 A branch is a mutable reference to a snapshot--a pointer that maps the branch name to a snapshot ID.
 The default branch is `main`.
 Every commit to the main branch updates this reference.
@@ -109,7 +109,7 @@ Tags are appropriate for publishing specific releases of a repository or for any
 
 Chunk references are "pointers" to chunks that exist in other files--HDF5, NetCDF, GRIB, etc.
 Icechunk can store these references alongside native Zarr chunks as "virtual datasets".
-You can then can update these virtual datasets incrementally (overwrite chunks, change metadata, etc.) without touching the underling files.
+You can then update these virtual datasets incrementally (overwrite chunks, change metadata, etc.) without touching the underling files.
 
 ## How Does It Work?