diff --git a/ROADMAP-TO-4.0.md b/ROADMAP-TO-4.0.md
index 38b24e37f..f1e9ca69d 100644
--- a/ROADMAP-TO-4.0.md
+++ b/ROADMAP-TO-4.0.md
@@ -5,7 +5,7 @@ List of desired features for a 4.0 release
 
 * Have a completely specified format for the `TreeStore` and `DictStore`.  The format should allow to have containers either in memory or on disk.  Also, it should allow a sparse or contiguous storage.  The user will be able to specify these properties by following the same conventions than for NDArray objects (alas, `urlpath` and `contiguous` params).
 
-    * New `.save()` and `.to_cframe()` methods should be implemented to convert from in-memory representations to on disk and viceversa.
+    * New `.save()` and `.to_cframe()` methods should be implemented to convert from in-memory representations to on disk and vice-versa.
     * The format for `TreeStore` and `DictStore` will initially be defined at Python level, and documented only in the Python-Blosc2 repository.  An implementation in the C library is desirable, but not mandatory at this time.
 
 * A new `Table` object should be implemented based on the `TreeStore` class (a subclass?), with a label ('table'?) in metalayers indicating that the contents of the tree can be interpreted as regular table.  As `TreeStore` is hierarchical, a subtree can also be interpreted as a `Table` if there a label in the metalayer of the subtree (or group in HDF5 parlance); that can lead to tables than can have different subtables embedded.  It is not clear yet if should impose the same number of rows for all the columns.
diff --git a/doc/getting_started/tutorials/08.schunk-slicing_and_beyond.ipynb b/doc/getting_started/tutorials/08.schunk-slicing_and_beyond.ipynb
index 55fbe5010..0130c0118 100644
--- a/doc/getting_started/tutorials/08.schunk-slicing_and_beyond.ipynb
+++ b/doc/getting_started/tutorials/08.schunk-slicing_and_beyond.ipynb
@@ -6,7 +6,7 @@
    "source": [
     "# Slicing, extending and serializing with SChunks\n",
     "\n",
-    "The usual way to store generic binary data in python-blosc2 is through a `SChunk` (super-chunk) object, where the data is split into chunks of the same size, which we studied in the last tutorial. We saw how to retrieve, update or append data in the form of chunks. In fact, one can work with the individual multi-byte items composing the data (and not the bytes directly), using native SChunk methods - such operations will be the subject of this tutorial. We will use NumPy arrays as data sources, but everything we're going to do woul work equally well with any Python object supporting the [Buffer Protocol](https://docs.python.org/3/c-api/buffer.html).\n",
+    "The usual way to store generic binary data in python-blosc2 is through a `SChunk` (super-chunk) object, where the data is split into chunks of the same size, which we studied in the last tutorial. We saw how to retrieve, update or append data in the form of chunks. In fact, one can work with the individual multi-byte items composing the data (and not the bytes directly), using native SChunk methods - such operations will be the subject of this tutorial. We will use NumPy arrays as data sources, but everything we're going to do would work equally well with any Python object supporting the [Buffer Protocol](https://docs.python.org/3/c-api/buffer.html).\n",
     "\n",
     "First, we create our own `SChunk` instance; this time, let's fill it with data upon creation."
    ]
@@ -93,7 +93,7 @@
   {
    "cell_type": "markdown",
    "metadata": {},
-   "source": "As you can see, the data is returned as a bytes object. If we want to get a more meaningful container instead, we can use `get_slice`. This method requires an initailised buffer into which to load the bytes, and one may pass any Python object (supporting the Buffer Protocol) as the `out` param to fill it with the data.  In this case we will use a NumPy array container."
+   "source": "As you can see, the data is returned as a bytes object. If we want to get a more meaningful container instead, we can use `get_slice`. This method requires an initialised buffer into which to load the bytes, and one may pass any Python object (supporting the Buffer Protocol) as the `out` param to fill it with the data.  In this case we will use a NumPy array container."
   },
   {
    "cell_type": "code",
diff --git a/doc/python-blosc2.rst b/doc/python-blosc2.rst
index 0af7a5a01..59950ce26 100644
--- a/doc/python-blosc2.rst
+++ b/doc/python-blosc2.rst
@@ -72,7 +72,7 @@
                 <h3 style="margin-top: 10px; margin-bottom: 15px;">Hierarchical Structures</h3>
             </div>
 
-        Efficiently store data hierachically with the `TreeStore class <https://www.blosc.org/python-blosc2/reference/tree_store.html#blosc2.TreeStore>`_ for convenience and optimized `performance <https://www.blosc.org/posts/new-treestore-blosc2/>`_.
+        Efficiently store data hierarchically with the `TreeStore class <https://www.blosc.org/python-blosc2/reference/tree_store.html#blosc2.TreeStore>`_ for convenience and optimized `performance <https://www.blosc.org/posts/new-treestore-blosc2/>`_.
 
     .. grid-item-card::
         :class-card: intro-card text-center no-border