From c2160b989349414b3c61f0e4e4e42d27e499076e Mon Sep 17 00:00:00 2001 From: Albert Graef Date: Tue, 16 Oct 2018 08:33:48 +0200 Subject: [PATCH] Typo in the manual. --- README.md | 2 +- midizap.1 | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 1fc4026..3846eb5 100644 --- a/README.md +++ b/README.md @@ -64,7 +64,7 @@ After installation the system-wide default configuration file will be in /etc/mi The ~/.midizaprc file, if it exists, takes priority over /etc/midizaprc, so it becomes your personal default midizap configuration. The midizaprc file included in the distribution is really just an example; you're expected to edit this file to adjust the bindings for the MIDI controllers and the applications that you use. -It is also possible to specify the configuration file to be used, by invoking midizap with the name of the midizaprc file on the command line. This is often used with more specialized configurations dealing with specific applications or MIDI controllers. E.g., to try one of sample configurations in the sources: +It is also possible to specify the configuration file to be used, by invoking midizap with the name of the midizaprc file on the command line. This is often used with more specialized configurations dealing with specific applications or MIDI controllers. E.g., to try one of the sample configurations in the sources: ~~~ midizap examples/APCmini.midizaprc diff --git a/midizap.1 b/midizap.1 index 836023a..1e33515 100644 --- a/midizap.1 +++ b/midizap.1 @@ -184,7 +184,7 @@ invoking midizap with the name of the midizaprc file on the command line. This is often used with more specialized configurations dealing with specific applications or MIDI controllers. -E.g., to try one of sample configurations in the sources: +E.g., to try one of the sample configurations in the sources: .IP .nf \f[C]