diff --git a/SVDRP-Help.md b/SVDRP-Help.md
index dcd108c..c1966b6 100644
--- a/SVDRP-Help.md
+++ b/SVDRP-Help.md
@@ -118,7 +118,7 @@ Make the device with the given number the primary device. Without option it retu
### PUTE [ <file> ]
-Put data into the EPG list. The data entered has to strictly follow the format defined in vdr(5) for the 'epg.data' file. A '.' on a line by itself terminates the input and starts processing of the data (all entered data is buffered until the terminating '.' is seen). If a file name is given, epg data will be read from this file (which must be accessible under the given name from the machine VDR is running on). In case of file input, no terminating '.' shall be given.
+Put data into the EPG list. The data entered has to strictly follow the format defined in vdr(5) for the 'epg.data' file. A '.' on a line by itself terminates the input and starts processing of the data (all entered data is buffered until the terminating '.' is seen). If a file name is given, epg data will be read from this file (which must be accessible under the given name from the machine VDR is running on). In case of file input, no terminating '.' shall be given.
### REMO [ on | off ]
diff --git a/Svdrpsend-Command-Reference.md b/Svdrpsend-Command-Reference.md
index c3d5b89..f1fc0b5 100644
--- a/Svdrpsend-Command-Reference.md
+++ b/Svdrpsend-Command-Reference.md
@@ -42,7 +42,7 @@
diff --git a/The-VDR-Plugin-System.md b/The-VDR-Plugin-System.md
index 262b95b..6225a71 100644
--- a/The-VDR-Plugin-System.md
+++ b/The-VDR-Plugin-System.md
@@ -1837,7 +1837,7 @@ osd->DrawText(x, y, s, Theme.Color(clrButtonRedFg), Theme.Color(clrButtonRedB
By default this will use the colors that have been defined in the respective
THEME_CLR() line, but may be overwritten through user supplied theme
-files (see man vdr(5) for information about the format of a theme file).
+files (see man vdr(5) for information about the format of a theme file).
Devices
diff --git a/VDR-Command-Reference.md b/VDR-Command-Reference.md
index 1a09f50..63f69cb 100644
--- a/VDR-Command-Reference.md
+++ b/VDR-Command-Reference.md
@@ -191,7 +191,7 @@
If started without any options, vdr tries to read command line
options from files named '*.conf' in the directory /etc/vdr/conf.d. Files
- are read in alphabetical order. See vdr(5) for details.
+ are read in alphabetical order. See vdr(5) for details.
SIGNALS
@@ -264,7 +264,7 @@
AUTHOR
diff --git a/VDR-File-Formats-and-Conventions.md b/VDR-File-Formats-and-Conventions.md
index dbb8221..d0fa87a 100644
--- a/VDR-File-Formats-and-Conventions.md
+++ b/VDR-File-Formats-and-Conventions.md
@@ -1072,11 +1072,11 @@ Calendar: date;echo;cal
| <channel id> |
is the "channel ID", made up from the parameters defined in
- 'channels.conf' |
+ 'channels.conf'
| <channel name> |
- is the "name" as in 'channels.conf' (for information only, may
+ | is the "name" as in 'channels.conf' (for information only, may
be left out) |
@@ -1268,7 +1268,7 @@ Calendar: date;echo;cal
AUTHOR
diff --git a/VDR-Manual.md b/VDR-Manual.md
index 1864509..97ef435 100644
--- a/VDR-Manual.md
+++ b/VDR-Manual.md
@@ -72,7 +72,7 @@
(defined in 'keymacros.conf')
Note that in normal viewing mode (no OSD active) the color keys can have user
- defined functionality, as configured in 'keymacros.conf'.
+ defined functionality, as configured in 'keymacros.conf'.
The default assignment is
Red Recordings menu
@@ -240,7 +240,7 @@
## Switching through channel groups
- If the 'channels.conf' file contains "group separators" you can switch
+ If the 'channels.conf' file contains "group separators" you can switch
through these groups by pressing the "Left" and "Right" key while no
menu is being displayed. The channel display will show the name of the
group, and if you press the "Ok" key while the group name is being
@@ -313,12 +313,12 @@
## Processing Recordings
- The configuration file 'reccmds.conf' can be used to define system commands
+ The configuration file 'reccmds.conf' can be used to define system commands
that can be applied to the recording that is currently highlighted in the
"Recordings" menu. The "Red" key in the "Recordings" menu opens the "Recording
- commands" menu if there are commands defined in the file 'reccmds.conf'. Pressing
+ commands" menu if there are commands defined in the file 'reccmds.conf'. Pressing
one of the keys '1'..'9' in the "Recordings" menu executes the corresponding
- command from 'reccmds.conf' (see also "Executing system commands" below).
+ command from 'reccmds.conf' (see also "Executing system commands" below).
## Replay Control
@@ -653,7 +653,7 @@ VDR version 2.6.6 added '/' to this list.
within the current one; if the "Sub folder" option is set to "yes", this will
be a folder that contains other folders (indicated by "..." following the
folder name in the list). The "Yellow" key deletes the current folder (note
- that this will merely delete the folder definition stored in 'folders.conf'
+ that this will merely delete the folder definition stored in 'folders.conf'
and has no effect on existing timers or recordings). The "Blue" key can be
used to edit an existing folder definition. The "Red" key opens a folder that
contains sub folders, while pressing Ok selects the current folder. Once a
@@ -1322,20 +1322,20 @@ VDR version 2.6.6 added '/' to this list.
## Executing system commands
The "VDR" menu option "Commands" allows you to execute any system commands
- defined in the configuration file 'commands.conf' (see vdr(5) for details).
+ defined in the configuration file 'commands.conf' (see vdr(5) for details).
The "Commands" option will only be present in the "VDR" menu if a valid
- 'commands.conf' file containing at least one command definition has been
+ 'commands.conf' file containing at least one command definition has been
found at program start.
This feature can be used to do virtually anything, like checking for new
mail, displaying the CPU temperature - you name it! All you need to do is
- enter the necessary command definition into 'commands.conf' and implement
+ enter the necessary command definition into 'commands.conf' and implement
the actual command that will be called. Such a command can typically be a
shell script or a Perl program. Anything that command writes to stdout will
be displayed on a result screen after executing the command. This screen will
use a 'fixed' font so that you can generate formatted output. In order to
avoid error messages going to stderr, command definitions should redirect
- stderr to stdout (see vdr(5)).
+ stderr to stdout (see vdr(5)).
WARNING: THE COMMANDS DEFINED IN 'commands.conf' WILL BE EXECUTED UNDER THE
======= SAME USER ID THAT VDR IS RUNNING WITH. BE VERY CAREFUL WHEN