matthiasbeyer/imag
1
0
Fork 0
Code Releases Activity

Remove trailing whitespace

Browse source 
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
This commit is contained in:
Matthias Beyer 2019-11-09 16:51:21 +01:00
parent 33e53dca6d
commit 0d27139cf7
3 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/src/01000-intro.md
View file

@ -1,7 +1,7 @@
# Introduction {#sec:introduction}
This document is the user documentation for imag, the personal
information management suite for the commandline.
information management suite for the commandline.
**Basically: This is Hobby stuff. Expect incompleteness, false statements and
generally read with grain of salt.**
@ -74,7 +74,7 @@ The difference between imag and the mentioned projects is:
querying.
* zim is a wiki, which could be used for PIM but is not specialized for it.
Recording habits might be possible, but not that simple as with imag
imag is not there
yet, though. Some parts can be used, though it is far away from being feature-complete.

4
doc/src/03010-conventions.md
View file

@ -47,7 +47,7 @@ Libraries which provide functionality for entries or the store but no
domain-functionality should be named "libimagentrything" whereas "thing" stands for
what the library provides.
All domain libraries should be prefixed with "libimag".
All domain libraries should be prefixed with "libimag".
### Library scope
@ -93,7 +93,7 @@ possible without a lot of effort, but still: more tests = better!
The commandline tools are the CLI-frontends for their respective libraries.
So `libimagdiary` has a CLI frontend `imag-diary`.
Those CLI frontends use functionality from `libimagrt` to build a
Those CLI frontends use functionality from `libimagrt` to build a
commandline interface which is consistent with the rest of the ecosystem.
Commandline applications use the runtime interfaces for receiving IDs from the

2
doc/src/09010-contributing.md
View file

@ -51,7 +51,7 @@ All dependencies are installable with the nix package manager by using a
## Commit guidelines
Make sure your patchset does not contain "Fixup" commits when publishing it, but feel
free to send "Fixup" commits in the review process.
free to send "Fixup" commits in the review process.
If squashing fails I will come back to you.
We do not follow some official Rust styleguide for our codebase, but we try to