branch: externals/org
commit b7a75ece505fdc058e39dacf7269736fe92f5684
Author: Ihor Radchenko <[email protected]>
Commit: Ihor Radchenko <[email protected]>
org-manual: Fix some grammar problems in the Tags section
---
doc/org-manual.org | 38 +++++++++++++++++++-------------------
1 file changed, 19 insertions(+), 19 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 79cd30e8be..df5680b61b 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -4961,11 +4961,11 @@ use the variables ~org-use-tag-inheritance~ and
~org-tags-exclude-from-inheritance~.
#+vindex: org-agenda-use-tag-inheritance
-Tag inheritance is relevant when the agenda search tries to match
-a tag, either in the ~tags~ or ~tags-todo~ agenda types. In other
+Tag inheritance is relevant when the agenda search tries to match a
+tag, either in the ~tags~ or ~tags-todo~ agenda types. In other
agenda types, ~org-use-tag-inheritance~ has no effect. Still, you may
-want to have your tags correctly set in the agenda, so that tag
-filtering works fine, with inherited tags. Set
+want your tags to be correctly set in the agenda, so that tag
+filtering works properly with inherited tags. Set
~org-agenda-use-tag-inheritance~ to control this: the default value
includes all agenda types, but setting this to ~nil~ can really speed
up agenda generation.
@@ -4989,7 +4989,7 @@ also a special command for inserting tags:
#+cindex: completion, of tags
#+vindex: org-tags-column
Enter new tags for the current headline. Org mode either offers
- completion or a special single-key interface for setting tags, see
+ completion or a special single-key interface for setting tags; see
below. After pressing {{{kbd(RET)}}}, the tags are inserted and
aligned to ~org-tags-column~. When called with a {{{kbd(C-u)}}}
prefix, all tags in the current buffer are aligned to that column,
@@ -5028,18 +5028,18 @@ a specific file, add an empty =TAGS= keyword to that
file:
#+vindex: org-tag-persistent-alist
If you have a preferred set of tags that you would like to use in
-every file, in addition to those defined on a per-file basis by =TAGS=
-keyword, then you may specify a list of tags with the variable
+every file, in addition to those defined on a per-file basis by the
+=TAGS= keyword, then you may specify a list of tags with the variable
~org-tag-persistent-alist~. You may turn this off on a per-file basis
by adding a =STARTUP= keyword to that file:
: #+STARTUP: noptag
By default, Org mode uses the standard minibuffer completion facilities
-for entering tags. However, it also implements another, quicker, tag
+for entering tags. However, it also implements another, quicker tag
selection method called /fast tag selection/. This allows you to
select and deselect tags with just a single key press. For this to
-work well you should assign unique letters to most of your commonly
+work well, you should assign unique letters to most of your commonly
used tags. You can do this globally by configuring the variable
~org-tag-alist~ in your Emacs init file. For example, you may find
the need to tag many items in different files with =@home=. In this
@@ -5081,7 +5081,7 @@ Do not forget to press {{{kbd(C-c C-c)}}} with point in
one of these
lines to activate any changes.
To set these mutually exclusive groups in the variable
-~org-tags-alist~, you must use the dummy tags ~:startgroup~ and
+~org-tag-alist~, you must use the dummy tags ~:startgroup~ and
~:endgroup~ instead of the braces. Similarly, you can use ~:newline~
to indicate a line break. The previous example would be set globally
by the following configuration:
@@ -5094,7 +5094,7 @@ by the following configuration:
("laptop" . ?l) ("pc" . ?p)))
#+end_src
-If at least one tag has a selection key then pressing {{{kbd(C-c
+If at least one tag has a selection key, then pressing {{{kbd(C-c
C-c)}}} automatically presents you with a special interface, listing
inherited tags, the tags of the current headline, and a list of all
valid tags with corresponding keys[fn:: Keys are automatically
@@ -5187,7 +5187,7 @@ tag/ for a set of other tags. The group tag can be seen
as the
"broader term" for its set of tags. Defining multiple group tags and
nesting them creates a tag hierarchy.
-One use-case is to create a taxonomy of terms (tags) that can be used
+One use case is to create a taxonomy of terms (tags) that can be used
to classify nodes in a document or set of documents.
When you search for a group tag, it returns matches for all members in
@@ -5197,7 +5197,7 @@ of the group or any of its subgroups. This makes tag
searches and
filters even more flexible.
You can set group tags by using brackets and inserting a colon between
-the group tag and its related tags---beware that all whitespaces are
+the group tag and its related tags---beware that all whitespace is
mandatory so that Org can parse this line correctly:
: #+TAGS: [ GTD : Control Persp ]
@@ -5223,8 +5223,8 @@ That can conceptually be seen as a hierarchy of tags:
- =Context=
- =Task=
-You can use the ~:startgrouptag~, ~:grouptags~ and ~:endgrouptag~
-keyword directly when setting ~org-tag-alist~ directly:
+You can use the ~:startgrouptag~, ~:grouptags~, and ~:endgrouptag~
+keywords when setting ~org-tag-alist~ directly:
#+begin_src emacs-lisp
(setq org-tag-alist '((:startgrouptag)
@@ -5241,9 +5241,9 @@ keyword directly when setting ~org-tag-alist~ directly:
(:endgrouptag)))
#+end_src
-The tags in a group can be mutually exclusive if using the same group
-syntax as is used for grouping mutually exclusive tags together; using
-curly brackets.
+Tags in a group can be made mutually exclusive by using the same group
+syntax as for grouping mutually exclusive tags together--using curly
+brackets.
: #+TAGS: { Context : @Home @Work @Call }
@@ -5314,7 +5314,7 @@ These commands all prompt for a match string which allows
basic
Boolean logic, such as =+boss+urgent-project1= to find entries with
tags =boss= and =urgent=, but not =project1= or =Kathy|Sally= to find
entries tagged with either =Kathy= or =Sally=. The full syntax of the
-search string is rich and allows also matching against TODO keywords,
+search string is rich and also allows matching against TODO keywords,
entry levels and properties. For a complete description with many
examples, see [[*Matching tags and properties]].
