update statuses

Author: sanketverma1704

docs/v1/v1.0.rst

@@ -13,7 +13,9 @@ interpreted as described in `RFC 2119
 Status
 ------
 
-This specification is deprecated. See :ref:`zarr-specs` for the latest version.
+This specification is deprecated. See `v3
+<https://zarr-specs.readthedocs.io/en/latest/v3/core/v3.0.html>`_ for the
+latest version.
 
 Storage
 -------

docs/v2/v2.0.rst

@@ -12,10 +12,9 @@ used for storing Zarr arrays. The key words "MUST", "MUST NOT", "REQUIRED",
 Status
 ------
 
-V3 specification is the latest version. Check :ref:`v3/core/v3.0` for the
-updated version.
-
-See :ref:`zarr-specs` for previous versions.
+This version is outdated and not actively maintained. See `v3
+<https://zarr-specs.readthedocs.io/en/latest/v3/core/v3.0.html>`_ for the
+latest version.
 
 .. _spec_v2_storage:
 

docs/v3/core/v3.0.rst

@@ -40,6 +40,8 @@ Status of this document
 
 ZEP0001 was accepted on May 15th, 2023 via https://github.com/zarr-developers/zarr-specs/issues/227.
 
+This specification is the latest version.
+
 
 Introduction
 ============
@@ -526,7 +528,7 @@ mandatory names:
 
       For example, in a 3 dimensional array, with a separator of ``/`` the identifier
       for the chunk at grid index (1, 23, 45) is the string ``"c/1/23/45"``.  With a
-      separator of ``.``, the identifier is the string ``"c.1.23.45"``. The initial prefix 
+      separator of ``.``, the identifier is the string ``"c.1.23.45"``. The initial prefix
       ``c`` ensures that metadata documents and chunks have separate prefixes.
 
       .. note:: A main difference with spec v2 is that the default chunk separator
@@ -1128,18 +1130,18 @@ of an additional operation:
   encoded representation is a byte string, then ``decoded_regions``
   specifies a list of byte ranges.
 
-- ``c.compute_encoded_size(input_size)``, a procedure that determines the 
+- ``c.compute_encoded_size(input_size)``, a procedure that determines the
   size of the encoded representation given a size of the decoded representation.
   This procedure cannot be implemented for codecs that produce variable-sized
-  encoded representations, such as compression algorithms. Depending on the 
+  encoded representations, such as compression algorithms. Depending on the
   type of the codec, the signature could differ:
 
-  - ``c.compute_encoded_size(array_size, data_type) -> (array_size, data_type)`` 
-    for ``array -> array`` codecs, where ``array_size`` is the number of items 
+  - ``c.compute_encoded_size(array_size, data_type) -> (array_size, data_type)``
+    for ``array -> array`` codecs, where ``array_size`` is the number of items
     in the array, i.e., the product of the components of the array's shape;
-  - ``c.compute_encoded_size(array_size, data_type) -> byte_size`` 
+  - ``c.compute_encoded_size(array_size, data_type) -> byte_size``
     for ``array -> bytes`` codecs;
-  - ``c.compute_encoded_size(byte_size) -> byte_size`` 
+  - ``c.compute_encoded_size(byte_size) -> byte_size``
     for ``bytes -> bytes`` codecs.
 
 .. note::