check on git

CAVEconnectome · Jan 18, 2024 · 73e14ab · 73e14ab
1 parent bbd58d4
commit 73e14ab
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 4 deletions.
diff --git a/changelog.md b/changelog.md
@@ -1,4 +1,6 @@
-# Changelog
+---
+title: Changelog
+---
 
 5.1.0
 ----

diff --git a/docs/client_api/annotation.md b/docs/client_api/annotation.md
@@ -1,4 +1,6 @@
-# client.annotation
+---
+title: client.annotation
+---
 
 Note: the functionality described here will be accurate if the datastack you are using
 is using the most up-to-date version of the annotation engine. If something seems

diff --git a/docs/client_api/overview.md b/docs/client_api/overview.md
@@ -4,5 +4,5 @@ The most common method of interacting with the CAVE Framework is by instantiatin
 client (`caveclient.CAVEclient`) and then using that client to interact with various
 services. Under the hood, the CAVEclient is a collection of individual clients, which
 can be accessed via properties. For example, to access the materialization client,
-you can use `client.materialize`, which will actually return a
-[caveclient.materializationengine.MaterializationClient][] object.
+you can use `client.materialize`, which (up to the exact version) will actually return a
+[caveclient.materializationengine.MaterializatonClientV3][] object.