summaryrefslogtreecommitdiff
path: root/man/i3status.man
diff options
context:
space:
mode:
authorMichael Stapelberg <michael@stapelberg.de>2012-05-02 17:26:08 +0200
committerMichael Stapelberg <michael@stapelberg.de>2012-05-02 17:26:08 +0200
commit192c38466d12ab0fc94c68ce1f826555942d1ae1 (patch)
tree267d6f72f8cecc5ac57fe51d69d5739ee4b26cfa /man/i3status.man
parente6cd45fe0aebfde805d36e44ecb742fc3b3cd964 (diff)
manpage: spelling / sentence fixes
Diffstat (limited to 'man/i3status.man')
-rw-r--r--man/i3status.man12
1 files changed, 7 insertions, 5 deletions
diff --git a/man/i3status.man b/man/i3status.man
index 785b369..8cac1bb 100644
--- a/man/i3status.man
+++ b/man/i3status.man
@@ -315,14 +315,16 @@ governor ("ondemand") changes the CPU frequency far more often than i3status
could display it. The display number is therefore often incorrect and doesn’t
tell you anything useful either.
-In general, i3status wants to display things which you would often look at
-anyways, like the current date/time, whether you are connected to a WiFi
-network or not, and if you have enough disk space to fit that 4.3 GiB download.
+In general, i3status wants to display things which you would look at
+occasionally anyways, like the current date/time, whether you are connected to
+a WiFi network or not, and if you have enough disk space to fit that 4.3 GiB
+download.
However, if you need to look at some kind of information more than once in a
while (like checking repeatedly how full your RAM is), you are probably better
-of with a script doing that, which pops up an alert when your RAM usage reaches
-a certain threshold.
+off with a script doing that, which pops up an alert when your RAM usage reaches
+a certain threshold. After all, the point of computers is not to burden you
+with additional boring tasks like repeatedly checking a number.
== External scripts/programs with i3status