===================================================================
RCS file: /cvs/mandoc/mdoc.7,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -p -r1.106 -r1.107
--- mandoc/mdoc.7	2010/05/14 17:31:25	1.106
+++ mandoc/mdoc.7	2010/05/15 07:01:51	1.107
@@ -1,4 +1,4 @@
-.\"	$Id: mdoc.7,v 1.106 2010/05/14 17:31:25 kristaps Exp $
+.\"	$Id: mdoc.7,v 1.107 2010/05/15 07:01:51 kristaps Exp $
 .\"
 .\" Copyright (c) 2009 Kristaps Dzonsons <kristaps@bsd.lv>
 .\"
@@ -14,7 +14,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: May 14 2010 $
+.Dd $Mdocdate: May 15 2010 $
 .Dt MDOC 7
 .Os
 .Sh NAME
@@ -301,10 +301,18 @@ When composing a manual, make sure that your sentences
 a line.
 By doing so, front-ends will be able to apply the proper amount of
 spacing after the end of sentence (unescaped) period, exclamation mark,
-or question mark.
+or question mark followed by zero or more non-sentence closing
+delimiters (
+.Ns Sq \&) ,
+.Sq \&] ,
+.Sq \&' ,
+.Sq \&" ) .
 .Pp
 The proper spacing is also intelligently preserved if a sentence ends at
-the boundary of a macro line.
+the boundary of a macro line, e.g.,
+.Pp
+.D1 \&Xr mandoc 1 \.
+.D1 \&Fl T \&Ns \&Cm ascii \.
 .Sh MANUAL STRUCTURE
 A well-formed
 .Nm