mdoc(7) police: protect trailing full stops of abbreviations

with a trailing zero-width space: `e.g.\&'.

2 files changed, 3 insertions, 3 deletions

diff --git a/share/man/man7/security.7 b/share/man/man7/security.7
index a58e5e4..e21a6e1 100644
--- a/share/man/man7/security.7
+++ b/share/man/man7/security.7
@@ -539,7 +539,7 @@ It is a very good idea to protect internal services from external access
 by firewalling them off at your border routers.  The idea here is to prevent
 saturation attacks from outside your LAN, not so much to protect internal
 services from network-based root compromise.  Always configure an exclusive
-firewall, i.e.
+firewall, i.e.\&
 .So
 firewall everything *except* ports A, B, C, D, and M-Z
 .Sc .
diff --git a/share/man/man7/tuning.7 b/share/man/man7/tuning.7
index 0410549..edbf619 100644
--- a/share/man/man7/tuning.7
+++ b/share/man/man7/tuning.7
@@ -193,7 +193,7 @@ case of a crash but could very easily be several seconds (even a minute!)
 behind updating the physical disk.  If you crash you may lose more work
 than otherwise.  Secondly, softupdates delays the freeing of filesystem
 blocks.  If you have a filesystem (such as the root filesystem) which is
-close to full, doing a major update of it, e.g.
+close to full, doing a major update of it, e.g.\&
 .Em make installworld,
 can run it out of space and cause the update to fail.
 .Pp
@@ -226,7 +226,7 @@ and
 utilities may be used to create simple striped filesystems.  Generally
 speaking, striping smaller partitions such as the root and /var/tmp,
 or essentially read-only partitions such as /usr is a complete waste of
-time.  You should only stripe partitions that require serious I/O performance...
+time.  You should only stripe partitions that require serious I/O performance,
 typically /var, /home, or custom partitions used to hold databases and web
 pages.  Choosing the proper stripe size is also
 important.  Filesystems tend to store meta-data on power-of-2 boundaries