From 79e06752cc349d7c132cf9ee0c1655337039092c Mon Sep 17 00:00:00 2001
From: Amanda Galtman <40716346+galtm@users.noreply.github.com>
Date: Mon, 9 Sep 2024 11:17:04 -0400
Subject: [PATCH] Fix a typo (ordinarly) (#19)

---
 xspec/schematron-xspec.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xspec/schematron-xspec.md b/xspec/schematron-xspec.md
index b0d8331e..46923eb7 100644
--- a/xspec/schematron-xspec.md
+++ b/xspec/schematron-xspec.md
@@ -37,7 +37,7 @@ sampleXML-.-|embeds or\nreferences|testingXSLT
 
 ## XProc implementation
 
-As depicted, a ready-to-go XSLT (**Compiled XSLT**) imports a ready-to-go XSLT (**Compiled Schematron XSLT** produced using the commodity tool) as if it were a compiled XSpec XSLT importing a target XSLT. In the usual case this is the XSLT under test -- and indeed ordinarly we would run the Schematron by producing and running it. In this case, however, the upstream compiled XSLT does not exist unless the processor compiles the upstream Schematron to produce it. An XSLT that does not exist is difficult to import from another module.
+As depicted, a ready-to-go XSLT (**Compiled XSLT**) imports a ready-to-go XSLT (**Compiled Schematron XSLT** produced using the commodity tool) as if it were a compiled XSpec XSLT importing a target XSLT. In the usual case this is the XSLT under test -- and indeed ordinarily we would run the Schematron by producing and running it. In this case, however, the upstream compiled XSLT does not exist unless the processor compiles the upstream Schematron to produce it. An XSLT that does not exist is difficult to import from another module.
 
 Rather than introduce a file-system or other runtime dependency into XProc - which would 'prefer' to be entirely side-effect-free - the pipeline here modifies the (compiled) XSLT on the fly, replacing its `xsl:import` instruction with the literal templates to be imported.