From beaa77d2d6c119da0251de254bc1b8b751129a7a Mon Sep 17 00:00:00 2001
From: Dirk Jagdmann <doj@cubic.org>
Date: Mon, 23 Mar 2020 03:04:48 -0700
Subject: [PATCH 158/170] fix whitespace

---
 doc/coding.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/coding.sgml b/doc/coding.sgml
index dc07c091..57961209 100644
--- a/doc/coding.sgml
+++ b/doc/coding.sgml
@@ -251,7 +251,7 @@ Register variables may give faster and shorter code, but they do also have an
 overhead. Register variables are actually zero page locations, so using them
 saves roughly one cycle per access. The calling routine may also use register
 variables, so the old values have to be saved on function entry and restored
-on exit. Saving an d restoring has an overhead of about 70 cycles per 2 byte
+on exit. Saving and restoring has an overhead of about 70 cycles per 2 byte
 variable. It is easy to see, that - apart from the additional code that is
 needed to save and restore the values - you need to make heavy use of a
 variable to justify the overhead.
-- 
2.26.0