summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBastien <bzg@gnu.org>2018-04-26 11:42:04 +0200
committerBastien <bzg@gnu.org>2018-04-26 11:42:04 +0200
commite3794f6dce8b9524a9cbe1da9ab3a2a8b8d76258 (patch)
tree28e00f11174a8a02a188f1842a6da56f2c56bca3
parent889a07583417ed66d0831a36e43927a8ab160f9d (diff)
downloadorg-mode-e3794f6dce8b9524a9cbe1da9ab3a2a8b8d76258.tar.gz
Continue previous commit
-rw-r--r--doc/org-manual.org18
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/org-manual.org b/doc/org-manual.org
index b3799ae..87208ee 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -4015,15 +4015,15 @@ a background color.
#+cindex: @samp{ORDERED}, property
The structure of Org files---hierarchy and lists---makes it easy to
define TODO dependencies. Usually, a parent TODO task should not be
-marked DONE until all subtasks, defined as children tasks, are marked
-as DONE. And sometimes there is a logical sequence to a number of
-(sub)tasks, so that one task cannot be acted upon before all siblings
-above it are done. If you customize the variable
-~org-enforce-todo-dependencies~, Org blocks entries from changing
-state to DONE while they have children that are not DONE.
-Furthermore, if an entry has a property =ORDERED=, each of its
-children is blocked until all earlier siblings are marked DONE. Here
-is an example:
+marked DONE until all TODO subtasks, defined as children tasks, are
+marked as DONE. And sometimes there is a logical sequence to a number
+of TODO (sub)tasks, so that one task cannot be acted upon before all
+siblings above it are done. If you customize the variable
+~org-enforce-todo-dependencies~, Org blocks entries from changing state
+to DONE while they have TODO children that are not DONE. Furthermore,
+if an entry has a property =ORDERED=, each of its TODO children is
+blocked until all earlier siblings are marked DONE. Here is an
+example:
#+begin_example
,* TODO Blocked until (two) is done