From 0ed41db478ccf77b89aca8c6e9e959b0c113336c Mon Sep 17 00:00:00 2001
From: Oliver Schmidt <ol.sc@web.de>
Date: Mon, 5 Apr 2021 23:50:07 +0200
Subject: [PATCH] Some minor clarifications.

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

diff --git a/doc/apple2.sgml b/doc/apple2.sgml
index 91c02c7ad..f957e1247 100644
--- a/doc/apple2.sgml
+++ b/doc/apple2.sgml
@@ -575,15 +575,13 @@ url="ca65.html" name="assembler manual">.
 
   <tag>Explanation of File Types</tag>
 
-  ProDOS associates a file type and an auxiliary type with each file.
+  ProDOS 8 associates a file type and an auxiliary type with each file.
   These type specifications are separate from the file's name, unlike
   Windows which uses the file name's suffix (a.k.a.
   extension) to specify the file type. For example, <tt/.exe/,
   <tt/.doc/, or <tt/.bat/.
-  The ProDOS low-level
-  Machine-Language Interface (MLI) functions for creating and opening
-  files require these types to be specified. And if they don't match
-  with the file being opened, the operation may fail.
+  The ProDOS 8 Machine-Language Interface (MLI) function for creating a
+  file require these types to be specified.
 
   In contrast, the ISO C function <tt/fopen()/ and the POSIX function
   <tt/open()/ have no parameter to specify either a file type or an
@@ -606,8 +604,6 @@ url="ca65.html" name="assembler manual">.
   The header file <tt/apple2_filetype.h/ also defines many values
   that can be used to set these variables. It is included in
   <tt/apple2.h/, which is in turn included in <tt/apple2enh.h/.
-  So it isn't necessary to include it directly. Just
-  include one of <tt/apple2.h/ or <tt/apple2enh.h/.
 
   <tag>Example</tag>
 
@@ -624,8 +620,8 @@ url="ca65.html" name="assembler manual">.
   carriage return instead of a line-feed (Linux/BSD/MacOS) or
   carriage return, line-feed pair (Windows).
 
-  The "sequential" text file terminology is in contrast to a
-  "random-access" text file which would
+  The 'sequential' text file terminology is in contrast to a
+  'random-access' text file which would
   have a fixed-length, non-zero record length, so that the
   file position of any individual record can be calculated.
 
diff --git a/doc/apple2enh.sgml b/doc/apple2enh.sgml
index 2d4381353..4aafbc256 100644
--- a/doc/apple2enh.sgml
+++ b/doc/apple2enh.sgml
@@ -580,15 +580,13 @@ url="ca65.html" name="assembler manual">.
 
   <tag>Explanation of File Types</tag>
 
-  ProDOS associates a file type and an auxiliary type with each file.
+  ProDOS 8 associates a file type and an auxiliary type with each file.
   These type specifications are separate from the file's name, unlike
   Windows which uses the file name's suffix (a.k.a.
   extension) to specify the file type. For example, <tt/.exe/,
   <tt/.doc/, or <tt/.bat/.
-  The ProDOS low-level
-  Machine-Language Interface (MLI) functions for creating and opening
-  files require these types to be specified. And if they don't match
-  with the file being opened, the operation may fail.
+  The ProDOS 8 Machine-Language Interface (MLI) function for creating a
+  file require these types to be specified.
 
   In contrast, the ISO C function <tt/fopen()/ and the POSIX function
   <tt/open()/ have no parameter to specify either a file type or an
@@ -611,8 +609,6 @@ url="ca65.html" name="assembler manual">.
   The header file <tt/apple2_filetype.h/ also defines many values
   that can be used to set these variables. It is included in
   <tt/apple2.h/, which is in turn included in <tt/apple2enh.h/.
-  So it isn't necessary to include it directly. Just
-  include one of <tt/apple2.h/ or <tt/apple2enh.h/.
 
   <tag>Example</tag>
 
@@ -629,8 +625,8 @@ url="ca65.html" name="assembler manual">.
   carriage return instead of a line-feed (Linux/BSD/MacOS) or
   carriage return, line-feed pair (Windows).
 
-  The "sequential" text file terminology is in contrast to a
-  "random-access" text file which would
+  The 'sequential' text file terminology is in contrast to a
+  'random-access' text file which would
   have a fixed-length, non-zero record length, so that the
   file position of any individual record can be calculated.