summaryrefslogtreecommitdiff
path: root/test
diff options
context:
space:
mode:
authorGreg Sjaardema <gsjaardema@gmail.com>2021-05-13 17:10:12 -0600
committerHans Kristian Rosbach <hk-github@circlestorm.org>2021-05-16 13:20:15 +0200
commit5339a31cf9349a7b7e7ab8a5a507fda917f53f87 (patch)
treee9183b87b6ef878f2f9156861a200f017f150d85 /test
parent54b1c13c37b53f2481f02576657cedfef29fce2f (diff)
downloadProject-Tick-5339a31cf9349a7b7e7ab8a5a507fda917f53f87.tar.gz
Project-Tick-5339a31cf9349a7b7e7ab8a5a507fda917f53f87.zip
Spelling fixes
Diffstat (limited to 'test')
-rw-r--r--test/abicheck.md2
-rw-r--r--test/data/lcet10.txt8
2 files changed, 5 insertions, 5 deletions
diff --git a/test/abicheck.md b/test/abicheck.md
index 6e9e58aade..3e291264ad 100644
--- a/test/abicheck.md
+++ b/test/abicheck.md
@@ -46,7 +46,7 @@ constantly downloading and building the old
version, you can check the .abi file into git.
To make this easier, a helper script could be written to automatically build
-all the configurations tested by .github/worflows/abicheck.yml
+all the configurations tested by .github/workflows/abicheck.yml
Then they could be checked into git en masse by a maintainer
when a new platform is added or a new major version (which
intentionally breaks backwards compatibility) is being prepared.
diff --git a/test/data/lcet10.txt b/test/data/lcet10.txt
index 26b187d048..1dbdfc56e4 100644
--- a/test/data/lcet10.txt
+++ b/test/data/lcet10.txt
@@ -897,7 +897,7 @@ current difficulty in exchanging electronically computer-based
instructional software, which in turn makes it difficult for one scholar
to build upon the work of others, will be resolved before too long.
Stand-alone curricular applications that involve electronic text will be
-sharable through networks, reinforcing their significance as intellectual
+shareable through networks, reinforcing their significance as intellectual
products as well as instructional tools.
The second aspect of electronic learning involves the use of research and
@@ -1587,7 +1587,7 @@ Bowdoin.
CALALUCA * PLD's principal focus and contribution to scholarship *
Various questions preparatory to beginning the project * Basis for
project * Basic rule in converting PLD * Concerning the images in PLD *
-Running PLD under a variety of retrieval softwares * Encoding the
+Running PLD under a variety of retrieval software * Encoding the
database a hard-fought issue * Various features demonstrated * Importance
of user documentation * Limitations of the CD-ROM version *
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
@@ -1654,7 +1654,7 @@ anything demonstrated at the Workshop.
What cannot practically be done is go back and reconvert and re-encode
data, a time-consuming and extremely costly enterprise. CALALUCA sees
PLD as a database that can, and should, be run under a variety of
-retrieval softwares. This will permit the widest possible searches.
+retrieval software. This will permit the widest possible searches.
Consequently, the need to produce a CD-ROM of PLD, as well as to develop
software that could handle some 1.3 gigabyte of heavily encoded text,
developed out of conversations with collection development and reference
@@ -5034,7 +5034,7 @@ schemes every single discrete area of a text that might someday be
searched. That was another decision. Searching by a column number, an
author, a word, a volume, permitting combination searches, and tagging
notations seemed logical choices as core elements. 3) How does one make
-the data available? Tieing it to a CD-ROM edition creates limitations,
+the data available? Tying it to a CD-ROM edition creates limitations,
but a magnetic tape file that is very large, is accompanied by the
encoding specifications, and that allows one to make local modifications
also allows one to incorporate any changes one may desire within the