Log in

or use your email

Search the Library

Keyword search across Doctrine Analysis, Core Glossary, Comparative Theology, and Regional Analysis. Mention a language name for the best results — e.g. "remnant burmese" or "what glossary terms conflict for burmese."

Type at least 2 characters to search.

Work with us

Tell us a bit about how you'd like to work with tri-bible.ai.

Stay informed Get our weekly newsletter. Never sold or shared, unsubscribe anytime.

Let us serve you Church leaders and ministry networks seeking translated curriculum Join our team Volunteers interested in reviewing translations
Download Translation Skill

Linguistic Gap Analysis

Linguistic Gap Analysis — Deuteronomy (English Destination Language Package)

Purpose and Scope

This is PRD Phase 1 Step 8. Because the destination language for this pipeline configuration is English and the source is also English, “linguistic gap” here does not mean cross-language untranslatability. It means the same phenomenon documented throughout the baseline Romans package and extended in 07_semantic_analysis.md/08_core_glossary.md: places where contemporary English vocabulary itself either (a) lacks a clean one-word equivalent for a load-bearing Hebrew concept (a genuine lexical gap), or (b) supplies a ready-made word whose dominant contemporary sense actively competes with, and can silently displace, Deuteronomy’s meaning (a crowded semantic neighborhood requiring fencing). This document consolidates both problem types across the full 34-chapter book, anchored in the core passage (Deut 6:1-9), and issues concrete transliteration-vs-paraphrase rulings plus a ranked risk list for Phase 2 handoff.

All term renderings below reuse 08_core_glossary.md and assets/bible_term_registry.json exactly; this document does not introduce new renderings, only organizes the existing register by gap type and fencing strategy and adds the ranked risk ordering PRD Step 8 requires.


1. Doctrine Vocabulary Matrix

DoctrineAvailable destination-language (English) termsWeaknesses of available vocabularyRecommended strategy
The Shema and Exclusive Love for God”hear,” “one,” “love,” “heart,” “fear,” “with all your heart/soul/might""Hear” is passive in modern usage (cf. therapeutic “I hear you”); “love” is romanticized/emotive; “heart” is emotion-coded rather than will-coded; “fear” is dread-coded and often reactively dropped by popular teaching; “one” (echad) sits inside live Jewish-Christian/Trinitarian debateRetain all baseline English words (no substitution) but attach mandatory explicit re-definition on first substantive use per document: “hear and obey,” “willed covenant loyalty” for love, “the seat of decision, not just feeling” for heart, “reverential awe, not anxious dread” for fear. State the curriculum’s own reading of echad explicitly (exclusive covenant claim + numerical monotheism) without adjudicating the wider Trinitarian debate as if Deut 6:4 settles it
Covenant Renewal”covenant,” “renew,” “assembly,” “oath""Covenant” defaults to a real-estate/contract-law sense (restrictive covenants, non-compete clauses); “renew” alone sounds administrative (subscription/license renewal) rather than a living relational re-commitment; English has no single word distinguishing a first covenant-making from a repeated covenant-renewal ceremonyPair “covenant” with explicit relational-not-legal-document framing on first use per document (per baseline rule); render the recurring ceremonies literally as “covenant renewal” rather than coining a new term, and note explicitly (chs. 5, 27, 29, 31) that renewal is Deuteronomy’s normal pattern, not evidence the first covenant failed or lapsed
Blessings and Curses of the Covenant”blessed,” “cursed,” “blessing,” “curse”Severe trivialization drift: “#blessed” hashtag culture and reflexive “bless you” (sneeze) on one side; superstition/folklore “curse” (haunted objects, sports curses) and casual profanity “cursing” on the other — neither register conveys real, historical, conditional, God-administered covenant sanctionNo substitute term exists that escapes trivialization better than “blessed”/“cursed” themselves (paraphrases like “covenant reward/penalty” lose the personal, relational force and biblical-language continuity into Gal 3:13). Retain “blessed”/“cursed” but require an explicit historical anchor (the Babylonian exile as the curse list’s actual fulfillment) on first substantive use per document, mirroring the baseline’s “grace”/“election” fencing pattern
Remembering God’s Redemption”remember,” “forget,” “teach diligently,” “firstfruits""Remember” and “forget” are both passive-cognition words in contemporary English (a fact recalled or dropped, morally neutral); Deuteronomy treats both as active — remembering produces obedience, forgetting produces idolatry. “Teach diligently” loses the “sharpen/repeat incisively” image of shanan if read as generic instructionExplicitly re-teach “remember” and “forget” as action-producing, not passive-recall, on each doctrinally load-bearing occurrence (5:15; 6:12; 8:2, 11, 18-19; 24:9); render shanan as “teach diligently” but gloss the sharpening/repetition sense at least once per document rather than leaving “diligently” to carry the whole weight
Obedience Motivated by Love not Merit”obey,” “obedience,” “love,” “circumcise the heart,” “commandments”Contemporary Western autonomy culture treats “obedience” with default suspicion (servility, “just following orders” — cf. baseline’s obedience_of_faith note); “circumcise” is almost exclusively clinical/surgical in modern usage with no live metaphorical currencyDistinguish explicitly, per document, between merit-based compliance (rejected) and love-motivated response (Deuteronomy’s actual pattern, cf. 6:5’s love preceding 6:6-9’s commands); supply the literal covenant-sign background before deploying “circumcise the heart” as metaphor, and flag the internal shift from command (10:16) to divine promise (30:6) as theologically significant, not incidental
The Coming Prophet like Moses”prophet,” “servant of the LORD,” “raise up""Prophet” is diluted by secular usage (“a tech prophet,” “a prophet of doom”); “servant” risks a demeaning/menial reading in contemporary usage, inverting an honorific titleElevate “prophet” beyond the baseline’s general Low/Medium treatment to explicit messianic framing at 18:15-19 (cf. Acts 3:22; 7:37); state plainly that this is a unique, climactic fulfillment in Christ, not one prophet among an open series; explicitly reframe “servant” as an exalted covenant-mediator title before its occurrence at 34:5
Choosing Life over Death”choose,” “life,” “death""Choose life” (30:19) is a live, widely recognized contemporary American political slogan (the pro-life/abortion debate); “life” and “death” default to individual-eternal-destiny categories for readers steeped in later NT usage, obscuring Deuteronomy’s own primarily this-worldly, national-covenantal senseExplicitly name and set aside the modern political slogan association before unpacking Moses’ actual meaning (covenant loyalty vs. abandonment, national historical consequence); state the historical/this-worldly primary sense of “life and death” here while noting, without collapsing the distinction, its later development into NT eternal categories (e.g. Rom 6:23)
Warnings against Idolatry”idol,” “carved image,” “detestable,” “jealous,” “utterly destroy,” “high places""Detestable”/“abomination” is narrowed in contemporary public discourse to a single contested modern flashpoint despite covering a genuinely wide Deuteronomic range; “jealous” is almost entirely negative/pathological in modern relationship discourse; “utterly destroy” (cherem) draws strong pre-formed secular moral objection (New Atheist-style critique) before any teaching beginsRepresent the full, accurate range of to’evah occurrences chapter by chapter rather than either narrowing to or avoiding the one contemporary flashpoint; actively re-teach “jealous” as rightful, exclusive covenant zeal rather than insecurity; supply Deuteronomy’s own covenantal-judicial, historically bounded framing for cherem without softening, euphemizing, or omitting it — mandatory theologian review on every occurrence, matching the baseline’s atonement/propitiation escalation tier

2. Full-Book Coverage Checklist

Every chapter of Deuteronomy was reviewed for load-bearing vocabulary in 07_semantic_analysis.md/08_core_glossary.md. This table confirms coverage and explicitly notes chapters contributing no new terms beyond those already registered, per the PRD’s full-coverage mandate.

ChaptersStatusNotes
1–3Reviewed — no new load-bearing termsHistorical narrative recap of the wilderness journey; “Israel,” “covenant,” and “law” background terms apply but introduce nothing new; conquest language here anticipates the cherem treatment fully developed at ch. 7, 20
4Covered”carved image” (pesel), “jealous God” (qanna), “election”/“treasured possession” backdrop, “statutes and judgments”
5Covered”covenant” renewal pattern, “statutes and judgments,” Decalogue restatement (no new terms beyond ch. 4/6 register)
6Covered (core passage)“hear (Shema),” “one (echad),” “love,” “heart,” “fear,” “teach diligently,” “frontlets,” “doorposts”
7Covered”election”/“treasured possession,” “holy,” “detestable,” cherem background
8Covered”remember,” “forget”
9–10Covered”stiff-necked,” “circumcise the heart,” “Father”-adjacent covenant-formation language reviewed, no new term beyond ch. 6/8 register
11Reviewed — reuses ch. 6/28 register”blessed”/“cursed” preview, “love,” no new terms
12Covered”the place the LORD will choose”
13Covered”detestable” (occult/false prophecy), “prophet” (false-prophet warning, sharpens ch. 18)
14Covered”clean and unclean,” “tithe”
15Reviewed — grouped with civil-law clusterDebt release, generosity law; reuses “covenant civil law cluster” register
16Covered”pilgrimage festivals” (Passover, Weeks, Booths)
17Covered”king,” “the place the LORD will choose” (reuse)
18Covered”prophet like Moses,” “detestable” (occult practices)
19Reviewed — grouped with civil-law clusterWitnesses, cities of refuge
20Coveredcherem (“utterly destroy”) — warfare regulations
21Covered”curse of God”/hanged man (Gal 3:13 link), civil-law cluster (unsolved murder, captive bride, firstborn rights)
22Covered”detestable” (mixed categories/cross-dressing)
23Covered”assembly of the LORD,” “detestable” (cultic prostitution wages)
24Reviewed — grouped with civil-law clusterCertificate of divorce
25Covered”detestable” (dishonest weights), levirate marriage (civil-law cluster)
26Covered”holy people”/“saints,” “firstfruits,” “treasured possession”/election
27Covered”covenant” renewal ceremony, “cursed” (Ebal recitation)
28Covered”blessed”/“cursed” — full covenant blessing/curse lists
29Covered”covenant” renewal (Moab), “oath”
30Covered”choose” (“choose life”), “circumcise the heart” (promise form), “life and death”
31Covered”be strong and courageous,” “covenant” (Torah deposited)
32Covered”the Rock,” “vengeance,” “Father” (32:6), “jealous God” (reuse)
33Reviewed — reuses ch. 28 registerMosaic blessing of the tribes; no new terms beyond “blessed”
34Covered”servant of the LORD” (Moses’ death)

No chapter was silently omitted; chapters without new terms are explicitly logged above as reviewed.


3. Missing Vocabulary (Genuine Lexical Gaps)

These are Hebrew concepts for which no single existing English word carries the full semantic load without supplementary explanation — the destination language is missing a clean lexical equivalent, not merely competing with a false friend.

Hebrew conceptNearest single English wordWhat the single word fails to carryGap-filling strategy
shema (שְׁמַע)“hear”Built-in obedient response; English “hear” stops at auditory reception or, worse, signals mere therapeutic acknowledgment (“I hear you”) with no commitment to actRender as “hear (and obey)” or gloss explicitly on first use; do not rely on “hear” alone to carry Deut 6:4’s full force
ahav in covenant context (אָהַב)“love”Willed, commanded, total-person covenant loyalty; English “love” defaults to spontaneous, uncommanded romantic/emotional feelingRetain “love” (no better one-word substitute exists) but explicitly re-anchor as commanded, willed devotion every occurrence in doctrinally central passages (6:5; 7:9; 10:12; 11:1; 13:3; 30:6, 16, 20)
levav (לֵבָב)“heart”Seat of will and moral decision; English “heart” is post-Romantic and almost exclusively emotion-codedNo substitute word (“mind,” “will”) captures the full integrated decision-and-affection sense; retain “heart” with explicit definitional correction on first use
shanan (שָׁנַן)“teach diligently”The literal image of sharpening/repeated incisive instructionSupply the sharpening image explicitly at least once; “diligently” alone is a flat intensifier, not an image
cherem (חֵרֶם)“utterly destroy,” “devote to destruction”A specialized covenant-war legal category (irrevocable ban, removing objects/persons from ordinary human claim) with no everyday English equivalent at allNo single word suffices; retain the descriptive phrase and supply Deuteronomy’s own covenantal-judicial framing explicitly every time — this is a structural gap, not merely a false-friend risk
qesheh-oref (קְשֵׁה־עֹרֶף)“stiff-necked”The specific yoke-resistant draft-animal imageRetain the traditional idiom (already reasonably transparent) but supply the agricultural image briefly
am segullah (עַם סְגֻלָּה)“treasured possession”A legal/relational category of personally valued property with no exact modern parallel (not mere “favorite” or “special”)Retain the phrase; supplement with 7:7’s explicit denial that size or merit grounds the choice
to’evah (תּוֹעֵבָה)“detestable”/“abomination”The category’s genuinely wide range (idolatry, occult practice, dishonest commerce, cross-dressing, cultic-prostitution wages) versus English usage’s narrowing to one contemporary controversyNo single word escapes this; the gap is not lexical absence but range mismatch — supply the full documented range explicitly per occurrence rather than assuming the word alone communicates it
naqam (נָקָם)“vengeance”God’s judicial, non-imitable prerogative versus English “vengeance“‘s inherently personal, imitable, petty connotationExplicitly state the non-imitability (cf. Rom 12:19) every time; “vengeance” alone invites the wrong (imitable) reading

4. Crowded Semantic Neighborhoods Needing Fencing

These are English words that are not missing — they exist and are commonly used — but sit in an overcrowded contemporary semantic space with strong competing senses that will confidently displace Deuteronomy’s meaning unless explicitly fenced off.

English wordCompeting contemporary senses crowding the neighborhoodFencing required
loveRomantic/emotional spontaneity (“falling in love,” “love at first sight”)Fence: this is commanded, willed, covenantal loyalty, not a feeling one falls into or out of
heartSeat of emotion (romantic, sentimental)Fence: seat of will/decision in Hebrew anthropology
fearAnxiety, dread, phobia; also actively suppressed in some popular “God is only love” teachingFence: reverential covenant awe, paired with love, not terror — and must not be silently dropped
jealous (of God)Insecure, controlling, a relationship red flag in popular psychologyFence: rightful, exclusive covenant zeal that only God has standing to claim
blessed”#blessed” social-media trivialization; reflexive “bless you”Fence: real, historical, conditional covenant-fidelity consequence
cursedSuperstition/folklore (haunted objects, sports curses); casual profanityFence: real, personal, God-administered covenant sanction, historically fulfilled in exile
choose / “choose life”Contemporary American pro-life political sloganFence: explicitly name and set aside the political frame; restore covenant-loyalty-vs.-abandonment sense
covenantReal-estate/contract-law “restrictive covenant”Fence: relational, promissory bond, not a fixed legal document, and one that Deuteronomy itself renews rather than only originates
lawCivil/criminal statute, bureaucratic codeFence: personal instruction from “the LORD your God,” not impersonal ordinance
election / “chosen people”Political voting (baseline); contemporary Israeli-Palestinian political discourse (this curriculum’s extension)Fence both senses explicitly; distinguish ancient corporate covenant election from both the modern political vote and the live geopolitical conflict
holy / saints”Holier-than-thou,” canonized-elite Catholic/Orthodox usageFence: corporate, all-Israel/all-believer identity, not individual sanctimony or an ascetic few
servantMenial, demeaning employment connotationFence: exalted covenant-mediator honorific title
remember / forgetNeutral, morally innocent cognitive eventsFence: active, action-producing (remember) or morally culpable (forget) covenant categories
father (of God)Painful/absent human father associations for some readers; Catholic priestly addressFence with both doctrinal explanation and pastoral sensitivity
kingHistorical curiosity or ceremonial figurehead in republicsFence: an active ruling authority nonetheless subject to Torah — transferable by analogy to any human power structure
detestable/abominationNarrowed public usage to one contested modern controversyFence: represent the text’s genuinely wide range accurately, chapter by chapter
frontlets (if rendered “phylacteries”)Matt 23:5’s negative Pharisaic-hypocrisy associationFence: distinguish the sincere original command from later ostentatious misuse; respect ongoing devout Jewish practice
circumcise (the heart)Exclusively clinical/surgical modern usageFence: supply the literal covenant-sign background before the metaphor is usable at all
put to the test (if rendered “tempt”)Modern “tempted to sin” enticement senseFence: distinguish testing/proving from enticement toward wrongdoing

5. Transliteration vs. Paraphrase Decisions

TermDecisionRationale
Shema (שְׁמַע)Paraphrase in running text (“hear and obey”); transliterate as a proper title when naming the confession as a unit (e.g., “the Shema,” referring to Deut 6:4 as a whole)English readers already encounter “the Shema” as a named confession in comparative-religion and interfaith contexts; using it as a title aids recognition, but the verb itself must be paraphrased/glossed in running exposition so the obedience sense is not lost
echad (אֶחָד)Paraphrase (“one”) with explicit theological comment, not transliterationNo recognition benefit to transliterating a basic numeral; the risk is interpretive, not lexical
ahav (אָהַב)Paraphrase (“love”) with mandatory re-anchoring glossTransliterating would create unnecessary jargon for a word most readers already have; the fix is definitional, not lexical substitution
levav (לֵבָב)Paraphrase (“heart”) with glossSame reasoning as above
totafot (טוֹטָפֹת)Paraphrase, avoiding the traditional “phylacteries” rendering; use “frontlets” and add a transliterated cross-reference note to tefillin for readers wanting the living Jewish-practice term”Phylacteries” imports Matt 23:5’s negative connotation by association; “frontlets” is neutral; naming tefillin respectfully acknowledges the term’s continued devout use rather than treating it as obsolete curiosity
cherem (חֵרֶם)Paraphrase (“utterly destroy” / “devote to destruction”); do not transliterateTransliterating an unfamiliar term for the single most morally fraught concept in the book would obscure rather than clarify meaning at first encounter; plain English description, fully explained, is more defensible than a technical-sounding foreign label that could seem euphemistic
to’evah (תּוֹעֵבָה)Paraphrase (“detestable”); do not transliterateSame reasoning: a Hebrew label risks sounding like a hedge; plain English with explicit range-mapping is preferred
qanna (קַנָּא)Paraphrase (“jealous God”); do not transliterateEstablished English Bible tradition already uses “jealous”; transliteration would break with reader-familiar phrasing for no clarity gain
am segullah (עַם סְגֻלָּה)Paraphrase (“treasured possession”); do not transliterateEstablished rendering; transliteration adds no comprehension value
bachar (בָּחַר)Paraphrase (“choose”); do not transliterateThe risk here is a contemporary political collision, not unfamiliarity; transliteration would not fix that risk and would add unnecessary jargon
berakah / arur (בְּרָכָה / אָרוּר)Paraphrase (“blessed”/“cursed”); do not transliterateDeep integration into English Bible tradition and hymnody; transliteration would sever the Gal 3:13 canonical link
tsur (צוּר, “the Rock”)Paraphrase (“the Rock,” capitalized as a divine title); do not transliterateAlready a stable English Bible-tradition title; transliteration adds nothing and would sever the 1 Cor 10:4 link
eved Adonai (עֶבֶד יְהוָה)Paraphrase (“servant of the LORD”); do not transliterateStandard title; needs definitional fencing (see Section 4), not transliteration
Pilgrimage festival names (Pesach, Shavuot, Sukkot)Hybrid: use established English names (“Passover,” “Feast of Weeks,” “Feast of Booths”) as primary rendering, with Hebrew transliteration and later Greek/NT-era name (“Shavuot”/“Pentecost”) noted alongside for cross-referenceBridges Deuteronomy’s own vocabulary to Acts 2’s “Pentecost” for readers tracing the whole-Bible thread, without replacing the established English liturgical names
chazak ve-ematz (“be strong and courageous”)Paraphrase, no transliterationPurely idiomatic exhortation; transliteration would add jargon without benefit, and the risk (secular self-help drift) is definitional, not lexical

General rule derived from this analysis: transliteration is reserved for (a) already-recognized proper nouns/titles familiar from comparative-religion or interfaith usage (“the Shema”), and (b) cases where naming the Hebrew term alongside the English gloss builds a respectful bridge to a living, continuing devout practice (tefillin, mezuzah). It is explicitly avoided for morally fraught or politically sensitive terms (cherem, to’evah, bachar), where a foreign-sounding label risks reading as an evasive euphemism rather than as clarifying precision.


6. Ranked List of Highest-Risk Ambiguities

Ranked by combined weight of: doctrinal centrality to this curriculum’s eight named doctrines, strength of competing contemporary sense, and presence of a live political/denominational collision (the two factors the baseline treats as more dangerous than sheer obsolescence, because they produce confident misreading rather than a flagged comprehension gap).

  1. “Choose life” (bachar, Deut 30:19) — Choosing Life over Death. Collides directly with a live, contested contemporary American political slogan; confident misreading is nearly guaranteed without explicit intervention. Mandatory theologian review.
  2. “Utterly destroy” (cherem) — Warnings against Idolatry. Highest pre-formed reader resistance of any term in the book; secular moral critique arrives fully formed before teaching begins. Mandatory theologian review on every occurrence.
  3. “Detestable”/“abomination” (to’evah) — Warnings against Idolatry. Public discourse has narrowed a genuinely wide category to one flashpoint; risk of both under- and over-representing the text. Mandatory theologian review.
  4. “Jealous God” (qanna) — The Shema and Exclusive Love for God / Warnings against Idolatry. Near-total negative connotation capture in popular psychology; risks making God sound insecure. Mandatory theologian review.
  5. “Love” (ahav) in Deut 6:5 — The Shema and Exclusive Love for God. Core-passage term; romantic-feeling drift risks converting the central command into optional sentiment.
  6. “Blessed”/“cursed” (berakah/arur) — Blessings and Curses of the Covenant. Severe hashtag/superstition trivialization on both ends of the pair; doctrine-defining vocabulary for an entire named doctrine.
  7. “Treasured possession”/election (am segullah, bachar) — Covenant Renewal (election dimension). Compounds the baseline’s political-voting false-friend with live Israeli-Palestinian political sensitivity.
  8. “Hear” (shema) — The Shema and Exclusive Love for God. Core-passage opening word; passive-acknowledgment drift (“I hear you”) undercuts the entire confession’s obedient-response force from its very first word.
  9. “Heart” (levav) — The Shema and Exclusive Love for God / Obedience Motivated by Love not Merit. Mirror-image risk to “love”: emotion-coding displaces will/decision-coding throughout the book’s central command structure.
  10. “Fear” (yare) — The Shema and Exclusive Love for God. Double risk: dread-coded misreading, or reactive suppression by well-meaning popular teaching that drops the term altogether, flattening the love/fear pairing.
  11. “Prophet like Moses” (Deut 18:15-19) — The Coming Prophet like Moses. Elevated beyond baseline’s general “prophet” treatment; failure to state the unique messianic climax explicitly risks reducing Christ to one prophet among many.
  12. “Circumcise the heart” — Obedience Motivated by Love not Merit. Almost entirely clinical modern connotation; metaphor is inert without supplied literal background, and the command-to-promise shift (10:16 → 30:6) is easily missed.
  13. “Covenant” renewal pattern — Covenant Renewal. Real-estate/contract false friend compounds with reader assumption that a covenant, once made, needs no renewal.
  14. “Curse of God”/hanged man (Deut 21:22-23) — Blessings and Curses of the Covenant. Load-bearing Galatians 3:13 cross-reference; risk of being left as an isolated ancient legal detail disconnected from the cross.
  15. “Vengeance” (naqam) — Blessings and Curses of the Covenant (contrast register). Risk of reading as license for personal retaliation rather than its actual point (removing retribution from human hands, per Rom 12:19).

7. Recommendations for Phase 2 Handoff

  1. Items ranked 1–4 above require mandatory human theologian review on every occurrence, matching the baseline’s escalation tier for atonement/propitiation language — no segment containing them may be marked approved without explicit clarifying context present in the drafted material.
  2. Items ranked 5–10 require the same first-substantive-use-per-document explicit clarification rule the baseline mandates for Critical false-friend terms (justification, election, grace, etc.); this curriculum extends that rule to “love,” “heart,” “fear,” “blessed,” “cursed,” and “hear.”
  3. The political/culture-war collision category (items 1, 3, 7) should be formally added to the standing risk-category framework in doctrine_risk_registry.json during the next registry update, as already flagged in 08_core_glossary.md.
  4. Transliteration should remain the exception, not the default, per Section 5’s general rule — reserved for named confessions (“the Shema”) and living-practice bridge terms (tefillin, mezuzah), never for morally or politically fraught categories where a foreign label risks reading as euphemism.
  5. Chapters logged as “reviewed, no new terms” in Section 2 should still receive full narrative/expository treatment in Phase 2 content — the absence of new vocabulary does not mean the absence of doctrinal content requiring careful handling (e.g., the conquest narratives in chs. 1-3 anticipate the cherem fencing developed later and should not be treated as doctrinally inert filler).

Library content is free and openly licensed under CC BY-NC-SA 4.0 — share and adapt it for non-commercial use, with attribution to tri-bible.ai.

Give feedback

How would you rate this page?

0 / 500 words