doc/storage.texi | 11 +++++++----

diff --git a/doc/storage.texi b/doc/storage.texi
index 85c382e65d42036aaab6563263319e24fd6b1b60d04288065d944def40a4440e..a3e3fe0b5285a0f97f4d8baa004afd52a0adb0bc54a2e6ba7c54c0d6f03b9c96 100644
--- a/doc/storage.texi
+++ b/doc/storage.texi
@@ -13,12 +13,14 @@   |     +- public-package-0.1.1.tar.gz.blake2_256
   |     +- public-package-0.2.tar.gz
   |     +- public-package-0.2.tar.gz.asc
   |     +- public-package-0.2.tar.gz.sha256
+  |     +- public-package-0.2.tar.gz.blake2_256
   +-- private-package
   |     +- .internal
   |     +- .metadata.rec
   |     +- private-package-0.1.tar.gz
   |     +- private-package-0.1.tar.gz.asc
   |     +- private-package-0.1.tar.gz.sha256
+  |     +- private-package-0.1.tar.gz.blake2_256
   |...
 @end verbatim
 
@@ -29,9 +31,10 @@ versions with checksums and write them in corresponding
 @file{.sha256}, @file{.blake2_256}, @file{.sha512}, @file{.md5} files.
 However no package package tarball is downloaded.
 
-If JSON API is enabled, them metadata is also downloaded and stored in
+If JSON API is enabled, then metadata is also downloaded and stored in
 @file{.metadata.rec} @url{https://www.gnu.org/software/recutils/, recfile}.
-It fully resembles Core Metadata structure.
+It fully resembles structure of
+@url{https://packaging.python.org/specifications/core-metadata/, Core Metadata}.
 
 When you request for particular package version, then its tarball is
 downloaded and verified against the stored checksum. But SHA256 is then
@@ -41,8 +44,8 @@ For example @file{public-package} has @code{0.1} version, downloaded a
 long time ago with MD5 checksum. @code{0.1.1} version is downloaded more
 recently with BLAKE2b-256 checksum, also storing that checksum for
 @code{0.1}. @code{0.2} version is downloaded tarball, having forced
-SHA256 recalculated checksum. Also upstream has corresponding
-@file{.asc} signature file.
+SHA256 and BLAKE2b-256 recalculated checksums. Also upstream has
+corresponding @file{.asc} signature file.
 
 @file{private-package} is private package, because it contains
 @file{.internal} file. It can be uploaded and queries to it are not