Browse Source

fix in-file cross-references

Robert Klein 5 years ago
1 changed files with 11 additions and 5 deletions
  1. 11 5

+ 11 - 5

@@ -458,7 +458,7 @@ docstrings by browsing the customize interface (=M-x customize-group
 * Drawers
-  :CUSTOM_ID: drawers
+  :CUSTOM_ID: drawer
 #+index: Drawers!Definition
@@ -627,12 +627,15 @@ agenda.
 The power of org-mode lies in its treatment of headlines as
 "containers" of information to which you can attach all sorts of data
-([[#todo-keywords][todo keywords]], [[tag][tags]], priorities, timestamps, [[#property][properties]], and an
+([[#todo-keywords][todo keywords]], [[#tag][tags]], priorities, timestamps, [[#property][properties]], and an
 unlimited amount of text). This turns org-mode's deceptively simple
 outline structure into a powerful "database" of information, in which
 units of data can be nested within one another.
 * Inheritance
+  :CUSTOM_ID: inheritance
+  :END:
 #+index: Inheritance!Definition
@@ -847,7 +850,7 @@ outline and yet remain easy to find via tags.
 ** Considerations: Tags vs. TODO keywords vs. Properties
 One question that often emerges for new users of org mode is how to
-decide when tags, [[#todo-keyword][TODO keywords]], or [[#property][properties]] are appropriate.
+decide when tags, [[#todo-keywords][TODO keywords]], or [[#property][properties]] are appropriate.
 For instance, should you define your projects by creating a special
 todo keyword for them (=PROJECT=) or by giving them a "=:project:="
@@ -906,7 +909,7 @@ larger trees.
 * Todo Keywords
-  :CUSTOM_ID: todo-keyword
+  :CUSTOM_ID: todo-keywords
 #+index: Todo Keywords!Definition
@@ -1016,7 +1019,10 @@ record of when each event in the sequence happened.
 #+index: SCHEDULED!Definition
 ** Restriction lock
+  :CUSTOM_ID: file-restriction
+  :END:
+# roklein AT roklein DOT de: is this the right place for the tag?
 #+index: Restriction lock!Definition
 ** Table