From d196dbcee5c1e24c1929add648814dd4c76990a3 Mon Sep 17 00:00:00 2001 From: Scott Lystig Fritchie Date: Mon, 14 Dec 2015 19:21:20 +0900 Subject: [PATCH] MD fixup --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 80850ba..6a8a64d 100644 --- a/README.md +++ b/README.md @@ -28,8 +28,8 @@ What if we want a file store that is always available to write new file data and attempts best-effort file reads? If we really do care about data loss and/or data corruption, then we -really want both #3 and #1. Unfortunately, systems that meet criteria -#1 are *very* +really want both #3 and #1. Unfortunately, systems that meet +criteria #1 are *very* rare. Why? This is 2015. We have decades of research that shows that computer hardware can (and indeed does) corrupt data at nearly every level of the modern