Merge pull request #246 from DimitriPapadopoulos/codespell

Fix typos found by codespell

Author: jbms

docs/v3/codecs/sharding-indexed/v1.0.rst

@@ -194,7 +194,7 @@ common optimizations.
   chunks can be optimized. In that case, the shard index can be read from the
   store by requesting the ``n`` last bytes, where ``n`` is 16 bytes multiplied 
   by the number of chunks in a shard. After parsing the shard index, single
-  chunks can be requested from the store by specifing the byte range. The 
+  chunks can be requested from the store by specifying the byte range. The 
   bytestream, then, needs to be decoded as above. 
 
 * **Encoding**: A simple implementation to encode a chunk in a shard would (a)

docs/v3/core/v3.0.rst

@@ -423,7 +423,7 @@ underlying store_:
 
 .. note::
 
-   When storing a Zarr hierachy in a filesystem-like store (e.g. the local
+   When storing a Zarr hierarchy in a filesystem-like store (e.g. the local
    filesystem or S3) as a sub-directory, it is recommended that the
    sub-directory name ends with ``.zarr`` to indicate the start of a hierarchy
    to users.