From bb8ec488fc2d53ea0dd2a517b78d40457fb5368f Mon Sep 17 00:00:00 2001 From: Xue Fuqiao Date: Tue, 28 Jul 2015 08:25:33 +0800 Subject: [PATCH] * doc/lispref/variables.texi (Variable Aliases): Typo fix. (Bug#21141) --- doc/emacs/frames.texi | 2 +- doc/lispref/variables.texi | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/emacs/frames.texi b/doc/emacs/frames.texi index 0667826b013..2ae7300e897 100644 --- a/doc/emacs/frames.texi +++ b/doc/emacs/frames.texi @@ -574,7 +574,7 @@ the following form: @end example @noindent -Within this format, any of the elements in braces may be omitted. +Within this format, any of the elements in brackets may be omitted. Here, @var{fontname} is the @dfn{family name} of the font, such as @samp{Monospace} or @samp{DejaVu Sans Mono}; @var{fontsize} is the @dfn{point size} of the font (one @dfn{printer's point} is about 1/72 diff --git a/doc/lispref/variables.texi b/doc/lispref/variables.texi index 27bc0610959..15491e52751 100644 --- a/doc/lispref/variables.texi +++ b/doc/lispref/variables.texi @@ -1903,8 +1903,8 @@ the variable was first made obsolete (usually a version number string). The optional argument @var{access-type}, if non-@code{nil}, should -should specify the kind of access that will trigger obsolescence -warnings; it can be either @code{get} or @code{set}. +specify the kind of access that will trigger obsolescence warnings; it +can be either @code{get} or @code{set}. @end defun You can make two variables synonyms and declare one obsolete at the -- 2.39.2