diff options
| author | Daniel Mendler <mail@daniel-mendler.de> | 2023-02-07 23:24:57 +0100 |
|---|---|---|
| committer | Daniel Mendler <mail@daniel-mendler.de> | 2023-02-07 23:24:57 +0100 |
| commit | b91063ba4aabce0e0400daaeb9b2f0e57cbb9af8 (patch) | |
| tree | 6a1f1acca7fe4437fbe2d9a42da7a3c8448e3059 | |
| parent | a9b75e5750dd61adc4cdf00c00f41eb7c9632463 (diff) | |
Improve wording in manual
| -rw-r--r-- | compat.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/compat.texi b/compat.texi index f170a89..a129c3b 100644 --- a/compat.texi +++ b/compat.texi @@ -238,10 +238,10 @@ convention or behavior can be accessed via the @code{compat-function} and @code{compat-call} macros. In this manual we call such definitions ``Extended Definitions''. An example is the function @code{plist-get}. Note that extended functions are subject to closer -scrutiny, since their usage is not completely painless thanks to -@code{compat-call}. If a particular extended function does not see -much usage or the extension yields only marginal benefits, we may not -provide it as part of Compat. +scrutiny, since their usage via @code{compat-call} is not completely +painless. If a particular extended function does not see much usage +or the extension yields only marginal benefits, we may not provide it +as part of Compat. @item Bug fixes are usually not ported back as part of Compat. Sometimes |