skip consolidate doctests; minor edits

Author: alimanfoo

docs/tutorial.rst

@@ -778,9 +778,11 @@ chunk size, which will reduce the number of chunks and thus reduce the number of
 round-trips required to retrieve data for an array (and thus reduce the impact of network
 latency). Another option is to try to increase the compression ratio by changing
 compression options or trying a different compressor (which will reduce the impact of
-limited network bandwidth). As of version 2.2, Zarr also provides the
-:class:`zarr.storage.LRUStoreCache` which can be used to implement a local in-memory cache
-layer over a remote store. E.g.::
+limited network bandwidth).
+
+As of version 2.2, Zarr also provides the :class:`zarr.storage.LRUStoreCache`
+which can be used to implement a local in-memory cache layer over a remote
+store. E.g.::
 
     >>> s3 = s3fs.S3FileSystem(anon=True, client_kwargs=dict(region_name='eu-west-2'))
     >>> store = s3fs.S3Map(root='zarr-demo/store', s3=s3, check=False)
@@ -797,10 +799,10 @@ layer over a remote store. E.g.::
     b'Hello from the cloud!'
     0.0009490990014455747
 
-If you are still experiencing poor performance with distributed/cloud storage, please
-raise an issue on the GitHub issue tracker with any profiling data you can provide, as
-there may be opportunities to optimise further either within Zarr or within the mapping
-interface to the storage.
+If you are still experiencing poor performance with distributed/cloud storage,
+please raise an issue on the GitHub issue tracker with any profiling data you
+can provide, as there may be opportunities to optimise further either within
+Zarr or within the mapping interface to the storage.
 
 .. _tutorial_copy:
 
@@ -809,27 +811,38 @@ Consolidating metadata
 
 (This is an experimental feature.)
 
-Since there is a significant overhead for every connection to s3, the pattern described in
-the previous section may incur significant latency while scanning the metadata of the data-set
-hierarchy, even though each individual file is small. For cases such as these, once the file
-is static and can be regarded as read-only, at least for the metadata/structure of the
-data-set, the many metadata files can be consolidated into a single one.
-Doing this can greatly increase the speed of reading the data-set hierarchy::
+Since there is a significant overhead for every connection to a cloud object
+store such as S3, the pattern described in the previous section may incur
+significant latency while scanning the metadata of the dataset hierarchy, even
+though each individual metadata object is small.  For cases such as these, once
+the data are static and can be regarded as read-only, at least for the
+metadata/structure of the dataset hierarchy, the many metadata objects can be
+consolidated into a single one via
+:func:`zarr.convenience.consolidate_metadata`. Doing this can greatly increase
+the speed of reading the dataset metadata, e.g.::
+
+   >>> zarr.consolidate_metadata(store)  # doctest: +SKIP
+
+This creates a special key with a copy of all of the metadata from all of the
+metadata objects in the store.
 
-   >>> zarr.consolidate_metadata(store)
+Later, to open a Zarr store with consolidated metadata, use
+:func:`zarr.convenience.open_consolidated`, e.g.::
 
-Creates a special key with a copy of all of the metadata from the many files.
-Later::
+   >>> root = zarr.open_consolidated(store)  # doctest: +SKIP
 
-   >>> root = zarr.open_consolidated(store)
+This uses the special key to read all of the metadata in a single call to the
+backend storage.
 
-Uses this special key to read all of the metadata in a single call to the backend storage.
+Note that, the hierarchy could still be opened in the normal way and altered,
+causing the consolidated metadata to become out of sync with the real state of
+the dataset hierarchy. In this case,
+:func:`zarr.convenience.consolidate_metadata` would need to be called again.
 
-Note that, the data-set could still be opened in the normal way and altered, causing the
-consolidated metadata to become out of sync with the real state of the data-set. In this
-case, :func:`zarr.consolidate_metadata` would need to be called again. The data-set
-returned by :func:`zarr.open_consolidated` is read-only for the metadata, but the data
-values can still be updated.
+To protect against consolidated metadata accidentally getting out of sync, the
+root group returned by :func:`zarr.convenience.open_consolidated` is read-only
+for the metadata, meaning that no new groups or arrays can be created, and
+arrays cannot be resized. However, data values with arrays can still be updated.
 
 Copying/migrating data
 ----------------------