form, typically @code{(@var{high} @var{low} @var{micro} @var{pico})};
otherwise, they use @code{(@var{ticks} . @var{hz})} form. Currently
this variable defaults to @code{t}, for behavior compatible with
-previous Emacs versions. Developers are encourage to test
+previous Emacs versions. Developers are encouraged to test
timestamp-related code with this variable set to @code{nil}, as it
will default to @code{nil} in a future Emacs version, and will be
removed in some version after that.
functions default to timestamps of the forms (HI LO US PS), (HI LO US)
or (HI LO), which are less regular and less efficient. This is part
of a long-planned change first documented in Emacs 27. Developers are
-encourage to test timestamp-related code with this variable set to
+encouraged to test timestamp-related code with this variable set to
nil, as it will default to nil in a future Emacs version and will be
removed some time after that.
related functions return timestamps in list form, typically
\(HIGH LOW USEC PSEC); otherwise, they use (TICKS . HZ) form.
Currently this variable defaults to t, for behavior compatible with
-previous Emacs versions. Developers are encourage to test
+previous Emacs versions. Developers are encouraged to test
timestamp-related code with this variable set to nil, as it will
default to nil in a future Emacs version, and will be removed in some
version after that. */);