[DATALAD RUNCMD] chore: run codespell throughout fixing a few new typos automagically

=== Do not change lines below ===
{
 "chain": [],
 "cmd": "codespell -w",
 "exit": 0,
 "extra_inputs": [],
 "inputs": [],
 "outputs": [],
 "pwd": "."
}
^^^ Do not change lines above ^^^

Author: yarikoptic

README.md

@@ -42,7 +42,7 @@ MicroJSON is compatible with any application or tool that process JSON data. Its
 
 ## Examples
 
-Refer to the examples foler to see samples of MicroJSON files as well as a simple parsing example, or the [example in the documentation](docs/example.md)
+Refer to the examples folder to see samples of MicroJSON files as well as a simple parsing example, or the [example in the documentation](docs/example.md)
 
 ## Specification
 

docs/index.md

@@ -40,7 +40,7 @@ A feature object represents a spatially bounded entity associated with propertie
 - `"geometry"`: A geometry object as defined in the section above or a JSON null value.
 - `"properties"`: (Optional) A JSON object containing properties and metadata specific to the feature, or a JSON null value. It consists of key-value pairs, where the key is a string and the value is a any JSON value. The value may be a string, number, array, object.
 - `"id"`: (Optional) A unique identifier for this feature.
-- `"ref"`: (Optional) A reference to an external resource, e.g. URI to a zarr strcture, e.g. "s3://zarr-demo/store/my_array.zarr".
+- `"ref"`: (Optional) A reference to an external resource, e.g. URI to a zarr structure, e.g. "s3://zarr-demo/store/my_array.zarr".
 - `"parentId"`: (Optional) A reference to the parent feature, e.g. the id of the feature that this feature is a part of.
 - `"feeatureClass"`: (Optional) A string indicating the class of the feature, e.g. "cell", "nucleus", "mitochondria", etc.
 

docs/ome.md

@@ -33,7 +33,7 @@ While TileJSON has traditionally been used in 2D applications, there is nothing
 2. Associate NGFF array chunks with tile indices (z/x/y) derived from spatial transformations, given the NGFF multiscale metadata and the corresponding TileJSON metadata.
 3. A practical observation is that if the multiscale pyramids differs, transformations between the two systems are needed, in addition to what is described above, which could be avoided by using the same multiscale pyramid structure in both systems. This is also valid for the tile size (expressed in the global coordinates), which should be the same in both systems for a specific zoom level.
 4. Layering of data is supported in TileJSON, as the array `vector_layers` in its schema. Layers are thus stored together for each tile, as a contrast to the NGFF, where the layers are stored in separate arrays as labeled images.
-5. The NGFF raster data hierarchy could be expressed with a TileJSON which does not have a vector layer but intead just maps the raster data endpoints as formatted in the field `tiles` in the TileJSON schema.
+5. The NGFF raster data hierarchy could be expressed with a TileJSON which does not have a vector layer but instead just maps the raster data endpoints as formatted in the field `tiles` in the TileJSON schema.
 
 ## Incorporating MicroJSON and Vector Tiles
 

docs/provenance.md

@@ -21,7 +21,7 @@ The provenance model structure comprises `WorkflowCollection`, `Workflow`, `Arti
 - **Workflow Object:** Captures essential workflow details, including identifiers and descriptive metadata. This metadata links MicroJSON objects to their respective workflows.
 - **Artifact and Artifact Collection Objects:** Represent single files or directories and collections of these, respectively, providing a link between the physical data and the workflows.
 - **Workflow Provenance Object:** Details specific instances of workflow runs, including run identifiers, duration, operator, and the input/output parameters.
-Of these, Workflow, WorkflowCollection, Artifact, and ArtifactCollection can funtion as the top object in the provenance part of a MicroJSON file.
+Of these, Workflow, WorkflowCollection, Artifact, and ArtifactCollection can function as the top object in the provenance part of a MicroJSON file.
 - **MicroJSON Link Object:** Provides a link to a specific MicroJSON object, specifying which parts of the object's properties are pertinent to the workflow run. While this object is required, and the id property is required, the specification of a field in the MicroJSON object is optional. If no field is specified, the entire MicroJSON object is considered to be pertinent to the workflow run or artifact.
 
 ## Data Provenance and MicroJSON Traceability Link

src/microjson/utils.py

@@ -206,7 +206,7 @@ def segmentations_encodings(
         x: int,
         y: int,
     ) -> tuple[Any, list[list[list[Any]]]]:
-        """Calculate object boundries as series of vertices/points
+        """Calculate object boundaries as series of vertices/points
         forming a polygon."""
         label, coordinates = [], []
         objects = ndimage.measurements.find_objects(label_image)