Update 'intro/translate-why/01.md'

Minor edit for clarity and to test renderer.

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

@@ -0,0 +1,25 @@
+# About the Translation Manual
+
+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 createing 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.
+
+### Contributors 
+  - Susan Quigley, MA in Linguistics
+  - Henry Whitney, BA in Education
+  - Tabitha Price, BA in Education
+  - James N. Pohlig, M.Div., MA in Linguistics, D. Litt. in Biblical Languages
+  - Bev Staley
+  - Carol Brinneman
+  - Jody Garcia
+  - Kara Anderson
+  - Kim Puterbaugh
+  - Lizz Carlton
+  - Door43 World Missions Community
+
+
+
+
+We welcome questions, comments, and suggestions

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

@@ -1,32 +0,0 @@
-# About the Translation Manual
-
-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 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
-* How to use the Translation Manual
-* Contributors to the Translation Manual (Fuller list)
-
-## Viewing
-
-To read or print the complete Translation Manual, see "Wycliffe Associates Translation Manual" on the "Translations" page of [Bible in Every Language](https://bibleineverylanguage.org/translations/) (https://bibleineverylanguage.org/translations/).
-
-The Translation Manual is also integrated into BTT Writer and VMAST so that translators can have  immediate access to it while translating. BTT Writer and VMAST are available on the Tools page of [Bible in Every Language](https://bibleineverylanguage.org/tools/) (https://bibleineverylanguage.org/tools/).
-
-## Questions, comments, and suggestions
-We welcome questions, comments, and suggestions. You may send them to helpdesk@techadvancement.com or training_wa@wycliffeassociates.org.
-
-## Contributors to the Translation Manual
-  - Christine Jarka, MSEd in Instructional Design
-  - Henry Whitney, BA in Education
-  - James N. Pohlig, M.Div., MA in Linguistics, D. Litt. in Biblical Languages
-  - Perry Oakes, PhD in Old Testament, MA in Linguistics
-  - Susan Quigley, MA in Linguistics
-  - Tabitha Price, BA in Education
-  - Door43 World Missions Community
-  - Wycliffe Associates Staff
-  

00-tM_front&back/tM-20-Appendix.md

@@ -1,17 +0,0 @@
-# Appendix to the Translation Manual
-
-## Decisions concerning the Translation Manual
-
-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.
-
-## How to use the Translation Manual
-
-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.
-
-A systematic, in-advance approach might involve reading sequentially through the sections of the manual: the Introduction, Translation Theory and Practice, Translation Topics, and Checking. A just-in-time learning approach might involve reading particular Translation Topics when directed to them by particular Translation Notes.
-
-The Translation Topics section of the Translation Manual deals with grammar, figures of speech,  writing styles, translating unknown ideas, and issues specific to Bible translation. Some of the pages describe a topic, tell why it is a translation issue, explain some examples from the Bible, and present translation strategies with examples of how the strategies might be applied. When translating a particular passage, translators will need to decide if any of the strategies would be appropriate for them to use. The examples of how strategies might be applied are meant to help translators learn how to apply the strategies. Translators are not expected to use any particular strategy.
-
-
-## Contributors to the Translation Manual
-{{manifest}}

00-tM_front&back/tM-Appendix.md

@@ -0,0 +1,24 @@
+# Appendix to the Translation Manual
+
+## Decisions concerning the Translation Manual
+
+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.  **(Not sure whether or not to include this. It seems we could say the same thing for all the helps.)**
+
+## How to use the Translation Manual
+
+The translation 
+
+## Contributors to the Translation Manual
+  - Christine Jarka, MSEd in Instructional Design
+  - 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
+ 
+  - Bev Staley
+  - Carol Brinneman
+  - Jody Garcia
+  - Kara Anderson
+  - Kim Puterbaugh
+  - Lizz Carlton
+

00-tT_front&back/tT-1-Intro.md

@@ -0,0 +1,9 @@
+# Introduction to the Translation Topics
+
+"Translation Topics" is a part of the the Wycliffe Associates Translation Manual. It deals with translation issues that arise because of grammar, discourse, figures of speech, and ideas that maybe unknown to speakers of the target language. It also deals with issues that are particularly relevant to Bible translation.
+
+The complete Translation Manual is available at BibleInEveryLanguage.org. The topics that are included in this set of Translation Resources are ones that are addressed in either the Translation Notes or the Translation Words for this book of the Bible. 
+
+Many of the topics include examples from the Bible, strategies for dealing with the issues, and examples of how those strategies might be applied. 
+
+To read or print the Wycliffe Associates Translation Manual, see the Translation Manual project on Bible in Every Language (https://door43.org/u/WycliffeAssociates/en_ta/).

00-tT_front&back/tT-11-Intro.md

@@ -1,29 +0,0 @@
-# Introduction to the Translation Topics
-
-"Translation Topics" is a part of the the Wycliffe Associates Translation Manual. It deals with translation issues that arise because of grammar, discourse, figures of speech, and ideas that maybe unknown to speakers of the target language. It also deals with issues that are particularly relevant to Bible translation. Many of the topics include examples from the Bible, strategies for dealing with the issues, and examples of how those strategies might be applied. 
-
-The topics that are included in this set of Translation Resources are ones that are addressed in either the Translation Notes or the Translation Words for this book of the Bible. 
-
-**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
-* How to use the Translation Manual
-* Contributors to the Translation Manual (Fuller list)
-
-## Viewing
-
-To read or print the complete Translation Manual, see "Wycliffe Associates Translation Manual" on the "Translations" page of [Bible in Every Language](https://bibleineverylanguage.org/translations/) (https://bibleineverylanguage.org/translations/).
-
-The Translation Manual is also integrated into BTT Writer and VMAST so that translators can have  immediate access to it while translating. BTT Writer and VMAST are available on the Tools page of [Bible in Every Language](https://bibleineverylanguage.org/tools/)  (https://bibleineverylanguage.org/tools/).
-
-## Questions, comments, and suggestions
-We welcome questions, comments, and suggestions. You may send them to helpdesk@techadvancement.com or training_wa@wycliffeassociates.org.
-
-## Contributors to the Translation Topics 
-  - Christine Jarka, MSEd in Instructional Design
-  - Henry Whitney, BA in Education
-  - James N. Pohlig, M.Div., MA in Linguistics, D. Litt. in Biblical Languages
-  - Perry Oakes, PhD in Old Testament, MA in Linguistics
-  - Susan Quigley, MA in Linguistics
-  - Tabitha Price, BA in Education
-  - Door43 World Missions Community
-  - Wycliffe Associates Staff

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 +0,0 @@
-How do we design a rubric for the quality of our translation?

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

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

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

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

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

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

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/level1/title.md

@@ -1,2 +0,0 @@
-Translation Team Check
-

archive/checking/level2/title.md

@@ -1,2 +0,0 @@
-Community Review
-

archive/checking/level3/title.md

@@ -1,2 +0,0 @@
-Church Leadership Review
-

archive/checking/vol2-things-to-check/01.md

@@ -8,8 +8,8 @@
     1. Check for any meaning that appears to be different than the meaning of the source text.
 
 1. Check to make sure that the main point or the theme of the passage is clear. Ask the translation team to summarize what the passage is saying or teaching. If they choose a minor point as the primary one, they might need to adjust the way that they translated the passage.
-1. Check that the different parts of the passage are connected in the right way–that the reasons, additions, results, conclusions, etc. in the Bible passage are marked with the proper connectors in the target language.
-1. Check for the consistency of the translationWords, as explained in the last section of "Steps in Checking a Translation." Ask how each term is used in the culture—who uses the terms, and on what occasions. Also ask what other terms are similar and what the differences are between the similar terms. This helps the translator to see if some terms might have unwanted meanings, and to see which term might be better, or if they might need to use different terms in different contexts.
+1. Check that the different parts of the passage are connected in the right way – that the reasons, additions, results, conclusions, etc. in the Bible passage are marked with the proper connectors in the target language.
+1. Check for the consistency of the translationWords, as explained in the last section of "Steps in Checking a Translation." Ask how each term is used in the culture – who uses the terms, and on what occasions. Also ask what other terms are similar and what the differences are between the similar terms. This helps the translator to see if some terms might have unwanted meanings, and to see which term might be better, or if they might need to use different terms in different contexts.
 1. Check figures of speech. Where there is a figure of speech in the Bible text, see how it has been translated and make sure it communicates the same meaning. Where there is a figure of speech in the translation, check to make sure it communicates the same meaning as in the Bible text.
 1. Check to see how abstract ideas were translated, such as love, forgiveness, joy, etc. Many of these are also Key Words.
 1. Check the translation of things or practices that might be unknown in the target culture. Showing the translation team pictures of these things and explaining to them what they are is very helpful.

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/intro/translation-guidelines/01.md

@@ -1,12 +0,0 @@
-
-The following statement on the principles and procedures used in translation is subscribed to by all contributors to the Bible In Every Language website (see https://bibleineverylanguage.org). 
-
-**All translation activities are carried out according to these common guidelines:**
-
-1. **Accurate** (see [Accurate Translations](../../translate/guidelines-accurate/01.md))
-
-1. **Clear** — (see [Clear Translations](../../translate/guidelines-clear/01.md)) 
-
-1. **Natural** — (see [Natural Translations](../../translate/guidelines-natural/01.md)) 
-
-

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/figs-inclusive/01.md

@@ -18,7 +18,7 @@ The Bible was first written in the Hebrew, Aramaic, and Greek languages. Like En
 
 >... the shepherds said one to each other, "Let <u>us</u> now go to Bethlehem, and see this thing that has happened, which the Lord has made known to <u>us</u>." (Luke 2:15 ULB)
 
-The shepherds were speaking to one another. When they said "us," they were including the people they were speaking to—one another.
+The shepherds were speaking to one another. When they said "us," they were including the people they were speaking to - one another.
 
 >Now it happened on one of those days that Jesus and his disciples entered into a boat, and he said to them, "Let <u>us</u> go over to the other side of the lake." Then they set sail. (Luke 8:22 ULB)
 

archive/translate/figs-infostructure/01.md

@@ -31,11 +31,11 @@ In English, this means that the people ate everything. But the next verse says t
 
 >Now the day was about to come to an end, and the twelve came to him and said, "Send the crowd away that they may go into the surrounding villages and countryside to find lodging and food, because we are here in an isolated place." (Luke 9:12 ULB)
 
-In this verse, what the disciples say to Jesus puts the important information first—that he should send the crowd away. But in languages that put the important information last, people would understand that the reason that they give—being in an isolated place—is the most important part of their message to Jesus. They might then think that the disciples are afraid of the spirits in that place, and that sending the people to buy food is a way to protect them from the spirits. That is the wrong message.
+In this verse, what the disciples say to Jesus puts the important information first - that he should send the crowd away. But in languages that put the important information last, people would understand that the reason that they give - being in an isolated place - is the most important part of their message to Jesus. They might then think that the disciples are afraid of the spirits in that place, and that sending the people to buy food is a way to protect them from the spirits. That is the wrong message.
 
 >Woe to you when all men speak well of you, for that is how their ancestors treated the false prophets. (Luke 6:26 ULB)
 
-In this verse, the most important part of the information is first—that "woe" is coming on the people for what they are doing. The reason that supports that warning comes last. This could be confusing for people who expect the important information to come last.
+In this verse, the most important part of the information is first - that "woe" is coming on the people for what they are doing. The reason that supports that warning comes last. This could be confusing for people who expect the important information to come last.
 
 ### Translation Strategies
 

archive/translate/file-formats/01.md

@@ -1,37 +0,0 @@
-
-### The Technical Nature of Translation
-
-While a large part of translation has to do with language, words, and sentences, it is also true that a major aspect of translation is technical in nature. From creating alphabets, typing, typesetting, formatting, publishing, and distributing, there are many technical aspects to translation. In order to make all this possible, there are some standards that have been adopted.
-
-### USFM: Bible Translation Format
-
-For many years, the standard format for Bible translation has been USFM (which stands for Unified Standard Format Markers). We have adopted this standard as well.
-
-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.  
-   \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).
-
-**Bible translations need to be written with USFM markers in order for Wycliffe Associates to make them accessible!**
-
-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.
-
-#### 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.
-
-### Conclusion
-
-The easiest way to get content marked up with USFM is by using an editor that is specifically designed to do that. If a word processor or a text editor is used, these markers must be manually entered.
-
-*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.

archive/translate/file-formats/02.md

@@ -1,38 +0,0 @@
-
-### The Technical Nature of Translation
-
-While a large part of translation has to do with language, words, and sentences, it is also true that a major aspect of translation is technical in nature. From creating alphabets, typing, typesetting, formatting, publishing, and distributing, there are many technical aspects to translation. In order to make all this possible, there are some standards that have been adopted.
-
-### USFM: Bible Translation Format
-
-For many years, the standard format for Bible translation has been USFM (which stands for Unified Standard Format Markers). We have adopted this standard as well.
-
-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.
-   \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).
-
-**Bible translations need to be written with USFM markers in order for Wycliffe Associates to make them accessible!**
-
-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 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 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
-
-The easiest way to get content marked up with USFM is by using an editor that is specifically designed to do that. If a word processor or a text editor is used, these markers must be manually entered.
-
-*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/authentic-assessment/01.md

@@ -55,7 +55,7 @@ Culturally Relevant
 4. Proper punctuation is used.
 
 **Natural**  
-1. The text sounds like how we speak. It uses common language  
+1. The text sounds like how we speak – uses common language  
 2. Sounds beautiful and academic   
 3. The text is efficient and effective in its communication
 

checking/authentic-assessment/sub-title.md

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

checking/authority-level1/01.md

@@ -1,10 +1,11 @@
 ### Affirmation by Translation Team
 
-The intent of this level is to affirm that the translators have taken steps to ensure the accuracy of their translation and that the translation is in agreement with standard Christian doctrine. Publishing content at this level makes it available to members of the language community and provides an open invitation (implied or direct) to them to suggest improvements to the translation.
+
+The intent of this level is to affirm the agreement of the translation team with standard Christian doctrine, as well as with the guidelines for ensuring the accuracy of the translation itself. Publishing content at this level makes it available to members of the language community and provides an open invitation (implied or direct) to them to suggest improvements to the translation.
 
 To achieve this level, the translation team asserts that the [Statement of Faith](../../intro/statement-of-faith/01.md) is an accurate reflection of their own beliefs and that the translated content is also in harmony with it.
 
 The translation team asserts that the translation has been done in accordance with the MAST process and that they have made use of available exegetical and translation checking resources in the translation process, including the Translation Notes and Translation Words.
 
-An explanation of the steps followed during level one checking is available at [Level One Check](../level1/01.md).
+An explanation of the steps followed during level one checking are available at [Level One Check](../level1/01.md).
 

checking/authority-level1/sub-title.md

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

checking/authority-level2/01.md

@@ -8,7 +8,7 @@ The intent of this level is two-fold:
 
 At this level, the model implements the concept of a "testimony of two or three witnesses" in the checking process.
 
-To achieve this level, the translation team will submit the translation to members of the language community that will use the translation. The language community will review the translation for **clarity** and **naturalness**. The team will also work with church leaders from the language community to review the translation for **accuracy** by checking it against the source texts, the exegetical resources, and the [Statement of Faith](../../intro/statement-of-faith/01.md).
+To achieve this level, the translation team will submit the translation to members of the language community that will use the translation. The language community will review the translation for **clarity** and **naturalness**. The team will also work with church leaders from the language community to review the translation for **accuracy** by checking it against the source texts, the exegetical resources, the [Statement of Faith](../../intro/statement-of-faith/01.md), and the [Translation Guidelines](../../intro/translation-guidelines/01.md).
 
 The translation team will edit the translation based on these reviews so that the language community affirms that it is natural and clear, and the church leaders affirm that it is accurate.
 

checking/authority-level2/sub-title.md

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

checking/authority-level3/sub-title.md

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

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?
+

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,45 +0,0 @@
-
-### 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
-
-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
-    * names of people and places
-    * words specific to the historical environment
-    * words that connect one thought to another
-    * words that show the author's attitude or beliefs.
-2. Discuss the words on your list. Use the Translation Notes and Translation Words to ensure that  you understand the meanings of each word. (Some words have more than one meaning.) Make an initial decision on how to translate each meaning of the source language word. Write your decisions next to each word. Sometimes there  is no word in the target language that means the same as the source language words. When that is the situation, you may choose to do one of the following:
-    * 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.
-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. 
-    * In the next column, write next to each source language word your translation of the word.
-   * 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.
-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.
-
-### 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.
-    * What key words from your chart are in the source text?
-    * Does the verse have any key words that should be on your key word chart?
-    * Use the Translation Notes and Translation Words to ensure that you understand the meanings of each new key word.
-    * Add the new key words to your chart. 
-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).)

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

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

checking/chk-peer-edit/01.md

@@ -1,8 +0,0 @@
-
-### How to do a Peer-Edit (MAST Step 6)
-
-* 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 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.
-* 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 +0,0 @@
-How can others help me check my work?

checking/chk-self-edit/01.md

@@ -1,10 +0,0 @@
-
-### How to do a Self-edit (MAST Step 5)
-
-* 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 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. 
-* 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 +0,0 @@
-How do I check my first draft?

checking/chk-team-check/01.md

@@ -1,20 +0,0 @@
-
-
-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. 
-
-### 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) .
-
-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.
-
-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/sub-title.md

@@ -1 +0,0 @@
-How do the translators check the translation?

checking/chk-team-check/title.md

@@ -1 +0,0 @@
-Checking a Translation

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

@@ -1,17 +0,0 @@
-### 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.
-
-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. 
-
-The wording will not be exactly the same between the source text and the back-translation, but it is important that:  
-(1) the meaning in the translation is the same as the meaning in the source text   
-(2) all of the events and important details found in the source text are present in the translation and  
-(3) no new or extra information has been added. 
-
-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))
-

checking/chk-verses/sub-title.md

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

checking/chk-verses/title.md

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

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/consistency-check/01.md

@@ -1,24 +1,25 @@
-In order for readers to be able to understand the translation easily, it is important that there be consistency in the following things: important words, spelling, punctuation, and formatting. Checking a translation for consistency is something that is done continually. First it is part of Steps 5-8 of MAST; a MAST facilitator may develop a specific strategy for a project to help maintain consistency for important words, spelling, punctuation, and formatting.
-
-Consistency checking is also part of the proofreading near the end of the refinement and revision processes. This is because during these processes it is very easy to find and resolve inconsistencies.
+In order for readers to be able to understand the translation easily, it is important that there be consistency in the following things: spelling, punctuation, and formatting. 
 
 #### 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/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?
+

checking/key-word-check/01.md

@@ -0,0 +1,14 @@
+
+### How to do a key word Check
+
+* Key words are the words that impact the theme and message of the passage--they are abstract, spiritual, geographical and historical terms. Make a list of the key words in the story or Bible passage that you translate, along with the term that you choose for it in the target language. Here are some things to consider in choosing an appropriate term in your mother-tongue.
+    * You may choose to borrow the term from the Gateway Language and adjust the spelling to fit your script and pronunciation.
+    * You may choose to create a phrase or combine a few words into one.
+    * You may choose a word with an added descriptor. 
+    * You may choose the common use word from the local Christian community. 
+    * You may choose a simple equivalent from every-day language use. 
+* Use the list of words and definitions in the Translation Words resource available on bibleineverylanguage.org and translationStudio to help you to make a list of these words and to understand what they mean. Your own list may include additional words, but 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 natural flow in the target language. Remember, key words are ones of significance, packed with essential meaning and are often difficult to directly translate. 
+* It is best if you can create a chart so that you can list the source word or phrase in one column and the target word or phrase in another column. Further columns could list equivalent terms in other languages and the references where these terms occur in the Bible. It is ideal if everyone translating Bible books that use these terms has access to the chart so that you can all use the same words or phrases in your translation.
+* Each time the key word occurs in the source text, make sure that the term you have chosen for the translation still makes sense in that context. If it does not, discuss the problem with others on the translation team and try to find a solution together. You may need to use a different term, or you may need to use more than one term for the different contexts, or you may need to find another way to communicate the key word that includes all of the meanings, such as using a longer phrase.
+* When you have decided that you need to use different target language words or phrases to translate one source language key word in different contexts, then make a new line on the chart for each different way that you are translating the source word. Repeat the source term in the source column, and put the new translation in the next column, under the first translation. If possible, share this chart with everyone on the translation team so that they can choose the right translation for the source word in the context that they are translating.
+

checking/key-word-check/sub-title.md

@@ -0,0 +1,2 @@
+How can we check that the correct key words are used in our translation?
+

checking/level1/01.md

@@ -10,7 +10,7 @@ These are the steps that the translation team must follow in order to achieve Ch
 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, carefuly 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. 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 assisted in the keyword check. For more information, see [Verse-by-verse Check](../verse-by-verse/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 assisted in the keyword check. 
 
 When these steps have been completed, edits have been incorporated into the translated portion, and the translation team is collectively satisifed with the product, it is considered level one checked. At this point, if the translation team desires to do so, they are invited to upload the translation to the Wycliffe Associates content server where the work can be seen on [bibleineverylanguage.org](https://bibleineverylanguage.org) to reach a broader community. 
 

checking/level1/title.md

@@ -0,0 +1,2 @@
+Level One Check - Translation Team Check
+

checking/level2/title.md

@@ -0,0 +1,2 @@
+Level Two Check - Community Check
+

checking/level3/01.md

@@ -8,7 +8,7 @@ Level Three is completed when the translation has been thoroughly checked and va
 
 Here are some specific steps that can be followed for this check. However, the most important aspect of this check is to consider the authentic assessment rubric created by the translation team as the guide. 
 
-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)?
+1. Does the translation conform to the Statement of Faith and Translation Guidelines?
 2. Did the translation team show a good understanding of the source language as well as the target language and culture?
 3. Does the language community affirm that the translation speaks in a clear and natural way in their language?
 4. Is the style that the translators followed appropriate for the community?

checking/level3/title.md

@@ -0,0 +1,2 @@
+Level Three Check - Church Leadership Check
+

checking/other-methods/01.md

@@ -0,0 +1,15 @@
+
+### Other Checking Methods
+
+As well as asking questions, there are other checking methods that you may also use to ensure that the translation is easy to read and sounds natural to the listeners. Here are some other methods that you may like to try:
+
+* **Retell Method**: You, the translator or tester, can read a few verses and ask someone else to retell what was said. This helps to check the clarity and naturalness of the translation and offers alternate ways of saying the same thing.
+
+* **Reading Method**: Someone other than you, the translator or tester, should read a portion of the translation while you take notes where the pauses and mistakes occur. This will show how easy or how difficult it is to read and understand the translation. Look at the places in the translation where the reader paused or made mistakes and consider what part of the translation was difficult. You may need to revise the translation at those points so that it is easier to read and understand.
+
+* **Offer Alternate translations**: In areas where you are not sure of the best way to express a word or phrase, ask other people for an alternative translation or offer a choice between two translations and see which alternative translation people think is the most clear.
+
+* **Reviewer Input**: Let others whom you respect read your translation. Ask them to take notes and tell you where it might be improved. Look for better word choices, natural expressions, and even spelling adjustments.
+
+* **Discussion Groups**: Ask people to read the translation aloud in a group of people and allow them and others to ask questions for clarification. Pay attention to the words they use, since alternate words and expressions come up when someone is trying to make sense of a difficult point, and these alternate words and expressions might be better than the ones in the translation. Pay attention to the places where people do not understand the translation, and work to make those places clearer.
+

checking/other-methods/sub-title.md

@@ -0,0 +1,2 @@
+What are some other methods that I can use to check the translation?
+

checking/other-methods/title.md

@@ -0,0 +1,2 @@
+Other Methods
+

checking/peer-edit/01.md

@@ -0,0 +1,8 @@
+
+### 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 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 compeleted a check of the passage, go over the suggested edits together. It is up to the translator to make changes.
+* Read the revised 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. 
+