From c3f2b13b264c8954b2f428c7e01d3df4245d5edb Mon Sep 17 00:00:00 2001 From: Guillaume Ayoub Date: Mon, 19 Apr 2010 16:58:54 +0200 Subject: [PATCH] Minor fixes in documentation. --- technical_choices.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/technical_choices.rst b/technical_choices.rst index 4e57c2c0..4f713a9e 100644 --- a/technical_choices.rst +++ b/technical_choices.rst @@ -118,7 +118,7 @@ The CalDAV RFC defines what must be done, what can be done and what cannot be done. Many violations of the protocol are totally defined and behaviours are given in such cases. -The Radicale Server assumes that the clients are perfect and that protocole +The Radicale Server assumes that the clients are perfect and that protocol violations do not exist. That is why most of the errors in client requests have undetermined consequences for the lazy server that can reply good answers, bad answers, or even no answer. @@ -154,4 +154,4 @@ The Radical Project is **only the server part** of this architecture. Code Architecture ----------------- -*To be written…* +*To be written*