Update README.md to include docs reference and remove user guide info.

Author: oj-tooth

README.md

@@ -1,7 +1,5 @@
 # OceanDataStore
 
-[**Documentation**](https://noc-msm.github.io/OceanDataStore/)
-
 A Python library designed to streamline writing, updating & accessing ocean model and observational data stored in cloud object storage.
 
 ## Installation
@@ -15,107 +13,15 @@ pip install git+https://github.com/NOC-MSM/OceanDataStore.git
 
 **Note:** we strongly recommend installing **OceanDataStore** into a new virtual environment using either ``venv`` or ``conda / mamba``.
 
-## User Guide
-
-### Creating a Credentials File
-
-To get started using **OceanDataStore**, users need to create a ``credentials.json`` file containing the following information:
-
-```json
-{
-    "secret": "your_secret",
-    "token": "your_token",
-    "endpoint_url": "https://noc-msm-o.s3-ext.jc.rl.ac.uk"
-}
-```
-
-### Sending Individual Files
-
-To create a new zarr store in an object store from a local file, use the `send_to_zarr` command:
-
-```bash
-ods send_to_zarr -f /path/to/file.nc -c credentials.json -b bucket_name -v var
-```
-
-The arguments used are:
-- `-f`: Path to the netCDF file containing the variables.
-- `-c`: Path to the JSON file containing the object store credentials.
-- `-b`: Bucket name in the object store where the variables will be stored.
-- `-v`: Variable within the netCDF file to send to the object store.
-
-In the example above, without a `-p` (or `--prefix`), the variables will be stored in `<bucket_name>/<var>`. If a `--prefix` is provided, the variables will be stored in `<bucket_name>/<prefix>/<var>`.
-
-### Sending Lots of Files
-
-To create a new zarr store in an object store using a large number of files, we can use [dask](https://www.dask.org) with the `send_to_zarr` command by passing a dask configuration JSON file:
-
-```bash
-ods send_to_zarr -f filepaths -c credentials.json -b bucket_name -p prefix \
-                 -gf filepath_domain -uc '{"lat":"lat_new", "lon":"lon_new"}' \
-                 -cs '{"x":500, "y":500, "depthw":25}' \
-                 -dc dask_config.json
-```
-
-The arguments used are:
-- `-f`: Paths to the multiple netCDF files containing the variables.
-- `-c`: Path to the JSON file containing the object store credentials.
-- `-b`: Bucket name in the object store where the variables will be stored.
-- `-p`: Prefix used to define path to object (see above).
-- `-gf`: Path to model grid file containing domain variables.
-- `-uc`: Coordinates dimension variables to update given as a JSON string '{current_coord : new_coord}'.
-- `-cs`: Chunk strategy used to rechunk model data.
-- `-dc`: Path to JSON file containing Dask configuration.
+## Documentation
 
-where the contents of the ``dask_config.json`` are:
-
-```json
-{
-    "config_kwargs": {
-        "temporary_directory":"..../jasmin_os_tmp/",
-        "local_directory":"..../jasmin_os_tmp/"
-    },
-    "cluster_kwargs": {
-        "n_workers" : 12,
-        "threads_per_worker" : 1,
-        "memory_limit":"2GB"
-    }
-}
-```
-
-In the example, a LocalCluster with 12 single threaded workers, each with 2 GB of available memory, is used to transfer a large collection of files to an object store.
-
-Users are strongly recommended to implement `send_to_zarr` workflows using a job scheduler, such as SLURM or PBS, to either run the LocalCluster on a single compute node or to use an existing the SLURMCluster or PBSCluster (dask job queue).
-
-**Note:** the netCDF4 library does not support multi-threaded access to datasets, so users should ensure that ``threads_per_worker : 1`` in their dask configuration JSON file to avoid raising CancelledError exceptions when using ``send_to_zarr`` or `update_zarr`.
-
-### Updating Existing Stores
-
-To update an existing zarr store in an object store, we can use the `update_zarr` command:
-
-```bash
-ods update_zarr -f /path/to/file.nc -c credentials.json -b bucket_name -p prefix -v var
-```
-
-This command will replace and/or append the values of variable `var` stored at the local filepath to the `/bucket_name/prefix/var` store provided it already exists in the object store.
-
-**Note:** compatability checks must be passed before local data will be appended to an existing store, these include chunk size & dimension compatability.
-
-### Updating Existing Stores With Lots of Files
-
-To update an existing zarr store in an object store using a large number of files, we can use [dask](https://www.dask.org) via the `update_zarr` command analogously to `send_to_zarr`:
-
-```bash
-ods update_zarr -f filepaths -c credentials.json -b bucket_name -p prefix \
-                -gf filepath_domain -uc '{"lat":"lat_new", "lon":"lon_new"}' \
-                -cs '{"x":500, "y":500, "depthw":25}' -ad time \
-                -dc dask_config.json
-```
+To learn more about OceanDataStore, click [**here**](https://noc-msm.github.io/OceanDataStore/) to explore the documentation.
 
 ## Examples
 
-For further examples of how to implement the commands in **OceanDataStore** in your own workflows, see the bash scripts in the `examples` directory.
+For examples of how to implement the commands in **OceanDataStore CLI** in your own workflows, see the bash scripts in the `examples` directory.
 
-## OceanDataStore Arguments
+## OceanDataStore CLI Arguments
 
 ### Mandatory Arguments