From 523453ac3e1e2daab53df0d5a2c7868181adb16e Mon Sep 17 00:00:00 2001
From: Adrian <andamian@gmail.com>
Date: Mon, 26 Jan 2026 14:53:15 -0800
Subject: [PATCH] small typos

---
 DALI.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/DALI.tex b/DALI.tex
index 883513c..f67d054 100644
--- a/DALI.tex
+++ b/DALI.tex
@@ -586,7 +586,7 @@ \subsection{Tables: VOSI-tables}
 describe their content
 as a tableset: schemas, tables, and columns.
 
-A concrete DAL service specification will specify if the VOSI-tables endpoint is
+A concrete DAL service specification will specify whether the VOSI-tables endpoint is
 permitted or required and may restrict the endpoint name or location.
 Since DAL services with a VOSI-tables endpoint will specify
 in the capabilities which version they are using, DAL services can make use of
@@ -980,7 +980,7 @@ \subsection{Shape}
   <PARAM name="ID" datatype="char" arraysize="23"
          ucd="meta.id;meta.dataset" value="cadc:IRIS/I212B2H0.fits" />
   ...
-  <PARAM name="POS" datatytpe="char" arraysize="*" xtype="shape"
+  <PARAM name="POS" datatype="char" arraysize="*" xtype="shape"
          ucd="obs.field" value="">
     <VALUES>
       <MAX value="polygon 134.38 -6.37 134.42 6.01
@@ -1170,7 +1170,7 @@ \subsubsection{RESPONSEFORMAT}
 of the result(s) the client can retrieve from the UWS result list
 endpoint; if a DALI-async job creates multiple results, the RESPONSEFORMAT
 should control the primary result type, but details can be specific to
-individual service specifications. While the list of supported values are
+individual service specifications. While the list of supported values is
 specific to a concrete service specification, the general usage is to support
 values that are MIME media types \citep{std:MIME} for known
 formats as well as