Minor documentation improvements

FossilOrigin-Name: 7a32076a08024b4b4bffeae0cdf83af7a5e4ef3d

3 files changed, 9 insertions, 1 deletions

diff --git a/doc/GetPixels.3 b/doc/GetPixels.3
index 05fe902..287e734 100644
--- a/doc/GetPixels.3
+++ b/doc/GetPixels.3
@@ -84,7 +84,7 @@ value in \fIobjPtr\fR, which speeds up future calls to
 \fBTk_GetPixels\fR is identical to \fBTk_GetPixelsFromObj\fR except
 that the screen distance is specified with a string instead
 of an object.  This prevents \fBTk_GetPixels\fR from caching the
-return value, so \fBTk_GetAnchor\fR is less efficient than
+return value, so \fBTk_GetPixels\fR is less efficient than
 \fBTk_GetPixelsFromObj\fR.
 .PP
 \fBTk_GetMMFromObj\fR and \fBTk_GetScreenMM\fR are similar to
diff --git a/doc/lower.n b/doc/lower.n
index d3b232d..0d8f252 100644
--- a/doc/lower.n
+++ b/doc/lower.n
@@ -27,6 +27,10 @@ In this case the \fBlower\fR command will insert
 \fIwindow\fR into the stacking order just below \fIbelowThis\fR
 (or the ancestor of \fIbelowThis\fR that is a sibling of \fIwindow\fR);
 this could end up either raising or lowering \fIwindow\fR.
+.PP
+All \fBtoplevel\fR windows may be restacked with respect to each
+other, whatever their relative path names, but the window manager is
+not obligated to strictly honor requests to restack.
 .SH "SEE ALSO"
 raise
 .SH KEYWORDS
diff --git a/doc/raise.n b/doc/raise.n
index d2a48ba..b2856c1 100644
--- a/doc/raise.n
+++ b/doc/raise.n
@@ -27,6 +27,10 @@ In this case the \fBraise\fR command will insert
 \fIwindow\fR into the stacking order just above \fIaboveThis\fR
 (or the ancestor of \fIaboveThis\fR that is a sibling of \fIwindow\fR);
 this could end up either raising or lowering \fIwindow\fR.
+.PP
+All \fBtoplevel\fR windows may be restacked with respect to each
+other, whatever their relative path names, but the window manager is
+not obligated to strictly honor requests to restack.
 .SH EXAMPLE
 .PP
 Make a button appear to be in a sibling frame that was created after