From 6176be8610733063da34341e3a3e09ba0cff1e69 Mon Sep 17 00:00:00 2001
From: Artemiy Volkov <artemiyv@acm.org>
Date: Fri, 15 Nov 2013 19:01:44 +0400
Subject: [PATCH] doc: ck_sequence: Fix header & function names.

---
 doc/ck_sequence | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/doc/ck_sequence b/doc/ck_sequence
index 1f71269..ad06dbe 100644
--- a/doc/ck_sequence
+++ b/doc/ck_sequence
@@ -30,7 +30,6 @@
 .Nm ck_sequence_init ,
 .Nm ck_sequence_read_begin ,
 .Nm ck_sequence_read_retry ,
-.Nm ck_sequence_read_retry. ,
 .Nm ck_sequence_write_begin ,
 .Nm ck_sequence_write_end
 .Nd sequence locks
@@ -68,7 +67,7 @@ the data associated with a ck_sequence_t it must pass the earlier return value
 of
 .Fn ck_sequence_read_begin
 to
-.Fn ck_sequence_read_retry. If
+.Fn "ck_sequence_read_retry". If
 .Fn ck_sequence_read_retry
 returns true then the copy of data may be inconsistent and the read process
 must be retried. Writers must rely on their own synchronization primitives.