; Fix typos

3 files changed, 4 insertions, 4 deletions

diff --git a/doc/misc/calc.texi b/doc/misc/calc.texi
index 56ebc589960..381da21cebe 100644
--- a/doc/misc/calc.texi
+++ b/doc/misc/calc.texi
@@ -18973,7 +18973,7 @@ number between zero and one.  It is equivalent to @samp{random(1.0)}.
 @kindex k a
 @pindex calc-random-again
 The @kbd{k a} (@code{calc-random-again}) command produces another random
-number, re-using the most recent value of @expr{M}.  With a numeric
+number, reusing the most recent value of @expr{M}.  With a numeric
 prefix argument @var{n}, it produces @var{n} more random numbers using
 that value of @expr{M}.
 
diff --git a/doc/misc/modus-themes.org b/doc/misc/modus-themes.org
index 3e353dc356d..fb1df473f75 100644
--- a/doc/misc/modus-themes.org
+++ b/doc/misc/modus-themes.org
@@ -486,7 +486,7 @@ The reason we recommend ~load-theme~ instead of the other option of
 ~enable-theme~ is that the former does a kind of "reset" on the face
 specs.  It quite literally loads (or reloads) the theme.  Whereas the
 ~enable-theme~ function simply puts an already loaded theme to the top
-of the list of enabled items, re-using whatever state was last loaded.
+of the list of enabled items, reusing whatever state was last loaded.
 
 As such, ~load-theme~ reads all customizations that may happen during
 any given Emacs session: even after the initial setup of a theme.
@@ -2821,7 +2821,7 @@ Reload the theme for changes to take effect.
 #+cindex: Remapping faces
 
 There are cases where we need to change the buffer-local attributes of a
-face.  This might be because we have our own minor mode that re-uses a
+face.  This might be because we have our own minor mode that reuses a
 face for a particular purpose, such as a line selection tool that
 activates ~hl-line-mode~, but we wish to keep it distinct from other
 buffers.  This is where ~face-remap-add-relative~ can be applied and may
diff --git a/doc/misc/org.org b/doc/misc/org.org
index 5423cf59759..31431a6ffc9 100644
--- a/doc/misc/org.org
+++ b/doc/misc/org.org
@@ -16408,7 +16408,7 @@ The iCalendar format standard requires globally unique identifier---or
 UID---for each entry.  The iCalendar export backend creates UIDs
 during export.  To save a copy of the UID in the Org file set the
 variable ~org-icalendar-store-UID~.  The backend looks for the =ID=
-property of the entry for re-using the same UID for subsequent
+property of the entry for reusing the same UID for subsequent
 exports.
 
 Since a single Org entry can result in multiple iCalendar