From ae288d452f7befcfe68a24a5152031be4a108ee1 Mon Sep 17 00:00:00 2001 From: Neil Clifford Date: Fri, 29 Sep 2017 11:14:48 +0100 Subject: [PATCH] Initial re-work of documentation --- docs/CM_Tutorial.adoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/CM_Tutorial.adoc b/docs/CM_Tutorial.adoc index f1e6a9bf2..c5d60f7ce 100755 --- a/docs/CM_Tutorial.adoc +++ b/docs/CM_Tutorial.adoc @@ -607,8 +607,7 @@ See link::CM_Tutorial_Behaviour.adoc[CM_Tutorial_Behaviour.adoc] for mre details Chronicle Map 3 is able to store entry checksums along with entries. With entry checksums it is possible to identify partially written entries (in case of operating system or power failure while) -and corrupted entries (in case of hardware memory or disk corruption) and clean them up during -[recovery](#recovery) procedure. +and corrupted entries (in case of hardware memory or disk corruption) and clean them up during the <> procedure. Entry checksums are 32-bit numbers, computed by a hash function with good avalanche effect. Theoretically there is still about a one-billionth chance that after entry corruption it passes the