From 94453188ab5afa5e7a20a8c869cfff7972e15cee Mon Sep 17 00:00:00 2001 From: Trent Smith Date: Mon, 4 Mar 2019 10:08:09 -0800 Subject: [PATCH] adressing comments --- rfcs/text/0000-dss-deletion-process.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rfcs/text/0000-dss-deletion-process.md b/rfcs/text/0000-dss-deletion-process.md index 3e5b6b7b..51f4f759 100644 --- a/rfcs/text/0000-dss-deletion-process.md +++ b/rfcs/text/0000-dss-deletion-process.md @@ -23,8 +23,8 @@ One of the DCP's primary objectives is to ensure the durability of the (meta)data it contains and to maintain a complete record of the changes made to it. The DCP achieves this by never overwriting a (meta)data file but instead treating an update to such a file as the addition of a new version of that -file. Instead of physically removing a file version, the DCP hides that -file version behind a deletion marker. +file. Instead of physically removing a file version during a logical deletion, the DCP hides that +file version behind a deletion marker. Physical deletion is only used as a last resort. Under certain circumstances however, the **physical deletion** of a file version is required. The first section of this specification describes the