From 040045f553a5e3bbce59b07f5c64c46bd64a50cb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Wolfgang=20M=C3=BCller?= <vehk@vehk.de>
Date: Tue, 16 Jul 2019 19:03:18 +0300
Subject: [PATCH] Proofreading ethermess.1

---
 ethermess.1 | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/ethermess.1 b/ethermess.1
index 2bcd98b..f443e57 100644
--- a/ethermess.1
+++ b/ethermess.1
@@ -12,7 +12,7 @@
 .Nm
 allows sending and receiving messages over Ethernet or Wi-Fi networks using
 the EtherMess protocol.
-Since EtherMess protocol uses bare Ethernet frames as its transport, IP
+Since the EtherMess protocol uses bare Ethernet frames as its transport, IP
 connectivity is not needed.
 .Pp
 The
@@ -49,7 +49,7 @@ knows about.
 .It /available
 Set your status to available.
 .It /unavailable
-Set your status to unavailable
+Set your status to unavailable.
 .It /nick Op Ar nick
 Set your nick to the one specified or display the current one.
 .It /target Ar target
@@ -80,10 +80,10 @@ A message from your default target will instead look like:
     16:20:03 <*~hutenosa> Lorem ipsum.
 .Ed
 .Ss Status
-There are four main types of status notification: join, quit, status
+There are four main types of status notifications: join, quit, status
 change, and nick change.
 .Pp
-The maximal form of a join is
+The verbose form of a join is
 .Bd -literal -compact
     20:08:19 >>> ~nick (status) [b7:00:f0:9f:a4:94]
 .Ed
@@ -111,6 +111,7 @@ A nick change looks like
 .Ed
 .Sh EXIT STATUS
 .Nm
-exit with status code 0 if it is exiting on user command and 1 if it is exiting due to backend having quit.
+exits with status code 0 if it is exiting on user command and 1 if it is
+exiting due to the backend having quit.
 .Sh SEE ALSO
 .Xr ethermess 7