added new folder

00-About_tT/tT-3-Appendix.md

@@ -2,7 +2,7 @@
 
 ## Decisions concerning the Translation Topics
 
-Many of the Translation Topics have links to other parts of the Wycliffe Associates Translation Manual. However only the topics that are addressed in either the Translation Notes or the Translation Words in this Translation Helps volume are included in this volume. Because of that, some of the links to other parts of the Translation Manual do not work. If you want to read those other parts of the Translation Manual, you can see them on Bible in Every Language (https://read.bibletranslationtools.org/u/WycliffeAssociates/en_tm/). The links that do not work are black, and those that work are some other color.
+Many of the Translation Topics have links to other parts of the Translation Manual. However only the topics that are addressed in either the Translation Notes or the Translation Words in this Translation Helps volume are included in this volume. Because of that, some of the links to other parts of the Translation Manual do not work. If you want to read those other parts of the Translation Manual, you can see them on Bible in Every Language at (https://door43.org/u/WycliffeAssociates/en_ta/). The links that do not work are black, and those that work are some other color.
 
 ## How to use the Translation Topics
 
@@ -22,7 +22,8 @@ A box next to the description tells what question the page answers. It may also
   - Henry Whitney, BA in Education
   - James N. Pohlig, M.Div., MA in Linguistics, D. Litt. in Biblical Languages
   - Susan Quigley, MA in Linguistics
-  - Tabitha Price, BA in Education
+  - Tabitha Price, BA
+ 
   - Bev Staley
   - Carol Brinneman
   - Jody Garcia

00-tM_front&back/tM-1-Intro.md

@@ -2,9 +2,9 @@
 
 The Translation Manual is an open licensed manual on Bible translation. It teaches the basics of translation theory and a process for doing Bible translation, it provides practical helps for dealing with various translation issues, and it provides instruction and processes for checking translations.
 
-The Translation Manual is intended to empower anyone, anywhere to equip themselves for creating high-quality translations of biblical content into their own language. The manual is designed to be highly flexible. It can be used in a systematic, in-advance approach, or it can be used for just-in-time learning (or both, as needed). It is modular in structure.
+The Translation Manual is intended to empower anyone, anywhere to equip themselves for creating high-quality translations of biblical content into their own language. The manual is designed to be highly flexible. It can be used in a systematic, in-advance approach or it can be used for just-in-time learning (or both, as needed). It is modular in structure.
 
-The Translation Manual is written primarily for mother-tongue Bible translators who have had little or no prior training in translation. The English version of the manual is primarily for people who speak English as a second language. Because of this, we have tried to keep the writing style easy to understand.
+The Translation Manual is written primarily for mother-tongue Bible translators who have had little or no prior training in translation. The English version of the manual is primarily for people who speak English as a second language. Because of this we have tried to keep the writing style easy to understand.
 
 **You can learn more about the Translation Manual** in the Appendix to the Translation Manual, rc://en_tm/00-tM_front&back/tM-3-Appendix.md. It has the following sections:
 * Decisions Concerning the Translation Manual

archive/checking/acceptable/sub-title.md

@@ -1 +1,2 @@
-Did the translation team use an acceptable style?
+Did the translation team use an acceptable style?
+

archive/checking/accuracy-check/sub-title.md

@@ -1 +1,2 @@
-How can I do an accuracy check?
+How can I do an accuracy check?
+

archive/checking/accuracy/sub-title.md

@@ -1 +1,2 @@
-Is the translation accurate?
+Is the translation accurate?
+

archive/checking/accurate/sub-title.md

@@ -1 +1,2 @@
-Is the translation accurate?
+Is the translation accurate?
+

archive/checking/alphabet/sub-title.md

@@ -1 +1,2 @@
-Does the translation use an appropriate alphabet?
+Does the translation use an appropriate alphabet?
+

archive/checking/alphabetchoice/sub-title.md

@@ -1 +1,2 @@
-Does the translation use an appropriate alphabet?
+Does the translation use an appropriate alphabet?
+

archive/checking/authentic-assessment/sub-title.md

@@ -1 +1,2 @@
-How do we design a rubric for the quality of our translation?
+How do we design a rubric for the quality of our translation?
+

archive/checking/authority-level1/sub-title.md

@@ -1 +1,2 @@
-What is affirmation level one?
+What is affirmation level one?
+

archive/checking/authority-level2/sub-title.md

@@ -1 +1,2 @@
-What is affirmation level two?
+What is affirmation level two?
+

archive/checking/authority-level3/sub-title.md

@@ -1 +1,2 @@
-What is affirmation level three?
+What is affirmation level three?
+

archive/checking/authority-process/sub-title.md

@@ -1 +1,2 @@
-What is the difference between the authority to check a Bible translation and the process for checking?
+What is the difference between the authority to check a Bible translation and the process for checking?
+

archive/checking/church-leader-check/sub-title.md

@@ -1 +1,2 @@
-How can the church leaders help improve the translation?
+How can the church leaders help improve the translation?
+

archive/checking/church-leader-check2/sub-title.md

@@ -1 +1,2 @@
-How can the church leaders help improve the translation?
+How can the church leaders help improve the translation?
+

archive/checking/clear/sub-title.md

@@ -1 +1,2 @@
-How can I tell if the translation is clear?
+How can I tell if the translation is clear?
+

archive/checking/community-evaluation/sub-title.md

@@ -1 +1,2 @@
-How can I show that the community approves the translation?
+How can I show that the community approves the translation?
+

archive/checking/complete/sub-title.md

@@ -1 +1,2 @@
-Is the translation complete?
+Is the translation complete?
+

archive/checking/config.yaml

@@ -1,232 +0,0 @@
-acceptable:
-  recommended:
-    - alphabet
-    - complete
-  dependencies:
-    - clear
-    - natural
-    - church-leader-check
-accuracy-check:
-  recommended:
-    - level2
-    - language-community-check
-    - church-leader-check
-    - other-methods
-    - guidelines-accurate
-  dependencies:
-    - level1
-    - guidelines-accurate
-    - important-term-check
-accurate:
-  recommended:
-    - complete
-    - accuracy-check
-    - guidelines-accurate
-  dependencies:
-    - alphabet
-    - church-leader-check
-alphabet:
-  recommended: []
-  dependencies:
-    - acceptable
-    - translate-alphabet
-authority-level1:
-  recommended:
-    - authority-level2
-    - level1
-  dependencies:
-    - authority-process
-authority-level2:
-  recommended:
-    - authority-level3
-  dependencies:
-    - authority-level1
-authority-level3:
-  recommended:
-    - level3
-    - level1
-  dependencies:
-    - authority-level2
-authority-process:
-  recommended:
-    - authority-level1
-    - level1
-  dependencies:
-    - goal-checking
-church-leader-check:
-  recommended:
-    - accuracy-check
-    - accurate
-    - good
-  dependencies:
-    - level2
-clear:
-  recommended:
-    - acceptable
-    - natural
-    - guidelines-clear
-    - language-community-check
-  dependencies:
-    - level2
-community-evaluation:
-  recommended:
-    - church-leader-check
-    - self-assessment
-  dependencies:
-    - language-community-check
-    - other-methods
-    - writing-decisions
-complete:
-  recommended:
-    - self-assessment
-    - good
-  dependencies:
-    - accurate
-formatting:
-  recommended:
-    - alphabet
-    - spelling
-    - punctuation
-  dependencies:
-    - vol2-things-to-check
-goal-checking:
-  recommended:
-    - intro-checking
-    - authority-process
-  dependencies:
-    - intro-levels
-good:
-  recommended:
-    - self-assessment
-    - level3
-  dependencies:
-    - complete
-headings:
-  recommended:
-    - community-evaluation
-  dependencies:
-    - acceptable
-    - punctuation
-    - verses
-important-term-check:
-  recommended:
-    - accuracy-check
-  dependencies:
-    - level1
-    - peer-check
-intro-check:
-  recommended:
-    - intro-checking
-  dependencies:
-    - translate-manual
-intro-checking:
-  recommended:
-    - intro-levels
-  dependencies:
-    - intro-check
-intro-levels:
-  recommended:
-    - intro-levels
-    - level1
-  dependencies:
-    - intro-checking
-language-community-check:
-  recommended:
-    - natural
-    - other-methods
-    - writing-decisions
-    - community-evaluation
-  dependencies:
-    - level2
-level1:
-  recommended:
-    - statement-of-faith
-    - translation-guidelines
-    - accuracy-check
-  dependencies:
-    - intro-levels
-level1-affirm:
-  recommended:
-    - level2
-  dependencies:
-    - statement-of-faith
-    - translation-guidelines
-    - level1
-    - accuracy-check
-level2:
-  recommended:
-    - language-community-check
-    - church-leader-check
-    - self-assessment
-    - good
-  dependencies:
-    - intro-levels
-    - accuracy-check
-level3:
-  recommended:
-    - level3-questions
-    - self-assessment
-  dependencies:
-    - intro-levels
-    - level2
-    - accuracy-check
-level3-approval:
-  recommended: []
-  dependencies:
-    - level3
-    - level3-questions
-    - self-assessment
-level3-questions:
-  recommended:
-    - accuracy-check
-    - level3-approval
-    - self-assessment
-  dependencies:
-    - level3
-natural:
-  recommended:
-    - acceptable
-    - guidelines-natural
-    - language-community-check
-  dependencies:
-    - alphabet
-    - level2
-    - clear
-other-methods:
-  recommended:
-    - writing-decisions
-    - community-evaluation
-  dependencies:
-    - language-community-check
-peer-check:
-  recommended:
-    - important-term-check
-  dependencies:
-    - level1
-    - self-check
-self-assessment:
-  recommended:
-    - good
-    - accuracy-check
-    - language-community-check
-    - accurate
-    - clear
-    - natural
-    - level3-questions
-    - level3-approval
-  dependencies:
-    - complete
-    - church-leader-check
-    - level3
-self-check:
-  recommended:
-    - peer-check
-  dependencies:
-    - level1
-verses:
-  recommended:
-    - headings
-  dependencies:
-    - spelling
-    - punctuation
-    - alphabet

archive/checking/goal-checking/sub-title.md

@@ -1 +1,2 @@
-What is the goal of Checking?
+What is the goal of Checking?
+

archive/checking/good/sub-title.md

@@ -1 +1,2 @@
-How can church leaders affirm that the translation is good?
+How can church leaders affirm that the translation is good?
+

archive/checking/intro-check/sub-title.md

@@ -1 +1,2 @@
-What is Authentic Assessment and how does it apply to quality assurance?
+What is Authentic Assessment and how does it apply to quality assurance?
+

archive/intro/config.yaml

@@ -1,54 +0,0 @@
-finding-answers:
-  recommended:
-    - process-manual
-  dependencies:
-    - ta-intro
-gl-strategy:
-  recommended:
-    - finding-answers
-  dependencies:
-    - uw-intro
-    - open-license
-    - translate/translate-terms
-open-license:
-  recommended:
-    - gl-strategy
-    - translate-source-licensing
-  dependencies:
-    - uw-intro
-    - statement-of-faith
-    - translation-guidelines
-    - translate/translate-terms
-statement-of-faith:
-  recommended:
-    - translation-guidelines
-    - open-license
-    - translate-source-licensing
-  dependencies:
-    - uw-intro
-ta-intro:
-  recommended: []
-  dependencies: []
-translate-why:
-  recommended:
-    - guidelines-intro
-    - translate-process
-  dependencies:
-    - uw-intro
-    - translate-manual
-    - translate-whatis
-translation-guidelines:
-  recommended:
-    - open-license
-    - translate-manual
-    - intro-checking
-  dependencies:
-    - uw-intro
-    - statement-of-faith
-    - translate/translate-terms
-uw-intro:
-  recommended:
-    - statement-of-faith
-    - gl-strategy
-  dependencies:
-    - ta-intro

archive/intro/config.yaml2

@@ -1,51 +0,0 @@
-cobt-defined:
-  recommended:
-   - translate-why
-  dependencies: []
-finding-answers:
-  recommended:
-  dependencies:
-    - ta-intro
-gl-strategy:
-  recommended:
-    - finding-answers
-  dependencies:
-    - open-license
-    - translate/translate-terms
-guidelines-church-approved:
-  recommended:
-  dependencies:
-guidelines-collaborative:
-  recommended:
-  dependencies:
-guidelines-ongoing:
-  recommended:
-  dependencies:
-mast-intro:
-  recommended:
-  dependencies:
-open-license:
-  recommended:
-    - gl-strategy
-    - translate-source-licensing
-  dependencies:
-    - statement-of-faith
-    - translate/translate-terms
-statement-of-faith:
-  recommended:
-    - open-license
-    - translate-source-licensing
-  dependencies:
-ta-intro:
-  recommended: []
-  dependencies: []
-translate-why:
-  recommended:
-    - guidelines-intro
-    - translate-process
-  dependencies:
-    - translate-manual
-    - translate-whatis
-wa:
-  recommended: []
-  dependencies: []

archive/jit/config.yaml

@@ -1,510 +0,0 @@
-biblicalimageryta:
-  recommended: []
-  dependencies:
-    - figs-intro
-    - figs-metaphor
-    - figs-metonymy
-bita-animals:
-  recommended: []
-  dependencies:
-    - bita-part1
-    - figs-metaphor
-    - figs-metonymy
-bita-farming:
-  recommended: []
-  dependencies:
-    - bita-part1
-    - figs-metaphor
-    - figs-metonymy
-bita-humanbehavior:
-  recommended: []
-  dependencies:
-    - bita-part1
-    - figs-metaphor
-    - figs-metonymy
-bita-hq:
-  recommended: []
-  dependencies:
-    - bita-part1
-    - figs-metaphor
-    - figs-metonymy
-bita-manmade:
-  recommended: []
-  dependencies:
-    - bita-part1
-    - figs-metaphor
-    - figs-metonymy
-bita-part1:
-  recommended: []
-  dependencies:
-    - biblicalimageryta
-    - figs-metaphor
-    - figs-simile
-bita-part2:
-  recommended: []
-  dependencies:
-    - biblicalimageryta
-    - figs-metonymy
-bita-part3:
-  recommended: []
-  dependencies:
-    - biblicalimageryta
-bita-phenom:
-  recommended: []
-  dependencies:
-    - bita-part1
-    - figs-metaphor
-    - figs-metonymy
-bita-plants:
-  recommended: []
-  dependencies:
-    - bita-part1
-    - figs-metaphor
-    - figs-metonymy
-figs-123person:
-  recommended:
-    - figs-you
-  dependencies:
-    - figs-explicitinfo
-    - figs-pronouns
-figs-abstractnouns:
-  recommended: []
-  dependencies:
-    - figs-partsofspeech
-    - figs-sentences
-figs-activepassive:
-  recommended:
-    - figs-abstractnouns
-    - figs-order
-  dependencies:
-    - figs-sentences
-    - figs-verbs
-figs-apostrophe:
-  recommended: []
-  dependencies:
-    - figs-intro
-figs-declarative:
-  recommended: []
-  dependencies:
-    - figs-sentencetypes
-figs-distinguish:
-  recommended:
-    - figs-doublenegatives
-  dependencies:
-    - figs-partsofspeech
-    - figs-sentences
-figs-doublenegatives:
-  recommended:
-    - figs-verbs
-  dependencies:
-    - figs-partsofspeech
-    - figs-sentences
-figs-doublet:
-  recommended: []
-  dependencies:
-    - figs-intro
-figs-ellipsis:
-  recommended: []
-  dependencies:
-    - figs-intro
-    - figs-sentences
-figs-euphemism:
-  recommended: []
-  dependencies:
-    - figs-intro
-figs-events:
-  recommended:
-    - writing-background
-    - writing-connectingwords
-    - writing-newevent
-    - translate-versebridge
-  dependencies:
-    - writing-intro
-    - figs-verbs
-figs-exclamations:
-  recommended: []
-  dependencies:
-    - figs-sentencetypes
-figs-exclusive:
-  recommended:
-    - figs-gendernotations
-  dependencies:
-    - figs-pronouns
-figs-exmetaphor:
-  recommended:
-    - bita-part1
-  dependencies:
-    - figs-metaphor
-    - figs-simile
-figs-explicit:
-  recommended:
-    - figs-explicitinfo
-  dependencies: []
-figs-explicitinfo:
-  recommended:
-    - figs-extrainfo
-  dependencies:
-    - figs-explicit
-figs-extrainfo:
-  recommended: []
-  dependencies:
-    - figs-explicit
-    - figs-explicitinfo
-figs-gendernotations:
-  recommended: []
-  dependencies:
-    - figs-pronouns
-    - figs-genericnoun
-figs-genericnoun:
-  recommended:
-    - figs-gendernotations
-  dependencies:
-    - figs-partsofspeech
-figs-go:
-  recommended: []
-  dependencies: []
-figs-grammar:
-  recommended: []
-  dependencies: []
-figs-hendiadys:
-  recommended:
-    - figs-doublet
-  dependencies:
-    - figs-intro
-    - figs-partsofspeech
-figs-hyperbole:
-  recommended: []
-  dependencies:
-    - figs-intro
-figs-hypo:
-  recommended: []
-  dependencies:
-    - writing-intro
-figs-idiom:
-  recommended: []
-  dependencies:
-    - figs-intro
-figs-imperative:
-  recommended: []
-  dependencies:
-    - figs-sentencetypes
-figs-intro:
-  recommended: []
-  dependencies: []
-figs-irony:
-  recommended:
-    - figs-litotes
-  dependencies:
-    - figs-intro
-figs-litotes:
-  recommended: []
-  dependencies:
-    - figs-intro
-figs-merism:
-  recommended: []
-  dependencies:
-    - figs-intro
-figs-metaphor:
-  recommended: []
-  dependencies:
-    - figs-intro
-    - figs-simile
-figs-metaphordead:
-  recommended: []
-  dependencies:
-    - figs-metaphor
-figs-metaphorparts:
-  recommended: []
-  dependencies:
-    - figs-metaphor
-figs-metonymy:
-  recommended: []
-  dependencies:
-    - figs-intro
-figs-nominaladj:
-  recommended: []
-  dependencies:
-    - figs-partsofspeech
-figs-order:
-  recommended: []
-  dependencies:
-    - figs-grammar
-    - figs-partsofspeech
-    - figs-sentences
-figs-parables:
-  recommended: []
-  dependencies:
-    - figs-intro
-figs-parallelism:
-  recommended:
-    - figs-personification
-  dependencies:
-    - figs-intro
-figs-partsofspeech:
-  recommended: []
-  dependencies:
-    - figs-grammar
-figs-pastforfuture:
-  recommended: []
-  dependencies:
-    - figs-intro
-    - figs-verbs
-figs-personification:
-  recommended:
-    - figs-apostrophe
-    - bita-part1
-  dependencies:
-    - figs-intro
-figs-possession:
-  recommended: []
-  dependencies:
-    - figs-partsofspeech
-    - figs-sentences
-figs-pronouns:
-  recommended: []
-  dependencies:
-    - figs-partsofspeech
-figs-quotations:
-  recommended:
-    - figs-quotesinquotes
-  dependencies:
-    - figs-pronouns
-    - figs-verbs
-    - writing-quotations
-figs-quotesinquotes:
-  dependencies:
-    - figs-quotations
-figs-rpronouns:
-  recommended: []
-  dependencies:
-    - figs-pronouns
-    - figs-sentences
-figs-rquestion:
-  recommended: []
-  dependencies:
-    - figs-intro
-    - figs-sentencetypes
-figs-sentences:
-  recommended:
-    - figs-order
-    - figs-distinguish
-  dependencies:
-    - figs-partsofspeech
-figs-sentencetypes:
-  recommended: []
-  dependencies: []
-figs-simile:
-  recommended:
-    - figs-metaphor
-    - bita-part1
-  dependencies:
-    - figs-intro
-figs-synecdoche:
-  recommended:
-    - figs-metonymy
-    - bita-part2
-  dependencies:
-    - figs-intro
-figs-verbs:
-  recommended:
-    - figs-sentences
-    - figs-activepassive
-    - figs-pastforfuture
-  dependencies:
-    - figs-partsofspeech
-figs-you:
-  recommended: []
-  dependencies:
-    - figs-yousingular
-    - figs-youdual
-figs-youcrowd:
-  recommended:
-    - figs-youdual
-  dependencies:
-    - figs-you
-    - figs-yousingular
-    - figs-pronouns
-figs-youdual:
-  recommended:
-    - figs-yousingular
-  dependencies:
-    - figs-you
-    - figs-pronouns
-    - figs-partsofspeech
-figs-youformal:
-  recommended:
-    - figs-youdual
-    - figs-yousingular
-  dependencies:
-    - figs-you
-    - figs-pronouns
-figs-yousingular:
-  recommended:
-    - figs-youdual
-  dependencies:
-    - figs-partsofspeech
-    - figs-you
-    - figs-pronouns
-guidelines-sonofgod:
-  recommended:
-    - guidelines-sonofgodprinciples
-  dependencies:
-    - guidelines-faithful
-guidelines-sonofgodprinciples:
-  recommended: []
-  dependencies:
-    - guidelines-faithful
-    - guidelines-sonofgod
-translate-bdistance:
-  recommended: []
-  dependencies:
-    - translate-decimal
-    - translate-fraction
-translate-bmoney:
-  recommended:
-    - translate-transliterate
-    - translate-unknown
-  dependencies: []
-translate-bvolume:
-  recommended:
-    - translate-fraction
-    - figs-explicitinfo
-  dependencies:
-    - translate-decimal
-translate-bweight:
-  recommended:
-    - translate-decimal
-    - translate-fraction
-  dependencies: []
-translate-decimal:
-  recommended: []
-  dependencies:
-    - translate-numbers
-    - translate-fraction
-translate-fraction:
-  recommended:
-    - translate-ordinal
-    - translate-bmoney
-  dependencies:
-    - translate-numbers
-translate-hebrewmonths:
-  recommended:
-    - translate-ordinal
-  dependencies: []
-translate-names:
-  recommended:
-    - translate-transliterate
-  dependencies:
-    - translate-unknown
-translate-numbers:
-  recommended:
-    - translate-ordinal
-    - translate-fraction
-  dependencies:
-    - translate-unknown
-translate-ordinal:
-  recommended:
-    - translate-fraction
-  dependencies:
-    - translate-numbers
-translate-symaction:
-  recommended: []
-  dependencies:
-    - translate-unknown
-translate-textvariants:
-  recommended:
-    - translate-chapverse
-    - translate-manuscripts
-    - translate-terms
-    - translate-original
-  dependencies:
-    - translate-source-text
-    - translate-manuscripts
-translate-transliterate:
-  recommended: []
-  dependencies:
-    - translate-unknown
-translate-unknown:
-  recommended:
-    - translate-transliterate
-    - translate-names
-  dependencies:
-    - figs-sentences
-translate-versebridge:
-  recommended:
-    - translate-chapverse
-  dependencies:
-    - translate-bibleorg
-writing-apocalypticwriting:
-  recommended: []
-  dependencies:
-    - writing-intro
-    - writing-symlanguage
-writing-background:
-  recommended:
-    - writing-connectingwords
-    - writing-newevent
-  dependencies:
-    - figs-events
-    - writing-intro
-writing-connectingwords:
-  recommended: []
-  dependencies:
-    - figs-partsofspeech
-    - figs-sentences
-writing-endofstory:
-  recommended: []
-  dependencies:
-    - writing-intro
-    - writing-background
-writing-intro:
-  recommended:
-    - writing-background
-    - writing-connectingwords
-    - writing-newevent
-    - writing-participants
-    - figs-events
-    - writing-poetry
-    - writing-proverbs
-    - writing-quotations
-    - writing-symlanguage
-  dependencies:
-    - writing-decisions
-writing-newevent:
-  recommended:
-    - writing-background
-    - writing-participants
-  dependencies:
-    - writing-intro
-    - figs-events
-writing-participants:
-  recommended:
-    - writing-pronouns
-  dependencies:
-    - figs-partsofspeech
-    - writing-intro
-writing-poetry:
-  recommended:
-    - writing-symlanguage
-  dependencies:
-    - figs-intro
-    - writing-intro
-writing-pronouns:
-  recommended: []
-  dependencies:
-    - figs-pronouns
-    - figs-sentences
-writing-proverbs:
-  recommended: []
-  dependencies:
-    - figs-metaphor
-    - figs-parallelism
-    - writing-intro
-writing-quotations:
-  recommended:
-    - figs-quotations
-  dependencies: []
-writing-symlanguage:
-  recommended: []
-  dependencies:
-    - writing-intro

archive/translate/config.yaml

@@ -1,432 +0,0 @@
-choose-team:
-  recommended:
-    - qualifications
-    - translate-source-text
-    - translate-alphabet
-    - writing-decisions
-  dependencies:
-    - guidelines-intro
-    - translate-whatis
-    - translate-why
-file-formats:
-  recommended: []
-  dependencies: []
-level1:
-  recommended:
-    - translate-help
-  dependencies:
-    - translation-difficulty
-    - translate-source-text
-    - writing-decisions
-first-draft:
-  recommended:
-    - translate-help
-  dependencies:
-    - translation-difficulty
-    - translate-source-text
-    - writing-decisions
-guidelines-accurate:
-  recommended:
-    - guidelines-clear
-    - guidelines-natural
-    - guidelines-church-approved
-    - translate-process
-  dependencies:
-    - guidelines-intro
-    - translation-guidelines
-guidelines-authoritative:
-  recommended:
-    - translate-discover
-  dependencies:
-    - guidelines-intro
-    - translation-guidelines
-guidelines-church-approved:
-  recommended:
-    - guidelines-clear
-    - guidelines-natural
-    - guidelines-accurate
-    - intro-check
-  dependencies:
-    - guidelines-intro
-    - translation-guidelines
-guidelines-clear:
-  recommended:
-    - guidelines-natural
-    - guidelines-accurate
-    - guidelines-church-approved
-    - translate-process
-  dependencies:
-    - guidelines-intro
-    - translation-guidelines
-guidelines-collaborative:
-  recommended:
-    - translate-discover
-  dependencies:
-    - guidelines-intro
-    - translation-guidelines
-guidelines-equal:
-  recommended:
-    - translate-discover
-    - figs-intro
-    - figs-rquestion
-  dependencies:
-    - guidelines-intro
-    - translation-guidelines
-guidelines-faithful:
-  recommended:
-    - translate-discover
-  dependencies:
-    - guidelines-intro
-    - translation-guidelines
-guidelines-historical:
-  recommended:
-    - translate-discover
-  dependencies:
-    - guidelines-intro
-    - translation-guidelines
-guidelines-intro:
-  recommended:
-    - guidelines-clear
-    - guidelines-natural
-    - guidelines-accurate
-    - guidelines-church-approved
-    - translate-process
-  dependencies:
-    - translation-guidelines
-    - translate-manual
-    - translate-whatis
-    - translate-terms
-guidelines-natural:
-  recommended:
-    - guidelines-clear
-    - guidelines-accurate
-    - guidelines-church-approved
-    - translate-process
-  dependencies:
-    - guidelines-intro
-    - translation-guidelines
-guidelines-ongoing:
-  recommended:
-    - translate-discover
-  dependencies:
-    - guidelines-intro
-    - translation-guidelines
-guidelines-sonofgod:
-  recommended:
-    - guidelines-sonofgodprinciples
-  dependencies:
-    - guidelines-faithful
-guidelines-sonofgodprinciples:
-  recommended: []
-  dependencies:
-    - guidelines-faithful
-    - guidelines-sonofgod
-mast:
-  recommended:
-    - qualifications
-    - translate-source-text
-    - self-check
-    - peer-check
-    - important-term-check
-    - accuracy-check
-  dependencies:
-    - guidelines-intro
-    - translate-whatis
-    - translate-why
-    - translate-alphabet
-    - writing-decisions  
-presentation-punctuation:
-  recommended:
-    - verses
-  dependencies:
-    - spelling
-    - translate-alphabet
-    - alphabet
-presentation-spelling:
-  recommended:
-    - punctuation
-  dependencies:
-    - vol2-intro
-    - acceptable
-    - translate-alphabet
-    - alphabet    
-qualifications:
-  recommended:
-    - translate-source-text
-  dependencies:
-    - choose-team
-resources-alter:
-  recommended: []
-  dependencies:
-    - translate-help
-    - resources-types
-resources-alterm:
-  recommended: []
-  dependencies:
-    - translate-help
-    - resources-types
-    - resources-alter
-resources-connect:
-  recommended: []
-  dependencies:
-    - translate-help
-    - resources-types
-resources-def:
-  recommended:
-    - resources-eplain
-    - resources-types
-  dependencies:
-    - translate-help
-    - resources-types
-resources-eplain:
-  recommended:
-    - resources-def
-  dependencies:
-    - translate-help
-    - resources-types
-resources-fofs:
-  recommended: []
-  dependencies:
-    - translate-help
-    - resources-types
-    - resources-alter
-resources-iordquote:
-  recommended: []
-  dependencies:
-    - translate-help
-    - resources-types
-resources-links:
-  recommended:
-    - resources-types
-    - resources-porp
-  dependencies:
-    - translate-help
-resources-long:
-  recommended: []
-  dependencies:
-    - translate-help
-    - resources-alter
-    - resources-fofs
-resources-porp:
-  recommended:
-    - resources-types
-  dependencies:
-    - translate-help
-    - resources-types
-resources-questions:
-  recommended:
-    - guidelines-faithful
-  dependencies:
-    - translate-help
-resources-synequi:
-  recommended:
-    - resources-types
-  dependencies:
-    - translate-help
-    - resources-types
-resources-types:
-  recommended:
-    - resources-links
-  dependencies:
-    - translate-help
-resources-words:
-  recommended:
-    - guidelines-faithful
-    - translate-unknown
-  dependencies:
-    - resources-porp
-    - translate-help
-translate-alphabet:
-  recommended:
-    - writing-decisions
-  dependencies:
-    - choose-team
-    - translate-source-text
-translate-bibleorg:
-  recommended:
-    - translate-chapverse
-  dependencies:
-    - translate-source-text
-translate-chapverse:
-  recommended:
-    - translate-versebridge
-  dependencies:
-    - translate-bibleorg
-translate-dynamic:
-  recommended:
-    - translate-tform
-  dependencies:
-    - guidelines-intro
-    - translate-process
-    - translate-literal
-    - translate-fandm
-translate-fandm:
-  recommended:
-    - translate-literal
-    - translate-dynamic
-    - translate-levels
-    - translate-form
-  dependencies:
-    - translate-process
-    - translate-discover
-    - translate-retell
-translate-form:
-  recommended:
-    - translate-literal
-    - translate-dynamic
-    - translate-levels
-  dependencies:
-    - translate-fandm
-    - translate-process
-    - translate-discover
-    - translate-retell
-translate-formatsignals:
-  recommended:
-    - translate-versebridge
-  dependencies:
-    - translate-process
-    - translate-bibleorg
-translate-help:
-  recommended:
-    - resources-types
-  dependencies:
-    - translation-difficulty
-translate-levels:
-  recommended:
-    - translate-literal
-    - translate-dynamic
-  dependencies:
-    - translate-fandm
-    - translate-discover
-    - translate-form
-translate-literal:
-  recommended:
-    - translate-dynamic
-  dependencies:
-    - translate-whatis
-    - translate-process
-    - translate-fandm
-    - translate-terms
-translate-manual:
-  recommended:
-    - translate-why
-    - guidelines-intro
-    - translate-process
-    - translation-difficulty
-  dependencies:
-    - ta-intro
-    - translation-guidelines
-    - finding-answers
-translate-manuscripts:
-  recommended:
-    - translate-chapverse
-    - translate-manuscripts
-    - translate-original
-    - translate-terms
-    - translate-textvariants
-  dependencies:
-    - translate-source-text
-translate-more:
-  recommended: []
-  dependencies:
-    - translate-whatis
-    - translate-why
-translate-original:
-  recommended:
-    - translate-chapverse
-    - translate-manuscripts
-    - translate-terms
-    - translate-textvariants
-  dependencies:
-    - translate-process
-    - translate-source-text
-translate-problem:
-  recommended:
-    - translate-dynamic
-  dependencies:
-    - translate-literal
-    - translate-wforw
-    - translate-fandm
-translate-process:
-  recommended:
-    - translate-discover
-    - translate-retell
-    - translate-terms
-    - translate-fandm
-  dependencies:
-    - translate-manual
-    - guidelines-intro
-translate-retell:
-  recommended:
-    - translate-fandm
-    - translate-terms
-    - translate-literal
-    - translate-dynamic
-  dependencies:
-    - translate-process
-    - translate-discover
-translate-source-licensing:
-  dependencies:
-    - translate-source-text
-    - open-license
-translate-source-text:
-  recommended:
-    - translate-source-licensing
-    - translate-original
-  dependencies:
-    - choose-team
-    - translate-terms
-translate-terms:
-  recommended:
-    - translate-whatis
-  dependencies:
-    - translate-manual
-translate-tform:
-  recommended:
-    - choose-team
-  dependencies:
-    - translate-dynamic
-    - translate-process
-    - translate-fandm
-    - translate-why
-translate-useulbudb:
-  recommended: []
-  dependencies:
-    - translate-whatis
-    - translate-why
-    - translate-more
-translate-wforw:
-  recommended:
-    - translate-problem
-    - figs-intro
-    - translate-dynamic
-  dependencies:
-    - translate-literal
-    - translate-fandm
-translate-whatis:
-  recommended:
-    - translate-why
-    - guidelines-intro
-    - translate-process
-    - translate-fandm
-    - translate-literal
-    - translate-dynamic
-  dependencies:
-    - translate-manual
-translation-difficulty:
-  recommended:
-    - qualifications
-    - translate-source-text
-    - translate-alphabet
-    - writing-decisions
-  dependencies:
-    - guidelines-intro
-    - translate-whatis
-    - translate-why
-writing-decisions:
-  recommended:
-    - translation-difficulty
-    - writing-intro
-  dependencies:
-    - translate-source-text
-    - choose-team

archive/translate/config.yaml2

@@ -1,420 +0,0 @@
-choose-team:
-  recommended:
-    - qualifications
-    - translate-source-text
-    - translate-alphabet
-    - writing-decisions
-  dependencies:
-    - guidelines-intro
-    - translate-whatis
-    - translate-why
-file-formats:
-  recommended: []
-  dependencies: []
-level1:
-  recommended:
-    - translate-help
-  dependencies:
-    - translation-difficulty
-    - translate-source-text
-    - writing-decisions
-first-draft:
-  recommended:
-    - translate-help
-  dependencies:
-    - translation-difficulty
-    - translate-source-text
-    - writing-decisions
-guidelines-accurate:
-  recommended:
-    - guidelines-clear
-    - guidelines-natural
-    - guidelines-church-approved
-    - translate-process
-  dependencies:
-    - guidelines-intro
-guidelines-authoritative:
-  recommended:
-    - translate-discover
-  dependencies:
-    - guidelines-intro
-guidelines-church-approved:
-  recommended:
-    - guidelines-clear
-    - guidelines-natural
-    - guidelines-accurate
-    - intro-check
-  dependencies:
-    - guidelines-intro
-guidelines-clear:
-  recommended:
-    - guidelines-natural
-    - guidelines-accurate
-    - guidelines-church-approved
-    - translate-process
-  dependencies:
-    - guidelines-intro
-guidelines-collaborative:
-  recommended:
-    - translate-discover
-  dependencies:
-    - guidelines-intro
-guidelines-equal:
-  recommended:
-    - translate-discover
-    - figs-intro
-    - figs-rquestion
-  dependencies:
-    - guidelines-intro
-guidelines-faithful:
-  recommended:
-    - translate-discover
-  dependencies:
-    - guidelines-intro
-guidelines-historical:
-  recommended:
-    - translate-discover
-  dependencies:
-    - guidelines-intro
-guidelines-intro:
-  recommended:
-    - guidelines-clear
-    - guidelines-natural
-    - guidelines-accurate
-    - guidelines-church-approved
-    - translate-process
-  dependencies:
-    - translate-manual
-    - translate-whatis
-    - translate-terms
-guidelines-natural:
-  recommended:
-    - guidelines-clear
-    - guidelines-accurate
-    - guidelines-church-approved
-    - translate-process
-  dependencies:
-    - guidelines-intro
-guidelines-ongoing:
-  recommended:
-    - translate-discover
-  dependencies:
-    - guidelines-intro
-guidelines-sonofgod:
-  recommended:
-    - guidelines-sonofgodprinciples
-  dependencies:
-    - guidelines-faithful
-guidelines-sonofgodprinciples:
-  recommended: []
-  dependencies:
-    - guidelines-faithful
-    - guidelines-sonofgod
-mast:
-  recommended:
-    - qualifications
-    - translate-source-text
-    - self-check
-    - peer-check
-    - important-term-check
-    - accuracy-check
-  dependencies:
-    - guidelines-intro
-    - translate-whatis
-    - translate-why
-    - translate-alphabet
-    - writing-decisions  
-presentation-punctuation:
-  recommended:
-    - verses
-  dependencies:
-    - spelling
-    - translate-alphabet
-    - alphabet
-presentation-spelling:
-  recommended:
-    - punctuation
-  dependencies:
-    - vol2-intro
-    - acceptable
-    - translate-alphabet
-    - alphabet    
-qualifications:
-  recommended:
-    - translate-source-text
-  dependencies:
-    - choose-team
-resources-alter:
-  recommended: []
-  dependencies:
-    - translate-help
-    - resources-types
-resources-alterm:
-  recommended: []
-  dependencies:
-    - translate-help
-    - resources-types
-    - resources-alter
-resources-connect:
-  recommended: []
-  dependencies:
-    - translate-help
-    - resources-types
-resources-def:
-  recommended:
-    - resources-eplain
-    - resources-types
-  dependencies:
-    - translate-help
-    - resources-types
-resources-eplain:
-  recommended:
-    - resources-def
-  dependencies:
-    - translate-help
-    - resources-types
-resources-fofs:
-  recommended: []
-  dependencies:
-    - translate-help
-    - resources-types
-    - resources-alter
-resources-iordquote:
-  recommended: []
-  dependencies:
-    - translate-help
-    - resources-types
-resources-links:
-  recommended:
-    - resources-types
-    - resources-porp
-  dependencies:
-    - translate-help
-resources-long:
-  recommended: []
-  dependencies:
-    - translate-help
-    - resources-alter
-    - resources-fofs
-resources-porp:
-  recommended:
-    - resources-types
-  dependencies:
-    - translate-help
-    - resources-types
-resources-questions:
-  recommended:
-    - guidelines-faithful
-  dependencies:
-    - translate-help
-resources-synequi:
-  recommended:
-    - resources-types
-  dependencies:
-    - translate-help
-    - resources-types
-resources-types:
-  recommended:
-    - resources-links
-  dependencies:
-    - translate-help
-resources-words:
-  recommended:
-    - guidelines-faithful
-    - translate-unknown
-  dependencies:
-    - resources-porp
-    - translate-help
-translate-alphabet:
-  recommended:
-    - writing-decisions
-  dependencies:
-    - choose-team
-    - translate-source-text
-translate-bibleorg:
-  recommended:
-    - translate-chapverse
-  dependencies:
-    - translate-source-text
-translate-chapverse:
-  recommended:
-    - translate-versebridge
-  dependencies:
-    - translate-bibleorg
-translate-dynamic:
-  recommended:
-    - translate-tform
-  dependencies:
-    - guidelines-intro
-    - translate-process
-    - translate-literal
-    - translate-fandm
-translate-fandm:
-  recommended:
-    - translate-literal
-    - translate-dynamic
-    - translate-levels
-    - translate-form
-  dependencies:
-    - translate-process
-    - translate-discover
-    - translate-retell
-translate-form:
-  recommended:
-    - translate-literal
-    - translate-dynamic
-    - translate-levels
-  dependencies:
-    - translate-fandm
-    - translate-process
-    - translate-discover
-    - translate-retell
-translate-formatsignals:
-  recommended:
-    - translate-versebridge
-  dependencies:
-    - translate-process
-    - translate-bibleorg
-translate-help:
-  recommended:
-    - resources-types
-  dependencies:
-    - translation-difficulty
-translate-levels:
-  recommended:
-    - translate-literal
-    - translate-dynamic
-  dependencies:
-    - translate-fandm
-    - translate-discover
-    - translate-form
-translate-literal:
-  recommended:
-    - translate-dynamic
-  dependencies:
-    - translate-whatis
-    - translate-process
-    - translate-fandm
-    - translate-terms
-translate-manual:
-  recommended:
-    - translate-why
-    - guidelines-intro
-    - translate-process
-    - translation-difficulty
-  dependencies:
-    - ta-intro
-    - finding-answers
-translate-manuscripts:
-  recommended:
-    - translate-chapverse
-    - translate-manuscripts
-    - translate-original
-    - translate-terms
-    - translate-textvariants
-  dependencies:
-    - translate-source-text
-translate-more:
-  recommended: []
-  dependencies:
-    - translate-whatis
-    - translate-why
-translate-original:
-  recommended:
-    - translate-chapverse
-    - translate-manuscripts
-    - translate-terms
-    - translate-textvariants
-  dependencies:
-    - translate-process
-    - translate-source-text
-translate-problem:
-  recommended:
-    - translate-dynamic
-  dependencies:
-    - translate-literal
-    - translate-wforw
-    - translate-fandm
-translate-process:
-  recommended:
-    - translate-discover
-    - translate-retell
-    - translate-terms
-    - translate-fandm
-  dependencies:
-    - translate-manual
-    - guidelines-intro
-translate-retell:
-  recommended:
-    - translate-fandm
-    - translate-terms
-    - translate-literal
-    - translate-dynamic
-  dependencies:
-    - translate-process
-    - translate-discover
-translate-source-licensing:
-  dependencies:
-    - translate-source-text
-    - open-license
-translate-source-text:
-  recommended:
-    - translate-source-licensing
-    - translate-original
-  dependencies:
-    - choose-team
-    - translate-terms
-translate-terms:
-  recommended:
-    - translate-whatis
-  dependencies:
-    - translate-manual
-translate-tform:
-  recommended:
-    - choose-team
-  dependencies:
-    - translate-dynamic
-    - translate-process
-    - translate-fandm
-    - translate-why
-translate-useulbudb:
-  recommended: []
-  dependencies:
-    - translate-whatis
-    - translate-why
-    - translate-more
-translate-wforw:
-  recommended:
-    - translate-problem
-    - figs-intro
-    - translate-dynamic
-  dependencies:
-    - translate-literal
-    - translate-fandm
-translate-whatis:
-  recommended:
-    - translate-why
-    - guidelines-intro
-    - translate-process
-    - translate-fandm
-    - translate-literal
-    - translate-dynamic
-  dependencies:
-    - translate-manual
-translation-difficulty:
-  recommended:
-    - qualifications
-    - translate-source-text
-    - translate-alphabet
-    - writing-decisions
-  dependencies:
-    - guidelines-intro
-    - translate-whatis
-    - translate-why
-writing-decisions:
-  recommended:
-    - translation-difficulty
-    - writing-intro
-  dependencies:
-    - translate-source-text
-    - choose-team

archive/translate/file-formats/01.md

@@ -9,9 +9,9 @@ For many years, the standard format for Bible translation has been USFM (which s
 
 USFM is a type of markup language that tells a computer program how to format the text. For instance, each chapter is marked like this "\c 1" or "\c 33". Verse markers might look like "\v 8" or "\v 14". Paragraphs are marked "\p". There are many other markers like this that have specific meaning. So a passage like John 1:1-2 in USFM will look like this:
 
-   \c 1  
-   \p  
-   \v 1 In the beginning was the Word, and the Word was with God, and the Word was God.  
+   \c 1
+   \p
+   \v 1 In the beginning was the Word, and the Word was with God, and the Word was God.
    \v 2 This one, the Word, was in the beginning with God.
 
 When a computer program that can read USFM sees this, it is able to format all of the chapter markers the same way (for instance, with a larger number) and all the verse numbers the same way (for instance, with a small superscript number).
@@ -22,11 +22,11 @@ To read more about USFM notation, please read http://paratext.org/about/usfm .
 
 #### How To Do a Bible Translation in USFM
 
-Most people do not know how to write using USFM markers. This is one of the reasons why BTT Writer was created. When you do a translation in BTT Writer, what you see looks very similar to a normal word processor document without showing the USFM markers. This way, when you upload your translation from BTT Writer, what is being uploaded is already formatted in USFM.
+Most people do not know how to write using USFM markers. This is one of the reasons why translationStudio was created. When you do a translation in translationStudio, what you see looks very similar to a normal word processor document without showing the USFM markers. This way, when you upload your translation from translationStudio, what is being uploaded is already formatted in USFM.
 
 #### Converting a Translation to USFM
 
-Though we strongly encourage translators to only do a translation using USFM markers, sometimes they do a translation without using USFM markers. This type of translation still can be used, but first the USFM markers must be added. One way to do this is to copy and paste it into BTT Writer, then place the verse markers in the correct place. When this is done, the translation will be able to be exported as USFM. This is a very arduous task, so we strongly recommend doing your Bible translation work from the beginning in BTT Writer or some other program that uses USFM markers.
+Though it is strongly encouraged to only do a translation using USFM markers, sometimes a translation is done without using USFM. This type of translation still can be used, but first the USFM markers must be added. One way to do this is to copy and paste it into translationStudio, then place the verse markers in the correct place. When this is done, the translation will be able to be exported as USFM. This is a very arduous task, so we strongly recommend doing your Bible translation work from the beginning in translationStudio or some other program that uses USFM markers.
 
 ### Conclusion
 
@@ -35,3 +35,4 @@ The easiest way to get content marked up with USFM is by using an editor that is
 *Note: Making text bold, italic, or underlined in a word processor does not make it bold, italic, or underlined in a markup language. This type of formatting must be done by writing the designated symbols.*
 
 When contemplating which software to use, please keep in mind that translation is not just about words; there are many technical aspects that need to be taken into consideration. Whatever software is used, just remember that Bible translations need to be written using USFM markers.
+

checking/chk-consistency/01.md

@@ -4,21 +4,21 @@ Consistency checking is also part of the proofreading near the end of the refine
 
 #### Important Words
 
-Check the important words throughout the whole translation to see that you have translated them in a consistent way. This does not mean that they must always be translated the same way, but that each sense of the word is translated in the same way. (See [Key Word Check](../../checking/chk-key-words/01.md))
+Check the important words throughout the whole translation to see that you have translated them in a consistent way. This does not mean that they must always be translated the same way, but that each sense of the word is translated in the same way. (See [Key Word Check](../checking/key-word-check/01.md))
 
 #### Spelling
 
-It will be good to have a consistent way of spelling all the words in your language. But in your checks, you may want to focus on checking the spelling of key terms, words you have borrowed from another language, and the names of people and places. (See: [Consistent Spelling](../../translate/presentation-spelling/01.md))
+It will be good to have a consistent way of spelling all the words in your language. But in your checks, you may want to focus on checking the spelling of key terms, words you have borrowed from another language, and the names of people and places. (See: [Consistent Spelling](../translate/presentation-spelling/01.md))
 
 #### Punctuation 
 
-Check to see what decisions your team has made concerning punctuation, and make sure that it is used in a consistent way throughout your Bible. (See [Consistent Punctuation](../../translate/presentation-punctuation/01.md))
+Check to see what decisions your team has made concerning punctuation, and make sure that it is used in a consistent way throughout your Bible. (See [Consistent Punctuation](../translate/presentation-punctuation/01.md))
 
 #### Formatting  
 
-Translators can use formatting to help readers understand how a text is organized. (See: [Formatting](../../translate/presentation-formatting/01.md))
+Translators can use formatting to help readers understand how a text is organized. (See: [Formatting](../translate/presentation-formatting/01.md))
 
-**Paragraphs** help readers see how ideas are organized. If you use paragraph breaks in your translation, check to see that the breaks are in places that will be helpful for the readers. If  you have a chapter with only one or two paragraphs, you may want to see if it could be broken up more. You may use the paragraph breaks in the Unlocked Literal Bible as a guide. You can see paragraphs in the Unlocked Literal Bible at [Bibleineverylanguage.org](https://read.bibletranslationtools.org/u/WycliffeAssociates/en_ulb). 
+**Paragraphs** help readers see how ideas are organized. If you use paragraph breaks in your translation, check to see that the breaks are in places that will be helpful for the readers. If  you have a chapter with only one or two paragraphs, you may want to see if it could be broken up more. You may use the paragraph breaks in the Unlocked Literal Bible as a guide. You can see paragraphs in the Unlocked Literal Bible at [Bibleineverylanguage.org](https://door43.org/u/WycliffeAssociates/en_ulb/e744fe644f/index.html). 
 
 **Indenting poetry** can help readers recognize that a portion of text is poetic, and it can help readers understand the structure of the poem. If you indent poetry, make sure that you do it in a consistent way. 
 

checking/chk-details/01.md

@@ -1,10 +0,0 @@
-Much of the checking that the team does is to make sure that the words and sentences in the translation communicate the meaning of the source text accurately, clearly, and naturally. But there are other things that need to be checked, particularly in written translations.
-
-* [Consistency Checks](../chk-consistency/01.md)  - Check to see that the following are consistent: translation of important words, spelling, punctuation, and formatting.
-
-* [Complete Versification](../chk-verses/01.md) - Check to see that all the verses that should be included are included.
-
-The translators should do these checks during MAST steps 5-8, particularly during the [Key Terms Check (Step 7)](../chk-key-words/01.md) and the [Verse-by Verse Check (Step 8)](../chk-verse-by-verse/01.md) ].
-
-These checks should also be done during the [Church Leadership Review](../re-church-review/01.md) or while addressing concerns found in the review processes. (See: [Addressing Concerns](../re-post-review/01.md))
-

checking/chk-details/sub-title.md

@@ -1 +0,0 @@
-What other details need to be checked in a Bible translation?

checking/chk-details/title.md

@@ -1 +0,0 @@
-Detail Checks

checking/chk-key-words/01.md

@@ -1,11 +1,7 @@
 
-### How to do a Key Words Check (MAST Step 7)
 
-The key words check involves two processes. The first is to make a chart of key words that shows key words and how you will translate them in your language. The second is to check the key words in each portion of scripture that you translate. 
 
-After you make your list of key words, you may want to refer to the Translation Words resource to help you understand the meanings of the key words and other words in the Bible. This will help you with checking those words during the second part of this step. To learn more about this resource, see [Translation Words](../../translate/resources-words/01.md).
-
-### Making a Key Word Chart for Your Language
+### Making a key word chart for your language
 
 1. When you are ready for MAST step 7, work with a translation partner. Together read the source text of the passage you have translated and write a list of any words in the passage that  you think are key words. Key words are 
     * words that have some moral, spiritual, theological, or religious meaning
@@ -17,7 +13,7 @@ After you make your list of key words, you may want to refer to the Translation
     * Choose the common use word from the local Christian community. 
     * Choose a word with an added descriptor. 
     * Create a phrase or combine a few words into one.
-    * Borrow the word from the gateway language and adjust the spelling to fit your script and pronunciation.
+    * Borrow the word from the Gateway Language and adjust the spelling to fit your script and pronunciation.
 3. As a team, discuss all of your lists, and list in alphabetical order all of the source language words that you decide are key words. 
     * If possible, do this on a computer so you can easily insert new words in alphabetical order.
     * Put this list in the first column of a chart. 
@@ -25,12 +21,12 @@ After you make your list of key words, you may want to refer to the Translation
    * Some words have more than one meaning or have to be translated differently in different contexts. If you need more than one way to translate a key word, make a new line on the chart for each way of translating it. Repeat the source term in the source column, and put the new translation in the next column, under the first translation.  
    * You may also want to use another column to write where in the book the word first occurs.
    * Be careful not to include too many words. If the list is too detailed, checking becomes tedious. Additionally, checking every (or almost every word) can push the translated material away from a natural flow in the target language.
-4. Make sure that all of the translators have access to the chart so that you can all use the same words or phrases in your translation.
+4. Make sure that everyone on the translation team has access to the chart so that you can all use the same words or phrases in your translation.
 5. As you translate other chapters and books of the Bible you will find more key words. 
 5. Meet occasionally as a team to discuss changes to the chart: key words that need to be added, translations that need to be corrected, and key words that need more than one translation.
-6. Make sure that all of the translators have access to the newest chart.
+6. Make sure that everyone on the translation team has access to the newest chart.
 
-### Checking the Key Words in a Chapter
+### Checking the key words in a chapter
 
 1. Work with another translation partner to compare your translation to the source text and your key words chart. 
 2. Compare each verse of the source text to your key words chart.
@@ -41,5 +37,4 @@ After you make your list of key words, you may want to refer to the Translation
 3. Read each verse in your translation to see how the key words are translated.
 4. If a key word is translated in the text differently than it is in the chart, discuss this with your translation partner. You will need to either change the translation in the verse to match what is in the chart or add to the chart another way of translating the key word.
 4. If the translation of a key word does not seem to have the right meaning, or if it does not seem to make sense in the context, discuss it with your translation partner to come up with a solution.
-5. Meet with the rest of team to discuss words that need to be added to the chart and words that need either correction or additional translations.
-6. Check the important words throughout the chapter to see that their meanings are translated consistently. (See: [Consistency Checks](../chk-consistency/01.md).)
+5. Meet with the rest of team to discuss words that need to be added to the chart and words that need either correction or additional translations.

checking/chk-key-words/sub-title.md

@@ -1 +1,2 @@
-How can we check that we have translated the key words correctly?
+How can we check that we have translated the key words correctly?
+

checking/chk-peer-edit/01.md

@@ -1,8 +1,8 @@
 
-### How to do a Peer-Edit (MAST Step 6)
+### How to do a Peer-Edit
 
-* Once you have completed a draft and checked the draft yourself (using the source text for comparison and any other helpful tools to ensure accurate meaning), give the drafted portion to another translator on the team to review. This person should read through it, comparing it to the source text and making notes of any missing or added material. The peer editor should not make changes to the translation, only make comments and suggestions for change. The peer editor should use any available tools for checking meaning, flow, and accuracy. 
+* Once you have completed a draft and checked the draft yourself (using the source text for comparison and any other helpful tools to ensure accurate meaning), give the drafted portion to another member of the translation team to review. This person should read through it, comparing it to the source text and making notes of any missing or added material. The peer editor should not make changes to the translation, only make comments and suggestions for change. The peer editor should use any available tools for checking meaning, flow, and accuracy. 
 * Once the peer editor has completed a check of the passage, go over the suggested edits together. It is up to the translator to make changes.
-* Read the new translation out loud to the peer editor and fix anything that does not sound like it is the way that someone from your community would say it.
+* Read the new translation out loud to this person and fix anything that does not sound like it is the way that someone from your community would say it.
 * If you are in disagreement about a suggested change, the translator is responsible for the decision at this level, but these areas should be reviewed as a team so others can provide feedback on the best possible solution to any disagreements. 
 

checking/chk-peer-edit/sub-title.md

@@ -1 +1,2 @@
-How can others help me check my work?
+How can others help me check my work?
+

checking/chk-self-edit/01.md

@@ -1,9 +1,9 @@
 
-### How to do a Self-edit (MAST Step 5)
+### How to do a Self-edit
 
-* If you have followed the first four steps of the MAST process, then you made your first draft of a passage by consuming the source text, verbalizing what you consumed, breaking it down into workable chunks, and then writing it down while you were not looking at the source text (see: [First Draft](../../translate/first-draft/01.md)). After you have translated a passage in this way, do a self-edit by looking again at the source text and comparing it to your translation. Make sure that your draft includes all the parts of the message of the source text and does not leave out anything. If some part of the message is missing, put it in your translation at the point where it fits best in your language. Also make sure you haven't added any extra information.
+* If you have followed the first for steps of the MAST process, then you made your first draft of a passage by consuming the source text, verbalizing what you consumed, breaking it down into workable chunks, and then writing it down while you were not looking at the source text. After you have translated a passage in this way, do a self-edit by looking again at the source text and comparing it to your translation. Make sure that your draft includes all the parts of the message of the source text and does not leave out anything. If some part of the message is missing, put it in your translation at the point where it fits best in your language. Also make sure you haven't included any extra information.
 * If possible, compare your translation with other translations of the same Bible passage. If one of those makes you think of a better way to say something, then translate it that way. If one of them helps you to understand something better than you did before, then change your translation so that it communicates the meaning better.
-* If possible, use the Translation Notes and Translation Questions as well as other tools available in BTT Writer and Bibleineverylanguage.org to check your work. 
+* If possible use the Translation Notes and Translation Questions as well as other tools available in BTT Writer and Bibleineverylanguage.org to check your work. 
 * After these steps, read your translation out loud to yourself. Fix anything that does not sound like it is the way that someone from your community would say it. 
 
 When you have completed these steps, you are ready to have a peer edit your work. 

checking/chk-self-edit/sub-title.md

@@ -1 +1,2 @@
-How do I check my first draft?
+How do I check my first draft?
+

checking/chk-team-check/01.md

@@ -1,20 +1,19 @@
 
 
-The translators will check the translation during MAST steps 5-8. They should check their translation often (usually as soon as a whole chapter is drafted) so that they can correct mistakes as early as possible in the translation process. Sometimes a step will have to be repeated before moving on to the next step. 
+The translation team will check the translation during MAST steps 5-8. They should check their translation often (usually as soon as a whole chapter is drafted) so that they can correct mistakes as early as possible in the translation process. Sometimes a step will have to be repeated before moving on to the next step. 
 
 ### Steps for translation checking:
 
-1. Once a portion has been drafted, the translator of that section will perform a self-edit, using the source text and other available tools to check the draft. For more information about how to do this, see [Self-Edit (MAST Step 5)](../chk-self-edit/01.md).
-2. When the translator has completed the self-edit, another translator on the team will perform a peer-edit, carefully comparing the translated text to the source text and using any other available tools to confirm the accuracy and meaningfulness of the translation. He may also provide feedback and comments on spelling, naturalness and flow. The person conducting the peer-edit does not have authority to make changes; his role is to provide feedback and suggestions to the translator of the draft who then makes changes as he deems necessary. For more information on how to conduct a peer-edit, see [Peer-Edit (MAST Step 6)](../chk-peer-edit/01.md).
-3. Then the keywords of the passage are systematically checked against the list of key words in the available tool designed specifically to support this checking step. Alternatively, the translation team can create their own list of key words--abstract spiritual terms, historical and geographical terms and names--and carefully compare their drafted text to that list. This step is typically done by the translator of that passage and at least one other translator. For more information, see [Key Word Check (MAST Step 7)](../chk-key-words/01.md). 
-4. Each verse is carefully checked comparing the drafted text to the original source text, looking for any missing portions or added material. This check is typically done with the translator of the passage and at least one other translator--preferably a different translator than the one who assisted in the keyword check. For more information, see [Verse-by-verse Check (MAST Step 8)](../chk-verse-by-verse/01.md) .
+1. Once a portion has been drafted, the translator of that section will perform a self-edit, using the source text and other available tools to check the draft. For more information about how to do this see [Self-Edit](../self-edit/01.md).
+2. When the translator has completed the self-edit, another translator on the team will perform a peer-edit, carefully comparing the translated text to the source text and using any other available tools to confirm the accuracy and meaningfulness of the translation. He may also provide feedback and comments on spelling, naturalness and flow. The person conducting the peer-edit does not have authority to make changes; his role is to provide feedback and suggestions to the translator of the draft who then makes changes as he deems necessary. For more information on how to conduct a peer-edit, see [Peer-Edit](../peer-edit/01.md).
+3. Then the keywords of the passage are systematically checked against the list of key words in the available tool designed specifically to support this checking step. Alternatively, the translation team can create their own list of key words--abstract spiritual terms, historical and geographical terms and names--and carefully compare their drafted text to that list. This step is typically done by the translator and at least one other member of the translation team. For more information, see [Key Word Check](../key-word-check/01.md). 
+4. Each verse is carefully checked comparing the drafted text to the original source text, looking for any missing portions or added material. This check is typically done with the translator of the passage and at least one other member of the translation team--preferably a different member than the one who assisted in the keyword check. For more information, see [Verse-by-verse Check](../verse-by-verse/01.md)
 
 When the team has completed these steps, has incorporated the edits into the translated portion, and is collectively satisfied with the product, they then affirm the following:
-
-* that the translation is accurate
-* that the translation is in line with the statement of faith
-* that they followed the MAST process, including each checking step
-* that they used the available resources to check and refine their work.
+  * that the translation is accurate
+  * that the translation is in line with the statement of faith
+  * that they followed the MAST process, including each checking step,
+  * that they used the available resources to check and refine their work.
 
 Then they are welcome to upload the translation to the Wycliffe Associates content server where the work can be seen on [bibleineverylanguage.org](https://bibleineverylanguage.org). This enables the broadest reach of the content as an active project, with an open invitation to others in the language community (implied or direct) to help improve the translation.
 

checking/chk-team-check/title.md

@@ -1 +1 @@
-Checking a Translation
+Translation Team Check

checking/chk-verse-by-verse/01.md

@@ -1,6 +1,4 @@
-### How to do a Verse-by-Verse Check (MAST Step 8)
-
-The verse-by-verse check requires at least three people—the translator of the passage and two other translators—one who can translate the mother tongue to the source language and one who can compare what that translators says with the source text.
+This step requires at least three people—the translator of the passage and two partners from the translation team—one partner who can translate the mother tongue to the source language and one partner who can compare what the first partner says with the source text.
 
 The translator will read their translation one verse at a time, out loud, in the mother tongue. Without using any resources, one partner will listen to the mother tongue translation and verbally translate the verse into the source language. The second partner will listen to the first partner’s verbal back-translation and compare it to the source text. 
 
@@ -11,7 +9,4 @@ The wording will not be exactly the same between the source text and the back-tr
 
 If it appears that the meaning in the translation is not the same as the meaning in the source text, the partner who compares the two will tell the translator. The three people will then discuss the verse to see if there really is a difference in meaning.
 
-If there really is a difference in meaning, or if all of the events and important details are not present, the text should be edited. The team should consult the source text, Translation Notes, Translation Words, and other translations or other resources to help them make corrections and improve the translation. 
-
-The verse-by-verse check is also a good time to check that the translation has all of the verses and that it is consistent in wording, spelling, punctuation, and formatting. (See [Complete Versification Check](../chk-verses/01.md) and [Consistency Checks](../chk-consistency/01.md))
-
+If there really is a difference in meaning, or if all of the events and important details are not present, the text should be edited. The team should consult the source text, Translation Notes, Translation Words, and other translations or other resources to help them make corrections and improve the translation. 

checking/chk-verses/01.md

@@ -5,9 +5,9 @@ Versification checking takes place during step 8 of MAST, the verse-by-verse che
 
 ### Reasons for Missing Verses
 
-1. **Textual Variants** - There are some verses that many Bible scholars do not believe were original to the Bible, but were added later. Therefore the translators of some Bibles chose to not include those verses, or included them only as footnotes. (For more information about this, see [Textual Variants](../../jit/translate-textvariants/01.md).) Your translation team will need to decide whether you will include these verses or not.
+1. **Textual Variants** - There are some verses that many Bible scholars do not believe were original to the Bible, but were added later. Therefore the translators of some Bibles chose to not include those verses, or included them only as footnotes. (For more information about this, see [Textual Variants](../../translate/translate-textvariants/01.md).) Your translation team will need to decide whether you will include these verses or not.
 1. **Different Numbering** - Some Bibles use a different system of verse numbering than other Bibles. (For more information about this, see [Chapter and Verse Numbers](../../translate/translate-chapverse/01.md).) Your translation team will need to decide which system to use.
-1. **Verse Bridges** - In some translations of the Bible, the contents of two or more verses are rearranged so that the order of information is more logical or easier to understand. When that happens, the verse numbers are combined, such as 4-5 or 4-6. The UDB does this sometimes, and on rare occasions, also the ULB. Because not all of the verse numbers appear or they do not appear where you expect them to be, it might look like some verses are missing. But the contents of those verses are there. (For more information about this, see [Verse Bridges](../../jit/translate-versebridge/01.md).) Your translation team will need to decide whether to use verse bridges or not.
+1. **Verse Bridges** - In some translations of the Bible, the contents of two or more verses are rearranged so that the order of information is more logical or easier to understand. When that happens, the verse numbers are combined, such as 4-5 or 4-6. The UDB does this sometimes, and on rare occasions, also the ULB. Because not all of the verse numbers appear or they do not appear where you expect them to be, it might look like some verses are missing. But the contents of those verses are there. (For more information about this, see [Verse Bridges](../../translate/translate-versebridge/01.md).) Your translation team will need to decide whether to use verse bridges or not.
 
 ### Checking for Missing Verse Numbers or Content
 

checking/chk-verses/sub-title.md

@@ -1 +1,2 @@
-Are any verses missing in the translation?
+Are any verses missing in the translation?
+

checking/chk-verses/title.md

@@ -1,2 +1,2 @@
-Complete Versification Check
+Complete Versification
 

checking/config.yaml

@@ -1,52 +1,232 @@
-chk-consistency:
+acceptable:
+  recommended:
+    - alphabet
+    - complete
+  dependencies:
+    - clear
+    - natural
+    - church-leader-check
+accuracy-check:
+  recommended:
+    - level2
+    - language-community-check
+    - church-leader-check
+    - other-methods
+    - guidelines-accurate
+  dependencies:
+    - level1
+    - guidelines-accurate
+    - important-term-check
+accurate:
+  recommended:
+    - complete
+    - accuracy-check
+    - guidelines-accurate
+  dependencies:
+    - alphabet
+    - church-leader-check
+alphabet:
   recommended: []
-  dependencies: []
-chk-details:
+  dependencies:
+    - acceptable
+    - translate-alphabet
+authority-level1:
+  recommended:
+    - authority-level2
+    - level1
+  dependencies:
+    - authority-process
+authority-level2:
+  recommended:
+    - authority-level3
+  dependencies:
+    - authority-level1
+authority-level3:
+  recommended:
+    - level3
+    - level1
+  dependencies:
+    - authority-level2
+authority-process:
+  recommended:
+    - authority-level1
+    - level1
+  dependencies:
+    - goal-checking
+church-leader-check:
+  recommended:
+    - accuracy-check
+    - accurate
+    - good
+  dependencies:
+    - level2
+clear:
+  recommended:
+    - acceptable
+    - natural
+    - guidelines-clear
+    - language-community-check
+  dependencies:
+    - level2
+community-evaluation:
+  recommended:
+    - church-leader-check
+    - self-assessment
+  dependencies:
+    - language-community-check
+    - other-methods
+    - writing-decisions
+complete:
+  recommended:
+    - self-assessment
+    - good
+  dependencies:
+    - accurate
+formatting:
+  recommended:
+    - alphabet
+    - spelling
+    - punctuation
+  dependencies:
+    - vol2-things-to-check
+goal-checking:
+  recommended:
+    - intro-checking
+    - authority-process
+  dependencies:
+    - intro-levels
+good:
+  recommended:
+    - self-assessment
+    - level3
+  dependencies:
+    - complete
+headings:
+  recommended:
+    - community-evaluation
+  dependencies:
+    - acceptable
+    - punctuation
+    - verses
+important-term-check:
+  recommended:
+    - accuracy-check
+  dependencies:
+    - level1
+    - peer-check
+intro-check:
+  recommended:
+    - intro-checking
+  dependencies:
+    - translate-manual
+intro-checking:
+  recommended:
+    - intro-levels
+  dependencies:
+    - intro-check
+intro-levels:
+  recommended:
+    - intro-levels
+    - level1
+  dependencies:
+    - intro-checking
+language-community-check:
+  recommended:
+    - natural
+    - other-methods
+    - writing-decisions
+    - community-evaluation
+  dependencies:
+    - level2
+level1:
+  recommended:
+    - statement-of-faith
+    - translation-guidelines
+    - accuracy-check
+  dependencies:
+    - intro-levels
+level1-affirm:
+  recommended:
+    - level2
+  dependencies:
+    - statement-of-faith
+    - translation-guidelines
+    - level1
+    - accuracy-check
+level2:
+  recommended:
+    - language-community-check
+    - church-leader-check
+    - self-assessment
+    - good
+  dependencies:
+    - intro-levels
+    - accuracy-check
+level3:
+  recommended:
+    - level3-questions
+    - self-assessment
+  dependencies:
+    - intro-levels
+    - level2
+    - accuracy-check
+level3-approval:
   recommended: []
-  dependencies: []
-chk-key-words:
-  recommended: []
-  dependencies: []
-chk-peer-edit: 
-  recommended: []
-  dependencies: []
-check-self-edit:
-  recommended: []
-  dependencies: []
-check-team-check:
-  recommended: []
-  dependencies: []
-check-verse-by-verse:
-  recommended: []
-  dependencies: []
-check-verses:
-  recommended: []
-  dependencies: []
-qa-authority:
-  recommended: []
-  dependencies: []
-qa-need:
-  recommended: []
-  dependencies: []
-qa-rubric:
-  recommended: []
-  dependencies: []
-qa-standards:
-  recommended: []
-  dependencies: []
-re-church-review:
-  recommended: []
-  dependencies: []
-re-community-review:
-  recommended: []
-  dependencies: []
-re-post-review:
-  recommended: []
-  dependencies: []
-re-refine-revise:
-  recommended: []
-  dependencies: []
-re-review-methods:
-  recommended: []
-  dependencies: []
-
+  dependencies:
+    - level3
+    - level3-questions
+    - self-assessment
+level3-questions:
+  recommended:
+    - accuracy-check
+    - level3-approval
+    - self-assessment
+  dependencies:
+    - level3
+natural:
+  recommended:
+    - acceptable
+    - guidelines-natural
+    - language-community-check
+  dependencies:
+    - alphabet
+    - level2
+    - clear
+other-methods:
+  recommended:
+    - writing-decisions
+    - community-evaluation
+  dependencies:
+    - language-community-check
+peer-check:
+  recommended:
+    - important-term-check
+  dependencies:
+    - level1
+    - self-check
+self-assessment:
+  recommended:
+    - good
+    - accuracy-check
+    - language-community-check
+    - accurate
+    - clear
+    - natural
+    - level3-questions
+    - level3-approval
+  dependencies:
+    - complete
+    - church-leader-check
+    - level3
+self-check:
+  recommended:
+    - peer-check
+  dependencies:
+    - level1
+verses:
+  recommended:
+    - headings
+  dependencies:
+    - spelling
+    - punctuation
+    - alphabet

checking/qa-authority/01.md

@@ -1,5 +1,5 @@
 The church in each people group has the authority to decide what is and what is not a good quality translation of the Bible in their language. This is because they know their language and culture best and they are the ones who will be using this translation. Their authority is independent of their current ability, experience, or access to resources that facilitate the production of high quality Bible translations. Their authority does not change. However, their capacity for producing high quality translations can improve with time.
 
-While the church in a language group has the authority to assure the quality of their own Bible translation, they can increase their capacity to do this by using the tools and resources available on bibleineverylanguage.org. Translation quality is something that can always be improved; this idea is true even if a translation is of high quality. The collection of resources on bibleineverylanguage.org is constantly growing to meet the needs of the churches as their desire for more in-depth resources increases.
+While the church in a language group has the authority to assure the quality of their own Bible translation, they can increase their capacity to do this by using the tools and resources available on bibleineverylanguage.org. Translation quality is something that can always be improved; this idea is true even if a translation is of high quality. The collection of resources on bibleineverylangauge.org is constantly growing to meet the needs of the churches as their desire for more in-depth resources increases.
 
 

checking/qa-authority/sub-title.md

@@ -1 +0,0 @@
-Why do we say that the the church has the authority to assess the quality of their Bible translation?

checking/qa-need/01.md

@@ -1,11 +1,11 @@
 Quality assurance is a vital part of the translation process. A high quality translation uses many people to ensure that the translation is clearly communicating the message that it should communicate. There are several important factors that are addressed in quality assurance.
 
-Quality assurance is the process used to ensure **an accurate translation.** The translator may not have understood fully the passage in the source text, and therefore may not have communicated it clearly in his translation. Using tools such as commentaries and other translations can be helpful in confirming that the meaning is accurately understood and conveyed.
+Quality assurance is the process used to ensure an accurate translation. The translator may not have understood fully the passage in the source text, and therefore not have communicated it clearly in his translation. Using tools such as commentaries and other translations can be helpful in confirming that the meaning is accurately understood and conveyed.
 
-Quality assurance is the process used to ensure **a clear and natural translation**. The translator may have worded something in a way that is unclear, ungrammatical, or awkward. Having othersread a translation to check for flow will provide insight for correcting such problems.
+Quality assurance is the process used to ensure a clear and natural translation. The translator may have worded something in a way that is unclear, ungrammatical, or awkward. Having others on the translation team and in the language community read a translation to check for flow will provide insight for correcting such problems.
 
-Quality assurance helps to ensure that a text has **consistent punctuation, spelling, and formatting**. Often the translation is into a previously unwritten language, so people will have to work together to agree on standards for these things.
+Quality assurance helps to ensure that a text has consistent punctuation, spelling, and formatting. Often the translation is into a previously unwritten language, so people will have to work together to agree on standards for these things.
 
-As soon as a translator has created a draft, he will check it himself. Then other translators will do some other checks and recommend improvements. After this, it is recommended that the community and church leadership review the translation and provide feedback to the translators so that the translation can be refined or revised as needed. 
+As soon as a translator has created a draft, he will check it himself. Then others on the translation team will do some other checks and recommend improvements. After this, it is recommended that the community and church leadership review the translation and provide feedback to the translation team so that the translation can be refined or revised as needed. 
 
 Quality assurance may seem tedious, but it is well worth the time and effort. And if everyone in the translation team, church, and community understands that every person is a part of the quality assurance process from the start, this will encourage people to read the translation and contribute to its improvement.

checking/qa-rubric/01.md

@@ -1,7 +1,7 @@
 
 It is important for a language community to design its own rubric. When a language community establishes its own standards, it fosters ownership of a project. 
 
-During the first few days of a MAST workshop, the facilitator guides a translation team through the process of developing a rubric for assessing the quality of their translation. Below are the steps used to create a rubric to guide quality assurance throughout the project. 
+During the first few days of a MAST workshop, the facilitator guides a translation team through the process of developing rubric for assessing the quality of their translation. Below are the steps used to create a rubric to guide quality assurance throughout the project. 
 
 1. The translation team will choose a leader/representative of their language group to manage the rubric building process. If this leader/representative does not speak a language that the facilitator understands, the team will choose someone to translate the rubric for the facilitator.
 
@@ -10,7 +10,7 @@ During the first few days of a MAST workshop, the facilitator guides a translati
     * What is a good translation?   
     * What are at least ten qualities of a good translation? 
 
-3. The translation team will then work together to make one list that includes all the items from each individual’s list. The leader/representative will combine the qualities that are the same and develop one master list of around 10 qualities. 
+3. The translation team will then work together to make one list that includes all the items from each individual’s list. The leader/representative will combine the qualities that are the same and develop one master list of at least 10 qualities. 
 
 4.	If the facilitator or anyone else at the event is familiar with Bible translation rubrics, he may review the team's rubric. If he sees that something important is missing in their rubric, he may ask questions of the group to help them to recognize other qualities that would be beneficial for their translation to have. 
 
@@ -64,7 +64,7 @@ Below you will see an example of how a rubric was created by following steps 2-8
   * Can be used by pastors to build up the church
 
 
-#### Steps 3 - 5: Condense the characteristics and settle on around 10 characteristics. 
+#### Step 4: Condense the characteristics and settle on around 10 characteristics. 
 
   * Accurate
   * Style
@@ -90,9 +90,9 @@ Notice that in condensing the qualities, some of the items on the list are combi
 
 **Accurate**   
 
-1. Key words are translated accurately.
-2. Nothing is added or missing from the text.
-3. The text reflects the author's intended meaning. 
+1. Key words are translated accurately  
+2. Nothing is added or missing from the text  
+3. The text reflects the author's intended meaning  
 
 **Style**   
 1. The text uses the same style of writing as the source text. For example, poems in the source text are poems in the translated text. Accounts of historical events are translated as historical events.
@@ -101,17 +101,17 @@ Notice that in condensing the qualities, some of the items on the list are combi
 **Clear**  
 1. The text is understood by a wide range of audiences.  
 2. The text uses common language.  
-3. The text uses proper language structures (word order, tenses, sentence structure).
+3. The text uses proper language structures (word order, tenses, sentence structure)  
 4. The punctuation is correct.
 
 **Natural**  
-1. The text sounds like how we speak. It uses common language .
+1. The text sounds like how we speak. It uses common language  
 2. The text sounds beautiful.
-3. The text is efficient and effective in its communication.
+3. The text is efficient and effective in its communication
 
 **Faithful**  
 1. The text does not favor a particular denomination’s understanding of scripture. 
-2. The text does not favor one person’s or one group of people’s opinion over another.
+2. The text does not favor one person’s or group of people’s opinion over another.
 3. The text does not promote false doctrine.
 4. The text uses proper familial terms for God the Father and his Son.
 
@@ -125,6 +125,7 @@ Notice that in condensing the qualities, some of the items on the list are combi
 2. The names of people and places are not replaced with names of people and places in my community. 
 3. The translation describes historical events the way the source text describes them. 
 
+
 #### Step 8. Make each item in this list into a question with a yes or no response.
 
 **Accurate**  
@@ -148,9 +149,9 @@ Notice that in condensing the qualities, some of the items on the list are combi
 3. Is the text efficient and effective in its communication?
     
 **Faithful**  
-1. Does the text avoid favoring a particular denomination’s understanding of scripture?
-2. Does the text avoid favoring one person’s or one group of people’s opinion over another?
-3. Does the text avoid promoting false doctrine?
+1. Does the text avoid favoring a particular denomination’s understanding of scripture. 
+2. Does the text avoid favoring one person’s or group of people’s opinion over another.
+3. Does the text avoid promoting false doctrine.
 4. Does the text use proper familial terms for God the Father and his Son?
     
 **Authoritative**  

checking/qa-standards/01.md

@@ -1,9 +1,9 @@
 
-People want their Bible translation to be high quality. However, they may have different ideas about what makes a good translation. If people do not agree on what makes a good translation, they can waste a lot of time and effort criticizing a translation or trying to change it to what each person thinks it should be. Because of this, it is important for the translators, the community, and the church leadership to have a **rubric** by which they can evaluate the work. Creating a rubric helps to establish standards by which to judge translation quality and ensures that all members of a team are striving for the same kind of translation
+People want their Bible translation to be high quality. However, they may have different ideas about what makes a good translation. If people do not agree on what makes a good translation, they can waste a lot of time and effort criticizing a translation or trying to change it to what each person thinks it should be. Because of this, it is important for the translation team, the community, and the church leadership to have a rubric by which they can evaluate the work. Creating a rubric helps to establish standards by which to judge translation quality and ensures that all members of a team are striving for the same kind of translation
 
-A **rubric** is a list of characteristics that people use to evaluate how good something is. It is essentially a standard by which to judge something. In the case of Bible translation, the translators work together to produce a list of characteristics that a good Bible translation must have. They use that list as they produce their translation and as they assess its quality. If they find that any part of the translation lacks a particular characteristic, they adjust the translation so that it will have that characteristic. 
+A rubric is a list of characteristics that people use to evaluate how good something is. It is essentially a standard by which to judge something. In the case of Bible translation, the translation team works together to produce a list of characteristics that a good Bible translation must have. They use that list as they produce their translation and as they assess its quality. If they find that any part of the translation lacks a particular characteristic, they adjust the translation so that it will have that characteristic. 
 
-The community and the church leadership use this same rubric as they review the translation. If they find that any part of the translation lacks a particular characteristic, they tell the translators. The translators then determine whether or not the translation actually lacks that characteristic and they decide whether or not they need to make any changes to the translation. This process is called refinement.
+The community and the church leadership use this same rubric as they review the translation. If they find that any part of the translation lacks a particular characteristic, they tell the translation team. The translation team then determines whether or not the translation actually lacks that characteristic and decides whether or not they need to make any changes to the translation. This leads to refining the translation.
 
 If after using a translation from a completed project, people are not satisfied with the translation, they may decide to revise the translation, particularly if they want to use a different rubric. As a community of believers grows, it is not uncommon for the community to have more than one translation, each translation based on its own rubric. 
  

checking/re-church-review/01.md

@@ -1,59 +1,55 @@
 
-The intent of the church leadership review is to provide feedback to the translators to help them to ensure  that their translation is a quality translation that is accurate, clear, and natural. This helps the translators to know that they are meeting the standards they established for quality in their rubric. (See: [Designing a Rubric for Bible  Translation Quality](../qa-rubric/01.md).) Also, involving the church leadership in the refinement process increases the likelihood that the translation will be accepted and used.
+The intent of the church leadership review is to provide feedback to the translation team to help them to ensure  that their translation is a quality translation that is accurate, clear, and natural. This helps the translation team to know that they are meeting the standards they established for quality in their rubric. (See: [Designing a Rubric for Bible  Translation Quality](../qa-rubric/01.md).) Also, involving the church leadership in the refinement process increases the likelihood that the translation will be accepted and used.
 
-We recommend that participants in this review be mother tongue speakers of the language who did not participate in the community review of the passage. When possible, these should be leaders who have been trained or ordained through their church network, and they should use every aspect of their own knowledge and training to check the scriptures.
-
-The translators will share their translation, their rubric, the source text, the Statement of Faith, and their key terms list with the leaders of multiple church organizations in their language community. The church leaders will review the translation in order to affirm that the translation aligns with the intent of the original texts and with the Statement of Faith, which is an expression of what the Church around the world has taught since the beginning. The translators may also ask the church leaders to check the translation for [complete versification](../verses/01.md) and [consistency](../consistency/01.md). The translators will then refine their translation based on the feedback provided.
+We recommend that participants in this review be mother tongue speakers of the language who did not participate in the community review of the passage. When possible these should be leaders who have been trained or ordained through their church network, and they should use every aspect of their own knowledge and training to check the scriptures.
 
+The translation team will share their translation, their rubric, and the Statement of Faith with the leaders of multiple church organizations in their language community. The church leaders will review the translation in order to affirm that the translation aligns with the intent of the original texts and with the Statement of Faith, which is an expression of what the Church around the world has taught since the beginning. The translators will then refine their translation based on the feedback provided.
 
 ### Review Process
 
-Church leaders should work together to review the work, although they may review it on their own and come together to discuss any concerns or suggestions. The leaders may choose from several different options how best to review the work as a team. 
-
+Church leaders should work together to review the work, although they may review it on their own and come together to discuss any concerns or suggestions. The leaders may choose from several different options, how best to review the work as a team. 
   * They may use the Reviewer’s Guide, taking turns asking and answering questions.
-  * They may go verse by verse through each passage, comparing it to the ULB and using the resources to help them affirm meaning and quality: Translation Notes, Translation Questions, and Translation Words.
+  * They may go verse by verse through each passage, comparing it to the ULB and using the resources--Translation Notes, Translation Questions and Translation Words--to help them affirm meaning and quality.
   * They may compare the translated text to a commonly used gateway language translation (other than the ULB). 
-
 Any of these are good ways to review the text. 
 
-While reviewing the work, the leaders should make notes of any questions or concerns they have. Then they can plan a time to meet with the translators and work through those questions and concerns. The leaders and the translators should use the available translation resources for help with anything they don’t understand. After they resolve the issues and make any needed changes, the translators may need to ask the community to review the refined passage again to make sure that it still communicates well. If meeting with the community leads to more changes, they may need to meet with with the church leaders again to affirm that the translation is still accurate.
+While reviewing the work, the leaders should make notes of any questions or concerns they have. Then they can plan a time to meet with the translation team and work through those questions and concerns. The leaders and the translators should use the available translation resources for help with anything they don’t understand. After they resolve the issues and make any needed changes, the translation team may need to ask the community to review the refined passage again to make sure that it still communicates well. If meeting with the community leads to more changes, the team may need to meet with with the church leaders again to affirm that the translation is still accurate.
 
 ### Questions about the Translation
 
-Here are some questions to ask yourselves while reviewing a portion of scripture. If you answer “yes” to any of these questions, please explain in more detail so that the translators can know what the specific problem is, what part of the text needs correction, and how you would like them to correct it.
+Here are some questions to ask yourselves while reviewing a portion of scripture. If you answer “yes” to any of these questions, please explain in more detail so that the translation team can know what the specific problem is, what part of the text needs correction, and how you would like them to correct it.
 
 1. Are there any doctrinal errors in the translation?
 2. Did you find any areas of the translation that seem to contradict the national language translation or the important matters of faith found in your Christian community?
-3. Did the translators add extra information or ideas that were not part of the message in the source text? (Some implied information may have been expressed explicitly for the meaning to be clear. This is a desirable part of meaningful translation.)
-4. Did the translators leave out information or ideas that were part of the message in the source text?
+3. Did the translation team add extra information or ideas that were not part of the message in the source text? (Some implied information may have been expressed explicitly for the meaning to be clear. This is a desirable part of meaningful translation.)
+4. Did the translation team leave out information or ideas that were part of the message in the source text?
 
-Here are some general questions to ask concerning the translation. If the answer is no to any of these questions, please note the area in the text that is a concern and explain your concern to the translators. 
+Here are some general questions to ask concerning the translation. If the answer is no to any of these questions, please note the area in the text that is a concern and explain your concern to the translation team. 
 
-1. Does the translation conform to the [Statement of Faith](../../cobt/statement-of-faith/01.md) and the [Qualities of a Good Translation](../../translate/guidelines-intro/01.md)?
+1. Does the translation conform to the [Statement of Faith](../../intro/statement-of-faith/01.md) and the [Qualities of a Good Translation](../../translate/guidelines-intro/01.md)?
 2. Does the translation have the qualities described in the rubric that the translators used?
-3. Did the translators show a good understanding of the source language as well as the target language and culture?
+3. Did the translation team show a good understanding of the source language as well as the target language and culture?
 4. Does the language community affirm that the translation speaks in a clear and natural way in their language?
 5. Is the style that the translators followed appropriate for the community?
 6. Is the dialect that the translators used  the best one to communicate to the wider language community? For example, have the translators used expressions, phrase connectors, and spellings that will be recognized by most people in the language community?
-7. As you read the translation, think about cultural issues in the local community that might make some passages in the book difficult to translate. Have the translators translated these passages in a way that makes the message of the source text clear, and avoids any misunderstanding that people might have because of the cultural issue?
+7. As you read the translation, think about cultural issues in the local community that might make some passages in the book difficult to translate. Has the translation team translated these passages in a way that makes the message of the source text clear, and avoids any misunderstanding that people might have because of the cultural issue?
 8. In these difficult passages, do you feel that the translator has used language that communicates the same message that is in the source text?
 9. In your judgment, does the translation communicate the same message as the source text? 
 
-### Recommended Resources
+### Recommended Tools
 
-The following resources are recommended for helping the church leaders check the accuracy of the translation: Translation Questions and the Reviewer’s Guide. (To learn how to use these resources, see: [Using Translation Questions](../../translate/resources-questions/01.md).) These will help the translators find out what people understand when they hear or read the translation.
+The following tools are recommended for helping the church leaders check the accuracy of the translation: Translation Questions and the Reviewer’s Guide. (See: [Using Translation Questions](../../translate/resources-questions/01.md).) These will help the translators find out what people understand when they hear or read the translation.
 
-The following resources are recommended for helping translators address issues that are discovered through the church leadership review process: Translation Notes and Translation Words. (To learn how to use these resources, see: [Translation Notes](../../translate/resources-types/01.md) and [Translation Words](../../translate/resources-words/01.md).) These resources can help the reviewers and translators better understand what was written in the source text so they can determine whether or not the translators need to change anything in the translation.
+The following tools are recommended for helping translation teams address issues that are discovered through the church leadership review process: Translation Notes and Translation Words. (See: [Translation Notes](../../translate/resources-types/01.md) and [Translation Words](../../translate/resources-words/01.md).) These tools can help the reviewers and translators better understand what was written in the source text so they can determine whether or not the translators need to change anything in the translation.
 
-Translation Notes and Translation Words are embedded in BTT Writer. All of these resources are available on bibleineverylanguage.org.
+Translation Notes and Translation Words are embedded in BTT Writer. All of these tools are available on bibleineverylanguage.org.
 
 ### Summary
 
 Key elements of the church leadership review are:  
-
 1. Church leaders from multiple church networks or denominations read (or listen to) the translated scriptures and contribute to their improvement.
-2. The church leaders refer to the WA translation resources and to their own Bible reference books to ensure accuracy and completeness of the translation.
-3. The translators are responsible to respond to feedback and implement changes in the translation where needed. 
+2. The church leaders refer to the WA translation helps and to their own Bible reference books to ensure accuracy and completeness of the translation.
+3. The translation team is responsible to respond to feedback and implement changes in the translation where needed. 
 
 
 

checking/re-church-review/sub-title.md

@@ -1 +0,0 @@
-How can the church leaders ensure that their Bible translation is of good quality?

checking/re-community-review/01.md

@@ -1,15 +1,15 @@
-The intent of the community review is to provide feedback to the translators to help them to ensure their translation is a quality translation that is accurate, clear, and natural. This helps the translators to know that they are meeting the standards they established for quality in their rubric. (See: [Designing a Rubric for Bible Translation Quality](../qa-rubric/01.md).) Also, involving the community in the refinement process increases the likelihood that the translation will be accepted and used. 
+The intent of the community review is to provide feedback to the translation team to help them to ensure their translation is a quality translation that is accurate, clear, and natural. This helps the translation team to know that they are meeting the standards they established for quality in their rubric. (See: [Designing a Rubric for Bible  Translation Quality](../qa-rubric/01.md).) Also, involving the community in the refinement process increases the likelihood that the translation will be accepted and used. 
 
-The translators will share the translation and their rubric with members of their language community. These people should be representative of their community. For example, there should be men and women, old and young, formally educated and not formally educated.  The translators will use one or more testing methods so that they can receive feedback from the community about whether or not the translation has the characteristics that they established in their rubric. (See: [Community Review Methods](../re-review-methods/01.md).) The translators will then refine their translation based on the feedback provided. 
+The translation team will share the translation and their rubric with members of their language community. These people should be representative of their community. For example, there should be men and women, old and young, formally educated and not formally educated.  The translators will use one or more testing methods so that they can receive feedback from the community about whether or not the translation has the characteristics that they established in their rubric. (See: [Community Review Methods](../re-review-methods/01.md).) The translators will then refine their translation based on the feedback provided. 
 
-The following resources are recommended for use in reviewing the translation: **Translation Questions** and the **Reviewer's Guide**. These will help the translators find out what people understand when they hear or read the translation. To learn about the Translation Questions, see: [Using Translation Questions](../../translate/resources-questions/01.md).
+The following tools are recommended for use in reviewing the translation: Translation Questions and the Reviewer's Guide. (See: [Using Translation Questions](../../translate/resources-questions/01.md).) These will help the translators find out what people understand when they hear or read the translation.
 
-The following resources are recommended for helping the translators address issues that are discovered through the community review process: **Translation Notes** and **Translation Words.** These resources can help the reviewers and translators better understand what was written in the source text so they can determine whether or not the translators need to change anything in the translation. To learn about these resources, see [Translation Notes](../../translate/resources-types/01.md) and [Translation Words](../../translate/resources-words/01.md).
+The following tools are recommended for helping translation teams address issues that are discovered through the community review process: Translation Notes and Translation Words. (See: [Translation Notes](../../translate/resources-types/01.md) and [Translation Words](../../translate/resources-words/01.md).) These tools can help the reviewers and translators better understand what was written in the source text so they can determine whether or not the translators need to change anything in the translation.
 
-Translation Questions, Translation Notes, and Translation Words are embedded in BTT Writer. All of these resources are available on bibleineverylanguage.org.
+Translation Questions, Translation Notes, and Translation Words are embedded in BTT Writer. All of these tools are available on bibleineverylanguage.org.
 
 Key elements of the community review are:  
-1. Christians in the community read (or listen to) the translated scriptures and contribute to their improvement
-2. The above listed resources are used for ensuring accuracy and completeness
-3. The translators are responsible to respond to feedback and implement changes in the translation where needed. 
+1. Christians in the community  read (or listen to) the translated scriptures and contribute to their improvement
+2. The above listed tools are used for ensuring accuracy and completeness
+3. The translation team is responsible to respond to feedback and implement changes in the translation where needed. 
 

checking/re-post-review/01.md

@@ -1,12 +0,0 @@
-
-After the community or the church leadership reviews the translated portions, they and the translators should take the following steps.
-
-1. The reviewers either send their results to the translators or discuss the results with them.
-2. The team (or the team with the reviewers) does any needed research to determine whether or not a change really is needed.
-3. The team (or the team with the reviewers) determines what kind of change is needed.
-4. The team makes the change.
-5. If the reviewers did not  check the translation for [complete versification](../verses/01.md) and [consistency](../consistency/01.md), the team checks it and makes any needed changes.
-6. If the team or reviewers are concerned that the community might not understand the correct meaning, they ask some community members to review the passage with the change. Discussion with community reviewers and church reviewers continues as needed.
-7. The team publishes the refined version or the revision.
-8. If it is a revision, the church will need to decide whether or not to continue to publish the first version. (The church might want both versions to be available for people to use.)
-

checking/re-post-review/sub-title.md

@@ -1 +0,0 @@
-What happens after the church leaders review the translation?

checking/re-post-review/title.md

@@ -1 +0,0 @@
-Addressing Concerns

checking/re-refine-revise/01.md

@@ -1,15 +1,15 @@
 
-Refinement and revision are key aspects of making a quality translation that people will actually use and benefit from. Ideally the language community and their church leaders review a translation and  provide feedback for the translators to improve their translation. This is the first step in the refinement and revision processes.
+Refinement and revision are key aspects of making a quality translation that people will actually use and benefit from. Ideally the language community and their church leaders review a translation and  provide feedback for the translation team to improve their translation. This is the first step in the refinement and revision processes.
 
 ### Refinement
 
-Refinement is the process of improving a translation before a translation project is complete. Refinement provides an open invitation (implied or direct) to members of the language community to suggest improvements to the translation. The translators are encouraged to print or otherwise publish their translation so that people can immediately use it and provide feedback about it. They also encouraged to invite members of the community and church leaders to review the translation and suggest improvements.
+Refinement is the process of improving a translation before a translation project is complete. Refinement provides an open invitation (implied or direct) to members of the language community to suggest improvements to the translation. The translation team is encouraged to print or otherwise publish their translation so that people can immediately use it and provide feedback about it. The team is also encouraged to invite members of the community and church leaders to review the translation and suggest improvements.
 
-In the refinement process, the community and church leadership use the rubric created by the translators in order to assess the quality of the translation. If they find that any part of the translation lacks a particular characteristic, they discuss this with the translators. Then the translators can adjust the translation so that it will have that characteristic. 
+In the refinement process, the community and church leadership use the rubric created by the translation team in order to assess the quality of the translation. If they find that any part of the translation lacks a particular characteristic, they discuss this with the translation team. Then the translation team can adjust the translation so that it will have that characteristic. 
 
 ### Revision
 
-Revision is the process of improving a translation after a translation project has been completed. Revision provides an opportunity for the church to improve a translation whenever they determine there is sufficient need for a revision. There are a variety of needs for a translation to be revised; this is a natural part of ongoing church-owned Bible translation.
+Revision is the process of improving a translation after a translation project has been completed. Revision provides an opportunity for the church to improve a translation whenever they determine there is sufficient need for a revision. There are a variety of needs for a translation to be revised; this is a natural part of ongoing Church-owned Bible Translation.
 
-One marked difference between refinement and revision is that refinement always uses the rubric established by the translators, while a revision often establishes a new rubric for assessing the quality of their work. This new rubric can be adapted from the original rubric. However if the language community determines that the standards established in the original rubric were not met, they may do a revision that meets those standards.
+One marked difference between refinement and revision is that refinement always uses the rubric established by the translation team, while a revision often establishes a new rubric for assessing the quality of their work. This new rubric can be adapted from the original rubric.  However if  the language community determines that the standards established in the original  rubric were not met, they may do a revision that meets those standards.
 

checking/re-refine-revise/sub-title.md

@@ -1 +0,0 @@
-What are refinement and revision?

checking/re-review-methods/01.md

@@ -19,5 +19,5 @@ As well as asking questions, there are other checking methods that you may also
 
 * **Reviewer Input**: The translators ask others whom they respect to read the translation and to take notes and tell where it might be improved. These reviewers might give better word choices, more natural expressions, and even spelling adjustments.
 
-* **Discussion Groups**: The translators asks someone to read the translation to a group of people. The translators encourage the reader and the others to ask questions for clarification. The translators pay attention to the words people use, since alternate words and expressions come up when someone is trying to make sense of a difficult point; these alternate words and expressions might be better than the ones in the translation. The translators pay attention to the places where people do not understand the translation, and then work to make those places clearer.
+* **Discussion Groups**: The translators asks someone to read the translation to a group of people. The translators encourages the reader and the others to ask questions for clarification. The translator pays attention to the words people use, since alternate words and expressions come up when someone is trying to make sense of a difficult point; these alternate words and expressions might be better than the ones in the translation. The translator pays attention to the places where people do not understand the translation, and then works to make those places clearer.
 

checking/re-review-methods/sub-title.md

@@ -1 +1,2 @@
-What are some methods the community can use to review the translation?
+What are some methods the community can use to review the translation?
+

checking/toc.yaml

@@ -11,8 +11,9 @@ sections:
       - title: "The Church's Authority to Assess Quality"
         link: qa-authority
   - title: "Checking a Translation"
-    link: chk-team-check
     sections:
+      - title: "Translation Team Check"
+        link: chk-team-check
       - title: "Self-Edit"
         link: chk-self-edit
       - title: "Peer-Edit"
@@ -23,7 +24,7 @@ sections:
         link: chk-verse-by-verse
       - title: "Detail Checks"
         sections:
-          - title: "Complete Versification Check"
+          - title: "Complete Versification"
             link: chk-verses
           - title: "Consistency Checks"
             link: chk-consistency
@@ -37,6 +38,5 @@ sections:
         link: re-review-methods
       - title: "Church Leadership Review"
         link: re-church-review
-      - title: "Addressing Concerns"
-        link: re-post-review
+
 

cobt/cobt-defined/01.md

@@ -1,15 +0,0 @@
-Church-owned Bible translation (COBT) is a paradigm for Bible translation based on the following four beliefs about the local church and the Bible. We define "local church" as a community of believers who have the same heart language.
-
-1. **The local church has the authority to translate the Bible into its own language.** God’s Spirit resides in every believer. He provides wisdom and gives each believer authority to share, teach, or translate God’s Word according to the specific abilities and opportunities God has given him.
-1. **The local church has the responsibility to translate the Bible into its own language.** God gives local believers the responsibility to evangelize and disciple their community. Translating the scripture into the heart language of the people is an essential part of that responsibility.
-1. **The local church with bilingual local believers has the ability to translate the Bible into their language.** The local believers understand their language and culture better than an outsider, and typically, the local multilingual believers have skill in sharing meaning through oral translation. 
-1. **The local believers are accountable to one another and to God for translating the Scripture** accurately and clearly in their heart language and for making it accessible to the community.
-
-The six behaviors of church-owned Bible translation are: 
-
-1. Mother-tongue speakers, in fellowship with their local church, take responsibility for translating the Bible into the heart language of their local community
-1. The local church manages community accessibility to the translated scripture.
-1. Continuing refinement and revision will take place within the community, with mother-tongue Christian speakers.
-1. The church engages the local community in Scripture usage.
-1. The local church shares the concept and methodology of church-owned Bible translation with other language communities.
-1. The local church takes ownership of generational revisions and updates to the Scripture.

cobt/cobt-defined/sub-title.md

@@ -1 +0,0 @@
-What is church-owned Bible translation?

cobt/cobt-defined/title.md

@@ -1 +0,0 @@
-Church-Owned Bible Translation Defined

cobt/config.yaml

@@ -1,33 +0,0 @@
-cobt-defined:
-  recommended:
-  dependencies: []
-finding-answers:
-  recommended:
-  dependencies: []
-gl-strategy:
-  recommended:
-  dependencies: []
-guidelines-church-approved:
-  recommended:
-  dependencies: []
-guidelines-collaborative:
-  recommended:
-  dependencies: []
-guidelines-ongoing:
-  recommended:
-  dependencies: []
-mast-intro:
-  recommended:
-  dependencies: []
-open-license:
-  recommended:
-  dependencies: []
-statement-of-faith:
-  recommended:
-  dependencies: []
-translate-why:
-  recommended:
-  dependencies: []
-wa:
-  recommended: []
-  dependencies: []

cobt/gl-strategy/01.md

@@ -1,3 +0,0 @@
-A gateway language (GL) is a language into which all our translation resources are being made available to help language communities translate scripture themselves. 
-
-Many people would not be able to use WA resources if they were only in English.  So, WA has chosen certain national languages, languages of education, and trade languages to be gateway languages. Teams translate these resources into gateway languages so that bilingual translators can then translate the Bible from a gateway language into their own language.  

cobt/gl-strategy/sub-title.md

@@ -1 +0,0 @@
-How can every language be reached?

cobt/gl-strategy/title.md

@@ -1,2 +0,0 @@
-Gateway Languages
-

cobt/guidelines-church-approved/01.md

@@ -1,7 +0,0 @@
-The goal of the translation of biblical content is to produce a high-quality translation that is used and loved by the church. High-quality translations are accurate, clear, and natural (see [Qualities of a Good Translation](../../translate/guidelines-intro/01.md)). But for a translation to be used and loved by the church, it must be church-affirmed. This means that the local church recognizes it to be the Word of God and desires to use it.
-
-In order to produce a translation that the church affirms, as many church networks as possible should be contacted and encouraged to become a part of the translation project and to send some of their people to be a part of the translation team. They should be consulted and asked for their input into the translation project, its goals, and its process. They should be involved in distributing the translation, reviewing it, and providing feedback so it can be refined. The more involved they are in these processes, the more likely they will affirm the translation.
-
-If the church cannot actively lead the translation and coordinate all the efforts, it is necessary that whoever is leading the translation be affirmed by the church networks, preferably before they even start.
-
-After the translators have checked the quality of their translation, they are encouraged to share it with the community and the church leaders so that they can review the translation and give feedback. Encouraging the community and as many church networks as possible to participate and give input will encourage them to own and affirm the translation. And if they do this, there should be nothing hindering the translation from being used to strengthen and encourage the church.

cobt/guidelines-church-approved/sub-title.md

@@ -1 +0,0 @@
-What is church affirmation?

cobt/guidelines-collaborative/sub-title.md

@@ -1 +0,0 @@
-What are collaborative translations?

cobt/guidelines-ongoing/01.md

@@ -1,15 +0,0 @@
-
-Bible translations should be **ongoing**. That is, even after a Bible translation is published, the church and the translators should understand that the translation will need to be revised sometime in the future. There are various reasons a translation might need to be revised:
-
-  * There might be random errors.
-  * There might be some words or phrases that are unclear or hard to understand.
-  * Languages change over time. At some point, the community might not use certain words or ways of speaking that were used in the translation.
-  * The church may decide that they want another translation with a different rubric, or standard.
-
-The language community may choose to continue to have a translation committee that is responsible for making any revisions. This committee could be made up of Bible translators, Bible scholars, church leaders, and others. 
-
-The church should encourage people to read the translation at home and in groups, and to tell a church leader or the translation committee if there appears to be a problem in the translation. The committee is then responsible for determining whether or not a change is needed and how to make it. The committee will need to decide which issues to deal with immediately and which ones to deal with at a later time.
-
-The committee will continue to make corrections to the translation so that it will communicate the same meaning as the source text, and so that it will be more accurate, more clear, and more natural than it was before. 
-
-

cobt/guidelines-ongoing/sub-title.md

@@ -1 +0,0 @@
-What is ongoing translation?

cobt/mast-intro/title.md

@@ -1 +0,0 @@
-MAST Bible Translation Process

cobt/open-license/01.md

@@ -1,48 +0,0 @@
-
-The **Creative Commons Attribution-ShareAlike 4.0 International License** (see https://creativecommons.org/licenses/by-sa/4.0/) provides all the needed rights for translation and distribution of biblical content and ensures that the content remains open. Except where otherwise noted, all our content is licensed CC BY-SA 4.0.
-
-The official license applied to the content on bibleineverylanguage.org is found at https://creativecommons.org/licenses/by-sa/4.0/legalcode. Below is a summary of that license.
-
-### Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
-
-This is a human-readable summary of (and not a substitute for) the license (see https://creativecommons.org/licenses/by-sa/4.0/).
-
-#### You are free to:
-
-* **Share** — copy and redistribute the material in any medium or format
-* **Adapt** — remix, transform, and build upon the material for any purpose, even commercially.
-
-The licensor cannot revoke these freedoms as long as you follow the license terms.
-
-#### Under the following conditions:
-
-* **Attribution** — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
-* **ShareAlike** — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
-
-**No additional restrictions** — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.
-
-#### Notices:
-
-You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation.
-
-No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.
-
-Suggested attribution statement for derivative works: "Original work created by the Door43 World Missions Community, available at https://door43.org/, and released under a Creative Commons Attribution-ShareAlike 4.0 International License (https://creativecommons.org/licenses/by-sa/4.0/ ). This work has been changed from the original, and the original authors have not endorsed this work."
-
-### Attribution
-
-When resources are made available at bibleineverylanguage.org , the original work must be attributed as specified by the open license under which it is available.
-
-Contributors to projects on bibleineverylanguage.org agree that **the attribution that occurs automatically in the revision history of every page is sufficient attribution for their work.** That is, every contributor on bibleineverylanguage.org  may be listed as "the bibleineverylanguage.org World Missions Community" or something to that effect.
-
-### Source Texts
-
-Source texts may only be used if they have one of the following licenses:
-
-* **CC0 Public Domain Dedication (CC0** (https://creativecommons.org/publicdomain/zero/1.0/)
-* **CC Attribution (CC BY)** (https://creativecommons.org/licenses/by/4.0/)
-* **CC Attribution-ShareAlike (CC BY-SA)** (https://creativecommons.org/licenses/by-sa/4.0/)
-* **Free Translate License** (https://ufw.io/freetranslate/)
-
-See [Copyrights, Licensing, and Source Texts](../../translate/translate-source-licensing/01.md) for more information.
-

cobt/open-license/sub-title.md

@@ -1 +0,0 @@
-What freedoms do users have with Bible In Every Language content?

cobt/open-license/title.md

@@ -1,2 +0,0 @@
-Open Copyright License
-

cobt/statement-of-faith/sub-title.md

@@ -1 +0,0 @@
-What do we believe, and what are divine familial terms?

cobt/toc.yaml

@@ -1,24 +0,0 @@
-title: "Church-Owned Bible Translation"
-sections: 
-  - title: "Introduction to Church-Owned Bible Translation"
-    link: wa
-  - title: "Church-Owned Bible Translation Defined"
-    link: cobt-defined
-  - title: "Why We Translate the Bible"
-    link: translate-why
-  - title: "Statement of Faith and Divine Familial Terms"
-    link: statement-of-faith
-  - title: "Church Affirmation"
-    link: guidelines-church-approved
-  - title: "Collaboration"
-    link: guidelines-collaborative
-  - title: "Ongoing Translation"
-    link: guidelines-ongoing
-  - title: "Open Copyright License"
-    link: open-license
-  - title: "Gateway Languages"
-    link: gl-strategy
-  - title: "WA Bible Translation Tools and Resources"
-    link: finding-answers
-  - title: "MAST Bible Translation Process"
-    link: mast-intro

cobt/translate-why/sub-title.md

@@ -1 +0,0 @@
-Why should we translate the Bible?

cobt/wa/01.md

@@ -1,12 +0,0 @@
-This section introduces church-owned Bible translation. It has the following topics:
-
-* [Church-Owned Bible Translation Defined](../../cobt/cobt-defined/01.md)
-* [Why We Translate the Bible](../../cobt/translate-why/01.md)
-* [Statement of Faith and Divine Familial Terms](../../cobt/statement-of-faith/01.md)
-* [Church Affirmation](../../cobt/guidelines-church-approved/01.md)
-* [Collaboration](../../cobt/guidelines-collaborative/01.md)
-* [Ongoing Translation](../../cobt/guidelines-ongoing/01.md)
-* [Open License](../../cobt/open-license/01.md)
-* [Gateway Languages Strategy](../../cobt/gl-strategy/01.md)
-* [WA Bible Translation Tools and Resources](../../cobt/finding-answers/01.md)
-* [MAST Bible Translation Process](../../cobt/mast-intro/01.md)

cobt/wa/sub-title.md

@@ -1 +0,0 @@
-What are the topics that show how Wycliffe Associates promotes church-owned Bible translation?

cobt/wa/title.md

@@ -1 +0,0 @@
-Introduction to Church-Owned Bible Translation

intro/config.yaml

@@ -1,6 +1,54 @@
+finding-answers:
+  recommended:
+    - process-manual
+  dependencies:
+    - ta-intro
+gl-strategy:
+  recommended:
+    - finding-answers
+  dependencies:
+    - uw-intro
+    - open-license
+    - translate/translate-terms
+open-license:
+  recommended:
+    - gl-strategy
+    - translate-source-licensing
+  dependencies:
+    - uw-intro
+    - statement-of-faith
+    - translation-guidelines
+    - translate/translate-terms
+statement-of-faith:
+  recommended:
+    - translation-guidelines
+    - open-license
+    - translate-source-licensing
+  dependencies:
+    - uw-intro
 ta-intro:
   recommended: []
   dependencies: []
-translate-terms:
+translate-why:
   recommended:
-  dependencies: []
+    - guidelines-intro
+    - translate-process
+  dependencies:
+    - uw-intro
+    - translate-manual
+    - translate-whatis
+translation-guidelines:
+  recommended:
+    - open-license
+    - translate-manual
+    - intro-checking
+  dependencies:
+    - uw-intro
+    - statement-of-faith
+    - translate/translate-terms
+uw-intro:
+  recommended:
+    - statement-of-faith
+    - gl-strategy
+  dependencies:
+    - ta-intro

intro/finding-answers/01.md

@@ -1,9 +1,9 @@
-Wycliffe Associates has a website with pages that provide information about Bible translation processes, along with Bible translation resources, tools, and links to support. The website is called [Bible in Every Language](https://bibleineverylanguage.org) and can be found at Bibleineverylanguage.org. It has the following pages.
+Wycliffe Associates has a website that provides information about Bible translation processes, along with Bible translation resources, tools, and links to support. The website is called [Bible in Every Language](https://bibleineverylanguage.org) and can be found at Bibleineverylanguage.org.
 
 * [Processes](https://bibleineverylanguage.org/processes) tells about MAST (a methodology for translation), DOT (a methodology for translation into sign languages), SUN (a writing system for deaf people who neither read nor sign), and REV (a program for revising translations).  
-* [Resources](https://bibleineverylanguage.org/resources) tells about the Unlocked Literal Bible, Open Bible Stories, and resources that give information to help people translate and check their translations. 
-* [Tools](https://bibleineverylanguage.org/tools) presents computer programs for Bible translation. 
+* [Resources](https://bibleineverylanguage.org/resources) tells about the Unlocked Literal Bible, Open Bible Stories, and resources that give information to help people translate and check their translations.  
+* [Tools](https://bibleineverylanguage.org/tools) presents computer programs for Bible translation.  
 * [Translations](https://bibleineverylanguage.org/translations) has links to the translation resources in English and in other languages as they are translated and uploaded to the website.  
-* [Support](https://bibleineverylanguage.org/support) provides points of contact for support with technical issues and translation. 
+* [Support](https://bibleineverylanguage.org/support) provides points of contact for support with technical issues and translation.
 
 Connect to tech support with an email to <helpdesk@techadvancement.com> for help with your questions.

intro/finding-answers/sub-title.md

@@ -1 +1,2 @@
-What Bible tranlation tools and resources does Wycliffe Associates provide?
+What Bible tranlation tools and resources does Wycliffe Associates provide?
+

intro/gl-strategy/01.md

@@ -0,0 +1,9 @@
+
+The Gateway Languages Strategy endeavors to equip all people groups with access to the Bible, biblical content, translation training, and translation resources in a language that bilingual people in those groups understand well. Those bilingual people can then translate the Bible and biblical content into a language they understand fully, that is, their own language. 
+
+A **Gateway Language** (GL) is a language of wider communication into which all our translation tools and resources will be made available. Bilingual speakers use Gateway Language resources to help them translate the Bible into their own heart language.
+
+Many Gateway Languages are national languages, languages of education, or trade languages within a country. Just as countries vary in their number of national or recognized languages, many will have more than one Gateway Language. India, for example, has several Gateway Languages, while Mozambique has only one. In addition, some Gateway Languages are used in multiple countries or even on multiple continents. For example, Portuguese is a Gateway Language from which bilingual speakers in Brazil and in several countries in Africa can translate the Bible into their heart language.
+
+The Gateway Languages Strategy prioritizes developing content and making it available in these diverse languages of the world. This provides tools to empower minority language communities to translate scripture themselves. 
+

intro/gl-strategy/sub-title.md

@@ -0,0 +1,2 @@
+How can every language be reached?
+

intro/gl-strategy/title.md

@@ -0,0 +1,2 @@
+Gateway Languages Strategy
+

intro/guidelines-church-approved/01.md

@@ -0,0 +1,7 @@
+The goal of the translation of biblical content is to produce a high-quality translation that is used and loved by the church. High-quality translations are accurate, clear, and natural (see [Qualities of a Good Translation](../../translate/guidelines-intro/01.md)). But for a translation to be used and loved by the church, it must be church-affirmed. This means that the local church recognizes it to be the Word of God and desires to use it.
+
+In order to produce a translation that the church affirms, as many church networks as possible should be contacted and encouraged to become a part of the translation  project and to send some of their people to be a part of the translation team. They should be consulted and asked for their input into the translation project, its goals, and its process. They should be involved in distributing the translation, reviewing it, and providing feedback so it can be refined. The more involved they are in these processes, the more likely they will affirm the translation.
+
+If the church cannot actively lead the translation and coordinate all the efforts, it is necessary that whoever is leading the translation be affirmed by the church networks, preferably before they even start.
+
+After the translation team has checked the quality of their translation, they are encouraged to share it with the community and the church leaders so that they can review the translation and give feedback. Encouraging the community and as many church networks as possible to participate and give input will encourage them to own and affirm the translation. And if they do this, there should be nothing hindering the translation from being used to strengthen and encourage the church.

intro/guidelines-church-approved/sub-title.md

@@ -0,0 +1,2 @@
+What is church affirmation?
+

intro/guidelines-collaborative/01.md

@@ -1,7 +1,7 @@
 
 Bible translations that are **collaborative** are those that have been translated by a group of speakers of the same language. To ensure that your translation is of the highest quality, work together with other believers who speak your language to translate, check, and distribute the translated content.
 
-Collaboration occurs in many ways during the translation process. First, as the team gathers from different churches and villages, they commit to collaborate on the project as a whole. Second, as translators on the team translate portions of scripture, they work with other translators on the team to check their translation and improve it. Third, the translators collaborate with community members and church leaders who read or listen to the scripture and provide feedback about how the translation can be improved. 
+Collaboration occurs in many ways during the translation process. First, as the team gathers from different churches and villages, they commit to collaborate on the project as a whole. Second, as individuals on the team translate portions of scripture, they work with other team members to check their translation and improve it. Third, the team collaborates with community members and church leaders who read or listen to the scripture and provide feedback about how the translation can be improved. 
  
 Whenever possible the translation team should endeavor to include other Christians from their language group in the translation process, so as to continue and expand on the collaborative nature of the project. 
 

intro/guidelines-collaborative/sub-title.md

@@ -0,0 +1,2 @@
+What are collaborative translations?
+