docarray · hanxiao · Jun 22, 2023 · Jun 22, 2023 · Jun 22, 2023 · Jun 22, 2023
diff --git a/.github/ISSUE_TEMPLATE/bug-v1-deprecated.yml b/.github/ISSUE_TEMPLATE/bug-v1-deprecated.yml
@@ -1,4 +1,4 @@
-name: 🐛 DocArray V1 Bug (0.1.0 - 0.20.1) (Deprecated Version)
+name: 🐛 DocArray <=0.21 Bug (0.1.0 - 0.20.1) (Deprecated Version)
 description: Report a bug or unexpected behavior in DocArray version prior to v2 (0.21.1)
 labels: [bug V1, unconfirmed]
 

diff --git a/README.md b/README.md
diff --git a/docarray/array/doc_list/io.py b/docarray/array/doc_list/io.py
@@ -555,7 +555,7 @@ def _stream_header(self) -> bytes:
         # Binary format for streaming case
 
         # V2 DocList streaming serialization format
-        # | 1 byte | 8 bytes | 4 bytes | variable(docarray v2) | 4 bytes | variable(docarray v2) ...
+        # | 1 byte | 8 bytes | 4 bytes | variable(DocArray >=0.30) | 4 bytes | variable(DocArray >=0.30) ...
 
         # 1 byte (uint8)
         version_byte = b'\x02'

diff --git a/docarray/documents/legacy/legacy_document.py b/docarray/documents/legacy/legacy_document.py
@@ -8,10 +8,10 @@
 
 class LegacyDocument(BaseDoc):
     """
-    This Document is the LegacyDocument. It follows the same schema as in DocArray v1.
+    This Document is the LegacyDocument. It follows the same schema as in DocArray <=0.21.
     It can be useful to start migrating a codebase from v1 to v2.
 
-    Nevertheless, the API is not totally compatible with DocArray v1 `Document`.
+    Nevertheless, the API is not totally compatible with DocArray <=0.21 `Document`.
     Indeed, none of the method associated with `Document` are present. Only the schema
     of the data is similar.
 

diff --git a/docs/assets/docarray-colorful.svg b/docs/assets/docarray-colorful.svg
diff --git a/docs/assets/docarray-dark.svg b/docs/assets/docarray-dark.svg
diff --git a/docs/how_to/add_doc_index.md b/docs/how_to/add_doc_index.md
@@ -384,7 +384,7 @@ When indexing documents, your implementation should behave in the following way:
 - Every field in the Document is mapped to a column in the database
 - This includes the `id` field, which is mapped to the primary key of the database (if your backend has such a concept)
 - The configuration of that column can be found in `self._column_infos[field_name].config`
-- In DocArray v1, we used to store a serialized representation of every document. This is not needed anymore, as every row in your database table should fully represent a single indexed document.
+- In DocArray <=0.21, we used to store a serialized representation of every document. This is not needed anymore, as every row in your database table should fully represent a single indexed document.
 
 To handle nested documents, the public `index()` method already flattens every incoming document for you.
 This means that `_index()` already receives a flattened representation of the data, and you don't need to worry about that.

diff --git a/docs/migration_guide.md b/docs/migration_guide.md
@@ -2,7 +2,7 @@
 
 If you are using DocArray v<0.30.0, you will be familiar with its [dataclass API](https://docarray.jina.ai/fundamentals/dataclass/).
 
-_DocArray v2 is that idea, taken seriously._ Every document is created through a dataclass-like interface,
+_DocArray >=0.30 is that idea, taken seriously._ Every document is created through a dataclass-like interface,
 courtesy of [Pydantic](https://pydantic-docs.helpmanual.io/usage/models/).
 
 This gives the following advantages:
@@ -33,7 +33,7 @@ and additional `chunks` and `matches`.
 - In v2 we have the [`LegacyDocument`][docarray.documents.legacy.LegacyDocument] class, 
   which extends `BaseDoc` while following the same schema as v1's `Document`.
   The `LegacyDocument` can be useful to start migrating your codebase from v1 to v2. 
-  Nevertheless, the API is not fully compatible with DocArray v1 `Document`.
+  Nevertheless, the API is not fully compatible with DocArray <=0.21 `Document`.
   Indeed, none of the methods associated with `Document` are present. 
   Only the schema of the data is similar.
 
@@ -100,7 +100,7 @@ book_titles = docs.title  # returns a list[str]
 ## Changes to Document Store
 
 In v2 the `Document Store` has been renamed to [`DocIndex`](user_guide/storing/docindex.md) and can be used for fast retrieval using vector similarity. 
-DocArray v2 `DocIndex` supports:
+DocArray >=0.30 `DocIndex` supports:
 
 - [Weaviate](https://weaviate.io/)
 - [Qdrant](https://qdrant.tech/)

diff --git a/docs/user_guide/representing/array.md b/docs/user_guide/representing/array.md
@@ -1,6 +1,6 @@
 # Array of documents
 
-DocArray allows users to represent and manipulate multi-modal data to build AI applications such as neural search and generative AI. 
+DocArray allows users to represent and manipulate multimodal data to build AI applications such as neural search and generative AI. 
 
 As you have seen in the [previous section](array.md), the fundamental building block of DocArray is the [`BaseDoc`][docarray.base_doc.doc.BaseDoc] class which represents a *single* document, a *single* datapoint.
 

diff --git a/docs/user_guide/sending/api/jina.md b/docs/user_guide/sending/api/jina.md
@@ -4,7 +4,7 @@ In this example we'll build an audio-to-text app using [Jina](https://docs.jina.
 
 We will use: 
 
-* DocArray V2: To load and preprocess multimodal data such as image, text and audio.
+* DocArray >=0.30: To load and preprocess multimodal data such as image, text and audio.
 * Jina: To serve the model quickly and create a client.
 
 ## Install packages

diff --git a/docs/user_guide/sending/first_step.md b/docs/user_guide/sending/first_step.md
@@ -1,7 +1,7 @@
 # Introduction
 
 In the representation section we saw how to use [`BaseDoc`][docarray.base_doc.doc.BaseDoc], [`DocList`][docarray.array.doc_list.doc_list.DocList] and [`DocVec`][docarray.array.doc_vec.doc_vec.DocVec]
-to represent multi-modal data. In this section we will see **how to send such data over the wire**.
+to represent multimodal data. In this section we will see **how to send such data over the wire**.
 
 This section is divided into two parts:
 

diff --git a/docs/user_guide/storing/first_step.md b/docs/user_guide/storing/first_step.md
@@ -1,6 +1,6 @@
 # Introduction
 
-In the previous sections we saw how to use [`BaseDoc`][docarray.base_doc.doc.BaseDoc], [`DocList`][docarray.array.doc_list.doc_list.DocList] and [`DocVec`][docarray.array.doc_vec.doc_vec.DocVec] to represent multi-modal data and send it over the wire.
+In the previous sections we saw how to use [`BaseDoc`][docarray.base_doc.doc.BaseDoc], [`DocList`][docarray.array.doc_list.doc_list.DocList] and [`DocVec`][docarray.array.doc_vec.doc_vec.DocVec] to represent multimodal data and send it over the wire.
 In this section we will see how to store and persist this data.
 
 DocArray offers two ways of storing your data, each of which have their own documentation sections:

diff --git a/mkdocs.yml b/mkdocs.yml
@@ -5,7 +5,7 @@ repo_name: docarray/docarray
 repo_url: https://github.com/docarray/docarray
 edit_uri: ''
 theme:
-  logo: assets/logo-light.svg
+  logo: assets/docarray-dark.svg
 
   favicon: assets/favicon.png
   name: material