Lots of improvements to look and feel of manual pages

FossilOrigin-Name: 719dc3b1128c165488999004be06a1432d8e6286

1 files changed, 12 insertions, 4 deletions

diff --git a/doc/Name.3 b/doc/Name.3
index e6cc727..6d1fdbf 100644
--- a/doc/Name.3
+++ b/doc/Name.3
@@ -5,7 +5,7 @@
 '\" See the file "license.terms" for information on usage and redistribution
 '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES.
 '\" 
-'\" RCS: @(#) $Id: Name.3,v 1.5 2007/01/05 00:00:48 nijtmans Exp $
+'\" RCS: @(#) $Id: Name.3,v 1.6 2007/10/24 14:32:57 dkf Exp $
 '\" 
 .so man.macros
 .TH Tk_Name 3 "" Tk "Tk Library Procedures"
@@ -55,9 +55,17 @@ The \fBTk_PathName\fR macro returns a
 hierarchical name for \fItkwin\fR.
 Path names have a structure similar to file names in Unix but with
 dots between elements instead of slashes:  the main window for
-an application has the path name ``.'';  its children have names like
-``.a'' and ``.b''; their children have names like ``.a.aa'' and
-``.b.bb''; and so on.  A window is considered to be a child of
+an application has the path name
+.QW . ;
+its children have names like
+.QW .a
+and
+.QW .b ;
+their children have names like
+.QW .a.aa
+and
+.QW .b.bb ;
+and so on.  A window is considered to be a child of
 another window for naming purposes if the second window was named
 as the first window's \fIparent\fR when the first window was created.
 This is not always the same as the X window hierarchy.  For