Perry'sEdits3Q2019Group4 (#195)

README.md

@@ -16,9 +16,9 @@ If you want to make your suggested changes then you may use the online editor to
 
 ## Structure
 
-The tA are written in a simple Markdown format and organized according to the [Resource Container Manual](https://resource-container.readthedocs.io/en/latest/container_types.html#manual-man) type.  See that link for more information but here is a quick summary.
+tA is written in a simple Markdown format and organized according to the [Resource Container Manual](https://resource-container.readthedocs.io/en/latest/container_types.html#manual-man) type.  See that link for more information but here is a quick summary.
 
-Each manual has it’s own directory in this repository (for example, the Checking Manual is in the [checking](https://git.door43.org/unfoldingWord/en_ta/src/branch/master/checking) directory). Each module has its own directory inside of these manual directories. Inside each of these are three files:
+Each manual has its own directory in this repository (for example, the Checking Manual is in the [checking](https://git.door43.org/unfoldingWord/en_ta/src/branch/master/checking) directory). Each module has its own directory inside of these manual directories. Inside each of these are three files:
 
 * `01.md` - This is the main body of the module
 * `sub-title.md` - This file contians the question that the module is intended to answer.

checking/Trans-Note-check

@@ -1,27 +0,0 @@
-How to do a TranslationNotes check in translationCore
-
-	•	Sign in to translationCore
-	•	Select the project (book of the Bible) that you want to check
-	•	Select the category or categories of Notes that you want to check
-	•	Select your Gateway Language
-	•	Click “Launch”
-	•	The verses to be checked will be listed on the left side, divided into different categories of Notes. Select a verse to check, and read the Note for that verse that is in the blue bar. It is best to check all of the verses in the same category before moving to a new category.
-	•	Some Notes refer to a more general issue that applies to the specific verse being examined. To understand this more general issue and how it applies to the current verse, read the information in the panel on the right side.
-	•	After selecting (highlighting) the translation for the word or phrase in the Note, click “Save.”
-	•	Consider whether or not the translation that was chosen for that word or phrase makes sense in this context. 
-	•	Decide whether or not the translation is correct, considering the issue that the Note talks about.
-	•	After considering these things, if you think that the translation is a good translation, then click “Save and Continue.”
-	•	If you think that there is a problem with the verse or that the translation for the word or phrase is not good, then either edit the verse to make it better, or make a comment telling someone who will review your work what you think might be wrong with the translation here.
-	•	If you have made an edit, you may need to make your selection again.
-	•	When you are finished making your edit or comment, click “Save and Continue.” If you prefer to only make a comment for the word or phrase and not make a selection for it, then click on the next verse in the list on the left to go on to the next verse.

-After a selection has been made for all of the verses in a Note category, the list of translations in that category can be reviewed. The instructions that follow are for the reviewer or for the translation team.
-	•	You will now be able to see a list of the translations that were made for each translationNote under each translationNote category on the left. Choose the category that you want to review. It may be that different members of the translation team will have different specialties. For example, one team member may be very good at reviewing metaphors, while another may be very good at understanding and correcting difficult grammar, such as passive voice constructions. 
-	•	You will want to review any comments that were made by others. To do that, click the funnel symbol to the right of “Menu” at the upper left. A list will open, including the word “Comments.”
-	•	Click the box next to “Comments.” This will make all verses that do not have comments in them disappear.
-	•	To read the comments, click on the first verse in the list.
-	•	Click on “Comment.”
-	•	Read the comment, and decide what you will do about it.
-	•	If you decide to make an edit to the verse, then click “Cancel” and then “Edit Verse.” This will open a small screen where you can edit the verse.
-	•	When you are finished making the edit, select the reason for the change, and then click “Save.”
-	•	Continue this process until you have acted on all of the comments that were left for you.

-After you have finished reviewing a Note category or a Bible book, you may still have questions about some verses or Note checks. You may want to discuss a difficult verse with others on the translation team and try to find a solution together, study more Bible translation resources, or refer to the question to a Bible translation expert. 

checking/accuracy-check/01.md

@@ -1,25 +1,28 @@
 
-### Checking the Translation for Accuracy
+### Checking the Translation for Accuracy by Pastors and Church Leaders
 
 It is very important to make sure that the new translation is accurate. A translation is accurate when it communicates the same meaning as the original. In other words, an accurate translation communicates the same message that the original writer intended to communicate. A translation can be accurate even though it uses more or fewer words or puts the ideas in a different order. Often this is necessary in order to make the original message clear in the target language.
 
 Although members of the translation team have checked the translation for accuracy with each other during the [Oral Partner Check](../peer-check/01.md), the translation will continue to improve as it is checked by many people, especially by pastors and church leaders. Each passage or book can be checked by one church leader, or, if many leaders are available, there can be several church leaders checking each passage or book. Having more than one person checking a story or passage can be helpful, because often different checkers will notice different things. 
 
-Those who do accuracy checking should be speakers of the language of the translation, be respected in the community, and know the Bible well in the source language. They should not be the same people who translated the passage or book that they are checking. The accuracy checkers will be helping the translation team make sure that the translation says everything that the source says, and that it does not add things that are not part of the source message. Keep in mind, however, that accurate translations also might include [Implicit Information](../../translate/figs-explicit/01.md).
+The church leaders who do accuracy checking should be speakers of the language of the translation, be respected in the community, and know the Bible well in the source language. They should not be the same people who translated the passage or book that they are checking. The accuracy checkers will be helping the translation team make sure that the translation says everything that the source says, and that it does not add things that are not part of the source message. Keep in mind, however, that accurate translations also might include [Implicit Information](../../translate/figs-explicit/01.md).
 
 It is true that the language community members who do the [Language Community Check](../language-community-check/01.md) *must not* look at the source text while they check the translation for naturalness and clarity. But for accuracy testing, the accuracy checkers *must* look at the source text so that they can compare it with the new translation.
 
-The people doing accuracy checking should follow these steps:
+The Church Leaders doing accuracy checking should follow these steps:
 
-1. Each of the accuracy checkers should read the translation (or listen to the recording) by himself, comparing it to the original Bible passage or story in the source language. The checker can do this using translationStudio. It can be helpful for the translator to read the translation out loud to the checker while the checker follows along looking at the source Bible or Bibles. As the checker reads (or listens to) the translation and compares it to the source, he should keep in mind these general questions:
+1. If possible, find out ahead of time which set of stories or which Bible passage you will be checking.
+Read the passage in several versions in any languages you understand. Read the passage in the ULT and UST, along with the Notes and translationWords. You can read these in translationStudio or in Bible Viewer. 
+ 
+1. Then each of the accuracy checkers should read the translation (or listen to the recording) by himself, comparing it to the original Bible passage or story in the source language. The checker can do this using translationStudio. It can be helpful for someone, such as the translator, to read the translation out loud to the checker while the checker follows along looking at the source Bible or Bibles. As the checker reads (or listens to) the translation and compares it to the source, he should keep in mind these general questions:
 
   * Does the translation add anything to the original meaning? (The original meaning also includes [Implicit Information](../../translate/figs-explicit/01.md).)
   * Is there any part of the meaning that is left out of the translation?
   * Has the translation changed the meaning in any way?    
   
-1. It can be helpful to read or listen to the Bible passage several times. You might not notice everything the first time through a passage or verse. This is especially true if the translation puts ideas or parts of a sentence in a different order than in the source. You may need to check for one part of the sentence, then read or listen again to check for another part of the sentence. When you have read or listened to the passage as many times as it takes to find all of its parts, then you can move to the next passage. For more ways to check if the translation is complete, see [complete](../complete/01.md).
+1. It can be helpful to read or listen to the translation of the Bible passage several times. You might not notice everything the first time through a passage or verse. This is especially true if the translation puts ideas or parts of a sentence in a different order than in the source. You may need to check for one part of the sentence, then read or listen again to check for another part of the sentence. When you have read or listened to the passage as many times as it takes to find all of its parts, then you can move to the next passage. For more ways to check if the translation is complete, see [complete](../complete/01.md).
 
-1. The checker should make notes where he thinks there might be a problem or something to be improved. Each checker will discuss these notes with the translation team.
+1. The checker should make notes where he thinks there might be a problem or something to be improved. Each checker will discuss these notes with the translation team. The notes could be in the margins of a printed translation draft, or in a spreadsheet, or using the comment feature of translationCore.
 
 1. After the checkers have checked a chapter or book of the Bible individually, they should all meet with the translator or translation team and review the chapter or book together. If possible, project the translation on the wall so that everyone can see it. As the team comes to the places where each checker made note of a problem or question, the checkers can ask their questions or make suggestions for improvement. As the checkers and the translation team discuss the questions and suggestions, they might think of other questions or new ways of saying things. This is good. As the checkers and the translation team work together, God will help them discover the best way to communicate the meaning of the story or Bible passage.
 
@@ -40,3 +43,5 @@ These questions can also be helpful for finding anything that might be inaccurat
 * Are the phrases used in the new translation helpful in understanding the more difficult phrases of the source translation? (Are the phrases of the new translation put together in a way that brings better understanding and still fit with the meaning of the source language translation?)
 * Another way to determine if the text is accurate is to ask comprehension questions about the translation, such as, “who did what, when, where, how, and why.” There are questions that have already been prepared to help with this. (To view the translationQuestions go to http://ufw.io/tq/.) The answers to those questions should be the same as the answers to those questions about the source language translation. If they are not, there is a problem in the translation.
 
+For more general types of things that need to be checked, go to [Types of Things to Check](../vol2-things-to-check/01.md). 
+

checking/accurate/01.md

@@ -1,6 +0,0 @@
-
-### An Accurate Translation
-
-It is very important to make sure that the new translation is accurate. Those who have been chosen to check the translation for accuracy have the responsibility to make sure that it communicates the same meaning as the original writer intended and expected to communicate.
-
-For instructions on how to do this, go to [Accuracy Check](../accuracy-check/01.md), and follow the steps in the section under the heading “All Levels.”

checking/accurate/sub-title.md

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

checking/accurate/title.md

@@ -1 +0,0 @@
-Accurate Translation

checking/alignment-tool/01.md

@@ -1,7 +1,7 @@
 #### In order to use the Alignment Tool to do Validation Checking:  
 
 1. Load the translation of the Bible book that you want to check into translationCore. 
-1. Choose the alignment tool. 
+1. Choose the Word Alignment tool. 
 1. Navigate through the verses using the menu of chapters and verses on the left side.
   *  When you click on a verse in the menu list to open it, the words of that verse appear in a vertical list, ordered from top to bottom, just to the right of the list of chapters and verses. Each word is in a separate box.
   *  The words of the original language (Greek, Hebrew, or Aramaic) text for that verse are also in separate boxes in a field to the right of the target language word list. There is a space under each of the original language word boxes outlined with a dotted line.
@@ -31,3 +31,7 @@ Because each target language will have different requirements for sentence struc
 * The leftmost original language word can also be unmerged by dragging and dropping it into the original language word box immediately to its left.
 * Any target language words that were aligned with that original language word then return to the word list.
 * The original language words should remain in the proper order. If the merge contains 3 or more original language words, unmerge the rightmost original language word first. Un-merging the center word(s) first may result in the original language words becoming out of order. When that happens, unmerge the remaining words in that box to properly return the original language words to their original order.
+
+#### After Aligning
+
+After you have finished aligning a Bible book and making questions and comments about the translation, it is time to either send the questions to the translation team or plan to meet together with the translation team and discuss them. For the steps to complete this process, return to where you left off on the [Steps for Validation Checking](../vol2-steps/01.md) page. 

checking/alignment-tool/sub-title.md

@@ -0,0 +1 @@
+How do I use the Alignment Tool for Validation Checking?

checking/alignment-tool/title.md

@@ -0,0 +1 @@
+The Alignment Tool

checking/authority-level1/01.md

@@ -1,8 +0,0 @@
-
-### Authority Level 1: Affirmation by Translation Team
-
-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. Content published at this level promotes the broadest reach of the content as an active project, with an open invitation (implied or direct) to members of the language community 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 translator (or team) asserts that the translation has been done in accordance with the [Translation Guidelines](../../intro/translation-guidelines/01.md) and that they have made use of available exegetical and translation checking resources in the translation process, including the translationNotes and translationWords.

checking/authority-level1/sub-title.md

@@ -1 +0,0 @@
-What is authority level 1?

checking/authority-level1/title.md

@@ -1 +0,0 @@
-Authority Level 1

checking/authority-level2/01.md

@@ -1,15 +0,0 @@
-
-### Authority Level 2: Affirmation by Community
-
-The intent of this level is two-fold:
-
-1. to affirm the effectiveness of the form of the language used in the translation, as determined by representatives of the language community
-1. to affirm the accuracy of the translation, as determined by pastors or leaders from the local churches that will use it
-
-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 translation team will then submit the translation to church leaders from the language community that will use the translation. These church leaders will 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 so that the church leaders affirm that it is accurate.

checking/authority-level2/sub-title.md

@@ -1 +0,0 @@
-What is authority level 2?

checking/authority-level2/title.md

@@ -1 +0,0 @@
-Authority Level 2

checking/authority-level3/01.md

@@ -1,10 +0,0 @@
-
-### Authority Level 3: Affirmation by Church Leadership
-
-The intent of this level is to affirm that the translation agrees with the intent of the original texts and with the sound doctrine of the Church historic and universal.
-
-To achieve this level, the translation team will submit the translation for review by the highest leadership of the Church that speaks the language. It is best if these leaders represent as many of the major groups of churches that exist in the language community as possible. Level 3 is thus achieved by the mutual agreement of the leadership of multiple church networks.
-
-The translation team will edit the translation so that the leadership of these church networks affirm that it is an accurate translation and will be accepted by their church fellowships.
-
-Level 3 is completed when the translation has been thoroughly checked and approved by the leadership (or their delegates) of at least two church networks that have personnel that are familiar with translation principles and are trained in biblical languages and content.

checking/authority-level3/sub-title.md

@@ -1 +0,0 @@
-What is authority level 3?

checking/authority-level3/title.md

@@ -1 +0,0 @@
-Authority Level 3

checking/authority-process/01.md

@@ -9,4 +9,4 @@ The Bible belongs to the Church historic (throughout history) and universal (thr
 
 With the above understanding, we also affirm that the church that speaks each language has the authority to decide for themselves what is and what is not a good quality translation of the Bible in their language. Authority to check and approve a Bible translation (which is constant) is separate from capacity, or the ability to carry out the process of checking a Bible translation (which can be increased). The authority for determining the quality of a Bible translation belongs to the church that speaks the language of the translation, independent of their current ability, experience, or access to resources that facilitate the checking of the Bible translation. So while the church in a language group has the authority to check and approve their own Bible translation, the unfoldingWord tools, including these modules of translationAcademy, are designed to ensure that each church also has the capacity to check the quality of their Bible translation using an excellent process. These tools are designed to give the church in each language group access to some of what Bible experts have said about the Bible and how those in other parts of the Church have translated it into other languages.
 
-The process for checking a translation will be described in the Process Manual of translationAcademy.
+The process for checking a translation will be described in the rest of this Checking Manual.

checking/clear/01.md

@@ -9,6 +9,6 @@ A translation should be clear. That means that someone reading or hearing it can
 
 Additional help:
 
-* One way to determine if the text is clear is to read a few verses at a time out loud and ask someone listening to retell the story after each section. If the person can easily restate your message, then the writing is clear. For other methods of testing the translation, see [Other Methods](.../other-methods/01.md).
+* One way to determine if the text is clear is to read a few verses at a time out loud and ask someone listening to retell the story after each section. If the person can easily restate your message, then the writing is clear. For other methods of testing the translation, see [Other Methods](../other-methods/01.md).
 * If there is a place where the translation is not clear, make a note of that so that you can discuss it with the translation team.
 

checking/community-evaluation/01.md

@@ -28,4 +28,4 @@ Please also answer the following questions. The answers to these questions will
 <br>
 <br>
 
-The community leaders might want to add their own information to this or make a summary statement about how acceptable this translation is to the local community. The wider church leadership will have access to this information, and it will help them validate the translation as approved by the local Christian community when they do the Pastor's Accuracy Check and also Validation Checking.
+The community leaders might want to add their own information to this or make a summary statement about how acceptable this translation is to the local community. The wider church leadership will have access to this information, and it will help them to understand and to have confidence in the checking process that has been done so far. This will help them to validate the translation as approved by the local Christian community both when they do the Accuracy Check and when they do the final Validation Check.

checking/complete/01.md

@@ -4,7 +4,7 @@
 The purpose of this section is to make sure that the translation is complete. In this section, the new translation must be compared to the source translation. As you compare the two translations, ask yourself these questions:
 
 1. Is the translation missing any of its parts? In other words, does the translation include all the events of the book that was translated?
-1. Does the translation include all the verses of the book that was translated? (When you look at the verse numbering of the source language translation, are all of the verses included in the target language translation?) Sometimes there are differences in verse numbering between translations. For example, in some translations some verses are grouped together or sometimes certain verses are put in footnotes. Even though there may be these kinds of differences between the source translation and the target translation, the target translation is still considered to be complete.
+1. Does the translation include all the verses of the book that was translated? (When you look at the verse numbering of the source language translation, are all of the verses included in the target language translation?) Sometimes there are differences in verse numbering between translations. For example, in some translations some verses are grouped together or sometimes certain verses are put in footnotes. Even though there may be these kinds of differences between the source translation and the target translation, the target translation is still considered to be complete. For more information, see [Complete Versification](../verses/01.md).
 1. Are there places in the translation where something seems to be left out, or there seems to be a different message than is found in the source language translation? (The wording and the order can be different, but the language that the translator used should give the same message as the source language translation.)
 
 If there is a place where the translation is not complete, make a note of that so that you can discuss it with the translation team.

checking/config.yaml

@@ -2,64 +2,43 @@ acceptable:
   recommended:
     - alphabet
     - complete
+    - community-evaluation
   dependencies:
     - clear
     - natural
     - church-leader-check
 accuracy-check:
   recommended:
-    - level2
     - language-community-check
-    - church-leader-check
     - other-methods
     - guidelines-accurate
   dependencies:
-    - level1
+    - church-leader-check
     - guidelines-accurate
     - important-term-check
-accurate:
-  recommended:
-    - complete
-    - accuracy-check
-    - guidelines-accurate
-  dependencies:
-    - alphabet
-    - church-leader-check
+alignment-tool:
+  recommended: 
+    - vol2-things-to-check
+  dependencies: 
+    - vol2-steps
 alphabet:
-  recommended: []
+  recommended:
+    - spelling
   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
+    - formatting
 authority-process:
-  recommended:
-    - authority-level1
-    - level1
+  recommended: 
+    - peer-check
   dependencies:
     - goal-checking
 church-leader-check:
   recommended:
     - accuracy-check
-    - accurate
     - good
-  dependencies:
-    - level2
+  dependencies: 
+    - trans-note-check
 clear:
   recommended:
     - acceptable
@@ -67,21 +46,24 @@ clear:
     - guidelines-clear
     - language-community-check
   dependencies:
-    - level2
+    - other-methods
 community-evaluation:
   recommended:
     - church-leader-check
     - self-assessment
+    - good
   dependencies:
     - language-community-check
     - other-methods
     - writing-decisions
+    - acceptable
 complete:
   recommended:
     - self-assessment
     - good
-  dependencies:
-    - accurate
+    - verses
+  dependencies: 
+    - punctuation
 formatting:
   recommended:
     - alphabet
@@ -89,21 +71,25 @@ formatting:
     - punctuation
   dependencies:
     - vol2-things-to-check
+    - level3-approval
 goal-checking:
   recommended:
     - intro-checking
     - authority-process
   dependencies:
-    - intro-levels
+    - intro-check
+    - intro-checking
 good:
   recommended:
     - self-assessment
     - level3
   dependencies:
     - complete
+    - community-evaluation
 headings:
   recommended:
     - community-evaluation
+    - publishing
   dependencies:
     - acceptable
     - punctuation
@@ -111,26 +97,20 @@ headings:
 important-term-check:
   recommended:
     - accuracy-check
+    - trans-note-check
   dependencies:
-    - level1
     - peer-check
+    - team-oral-chunk-check
 intro-check:
   recommended:
-    - intro-checking
+    - goal-checking
   dependencies:
-    - translate-manual
+    - intro-checking
 intro-checking:
   recommended:
-    - intro-levels
-  dependencies:
     - intro-check
-intro-levels:
-  recommended:
-    - intro-levels
-    - level1
-    - translate-source-version
   dependencies:
-    - intro-checking
+    - translate-manual
 language-community-check:
   recommended:
     - natural
@@ -138,45 +118,20 @@ language-community-check:
     - 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:
+    - vol2-steps
     - level3-questions
-    - self-assessment
   dependencies:
-    - intro-levels
-    - level2
     - accuracy-check
+    - good
 level3-approval:
-  recommended: []
+  recommended:
+    - formatting
   dependencies:
     - level3
     - level3-questions
-    - self-assessment
 level3-questions:
   recommended:
     - accuracy-check
@@ -184,6 +139,7 @@ level3-questions:
     - self-assessment
   dependencies:
     - level3
+    - vol2-things-to-check
 natural:
   recommended:
     - acceptable
@@ -191,23 +147,28 @@ natural:
     - language-community-check
   dependencies:
     - alphabet
-    - level2
     - clear
 other-methods:
   recommended:
     - writing-decisions
     - community-evaluation
+    - clear
   dependencies:
     - language-community-check
 peer-check:
   recommended:
-    - important-term-check
+    - team-oral-chunk-check
   dependencies:
-    - level1
-    - self-check
+    - first-draft
+publishing:
+  recommended:
+    - vol2-backtranslation
+  dependencies:
+    - headings
 punctuation:
   recommended:
     - verses
+    - complete
   dependencies:
     - spelling
     - translate-alphabet
@@ -226,19 +187,23 @@ self-assessment:
     - complete
     - church-leader-check
     - level3
-self-check:
-  recommended:
-    - peer-check
-  dependencies:
-    - level1
 spelling:
   recommended:
     - punctuation
   dependencies:
-    - vol2-intro
     - acceptable
     - translate-alphabet
     - alphabet
+team-oral-chunk-check:
+  recommended:
+    - important-term-check
+  dependencies:
+    - peer-check
+trans-note-check:
+  recommended:
+    - church-leader-check
+  dependencies:
+    - important-term-check
 verses:
   recommended:
     - headings
@@ -246,10 +211,12 @@ verses:
     - spelling
     - punctuation
     - alphabet
+    - complete
 vol2-backtranslation:
   recommended:
     - vol2-backtranslation-purpose
   dependencies:
+    - publishing
     - vol2-steps
 vol2-backtranslation-guidelines:
   recommended:
@@ -276,19 +243,13 @@ vol2-backtranslation-written:
     - vol2-backtranslation-guidelines
   dependencies:
     - vol2-backtranslation-kinds
-vol2-intro:
-  recommended:
-    - vol2-steps
-  dependencies:
-    - church-leader-check
-    - level3
 vol2-steps:
   recommended:
-    - vol2-backtranslation
+    - alignment-tool
   dependencies:
-    - vol2-intro
+    - level3
 vol2-things-to-check:
   recommended:
-    - formatting
+    - level3-questions
   dependencies:
-    - vol2-steps
+    - alignment-tool

checking/formatting/01.md

@@ -1,5 +1,5 @@
 
-There are checks that you can do before, during, and after translation of a book of the Bible that will make the translation go much easier, look good, and be as easy to read as possible. The modules in this section give more information about the following topics.
+There are checks that you can do before, during, and after translation of a book of the Bible that will make the translation go much easier, look good, and be as easy to read as possible. The modules on these topics are gathered here under Formatting and Publishing, but they are things that the translation team should be thinking and deciding about throughout the translation process. 
 
 ### Before Translating
 

checking/formatting/title.md

@@ -1 +1 @@
-How to Do a Formatting Check
+How to Check for Good Formatting

checking/good/01.md

@@ -4,7 +4,7 @@
 We, as church leaders in our language community, affirm the following:
 
 1. The translation conforms to the Statement of Faith and Translation Guidelines.
-1. The translation is accurate and clear in the target language.
+1. The translation is accurate, clear, and natural in the target language.
 1. The translation uses an acceptable style of the language.
 1. The translation uses an appropriate alphabet and system of spelling.
 1. The community approves of the translation.

checking/good/sub-title.md

@@ -1 +1 @@
-How can church leaders affirm that the translation is good?
+How can church leaders affirm that the translation is accurate, clear, natural, and acceptable to the community?

checking/good/title.md

@@ -1 +1 @@
-Accuracy Affirmation
+Accuracy and Community Affirmation

checking/important-term-check/sub-title.md

@@ -1 +1 @@
-How can I check for the important words in my translation?
+How can I check the accuracy of the important words in my translation?

checking/intro-check/01.md

@@ -1,11 +1,11 @@
 
 ### Translation Checking Manual
 
-This manual describes how to check Bible translations in Other Languages (OLs) for accuracy, clarity, and naturalness. The Manual also discusses the importance of obtaining approval for the translation and the translation process from the church leaders of the language area. 
+This manual describes how to check Bible translations in Other Languages (OLs) for accuracy, clarity, and naturalness. (For the process to check Gateway Languages (GLs), see the [Gateway Language Manual](https://gl-manual.readthedocs.io/en/latest/)). This Translation Checking Manual also discusses the importance of obtaining approval for the translation and the translation process from the church leaders of the language area. 
 
-The manual begins with instructions for checking the translation that the translation team will use to check each other’s work. These checks include the oral partner check and the team oral chunk check. Then there are instructions for the translation team to use for checking the translation with the Translation Core software. These include the Translation Words and Translation Notes checks. 
+The manual begins with instructions for checking the translation that the translation team will use to check each other’s work. These checks include the [Oral Partner Check](../peer-check/01.md) and the [Team Oral Chunk Check](../vol2-intro/01.md). Then there are instructions for the translation team to use for checking the translation with the translationCore software. These include the [Translation Words Check](../important-term-check/01.md) and the [Translation Notes check](../trans-note-check/01.md). 
 
-After this, the translation team will need to check the translation with the language community for clarity and naturalness. This is necessary because other speakers of the language can often suggest better ways of saying things that the translation team may not have thought of. Sometimes the translation team makes the translation sound strange because they are following the words of the source language too closely. Other speakers of the language can help them fix that. 
-Another check that the translation team can do at this point is the OL pastor’s check. Since the OL pastors are familiar with the Bible in the Gateway Language (GL), they can check the translation for accuracy to the GL Bible. They can also catch mistakes that the translation team did not see because the translation team is so close to and involved in their work. Also, the translation team may lack some of the expertise or knowledge of the Bible that other OL pastors might have who are not part of the translation team. In this way, the whole language community can work together to make sure that the Bible translation is accurate, clear, and natural in the target language.  
+After this, the translation team will need to check the translation with the [Language Community](../language-community-check/01.md) for clarity and naturalness. This is necessary because other speakers of the language can often suggest better ways of saying things that the translation team may not have thought of. Sometimes the translation team makes the translation sound strange because they are following the words of the source language too closely. Other speakers of the language can help them fix that. 
+Another check that the translation team can do at this point is the OL pastor or [Church Leader Check](../accuracy-check/01.md). Since the OL pastors are familiar with the Bible in the Gateway Language (GL), they can check the translation for accuracy to the GL Bible. They can also catch mistakes that the translation team did not see because the translation team is so close to and involved in their work. Also, the translation team may lack some of the expertise or knowledge of the Bible that other OL pastors might have who are not part of the translation team. In this way, the whole language community can work together to make sure that the Bible translation is accurate, clear, and natural in the target language.  
 
-A further check for the accuracy of the Bible translation is to align it to the original languages of the Bible using the Word Alignment tool in Translation Core. After all of these checks have been performed and the translation has been aligned, the leaders of the OL church networks will want to review the translation and give their endorsement. Because many leaders of church networks do not speak the language of the translation, there are also instructions for creating a back translation, which allows people to check a translation in a language that they do not speak.
+A further check for the accuracy of the Bible translation is to align it to the original languages of the Bible using the [Word Alignment](../alignment-tool/01.md) tool in Translation Core. After all of these checks have been performed and the translation has been aligned, the leaders of the OL church networks will want to [Review](../vol2-steps/01.md) the translation and give their [Endorsement](../level3-approval/01.md). Because many leaders of church networks do not speak the language of the translation, there are also instructions for creating a [Back Translation](../vol2-backtranslation/01.md), which allows people to check a translation in a language that they do not speak.

checking/intro-checking/01.md

@@ -23,4 +23,6 @@ Also, the translation team is very close to and involved in their work, and so t
 
 This Checking Manual is a guide to the process of checking. It will guide you through several kinds of checks that will allow you to fix these problems. We believe that having many people doing a variety of different checks will result in a faster checking process, allow broad church participation and ownership, and produce better translations.
 
+For more examples of the things that need to be checked, go to: [Types of Things to Check](../vol2-things-to-check/01.md).
+
 *Credits: Quotation used by permission, © 2013, SIL International, Sharing Our Native Culture, p. 69.*

checking/intro-levels/01.md

@@ -1,23 +0,0 @@
-
-### How Checking Levels Work
-
-Here are some important tips to remember when working with Checking Levels:
-
-* Only translations that have reached Checking Level One or higher will be made available on the unfoldingWord website and the unfoldingWord mobile app. (see http://ufw.io/content/)
-* Only translations that have reached Checking Level Three will be approved as source texts for other translations.
-* When a checking level has been completed and all appropriate edits have been made to the translation on door43, the checkers will inform unfoldingWord of the details of the check, including who did the checking and their title or qualifications as a translation checker. unfoldingWord will then harvest a copy of what is on door43, digitally publish a static copy of it on the unfoldingWord website (see https://unfoldingword.bible ) and make it available on the unfoldingWord mobile app. A print-ready PDF will also be produced and made available for download. It will continue to be possible to change the checked version on door43, allowing for future checking and editing.
-* For *Open Bible Stories* projects: Only *Open Bible Stories* translations that have been made from version 3.0 or higher of the English source text are eligible to be checked to Level One (or higher). Translations made from versions before 3.0 must be updated before proceeding with Checking Levels. (see [Source Texts and Version Numbers](../../translate/translate-source-version/01.md))
-
-### The Checking Levels
-
-The strategy for quality assurance of unfoldingWord content, including *Open Bible Stories*, is described briefly here and in detail at http://ufw.io/qa/.
-
-The three-level checking scale we use is dependent on the unfoldingWord [Translation Guidelines](../../intro/translation-guidelines/01.md). All translated content is compared against the theology of the Statement of Faith and against the procedures and methodologies of the Translation Guidelines. With these documents forming the foundation, these are the three levels of checking used in the unfoldingWord project:
-
-* [Checking Level One - Affirmation by Translation Team](../level1/01.md)
-* [Checking Level Two - Affirmation by Community](../level2/01.md)
-* [Checking Level Three - Affirmation by Church Leadership](../level3/01.md)
-
-### Checking the Checkers
-
-The process and checking framework described in this document depends on an ongoing process of checking and revising content, as determined by the Church that uses the content. Feedback loops are encouraged (and modeled in translation software, where feasible) with a view to maximizing input from the greatest number of users of the content. The translations of the content are made available on the translation platform (see http://door43.org ), which is designed to make it easy for users to collaboratively create content that increases in quality over time.

checking/intro-levels/sub-title.md

@@ -1 +0,0 @@
-How do the checking levels work?

checking/intro-levels/title.md

@@ -1 +0,0 @@
-Introduction to the Checking Levels

checking/level1-affirm/01.md

@@ -1,24 +0,0 @@
-
-### Proper Documentation for Level 1 Affirmation
-
-We, the members of the translation team, affirm that we have completed the steps below for level 1 checking:
-
-* Initial study of the text, using:
-  * The translationNotes
-  * The definitions of translationWords
-* Individual blind drafting
-* Individual self check
-* Peer check
-* Key word check as a team
-* Verse-by-verse accuracy check as a team
-* Final editing, including everything learned from the earlier editing sessions, the translationNotes, and the definitions of translationWords
-
-Names of translation team members:
-
-* Name or pseudonym:
-* Name or pseudonym:
-* Name or pseudonym:
-* Name or pseudonym:
-* Name or pseudonym:
-* Name or pseudonym:
-

checking/level1-affirm/sub-title.md

@@ -1 +0,0 @@
-How do I affirm that I have finished level 1 checking?

checking/level1-affirm/title.md

@@ -1 +0,0 @@
-Level 1 Affirmation

checking/level1/01.md

@@ -1,22 +0,0 @@
-
-### Checking Level One – Translation Team Check
-
-Level One checking will be done primarily by the translation team, with some help from others in the language community. The translator or translation team should check their translation before they translate very many stories or chapters of the Bible, so that they can correct mistakes as early as possible in the translation process. Many of the steps in this process will need to be done several times before the translation is finished.
-
-For the purposes of the unfoldingWord project, translations of Bible texts and biblical content are able to be published after they reach Checking Level One. 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.
-
-### Steps for checking under Level One:
-
-These are the steps that the translation team must follow in order to achieve Checking Level One:
-
-1. **Contact.**  Make contact with at least one element of the unfoldingWord network, notifying unfoldingWord that you intend to begin translation. To get information about how to do that, see [Finding Answers](../../intro/finding-answers/01.md)
-1. **Review.**  Review the [Translation Guidelines](../../intro/translation-guidelines/01.md).
-1. **Agree.**  Agree that the Statement of Faith is an accurate reflection of your own beliefs and that you intend to translate the content in harmony with it and also in accordance with the Translation Guidelines by signing the form. (see http://ufw.io/forms/)
-1. **Draft.**  Make a draft translation of some portions of the text. For instructions on how to make a draft translation, see [First Draft](../../translate/first-draft/01.md)
-1. **Self Check**. For instructions on how to do a Self Check of your draft translation, see [Self Check](../self-check/01.md).
-1. **Peer Check**. For instructions on how to do a Peer Check of your draft translation, see [Peer Check](../peer-check/01.md).
-1. **translationWord Check**. For instructions on how to do an translationWord Check of your draft translation, see [translationWord Check](../important-term-check/01.md).
-1. **Accuracy Check**. For instructions on how to do an Accuracy Check of your draft translation, see [Accuracy Check](../accuracy-check/01.md).
-1. **Affirmation**. Affirm that you, as a translation team or individual, have made full use of the translationNotes, the definitions of translationWords, and the other exegetical and translation checking resources in the translation process, and that you have followed the steps for checking under Level One.
-
-(For instructions on how to affirm completion of Level One, see [Level 1 Affirmation](../level1-affirm/01.md).)

checking/level1/sub-title.md

@@ -1 +0,0 @@
-How do I do a level one check?

checking/level1/title.md

@@ -1 +0,0 @@
-Checking Level One - Affirmation by Translation Team

checking/level2/01.md

@@ -1,11 +0,0 @@
-
-### Checking Level Two - External Check
-
-The purpose of Level Two checking is to verify that representative groups from the local language community agree that the translation is a good one.
-
-Level Two checking will be done in two ways:
-
-1. **Language Community Check**. The translation will be checked by members of the language community to make sure that it is clear, natural, and understandable. For the steps to follow to do the Language Community Check, see [Language Community Check](../language-community-check/01.md).
-1. **Church Leader Check**. The translation will be checked by a group of church leaders from the language community to make sure that it is accurate. For the steps to follow to do the Church Leader Check, see [Church Leader Check](../church-leader-check/01.md).
-
-Once this has been done, this work needs to be affirmed (see [Level 2 Affirmation](../good/01.md)).

checking/level2/sub-title.md

@@ -1 +0,0 @@
-How do I do a level 2 check?

checking/level2/title.md

@@ -1 +0,0 @@
-Checking Level Two - Affirmation by Community

checking/level3/01.md

@@ -5,7 +5,7 @@ Validation Checking will be done by people who are chosen by the church leaders
 
 If these people do not exist in the language community, then the translation team will prepare a [backtranslation](../vol2-backtranslation/01.md) so that Bible experts from outside of the language community can do the Validation Checking.
 
-Those who do Validation Checking should be other than the people who did the previous [Accuracy Checking](../accuracy-check/01.md).
+Those who do Validation Checking should be other than the people who did the previous [Accuracy Checking](../accuracy-check/01.md). Since Validation Checking is also a form of accuracy checking, the translation will receive the maximum benefit if different people do each of these checks.   
 
 The purpose of Validation Checking is to ensure that the translation accurately communicates the message of the original biblical texts and reflects the sound doctrine of the Church through history and throughout the world. After Validation Checking, the leaders of the churches that speak the target language affirm that the translation is trustworthy for their people. 
 
@@ -13,4 +13,6 @@ It is best if the leaders from every Church network in the language community ca
 
 The tool that we recommend for Validation Checking is the Alignment Tool in translationCore. To learn more, go to [Alignment Tool](../alignment-tool/01.md).
 
-To proceed with Validation Checking, go to [Questions for Validation Checking](../level3-questions/01.md).
+To learn more about the kinds of things that need to be checked, go to [Types of Things to Check](../vol2-things-to-check/01.md).
+
+To proceed with Validation Checking, go to [Steps for Validation Checking](../vol2-steps/01.md).

checking/level3/sub-title.md

@@ -1 +1 @@
-How do I do a level 3 check?
+What is a Validation Check?

checking/level3/title.md

@@ -1 +1 @@
-Checking Level Three - Affirmation by Church Leadership
+Validation Check - Affirmation by a Network of Churches

checking/other-methods/01.md

@@ -1,7 +1,7 @@
 
 ### Other Checking Methods
 
-As well as asking questions, there are other checking methods that you may also use to ensure that the translation is clear, easy to read, and sounds natural to the listeners. Here are some other methods that you may like to try:
+As well as asking questions, there are other checking methods that you may also use to ensure that the translation is [clear](../clear/01.md), easy to read, and sounds [natural](../natural/01.md) to the listeners. Here are some other methods that you may like to try:
 
 * **Retell Method**:  You, the translator or tester, can read a passage or story and ask someone else to retell what was said. If the person can easily retell the passage, then the passage was clear. Make a note of any place that the person left out or told incorrectly, along with the chapter and verse. The translation team may need to revise those places in the translation to make them more clear. Also make note of any different ways that the person said things that mean the same thing as in the translation. It may be that these ways of saying things are more natural than the ways in the translation. The translation team can use these ways of saying the same thing to make the translation more natural.
 

checking/other-methods/sub-title.md

@@ -1 +1 @@
-What are some other methods that I can use to check the translation?
+What are some other methods that I can use to check the translation for clarity and naturalness?

checking/other-methods/title.md

@@ -1 +1 @@
-Other Methods
+Other Methods for Community Checking

checking/peer-check/01.md

@@ -1,7 +1,7 @@
 
 ### How to do an Oral Partner Check
 
-At this point, you have already gone through the steps of drafting your translation. Now you are ready for others to help you to check it, find any errors or problems, and make it better. To do so, follow these steps.
+At this point, you have already gone through the steps of drafting at least one chapter of your translation, following the guidelines in the module called [First Draft](../../translate/first-draft/01.md). Now you are ready for others to help you to check it, to find any errors or problems, and to make it better. The translator or translation team should check their translation before they translate very many stories or chapters of the Bible, so that they can correct mistakes as early as possible in the translation process. Many of the steps in this process will need to be done several times before the translation is finished. To do an Oral Partner Check, follow these steps.
 
 * Read your translation to a partner (a member of the translation team) who did not work on this passage.  
 * The partner can listen first for naturalness (without looking at the source text) and tell you which parts do not sound natural in your language. Together, you can think of how someone would say that meaning in your language.  

checking/publishing/publishing.md

@@ -0,0 +1,10 @@
+### Publishing on Door43 and unfoldingWord.Bible
+
+* Throughout the translation and checking process, the translation draft will be uploaded to and maintained in a repository under the username that you have chosen on the Door43 website. This is where translationStudio and translationCore send the drafts when you tell them to upload. 
+* When checking has been completed and all appropriate edits have been made to the translation on door43, the checkers or church leaders will inform unfoldingWord of their desire to publish, and provide unfoldingWord with the documents affirming that the [Pastors](../good/01.md), the [Community](../community-evaluation/01.md), and the [Church Network Leaders](../level3-approval/01.md) affirm that the translation is trustworthy. The documents also contain an affirmation of the unfoldingWord [Translation Guidelines](../../intro/translation-guidelines/01.md) and the unfoldingWord [Statement of Faith](../../intro/statement-of-faith/01.md). All translated content is expected to be in accordance with the theology of the Statement of Faith and have followed the procedures and methodologies of the Translation Guidelines. unfoldingWord has no way to verify the accuracy of the translations or the affirmations, and so relies on the integrity of the leadership of the church networks.
+* After obtaining these affirmations, unfoldingWord will then make a copy of the translation that is on door43, digitally publish a static copy of it on the unfoldingWord website (see https://unfoldingword.bible) and make it available on the unfoldingWord mobile app. A print-ready PDF will also be produced and made available for download. It will continue to be possible to change the checked version on door43, allowing for future checking and editing.
+* unfoldingWord will also need to know the version number of the source that was used for the translation. This number will be incorporated into the version number for the translation so that it will be easy to keep track of the state of the source and the translation as they both improve and change over time. For information about version numbers, see [Source Texts and Version Numbers](../../translate/translate-source-version/01.md).
+
+### Checking the Checkers
+
+The process and checking framework described in this document depends on an ongoing process of checking and revising content, as determined by the Church that uses the content. Feedback loops are encouraged (and modeled in translation software, where feasible) with a view to maximizing input from the greatest number of users of the content. For that reason, the translations of the content continue to be made available on the translation platform (see http://door43.org) indefinitely so that users can continue to improve it. In this way, the church can work together to create biblical content that only increases in quality over time.

checking/publishing/sub-title.md

@@ -0,0 +1 @@
+How can our translation get published on Door43 and unfoldingWord?

checking/publishing/title.md

@@ -0,0 +1 @@
+Publishing

checking/self-assessment/01.md

@@ -109,8 +109,8 @@ This section can be strengthened through doing more accuracy checking. (See [Acc
 
 **no | yes** Church leaders who have checked this translation are native speakers of the target language, and include someone who understands well one of the languages in which the source text is available.
 
-**no | yes** People from the language community, both men and women, old and young, have reviewed the translation of this chapter and agree that it is natural and clear. *(Note: this addresses the first part of the community check for Level 2.)*
+**no | yes** People from the language community, both men and women, old and young, have reviewed the translation of this chapter and agree that it is natural and clear. 
 
-**no | yes** Church leaders from at least two different church networks have reviewed the translation of this chapter and agree that it is accurate. *(This addresses the final aspect of Level 2, the Church check).*
+**no | yes** Church leaders from at least two different church networks have reviewed the translation of this chapter and agree that it is accurate. 
 
-**no | yes** The leadership or their delegates of at least two different church networks have reviewed the translation of this chapter and endorse it as a faithful translation of this chapter of the Bible in this language. *(This addresses Level 3.)*
+**no | yes** The leadership or their delegates of at least two different church networks have reviewed the translation of this chapter and endorse it as a faithful translation of this chapter of the Bible in this language. 

checking/self-check/01.md

@@ -1,7 +0,0 @@
-
-### How to do a Self-Check
-
-* If you have followed the guidelines for making a [First Draft](../../translate/first-draft/01.md) translation, then you made your first translation of a passage by studying the source text, and then you wrote it down while you were not looking at the source text. After you have translated a passage in this way, do a self-check by looking again at the source text and comparing it to your translation. Make sure that it says all the parts of the message of the source text and does not leave out anything. If some part of the message was missing, put it in your translation at the point where it fits best in your language.
-* If you are translating the Bible, 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 revise your translation in that way. If one of those helps you to understand something better than you did before, then change your translation so that it communicates the meaning better.
-* 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. Sometimes parts of sentences need to be put in a different order.
-

checking/self-check/sub-title.md

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

checking/self-check/title.md

@@ -1 +0,0 @@
-Self Check

checking/spelling/01.md

@@ -1,8 +1,8 @@
 
-In order for the reader to be able to read and understand the translation easily, it is important that you spell words consistently. This can be difficult if there is not a tradition of writing or spelling in the target language. Several people working on different parts of a translation also makes this difficult.  For that reason, it is important for the translation team to meet together before they start translating to talk about how they plan to spell words.
+In order for the reader to be able to read and understand the translation easily, it is important that you spell words consistently. This can be difficult if there is not a tradition of writing or spelling in the target language. When there are several people working on different parts of a translation, they may spell the same words differently from each other.  For that reason, it is important for the translation team to meet together before they start translating to talk about how they plan to spell words.
 
-Discuss the words that are difficult to spell as a team. If the words have sounds in them that are difficult to represent, then you may need to make a change in the writing system that you are using (see [Alphabet/Orthography](../../translate/translate-alphabet/01.md)). If the sounds in the words can be represented in different ways, then the team will need to agree on how to spell them. Make a list of the agreed upon spellings of these words in alphabetical order. Make sure that each member of the team has a copy of the list, to consult when translating. Add to the list as you come across more difficult words, but make sure everyone has the current list. It may be helpful to use a spreadsheet to maintain your spelling list.
+As a team, discuss the words that are difficult to spell. If the words have sounds in them that are difficult to represent, then you may need to make a change in the writing system that you are using (see [Alphabet/Orthography](../../translate/translate-alphabet/01.md)). If the sounds in the words can be represented in different ways, then the team will need to agree on how to spell them. Make a list of the agreed-upon spellings of these words in alphabetical order. Make sure that each member of the team has a copy of this list that they can consult when translating. Add other difficult words to the list as you come across them, and make sure that these are added to everyone's list with the same spelling. It may be helpful to use a spreadsheet to maintain your spelling list. This can be easily updated and shared electronically, or printed out periodically.
 
 The names of people and places in the Bible can be difficult to spell because many of them are unknown in target languages. Be sure to include these in your spelling list.
 
-Computers can be a great help for checking spelling. If you are working on a Gateway Language, a word processor may have a dictionary already available. If you are translating into an Other Language, you can use the find and replace feature to fix misspelled words. ParaTExt also has a spell check feature which will find all variant spellings of words. It will present these to you and then you can choose which spellings you have decided to use.
+Computers can be a great help for checking spelling. If you are working on a Gateway Language, a word processor may have a dictionary already available. If you are translating into an Other Language, you can use the find-and-replace feature of a word processor to fix misspelled words. ParaTExt also has a spell check feature which will find all variant spellings of words. It will present these to you and then you can choose which spellings you have decided to use.

checking/team-oral-chunk-check/01.md

@@ -0,0 +1,15 @@
+To check the translation of a passage or chapter as a team, do a Team Oral Chunk Check. To do this, each translator will read his translation out loud to the rest of the team. At the end of each chunk, the translator will stop so that the team can discuss that chunk. Ideally, each written translation is projected where all can see it while the translator reads the text orally.
+
+The duties of the team members are divided - it is important that each team member only plays one of the following roles at a time.
+
+1. One or more team members listen for naturalness. If something is unnatural, at the end of reading the chunk, they recommend a more natural way to say it.
+1. One or more team members follow along in the source text, noting anything that is added, missing, or changed. At the end of reading the chunk, they alert the team that something is added, missing, or changed.
+1. Another team member follows along in the report mode of translationCore, noting all of the highlighted key terms in the source text. The team then discusses any key terms in the translation that seem inconsistent or inappropriate, along with any other problems that surface in the reading. If this mode is not available, this team member can look up the key terms on the team’s key term spreadsheet.  
+
+These steps can be repeated as necessary until the team is satisfied with their translation.
+
+At this point, the translation is considered a first draft, and the team needs to also do the following.
+
+1. Someone on the translation team needs to enter the text into translationStudio. If the team has been using translationStudio from the beginning of drafting, then all that needs to be entered at this point are the changes that the team has made.
+1. A new audio recording should be made of the translation, incorporating all of the changes and improvements that the team has made.
+1. The translationStudio files and the audio recording should be uploaded to the team repository on Door43.

checking/team-oral-chunk-check/sub-title.md

@@ -0,0 +1 @@
+How can we check our translation as a team?

checking/team-oral-chunk-check/title.md

@@ -0,0 +1 @@
+Team Oral Chunk Check

checking/toc.yaml

@@ -2,110 +2,89 @@ title: "Table of Contents"
 sections:
   - title: "Introduction to Checking"
     sections:
-      - title: "Introduction to the Checking Manual"
-        link: intro-check
       - title: "Introduction to Translation Checking"
         link: intro-checking
-      - title: "Introduction to the Checking Levels"
-        link: intro-levels
+      - title: "Introduction to the Checking Manual"
+        link: intro-check
       - title: "The Goal of Checking"
         link: goal-checking
-  
-  - title: "Types of Checks"
-    sections:
-      - title: "Self Check"
-        link: self-check
-      - title: "Peer Check"
-        link: peer-check
-      - title: "translationWord Check"
-        link: important-term-check
-      - title: "Accuracy Check"
-        link: accuracy-check
-      - title: "Language Community Check"
-        link: language-community-check
-      - title: "Church Leader Check"
-        link: church-leader-check
-      - title: "Other Methods"
-        link: other-methods
-
-  - title: "What to Check For"
-    sections:
-      - title: "Accurate Translation"
-        link: accurate
-      - title: "Clear Translation"
-        link: clear
-      - title: "Natural Translation"
-        link: natural
-      - title: "Acceptable Style"
-        link: acceptable
-      - title: "Complete Translation"
-        link: complete
-      - title: "Self-Assessment Rubric"
-        link: self-assessment
-
-  - title: "Defining Church Authority"
-    sections:
       - title: "Checking Authority and Process"
         link: authority-process
-      - title: "Authority Level 1"
-        link: authority-level1
-      - title: "Authority Level 2"
-        link: authority-level2
-      - title: "Authority Level 3"
-        link: authority-level3
-  
-  - title: "Checking Process"
+  - title: "The Checking Process"
     sections:
-      - title: "Checking Level One - Affirmation by Translation Team"
-        link: level1
+      - title: "Oral Partner Check"
+        link: peer-check
+      - title: "Team Oral Chunk Check"
+        link: team-oral-chunk-check
+      - title: "translationWords Check in tC"
+        link: important-term-check
+      - title: "translationNotes Check in tC"
+        link: trans-note-check
+      - title: "Church Leader Check"
+        link: church-leader-check
         sections:
-          - title: "Level 1 Affirmation"
-            link: level1-affirm
-      - title: "Checking Level Two - Affirmation by Community"
-        link: level2
+          - title: "Checking the Translation for Accuracy"
+            link: accuracy-check
+      - title: "Language Community Check" 
         sections:
+          - title: "Checking the Translation for Clarity and Naturalness"
+            link: language-community-check  
+          - title: "Other Methods"
+            link: other-methods
+          - title: "Clear Translation"
+            link: clear
+          - title: "Natural Translation"
+            link: natural
+          - title: "Acceptable Style"
+            link: acceptable
           - title: "Language Community Evaluation Questions"
             link: community-evaluation
-          - title: "Level 2 Affirmation"
-            link: good
-      - title: "Checking Level Three - Affirmation by Church Leadership"
+      - title: "Affirmation of Accuracy and Community Acceptance"
+        link: good
+      - title: "Validation Checking"
         link: level3
         sections:
-          - title: "Questions for Checking on Level Three"
+          - title: "Steps for Validation Checking"
+            link: vol2-steps
+          - title: "Validating with the Alignment Tool in tC"
+            link: alignment-tool
+          - title: "Types of Things to Check"
+            link: vol2-things-to-check
+          - title: "Questions for Validation Checking"
             link: level3-questions
-          - title: "Level 3 Approval"
+          - title: "Validation Approval"
             link: level3-approval
-  
-  - title: "Introduction to Translation Checking - Part 2"
-    link: vol2-intro
-  - title: "Steps in Checking a Translation"
-    link: vol2-steps
+  - title: "Formatting and Publishing"
     sections:
-      - title: "Back Translation"
-        link: vol2-backtranslation
+      - title: "How to Check for Good Formatting"
+        link: formatting
+      - title: "Appropriate Alphabet"
+        link: alphabet
+      - title: "Consistent Spelling"
+        link: spelling
+      - title: "Consistent Punctuation"
+        link: punctuation
+      - title: "Complete Translation"
+        link: complete
+      - title: "Complete Versification"
+        link: verses
+      - title: "Section Headings"
+        link: headings  
+      - title: "Publishing"
+        link: publishing
+  - title: "Back Translation"
+    link: vol2-backtranslation
+    sections:
+      - title: "The Purpose of the Back Translation"
+        link: vol2-backtranslation-purpose
+      - title: "The Back Translator"
+        link: vol2-backtranslation-who
+      - title: "Kinds of Back Translations"
+        link: vol2-backtranslation-kinds
         sections:
-          - title: "The Purpose of the Back Translation"
-            link: vol2-backtranslation-purpose
-          - title: "The Back Translator"
-            link: vol2-backtranslation-who
-          - title: "Kinds of Back Translations"
-            link: vol2-backtranslation-kinds
           - title: "Kinds of Written Back Translations"
             link: vol2-backtranslation-written
           - title: "Guidelines for Creating a Good Back Translation"
             link: vol2-backtranslation-guidelines
-      - title: "Types of Things to Check"
-        link: vol2-things-to-check
-      - title: "How to Do a Formatting Check"
-        link: formatting
-        sections:
-          - title: "Appropriate Alphabet"
-            link: alphabet
-          - title: "Consistent Spelling"
-            link: spelling
-          - title: "Consistent Punctuation"
-            link: punctuation
-          - title: "Complete Versification"
-            link: verses
-          - title: "Section Headings"
-            link: headings
+  - title: "Self-Assessment Rubric"
+    link: self-assessment

checking/trans-note-check/01.md

@@ -0,0 +1,31 @@
+### How to do a TranslationNotes check in translationCore  
+
+1. Sign in to translationCore
+1. Select the project (book of the Bible) that you want to check
+1. Select the category or categories of Notes that you want to check
+1. Select your Gateway Language
+1. Click “Launch.” The verses to be checked will be listed on the left side, divided into different categories of Notes. 
+1. Select a verse to check, and read the Note for that verse that is in the blue bar. It is best to check all of the verses in the same category before moving to a new category.  
+
+Some Notes refer to a more general issue that applies to the specific verse being examined. To understand this more general issue and how it applies to the current verse, read the information in the panel on the right side.  
+
+1. After selecting (highlighting) the translation for the word or phrase in the Note, click “Save.”
+1. Consider whether or not the translation that was chosen for that word or phrase makes sense in this context. 
+1. Decide whether or not the translation is correct, considering the issue that the Note talks about.
+1. After considering these things, if you think that the translation is a good translation, then click “Save and Continue.” 
+1. If you think that there is a problem with the verse or that the translation for the word or phrase is not good, then either edit the verse to make it better, or make a comment telling someone who will review your work what you think might be wrong with the translation here.
+If you have made an edit, you may need to make your selection again.
+1. When you are finished making your edit or comment, click “Save and Continue.” If you prefer to only make a comment for the word or phrase and not make a selection for it, then click on the next verse in the list on the left to go on to the next verse.  
+
+After a selection has been made for all of the verses in a Note category, the list of translations in that category can be reviewed. The instructions that follow are for the reviewer or for the translation team.
+1. You will now be able to see a list of the translations that were made for each translationNote under each translationNote category on the left. Choose the category that you want to review. It may be that different members of the translation team will have different specialties. For example, one team member may be very good at reviewing metaphors, while another may be very good at understanding and correcting difficult grammar, such as passive voice constructions. 
+1. 	You will want to review any comments that were made by others. To do that, click the funnel symbol to the right of “Menu” at the upper left. A list will open, including the word “Comments.”
+1. 	Click the box next to “Comments.” This will make all verses that do not have comments in them disappear.
+1. 	To read the comments, click on the first verse in the list.
+1. 	Click on “Comment.”
+1. 	Read the comment, and decide what you will do about it.
+1. 	If you decide to make an edit to the verse, then click “Cancel” and then “Edit Verse.” This will open a small screen where you can edit the verse.
+1. 	When you are finished making the edit, select the reason for the change, and then click “Save.”
+1. 	Continue this process until you have acted on all of the comments that were left for you.  
+
+After you have finished reviewing a Note category or a Bible book, you may still have questions about some verses or Note checks. You may want to discuss a difficult verse with others on the translation team and try to find a solution together, study more Bible translation resources, or refer the question to a Bible translation expert. 

checking/trans-note-check/sub-title.md

@@ -0,0 +1 @@
+How do I do a Translation Notes Check?

checking/trans-note-check/title.md

@@ -0,0 +1 @@
+### Translation Notes Check

checking/verses/01.md

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

checking/vol2-backtranslation-guidelines/01.md

@@ -1,6 +1,8 @@
 
 ### 1. Show the Target Language Usage for Words and Clauses
 
+For the purposes of this module, "target language" refers to the language into which the Bible draft was made, and "language of wider communication" refers to the language into which the back translation is being made. 
+
 #### a. Use the meaning of the word in context
 
 If a word has only one basic meaning, then the back translator should use a word in the language of wider communication that represents that basic meaning throughout the back translation. If, however, a word in the target language has more than one meaning, so that the meaning changes depending on the context that it is in, then the back translator should use the word or phrase in the language of wider communication that best represents the way that the word was used in that context. In order to avoid confusion for the translation checker, the back translator can put the other meaning in parentheses the first time that he uses the word in a different way, so that the translation checker can see and understand that this word has more than one meaning. For example, he might write, “come (go)” if the target language word was translated as “go” earlier in the back translation but in the new context it is better translated as “come.”

checking/vol2-backtranslation-kinds/01.md

@@ -9,7 +9,7 @@ An advantage of the oral back translation is that the back translator is immedia
 
 #### Written
 
-There are two types of written back translations. The differences between the two will be discussed in the next module. A written back translation has several advantages over an oral back translation. First, when a back translation is written, the translation team can read it to see if there are any places where the back translator has misunderstood their translation. If the back translator misunderstood the translation, then other readers or hearers of the translation certainly will misunderstand it also, and so the translation team will need to revise their translation at those points.
+There are two types of written back translations. For the differences between the two, see [Written Back Translations](../vol2-backtranslation-written/01.md). A written back translation has several advantages over an oral back translation. First, when a back translation is written, the translation team can read it to see if there are any places where the back translator has misunderstood their translation. If the back translator misunderstood the translation, then other readers or hearers of the translation certainly will misunderstand it also, and so the translation team will need to revise their translation at those points.
 
 Second, when the back translation is written, the translation checker can read the back translation before meeting with the translation team and take time to research any question that arises from the back translation. Even when the translation checker does not need to research a problem, the written back translation allows him more time to think about the translation. He can identify and address more of the problems in the translation and sometimes come to better solutions to the problems because he has more time to think about each one than when he has only a few seconds to think about each sentence.
 

checking/vol2-backtranslation-purpose/01.md

@@ -1,7 +1,7 @@
 
 ### Why is a back translation necessary?
 
-The purpose of a back translation is to allow a consultant or checker of biblical material who does not understand the target language to be able to see what is in the target language translation, even though he or she does not understand the target language. Therefore, the language of the back translation needs to be a language that both the person doing the back translation (the back translator) and the checker understand well.  Often this means that the back translator will need to translate the target language text back into the same language of wider communication that was used for the source text.
+The purpose of a back translation is to allow a consultant or checker of biblical material who does not understand the target language to be able to see what is in the target language translation, even though he or she does not understand the target language. In this way, the checker can "look through" the back translation and check the target language translation without knowing the target language. Therefore, the language of the back translation needs to be a language that both the person doing the back translation (the back translator) and the checker understand well.  Often this means that the back translator will need to translate the target language text back into the same language of wider communication that was used for the source text.
 
 Some people might consider this to be unnecessary, since the biblical text already exists in the source language. But remember the purpose of the back translation: it is to allow the checker to see what is in the target language translation. Just reading the original source language text does not allow the checker to see what is in the target language translation. Therefore, the back translator must make a new translation back into the language of wider communication that is based only on the target language translation. For this reason, the back translator *cannot* look at the source language text when doing his back translation, but *only* at the target language text. In this way, the checker can identify any problems that might exist in the target language translation and work with the translator to fix those problems.
 

checking/vol2-backtranslation-who/01.md

@@ -3,7 +3,7 @@
 
 To do a good back translation, the person must have three qualifications.
 
-1. The person who makes the back translation should be someone who is a mother-tongue speaker of the local target language and who also speaks the language of wider communication well.
+1. The person who makes the back translation should be someone who is a mother-tongue speaker of the local target language and who also speaks the language of wider communication well. In order to make a written back translation, he must also be able to read and write both languages well.
 1. This person must also be someone who was not involved in making the local target language translation that he is back translating. The reason for this is that someone who made the local target language translation knows what he intended the translation to mean, and will put that meaning in the back translation with the result that it looks the same as the source translation. But it is possible that a speaker of the local target language who did not work on the local target language translation will understand the translation differently, or will not understand parts of it at all. The checker wants to know what these other meanings are that other speakers of the local target language will understand from the translation so that he can work with the translation team to make those places communicate the right meaning more clearly.
 1. The person who does the back translation should also be someone who does not know the Bible well. The reason for this is that the back translator must give only the meaning that he understands from looking at the target language translation, not from knowledge that he might have from reading the Bible in another language.
 

checking/vol2-backtranslation-written/01.md

@@ -7,4 +7,4 @@ An interlinear back translation is one in which the back translator puts a trans
 
 ### Free Back Translation
 
-A free back translation is one in which the back translator makes a translation in the language of wider communication in a separate space from the target language translation. The disadvantage of this method is that the back translation is not related as closely to the target language translation. The back translator can overcome this disadvantage when back translating the Bible, however, by including the verse numbers with the back translation. By referring to the verse numbers in both translations, the translation checker can keep track of which part of the back translation represents which part of the target language translation. The advantage of this method is that the back translation can use the grammar and word order of the language of wider communication, and so it is much easier for the translation checker to read and understand. Even while using the grammar and word order of the language of wider communication, however, the back translator should remember to translate the words in a literal way. We recommend that the back translator use the method of free back translation.
+A free back translation is one in which the back translator makes a translation in the language of wider communication in a separate space from the target language translation. The disadvantage of this method is that the back translation is not related as closely to the target language translation. The back translator can help to overcome this disadvantage when back translating the Bible, however, by including the verse numbers and punctuation with the back translation. By referring to the verse numbers in both translations and carefully reproducing the punctuation marks in their proper places, the translation checker can keep track of which part of the back translation represents which part of the target language translation. The advantage of this method is that the back translation can use the grammar and word order of the language of wider communication, and so it is much easier for the translation checker to read and understand. Even while using the grammar and word order of the language of wider communication, however, the back translator should remember to translate the words in a literal way. This provides the most beneficial combination of literalness and readability for the checker. We recommend that the back translator use this method of free back translation.

checking/vol2-backtranslation/01.md

@@ -1,6 +1,6 @@
 
 ### What is a back translation?
 
-A back translation is a translation of the biblical text from the local target language back into the language of wider communication. It is called a “back translation” because it is a translation in the opposite direction than what was done to create the local target language translation.
+A back translation is a translation of the biblical text from the local target language (the OL) back into the language of wider communication (the GL). It is called a “back translation” because it is a translation in the opposite direction than what was done to create the local target language translation. The purpose of a back translation is to allow someone who does not speak the target language to know what the target language translation says.
 
-A back translation is not done in a completely normal style, however, because it does not have naturalness as a goal in the language of the translation (in this case, the language of wider communication). Instead, its goal is to represent the words and expressions of the local language translation in a literal way, while also using the grammar and word order of the language of wider communication. In this way, the translation checker can most clearly see the meaning of the words in the target language text, and can also understand the back translation well and read it more quickly and easily.
+A back translation is not done in a completely normal style, however, because it does not have naturalness as a goal in the language of the translation (which is in this case, the language of wider communication). Instead, the goal of the back translation is to represent the words and expressions of the local language translation in a literal way, while also using the grammar and word order of the language of wider communication. In this way, the translation checker can most clearly see the meaning of the words in the target language text, and can also understand the back translation well and read it more quickly and easily.

checking/vol2-intro/01.md

@@ -1,16 +0,0 @@
-
-To do a Team Oral Chunk Check, each translator will read his translation out loud to the rest of the team. At the end of each chunk, the translator will stop so that the team can discuss that chunk. Ideally, each written translation is projected where all can see it while the translator reads the text orally.  
-
-The duties of the team members are divided - it is important that each team member only plays one of the following roles at a time. 
-* One or more team members listen for naturalness. If something is unnatural, at the end of reading the chunk, they recommend a more natural way to say it.
-* One or more team members follow along in the source text, noting anything that is added, missing, or changed. At the end of reading the chunk, they alert the team that something is added, missing, or changed.  
-* Another team member follows along in the report mode of translationCore, noting all of the highlighted key terms in the source text. The team then discusses any key terms in the translation that seem inconsistent or inappropriate, along with any other problems that surface in the reading. If this mode is not available, this team member can look up the key terms on the team's key term spreadsheet.  
-
-These steps can be repeated as necessary until the team is satisfied with their translation. 
-
-At this point, the translation is considered a first draft, and the team needs to also do the following. 
-
-* Someone on the translation team needs to enter the text into translationStudio. If the team has been using translationStudio from the beginning of drafting, then all that needs to be entered at this point are the changes that the team has made.
-* A new audio recording should be made of the translation, incorporating all of the changes and improvements that the team has made.
-* The translationStudio files and the audio recording should be uploaded to the team repository on Door43.
-

checking/vol2-intro/sub-title.md

@@ -1 +0,0 @@
-#### How do I do a Team Oral Chunk Check?

checking/vol2-intro/title.md

@@ -1 +0,0 @@
-### Team Oral Chunk Check

checking/vol2-steps/01.md

@@ -1,5 +1,7 @@
 
-### Steps in Checking a Translation
+### Steps for Validation Checking
+
+These are steps for the Church Network Delegates to follow when doing Validation Checking. These steps assume that the checker has direct access to the translator or translation team, and can ask questions face-to-face as the checker and the translation team review the translation together. If this is not possible, then the checker should write down the questions for the translation team to review. This could be in the margins of a printed translation draft, or in a spreadsheet, or, preferably, using the comment feature of translationCore.
 
 #### Before Checking
 
@@ -11,7 +13,8 @@
 
 #### While Checking
 
-1. **Ask Questions**. When you see something that you think might be a problem in the translation, do not make a statement to the translator that there is a problem in the translation. If you do not speak the target language, then you do not know if there is a problem or not. You only suspect that there could be a problem. Even if you do speak the target language, it is more polite to ask a question than to make a statement that something is wrong. You could ask something like, “What would you think about saying it this way?” and then suggest an alternative way to translate it. Then together you can discuss the different translation ideas, and you can give reasons why you think one translation alternative might be better than another. Then, after considering the alternatives, the translator or translation team must decide which way is best.
+1. **Align the passage**. Use the Aligning Tool in translationCore to align the passage with the original language. As a result of the aligning process, you will have questions about parts of the translation. Make note of these with the comment feature in translationCore so that you can ask the translation team about them when you meet, or so that the translation team can see and discuss them before you meet. For instructions about the alignment tool, go to [Alignment Tool](../alignment-tool/01.md). 
+1. **Ask Questions**. When you are with the translation team and you want to address something that you think might be a problem in the translation, do not make a statement to the translator that there is a problem in the translation. If you do not speak the target language, then you do not know if there is a problem or not. You only suspect that there could be a problem. Even if you do speak the target language, it is more polite to ask a question than to make a statement that something is wrong. You could ask something like, “What would you think about saying it this way?” and then suggest an alternative way to translate it. Then together you can discuss the different translation ideas, and you can give reasons why you think one translation alternative might be better than another. Then, after considering the alternatives, the translator or translation team must decide which way is best. For topics to ask questions about while checking a Bible translation, see [Types of Things to Check](../vol2-things-to-check/01.md). 
 1. **Explore the target language and culture**.  The questions that you ask will be to discover what the phrase means in the target language. The best questions are the ones that help the translator to think about what the phrase means and how it is used. Useful questions are, “In what situations is this phrase used in your language?” or “Who usually says things like this, and why do they say it?” It is also useful to help the translator to think about what a person from his village would say if in the same situation as the person in the Bible.
 1. **Teach the translator**. After you explore the meaning of a phrase in the target language and culture, you can tell the translator what the phrase means in the source language and culture. Then together you can decide if the phrase in the translation or the phrase he has just thought of has that same meaning or not.
 
@@ -21,11 +24,11 @@ If you speak the target language, then you can read or hear the translation and
 
 #### Using a Written Back Translation
 
-If you do not speak the target language, you will need to work from a back translation in a language that you do understand. This can be written separately from the translation, or it can be written as an interlinear, that is, with a line of back translation written under each line of the translation. It is easier to compare the translation to the back translation when they are written as an interlinear, and it is easier to read a back translation that is written separately. Each method has its own strength. The person who makes the back translation should be someone who was not involved in making the translation.
+If you do not speak the target language, then you will not be able to do the alignment. But you may be a Bible scholar who speaks the Gateway Language and you can help the translation team to improve their translation. In that case, you will need to work from a back translation in the Gateway Language. This can be written separately from the translation, or it can be written as an interlinear, that is, with a line of back translation written under each line of the translation. It is easier to compare the translation to the back translation when they are written as an interlinear, and it is easier to read a back translation that is written separately. Each method has its own strength. The person who makes the back translation should be someone who was not involved in making the translation. See [Back Translation](../vol2-backtranslation/01.md) for more details.
 
 1. If possible, review the back translation in written form before meeting with the translator or translation team face-to-face. This will give you time to think about the passage and to do further research on questions that arise because of what the back translation says. It will also save a lot of time when you meet with the translation team, because there will be a lot of text that you do not need to talk about because you read it in the back translation and it did not have problems. When you meet together, you will be much more productive because you can spend all of your time on the problem areas.
 1. As you work through the back translation, make notes of questions that you want to ask the translator, either for clarification or to help the translator think about possible problems with the translation.
-1. Ask the translator for a copy of the translation (if it is not interlinear), so that you can compare the translation with the back translation and make note of the connectors that the target language uses and other features that might not be visible in the back translation. Looking at the translation can also help to identify places where the back translation might not accurately represent the translation. For example, where the same words are used in the translation but they are different in the back translation. In this case, it is good to ask the translator why the back translation is different, and if it needs to be corrected.
+1. Ask the translator for a copy of the translation (if it is not interlinear), so that you can compare the translation with the back translation and make note of the connectors that the target language uses and other features that might not be visible in the back translation. Looking at the translation can also help to identify places where the back translation might not accurately represent the translation, for example, where the same words are used in the translation but they are different in the back translation. In this case, it is good to ask the translator why the back translation is different, and if it needs to be corrected.
 1. If you cannot review the back translation before meeting with the translator, then work through it with the translator, discussing questions and problems as you work together. Often, as the back translation is compared to the translation, the translator will also discover problems with the translation.
 
 #### Using an Oral Back Translation
@@ -41,4 +44,6 @@ Some questions will need to be set aside for later, after the checking session.
 
 ### Key Words
 
-Make sure that the translation team is keeping a list of the translationWords (important terms) from the Bible passages that they are translating, along with the term in the target language that they have decided to use for each of these important terms. You and the translation team will probably need to add to this list and modify the terms from the target language as you progress through the translation of the Bible. Use the list of translationWords to alert you when there are Key Words in the passage that you are translating. Whenever there is a Key Word in the Bible, make sure that the translation uses the term or phrase that has been chosen for that Key Word, and also make sure that it makes sense each time. If it does not make sense, then you will need to discuss why it makes sense in some places but not in others. Then you may need to modify or change the chosen term, or decide to use more than one term in the target language to fit different ways that the Key Word is used. One useful way to do this is to keep track of each important term on a spreadsheet, with columns for the source language term, the target language term, alternative terms and the Bible passages where you are using each term. We hope that this feature will be in future versions of translationStudio.
+Make sure that the translation team is keeping a [list of the Key Words](../../translate/translate-key-terms/01.md) (important terms, also known as translationWords) from the Bible passages that they are translating, along with the term in the target language that they have decided to use for each of these important terms. You and the translation team will probably need to add to this list and modify the terms from the target language as you progress through the translation of the Bible. Use the list of Key Words to alert you when there are Key Words in the passage that you are translating. Whenever there is a Key Word in the Bible, make sure that the translation uses the term or phrase that has been chosen for that Key Word, and also make sure that it makes sense each time. If it does not make sense, then you will need to discuss why it makes sense in some places but not in others. Then you may need to modify or change the chosen term, or decide to use more than one term in the target language to fit different ways that the Key Word is used. One useful way to do this is to keep track of each important term on a spreadsheet, with columns for the source language term, the target language term, alternative terms and the Bible passages where you are using each term. We hope that this feature will be in future versions of translationStudio.
+
+When you have finished Validation Checking for a Bible book, answer the questions at: [Questions for Validation Checking](../level3-questions/01.md).

checking/vol2-steps/sub-title.md

@@ -1 +1 @@
-What are the steps I should follow to check someone else’s translation?
+What are the steps I should follow to check a translation at the Validation stage?

checking/vol2-steps/title.md

@@ -1 +1 @@
-Steps in Checking a Translation
+Steps for Validation Checking

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

@@ -10,7 +10,7 @@
 
 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 for the consistency of the translationWords, as explained in the last section of [Steps for Validation Checking](../vol2-steps/01.md). 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.

translate/first-draft/01.md

@@ -1,12 +1,25 @@
 
 ### How do I start?
 
-* Pray that God would help you to understand the passage that you are translating and that he would help you to find the best way to communicate that passage in your language.
-* If you are translating Open Bible Stories, read the entire story before starting to translate it. If you are translating the Bible, read the entire chapter before you start to translate any part of it. This way you will understand how the part you are translating fits into the larger context, and you will translate it better.
-* Read the passage that you plan to translate in as many different translations as you have. If you are using translationStudio, it contains at least two Bible texts, the unfoldingWord Literal Text (ULT) and the unfoldingWord Simplified Text (UST). The ULT will help you to see the form of the original text, and the UST will help you to understand the meaning of the original text. Think about how to communicate the meaning in the form that people would use in your language. 
-* Read any Bible helps or commentaries that you have that talk about that passage.
-* Read the translationNotes for the passage that you plan to translate.
-* Read the definitions of important terms in the list called “translationWords” for each highlighted word in the passage that you plan to translate.
-* Discuss the passage, the translationNotes, and the translationWords with others in the translation team.
-* When you understand well what the passage is saying, say it out loud in your language in the way that someone from your language community would say it. If possible, say it to another member of the translation team. Let the translation team member correct it until it sounds good in your language. Do not follow the order of words from the source text if it is more natural for your language to use a different order. To help with this, say the whole passage (the chunk of text) without looking at the source text. This will help you to say these things in a way that is natural for your language, rather than in a way that was natural for the source language but that is not the best way to say it in your language. Then type it into translationStudio (or record it).  
+Follow these steps in order to get started:
 
+1. **Organize.** Talk with the pastors and other believers from your language group and form a committee of people who can work together as a translation team. 
+1. **Contact.**  Make contact with at least one element of the unfoldingWord network, notifying unfoldingWord that you intend to begin translation. To get information about how to do that, see [Finding Answers](../../intro/finding-answers/01.md)
+1. **Review.**  Review the [Translation Guidelines](../../intro/translation-guidelines/01.md).
+1. **Agree.**  Agree that the Statement of Faith is an accurate reflection of your own beliefs and that you intend to translate the content in harmony with it and also in accordance with the Translation Guidelines by signing the form. (see http://ufw.io/forms/)
+1. **Pray.** Pray that God would help you to understand the passage that you are translating and that he would help you to find the best way to communicate that passage in your language.
+1. **Read.** 
+  * If you are translating Open Bible Stories, read the entire story before starting to translate it. If you are translating the Bible, read the entire chapter before you start to translate any part of it. This way you will understand how the part you are translating fits into the larger context, and you will translate it better.
+  * Read the passage that you plan to translate in as many different translations as you have. If you are using translationStudio, it contains at least two Bible texts, the unfoldingWord Literal Text (ULT) and the unfoldingWord Simplified Text (UST). The ULT will help you to see the form of the original text, and the UST will help you to understand the meaning of the original text. Think about how to communicate the meaning in the form that people would use in your language. 
+  * Read any Bible helps or commentaries that you have that talk about that passage.
+  * Read the translationNotes for the passage that you plan to translate.
+  * Read the definitions of important terms in the list called “translationWords” for each highlighted word in the passage that you plan to translate.
+1. **Talk.** Discuss the passage, the translationNotes, and the translationWords with others in the translation team. Help each other to understand what they mean. If there are parts that you still do not understand, ask pastors or other church leaders for help.
+2. **Translate.** When you understand well what the passage is saying, say the first chunk (1-3 verses) out loud in your language in the way that someone from your language community would say it. If possible, say it to another member of the translation team. Let the translation team member correct it until it sounds good in your language. Do not follow the order of words from the source text if it is more natural for your language to use a different order. To help with this, say the whole chunk of text without looking at the source text. This will help you to say these things in a way that is natural for your language, rather than in a way that was natural for the source language but that is not the best way to say it in your language. Still without looking at the source text, type your translation of the chunk into translationStudio (or record it). When you type (or write) from your memory without looking at the source text, your translation will be more natural. 
+1. **Check**. Since you typed or recorded your translation of a chunk without looking at the source text, you might have left out a few things. Now is the time to add those things to your translation.  
+  * Look again at the source text and carefully compare it to your translation. Make sure that it says all of the parts of the message of the source text and does not leave out anything. If some part of the message was missing, put it in your translation at the point where it fits best in your language. It does not need to be in the same order as the source as long as it sounds natural and gives the same meaning. 
+  * If you are translating the Bible, 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 revise your translation in that way. If one of those helps you to understand something better than you did before, then change your translation so that it communicates the meaning better.
+  * 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. Sometimes parts of sentences need to be put in a different order.  
+
+Now translate the next chunk of the passage in the same way (step 8) and check it in the same way (step 9). When you finish the passage or chapter, it is ready for the [Oral Partner Check](../../checking/peer-check/01.md). To translate the next passage or chapter, start again at step 5.
+ 

translate/translate-key-terms/01.md

@@ -0,0 +1,6 @@
+Making a Key Terms Spreadsheet
+
+* 	Make a list of the translationWords in the story or Bible passage that you translate, along with the term that you choose for it in the target language. It is best if you can do this on a spreadsheet 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. Make sure that everyone translating Bible books that use these terms has access to the spreadsheet, or a chart on paper, so that you can all use the same words or phrases in your translation.
+* 	Use the list of words and definitions in the translationWords section of Door43 or translationStudio to help you to make a list of these words and to understand what they mean. translationStudio will show you these words and their definitions as you encounter them in the source text, and the translationWords tool in translationCore will give you a list of all of the key terms in each book of the Bible.
+* 	Each time the translationWord 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 translationWord 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 translationWord in different contexts, then make a new line on the spreadsheet for each different way that you are translating the source translationWord. Repeat the source term in the source column, and put the new translation in the next column, under the first translation. Share this spreadsheet with everyone on the translation team so that they can choose the right translation for the source translationWord in the context that they are translating.

translate/translate-key-terms/sub-title.md

@@ -0,0 +1 @@
+How do I make a key terms spreadsheet?

translate/translate-key-terms/title.md

@@ -0,0 +1 @@
+Making a Key Terms Spreadsheet