add notes

docs/client_api/chunkedgraph.md

@@ -2,17 +2,13 @@
 title: client.chunkedgraph
 ---
 
-Note: the functionality described here will be accurate if the datastack you are using
-is using the most up-to-date version of the chunkedgraph engine. If something seems
-wrong with the documentation here, try checking the version of the chunkedgraph
-engine returned by your client:
-
-```python
-type(client.chunkedgraph)
-```
-
-Extended documentation for all versions of the chunkedgraph client can be found
-[here](../extended_api/chunkedgraph.md).
+!!! note
+    The functionality described here will be accurate if the datastack you are using is using the most up-to-date version of the chunkedgraph service. If something seems wrong with the documentation here, try checking the version of the chunkedgraph returned by your client:
+    ```python
+    type(client.chunkedgraph)
+    ```
+    Extended documentation for all versions of the chunkedgraph client can be found
+    [here](../extended_api/chunkedgraph.md).
 
 ::: caveclient.chunkedgraph.ChunkedGraphClientV1
     options:

docs/client_api/index.md

@@ -8,3 +8,7 @@ services. Under the hood, the CAVEclient is a collection of individual clients,
 can be accessed via properties. For example, to access the materialization client,
 you can use `client.materialize`, which (up to the exact version) will actually return a
 [caveclient.materializationengine.MaterializatonClientV3][] object.
+
+These pages describe the functionality of each of the individual clients, assuming
+that you are using the most up-to-date version of each. For more detailed information
+on all versions of all clients available, visit the [extended API documentation](../extended_api/index.md).

docs/client_api/l2cache.md

@@ -2,16 +2,13 @@
 title: client.l2cache
 ---
 
-Note: the functionality described here will be accurate if the datastack you are using
-is using the most up-to-date version of the level-2 cache. If something seems
-wrong with the documentation here, try checking the version of the level-2 cache returned by your client:
-
-```python
-type(client.l2cache)
-```
-
-Extended documentation for all versions of the level-2 cache client can be found
-[here](../extended_api/l2cache.md).
+!!! note
+    The functionality described here will be accurate if the datastack you are using is using the most up-to-date version of the L2 cache. If something seems wrong with the documentation here, try checking the version of the L2 cache returned by your client:
+    ```python
+    type(client.l2cache)
+    ```
+    Extended documentation for all versions of the L2 cache client can be found
+    [here](../extended_api/l2cache.md).
 
 ::: caveclient.l2cache.L2CacheClientLegacy
     options:

docs/client_api/materialize.md

@@ -2,17 +2,13 @@
 title: client.materialize
 ---
 
-Note: the functionality described here will be accurate if the datastack you are using
-is using the most up-to-date version of the materialization engine. If something seems
-wrong with the documentation here, try checking the version of the materialization
-engine returned by your client:
-
-```python
-type(client.materialize)
-```
-
-Extended documentation for all versions of the materialization client can be found
-[here](../extended_api/materialization.md).
+!!! note
+    The functionality described here will be accurate if the datastack you are using is using the most up-to-date version of the materialization engine. If something seems wrong with the documentation here, try checking the version of the materialization client returned by your client:
+    ```python
+    type(client.materialize)
+    ```
+    Extended documentation for all versions of the annotation client can be found
+    [here](../extended_api/materializationengine.md).
 
 ::: caveclient.materializationengine.MaterializatonClientV3
     options:

docs/client_api/state.md

@@ -2,17 +2,13 @@
 title: client.state
 ---
 
-Note: the functionality described here will be accurate if the datastack you are using
-is using the most up-to-date version of the state engine. If something seems
-wrong with the documentation here, try checking the version of the state
-engine returned by your client:
-
-```python
-type(client.state)
-```
-
-Extended documentation for all versions of the state client can be found
-[here](../extended_api/state.md).
+!!! note
+    The functionality described here will be accurate if the datastack you are using is using the most up-to-date version of the JSON  state service. If something seems wrong with the documentation here, try checking the version of the JSON state service returned by your client:
+    ```python
+    type(client.state)
+    ```
+    Extended documentation for all versions of the state client can be found
+    [here](../extended_api/jsonservice.md).
 
 ::: caveclient.jsonservice.JSONServiceV1
     options: