[elpa] externals/denote 1be0255183 340/355: Reword some statements in the manual

[ELPA Syncer]

branch: externals/denote
commit 1be025518328bcc384d661d28c61ac319ad1ea94
Author: Protesilaos Stavrou <info@protesilaos.com>
Commit: Protesilaos Stavrou <info@protesilaos.com>

    Reword some statements in the manual
---
 README.org | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/README.org b/README.org
index 68e3f933a1..c6f487edee 100644
--- a/README.org
+++ b/README.org
@@ -88,14 +88,13 @@ principles:
 
 + Composability :: Be a good Emacs citizen, by integrating with other
   packages or built-in functionality instead of re-inventing functions
-  such as for filtering or greping.  Do not introduce strong
-  dependencies on specific libraries. The author of Denote (Protesilaos,
-  aka "Prot") writes ordinary notes in plain text (=.txt=), switching to
-  an Org file only when its expanded set of functionality is required
-  for the task at hand ([[#h:17896c8c-d97a-4faa-abf6-31df99746ca6][Points of 
entry]]).
+  such as for filtering or greping.  The author of Denote (Protesilaos,
+  aka "Prot") writes ordinary notes in plain text (=.txt=), switching on
+  demand to an Org file only when its expanded set of functionality is
+  required for the task at hand 
([[#h:17896c8c-d97a-4faa-abf6-31df99746ca6][Points of entry]]).
 
 + Portability :: Notes are plain text and should remain portable.  The
-  way Denote writes file names, the front matter it included in the
+  way Denote writes file names, the front matter it includes in the
   note's header, and the links it establishes must all be adequately
   usable with standard Unix tools.  No need for a databse or some
   specialised software.  As Denote develops and this manual is fully
@@ -108,8 +107,9 @@ principles:
   <https://zettelkasten.de/introduction/>.  Notes are atomic (one file
   per note) and have a unique identifier.  However, Denote does not
   enforce a particular methodology for knowledge management, such as a
-  restricted vocabulary or mutually exclusive sets of keywords.  It is
-  up to the user to apply the requisite rigor and/or creativity in
+  restricted vocabulary or mutually exclusive sets of keywords.  Denote
+  also does not check if the user writes thematically atomic notes.  It
+  is up to the user to apply the requisite rigor and/or creativity in
   pursuit of their preferred workflow 
([[#h:6060a7e6-f179-4d42-a9de-a9968aaebecc][Writing metanotes]]).
 
 + Hackability :: Denote's code base consists of small and reusable