notebook tweaks

docs/source/tutorial_notebooks/query_gcr_datasets.ipynb

@@ -196,11 +196,11 @@
    ]
   },
   {
-   "cell_type": "raw",
-   "id": "47b0d238-0fb6-436d-a905-5b39e9831903",
+   "cell_type": "markdown",
+   "id": "ad32a278-694a-4364-8dcd-39cdc702039c",
    "metadata": {},
    "source": [
-    "Among the more interesting for our purposes are `name`, `relative_path`, `access_api`, `access_api_configuration` and `location_type. In the case of catalogs registered with GCRCatalogs, `name` in the data registry is the same name GCRCatalogs uses to refer to it: the basename of the corresponding config file, not including the suffix `.yaml`.  But keep in mind that, unlike GCRCatalog, the dataregistry always respects case in names\n",
+    "Among the more interesting for our purposes are `name`, `relative_path`, `access_api`, `access_api_configuration` and `location_type`. In the case of catalogs registered with GCRCatalogs, `name` in the data registry is the same name GCRCatalogs uses to refer to it: the basename of the corresponding config file, not including the suffix `.yaml`.  But keep in mind that, unlike GCRCatalog, the dataregistry always respects case in names\n",
     "\n",
     "Let's look at those properties for the dataset `cosmoDC2_v1.1.4`."
    ]
@@ -289,10 +289,10 @@
   },
   {
    "cell_type": "markdown",
-   "id": "bca5969a-e267-427a-8b15-e88b6556d9a8",
+   "id": "d4f05dbc-b6cf-49fa-beb8-34203f3e90fc",
    "metadata": {},
    "source": [
-    "It all looks pretty much as you would expect, except what happened to `dataset.relative_path`?   That doesn't look like a path. You can see the reason in the catalog's configuration:  it's based on something else. The data registry makes no attempt to sort this out, as GCRCatalogs would.  The same thing would happen for a composite catalog: the data registry just stores the catalog's configuration; it doesn't know how to parse it. You can also see this in the value for `dataset.location_type`. \"metadata_only\" means that the data registry is only storing metadata for the catalog; it is not attempting to manage the associated files."
+    "It all looks pretty much as you would expect, except what happened to the value of `dataset.relative_path`?   That doesn't look like a path. You can see the reason in the catalog's configuration:  it's based on another catalog. Or you can see it in the value for `dataset.location_type`. \"meta_only\" means that the data registry is only storing metadata for the catalog; it is not keeping track of the (indirectly) associated files.  The same thing would happen for a composite catalog: the data registry just stores the catalog's configuration. It doesn't know how to parse it as GCRCatalogs would."
    ]
   },
   {