[PATCH -perfbook] advsync: Fix markers of end-of-sentence periods

[PATCH -perfbook] advsync: Fix markers of end-of-sentence periods

[Akira Yokosawa]

Fixes: b97c0b4f0770 ("advsync: Fix punctuation-check complaints")
Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
Paul,

Current punctcheck.pl ignores markers of mid-sentence periods
at line ends.
It might be possible to catch this type of errors.
Let me see if it is actually doable without false positives.

        Thanks, Akira
--
 advsync/advsync.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/advsync/advsync.tex b/advsync/advsync.tex
index 1a5034b1..13cf6cd4 100644
--- a/advsync/advsync.tex
+++ b/advsync/advsync.tex
@@ -507,7 +507,7 @@ For example, when running on typical computer systems, both loads and
 stores can result in page faults.
 Which cause in-kernel page-fault handlers to be invoked.
 Which might acquire locks, or even do I/O, potentially even using
-something like network file system (NFS).\@
+something like network file system (NFS)\@.
 All of which are most emphatically blocking operations.
 
 Nor are page faults the only kernel-induced hazard.
@@ -553,7 +553,7 @@ synchronization is far more important in theory than it is in practice.
 \label{sec:advsync:NBS Subdivided Operations}
 
 One common trick that provides a given algorithm a loftier place on
-the NBS ranking is to replace blocking operations with a polling API.\@
+the NBS ranking is to replace blocking operations with a polling API\@.
 For example, instead of having a reliable dequeue operation that might be
 merely lock-free or even blocking, instead provide a dequeue operation
 that will spuriously fail in a wait-free manner rather than exhibiting

base-commit: 5f28b7cb0d4c447c9d6397770906c7cb4c96832c
-- 
2.25.1