From 180bb0823a5c92ae1db2cde9d30cf818a7e2a6be Mon Sep 17 00:00:00 2001
From: Oliver Schmidt <ol.sc@web.de>
Date: Mon, 3 Dec 2018 12:52:00 +0100
Subject: [PATCH] Fixed typo.

---
 doc/apple2.sgml    | 2 +-
 doc/apple2enh.sgml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/apple2.sgml b/doc/apple2.sgml
index f61a8a68e..ac5059902 100644
--- a/doc/apple2.sgml
+++ b/doc/apple2.sgml
@@ -492,7 +492,7 @@ files show up in a directory as <tt/&lt;NO DATE&gt;/.
 
 There's no common interface to set realtime clocks so if a realtme clock <bf/IS/
 present there's just nothing to do. However, if there's <bf/NO/ realtime clock present,
-the user might very well be interest to "manually" set the RAM location in order to
+the user might very well be interested to "manually" set the RAM location in order to
 have timestamps. But he surely doesn't want to manually set the RAM location over and
 over again. Rather he wants to set it just once after booting ProDOS 8.
 
diff --git a/doc/apple2enh.sgml b/doc/apple2enh.sgml
index 649c6ef9f..d8d24ea32 100644
--- a/doc/apple2enh.sgml
+++ b/doc/apple2enh.sgml
@@ -493,7 +493,7 @@ files show up in a directory as <tt/&lt;NO DATE&gt;/.
 
 There's no common interface to set realtime clocks so if a realtme clock <bf/IS/
 present there's just nothing to do. However, if there's <bf/NO/ realtime clock present,
-the user might very well be interest to "manually" set the RAM location in order to
+the user might very well be interested to "manually" set the RAM location in order to
 have timestamps. But he surely doesn't want to manually set the RAM location over and
 over again. Rather he wants to set it just once after booting ProDOS 8.
 
-- 
2.39.5