From a9b257a397cdd6d1852ae78a193c4263fc6ea18b Mon Sep 17 00:00:00 2001 From: Stefan Kangas Date: Sat, 1 Feb 2025 04:08:43 +0100 Subject: [PATCH] Improve wording in symbols.texi * doc/lispref/symbols.texi (Symbol Components): Improve wording (Bug#75512). Reported by Matt Trzcinski . (cherry picked from commit 3bccd04c5c659307231f9e03895d71d26c1d5f8f) --- doc/lispref/symbols.texi | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/lispref/symbols.texi b/doc/lispref/symbols.texi index 4a505768b58..87f0e43eef9 100644 --- a/doc/lispref/symbols.texi +++ b/doc/lispref/symbols.texi @@ -106,11 +106,11 @@ reference any object. (This is not the same thing as holding the symbol a value cell that is void results in an error, such as @samp{Symbol's value as variable is void}. - Because each symbol has separate value and function cells, variables -names and function names do not conflict. For example, the symbol -@code{buffer-file-name} has a value (the name of the file being -visited in the current buffer) as well as a function definition (a -primitive function that returns the name of the file): + Because each symbol has separate value and function cells, the names +of variables and functions do not conflict. For example, the symbol +@code{buffer-file-name} has a value (the name of the file being visited +in the current buffer) as well as a function definition (a primitive +function that returns the name of the file): @example buffer-file-name -- 2.39.5