Visium HD plotting tutorial

notebooks.md

@@ -183,6 +183,28 @@ Many different technologies can be visualised out-of-the-box. See below for a co
 
                 notebooks/examples/technology_cosmx.ipynb
 
+    .. grid-item::
+
+        .. container:: custom-card
+
+            .. image:: _static/img/visium_hd.png
+                :target: notebooks/examples/technology_visium_hd.html
+
+            .. toctree::
+                :maxdepth: 1
+
+                notebooks/examples/technology_visium_hd.ipynb
+
+
+```
+
+## Advanced
+
+Advanced tutorials that showcase more complex functionalities of the SpatialData ecosystem.
+
+```{eval-rst}
+.. grid:: 2 3 3 3
+
     .. grid-item::
 
         .. container:: custom-card

notebooks/examples/tables.ipynb

@@ -1488,7 +1488,7 @@
    },
    "source": [
     "### Change the annotation target of table\n",
-    "We have a helper function, `set_table_annotates_element` to change the metadata regarding the annotation target of table in a `SpatialData` object. This function takes as arguments the `table_name`, `region` and optionally the `region_key` and `instance_key`. The latter two don't have to necessarily be specified if the table is already annotating a `SpatialElement`. The current values will be reused if not specified. For any of the arguments specified, they must be present at their respective location in the `SpatialData`object or table."
+    "We have a helper function, `set_table_annotates_spatialelement` to change the metadata regarding the annotation target of table in a `SpatialData` object. This function takes as arguments the `table_name`, `region` and optionally the `region_key` and `instance_key`. The latter two don't have to necessarily be specified if the table is already annotating a `SpatialElement`. The current values will be reused if not specified. For any of the arguments specified, they must be present at their respective location in the `SpatialData`object or table."
    ]
   },
   {