susanquigley-Quality_Assurance (#54)

Update 'checking/re-intro/title.md'

Refinement and Revision

Church Review - typo

51 Church Leadership Review

Church Review

Church Review - fixed link

51 Church Leadership Review

Discussion in Google Docs

fixed typo

fixed typo

49 Affirmation Level1 (Team Check)

Added the part about affirmation to Team Check page

47 Church Affirmation

48 Level One Checking

Forgot to delete a paragraph earlier.

47 Church Affirmation

Issue 46 QA - added "every person is a part"

Update 'intro/guidelines-collaborative/01.md'

53 Quality Assurance section: brief explanation

COBT - Removed "Training" from title

Manual Intro: Changed "Checking" to "Quality Assurance"

Collaborative - Removed "test" and "level"

Update 'checking/chk-team-check/01.md'

Things I missed in Issue 48 Level One Checking

Updating Quality Assurance Table of Contents

Adding Church Leadership Review

Adding Introduction to Refinement and Revision

Adding Introduction to Refinement and Revision

Archiving Affirmation Level Three

Archiving Affirmation Level Three

Archiving Affirmation Level Three

Archiving Affirmation Level Two

Archiving Affirmation Level Two

Archiving Affirmation Level Two

Archiving Affirmation Level One

Archiving Affirmation Level One

Archiving Affirmation Level One

Issue 47 Church Affirmation

Combined paragraphs 2 and 3 into one.

48 Level One Checking

Changed "level one check" to "team check"

47 Church Affirmation: Delete Levels

Archiving The Checking Levels

Archiving The Checking Levels

Archiving Level One Check

Archiving Level One Check

Update 'archive/checking/level1/title.md'

Archiving Level One Check

Adding Translation Team Check

Adding Translation Team Check

Add 'checking/chk-team-check/01.md'

This is from en_tm/checking/level1/01.md.
I will adapt it to be an intro to the translation team check.

44 Translation Questions - added a point

Update 'checking/re-community-review/01.md'

Community Review: Add link to "Comm Review Methods"

45 Community Review

44 Translation Questions

Changed wording to distinguish use for self-check and community review.

Reviewed-on: WycliffeAssociates/en_tm#54

archive/checking/level1/title.md

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

archive/checking/level2/title.md

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

archive/checking/level3/title.md

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

checking/chk-consistency/01.md

@@ -1,20 +1,19 @@
-In order for readers to be able to understand the translation easily, it is important that there be consistency in the following things: spelling, punctuation, and formatting. 
+In order for readers to be able to understand the translation easily, it is important that there be consistency in the following things: important words, spelling, punctuation, and formatting. Checking a translation for consistency is something that is done continually. First it is part of Steps 5-8 of MAST; a MAST facilitator may develop a specific strategy for a project to help maintain consistency for important words, spelling, punctuation, and formatting.
+
+Consistency checking is also part of the proofreading near the end of the refinement and revision processes. This is because during these processes it is very easy to find and resolve inconsistencies.
 
 #### Important Words
 
 Check the important words throughout the whole translation to see that you have translated them in a consistent way. This does not mean that they must always be translated the same way, but that each sense of the word is translated in the same way. (See [Key Word Check](../checking/key-word-check/01.md))
 
-
 #### Spelling
 
 It will be good to have a consistent way of spelling all the words in your language. But in your checks, you may want to focus on checking the spelling of key terms, words you have borrowed from another language, and the names of people and places. (See: [Consistent Spelling](../translate/presentation-spelling/01.md))
 
-
 #### Punctuation 
 
 Check to see what decisions your team has made concerning punctuation, and make sure that it is used in a consistent way throughout your Bible. (See [Consistent Punctuation](../translate/presentation-punctuation/01.md))
 
-
 #### Formatting  
 
 Translators can use formatting to help readers understand how a text is organized. (See: [Formatting](../translate/presentation-formatting/01.md))

checking/chk-key-words/01.md

@@ -0,0 +1,40 @@
+
+
+
+### Making a key word chart for your language
+
+1. When you are ready for MAST step 7, work with a translation partner. Together read the source text of the passage you have translated and write a list of any words in the passage that  you think are key words. Key words are 
+    * words that have some moral, spiritual, theological, or religious meaning
+    * names of people and places
+    * words specific to the historical environment
+    * words that connect one thought to another
+    * words that show the author's attitude or beliefs.
+2. Discuss the words on your list. Use the Translation Notes and Translation Words to ensure that  you understand the meanings of each word. (Some words have more than one meaning.) Make an initial decision on how to translate each meaning of the source language word. Write your decisions next to each word. Sometimes there  is no word in the target language that means the same as the source language words. When that is the situation, you may choose to do one of the following:
+    * Choose the common use word from the local Christian community. 
+    * Choose a word with an added descriptor. 
+    * Create a phrase or combine a few words into one.
+    * Borrow the word from the Gateway Language and adjust the spelling to fit your script and pronunciation.
+3. As a team, discuss all of your lists, and list in alphabetical order all of the source language words that you decide are key words. 
+    * If possible, do this on a computer so you can easily insert new words in alphabetical order.
+    * Put this list in the first column of a chart. 
+    * In the next column, write next to each source language word your translation of the word.
+   * Some words have more than one meaning or have to be translated differently in different contexts. If you need more than one way to translate a key word, make a new line on the chart for each way of translating it. Repeat the source term in the source column, and put the new translation in the next column, under the first translation.  
+   * You may also want to use another column to write where in the book the word first occurs.
+   * Be careful not to include too many words. If the list is too detailed, checking becomes tedious. Additionally, checking every (or almost every word) can push the translated material away from a natural flow in the target language.
+4. Make sure that everyone on the translation team has access to the chart so that you can all use the same words or phrases in your translation.
+5. As you translate other chapters and books of the Bible you will find more key words. 
+5. Meet occasionally as a team to discuss changes to the chart: key words that need to be added, translations that need to be corrected, and key words that need more than one translation.
+6. Make sure that everyone on the translation team has access to the newest chart.
+
+### Checking the key words in a chapter
+
+1. Work with another translation partner to compare your translation to the source text and your key words chart. 
+2. Compare each verse of the source text to your key words chart.
+    * What key words from your chart are in the source text?
+    * Does the verse have any key words that should be on your key word chart?
+    * Use the Translation Notes and Translation Words to ensure that you understand the meanings of each new key word.
+    * Add the new key words to your chart. 
+3. Read each verse in your translation to see how the key words are translated.
+4. If a key word is translated in the text differently than it is in the chart, discuss this with your translation partner. You will need to either change the translation in the verse to match what is in the chart or add to the chart another way of translating the key word.
+4. If the translation of a key word does not seem to have the right meaning, or if it does not seem to make sense in the context, discuss it with your translation partner to come up with a solution.
+5. Meet with the rest of team to discuss words that need to be added to the chart and words that need either correction or additional translations.

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

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

checking/chk-peer-edit/01.md

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

checking/chk-self-edit/01.md

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

checking/chk-team-check/01.md

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

checking/chk-team-check/sub-title.md

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

checking/chk-team-check/title.md

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

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

@@ -0,0 +1,12 @@
+This step requires at least three people—the translator of the passage and two partners from the translation team—one partner who can translate the mother tongue to the source language and one partner who can compare what the first partner says with the source text.
+
+The translator will read their translation one verse at a time, out loud, in the mother tongue. Without using any resources, one partner will listen to the mother tongue translation and verbally translate the verse into the source language. The second partner will listen to the first partner’s verbal back-translation and compare it to the source text. 
+
+The wording will not be exactly the same between the source text and the back-translation, but it is important that:  
+(1) the meaning in the translation is the same as the meaning in the source text   
+(2) all of the events and important details found in the source text are present in the translation and  
+(3) no new or extra information has been added. 
+
+If it appears that the meaning in the translation is not the same as the meaning in the source text, the partner who compares the two will tell the translator. The three people will then discuss the verse to see if there really is a difference in meaning.
+
+If there really is a difference in meaning, or if all of the events and important details are not present, the text should be edited. The team should consult the source text, Translation Notes, Translation Words, and other translations or other resources to help them make corrections and improve the translation. 

checking/chk-verses/01.md

@@ -1,5 +1,7 @@
 
-It is important that your target language translation include all of the verses that are there in the source language Bible. We do not want some verses to be missing by mistake. But remember that there can be good reasons why some Bibles have certain verses that other Bibles do not have.
+It is important that your target language translation include all of the verses that are in the source language Bible. We do not want some verses to be missing by mistake. But remember that there can be good reasons why some Bibles have certain verses that other Bibles do not have.
+
+Versification checking takes place during step 8 of MAST, the verse-by-verse check. It is also part of the proofreading near the end of the refinement and revision processes. This is because during these processes it is very easy to find and resolve errors in the versification.
 
 ### Reasons for Missing Verses
 
@@ -7,10 +9,10 @@ It is important that your target language translation include all of the verses
 1. **Different Numbering** - Some Bibles use a different system of verse numbering than other Bibles. (For more information about this, see [Chapter and Verse Numbers](../../translate/translate-chapverse/01.md).) Your translation team will need to decide which system to use.
 1. **Verse Bridges** - In some translations of the Bible, the contents of two or more verses are rearranged so that the order of information is more logical or easier to understand. When that happens, the verse numbers are combined, such as 4-5 or 4-6. The UDB does this sometimes, and on rare occasions, also the ULB. Because not all of the verse numbers appear or they do not appear where you expect them to be, it might look like some verses are missing. But the contents of those verses are there. (For more information about this, see [Verse Bridges](../../translate/translate-versebridge/01.md).) Your translation team will need to decide whether to use verse bridges or not.
 
-### Checking for Missing Verses
+### Checking for Missing Verse Numbers or Content
 
 * Look at the source text and your translation, and check the verse numbers to see that every verse in each chapter of the source text is also your translation.
-*  If any verse is missing, find out if it is missing on purpose because of one of the three reasons above, or if it is missing by mistake.
-*  If a verse is missing by mistake, check to see if it is missing because of a formatting  error or if you need to go back and translate that verse.
+*  If the number or content of any verse is missing, find out if it is missing on purpose because of one of the three reasons above, or if it is missing by mistake.
+*  If the number or content of any verse is missing by mistake, check to see if it is missing because of a formatting  error or if you need to go back and translate that verse.
 * Make the correction.
 

checking/key-word-check/01.md

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

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

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

checking/level1/title.md

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

checking/level2/title.md

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

checking/level3/title.md

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

checking/other-methods/01.md

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

checking/other-methods/sub-title.md

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

checking/other-methods/title.md

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

checking/qa-authority/01.md

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

checking/qa-authority/title.md

@@ -0,0 +1 @@
+The Church's Authority to Assess Quality

checking/qa-need/01.md

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

checking/qa-need/sub-title.md

@@ -0,0 +1 @@
+What is quality assurance for?

checking/qa-need/title.md

@@ -0,0 +1 @@
+The Need for Quality Assurance

checking/qa-rubric/01.md

@@ -0,0 +1,167 @@
+
+It is important for a language community to design its own rubric. When a language community establishes its own standards, it fosters ownership of a project. 
+
+During the first few days of a MAST workshop, the facilitator guides a translation team through the process of developing rubric for assessing the quality of their translation. Below are the steps used to create a rubric to guide quality assurance throughout the project. 
+
+1. The translation team will choose a leader/representative of their language group to manage the rubric building process. If this leader/representative does not speak a language that the facilitator understands, the team will choose someone to translate the rubric for the facilitator.
+
+2. The individuals on the team will independently answer the following questions: 
+
+    * What is a good translation?   
+    * What are at least ten qualities of a good translation? 
+
+3. The translation team will then work together to make one list that includes all the items from each individual’s list. The leader/representative will combine the qualities that are the same and develop one master list of at least 10 qualities. 
+
+4.	If the facilitator or anyone else at the event is familiar with Bible translation rubrics, he may review the team's rubric. If he sees that something important is missing in their rubric, he may ask questions of the group to help them to recognize other qualities that would be beneficial for their translation to have. 
+
+    If there is no one at the event who is familiar with Bible translation rubrics, the team can compare their rubric with sample rubrics. Some examples can be found at v-raft.com. The following are questions that may help them decide whether or not to make any changes to their rubric:
+
+    * Are there qualities in any of those rubrics that you would like to add to your own? 
+    * Are there any qualities in your own that you now think may not be very important?  
+
+5.	The team will have a discussion and agree on the qualities to include in their rubric. There should be about 10 qualities.
+
+6.	The team will verbally define each of the qualities established in the rubric and then record the definitions. Each definition should be clear enough that anyone from that language group could use the rubric and understand the qualities the team wants their translation to have.
+
+7. The team will create a list of things the translation needs in order for it to have each of those characteristics. 
+
+8. The team will make each item in this list into a question with a yes or no response.
+
+9. The team should make sure that the rubric is clear enough that if a person who speaks the language were to later check a translated chapter, they could pick up that chapter, take the rubric and the source text, and determine whether the standards established in the rubric were met.
+ 
+10.	Finally, now is a good time for the team to discuss the following:  
+ 
+    * After the translation project is completed, how would you answer someone who asks, "Is this translation of good quality?"  They should realize that if all of these standards established in the rubric are met, then the translation they have been working on will be a good quality translation.
+
+11.	When possible, the team will translate the rubric into English and share it at [v-raft.com](https://v-raft.com).
+
+
+### Example of Creating a Rubric
+Below you will see an example of how a rubric was created by following steps 2-8 above. (Steps involving individual work or discussion are not shown.)
+
+#### Step 3: The group's combined list of characteristics
+
+  * Accurate  
+  * Community Oriented  
+  * Clear  
+  * Grammatically consistent  
+  * Natural  
+  * Faithful to Original Languages  
+  * Authoritative  
+  * Historical  
+  * Equal  
+  * Acceptable  
+  * Trustworthy  
+  * Has Appropriate Familial Terms for God the Father and his Son
+  * Culturally Relevant
+  * Uses traditional words rather than the ones kids use
+  * Theologically accurate
+  * Uses a certain name for God
+  * Is easy for non-believers to understand
+  * Is easy for children to understand
+  * Does not create too many new words 
+  * Does not use too many words from the gateway language
+  * Can be used by pastors to build up the church
+
+
+#### Step 4: Condense the characteristics and settle on around 10 characteristics. 
+
+  * Accurate
+  * Style
+  * Clear
+  * Natural
+  * Faithful
+  * Authoritative
+  * Historical
+
+Notice that in condensing the qualities, some of the items on the list are combined so there are no longer 10 separate qualities. Also after discussion, the team decided not to include some qualities, because they pertained to community acceptance and not the quality of the translation itself or because they were qualities for a type of Bible the team did not want to produce. 
+
+#### Step 6: Define the characteristics
+
+  * Accurate - The translation says the same thing as the source text.
+  * Style - The translation uses the same style as the source text.
+  * Clear - People can understand what the translation says.
+  * Natural - The translation sounds like the way we speak.
+  * Faithful - The translation does not unnecessarily favor one opinion over another.
+  * Authoritative - The translation can be recognized to be from God.
+  * Historical - The translation does not make people think it is about people in my culture.
+
+#### Step 7: List what the translation needs in order for it to have each of the characteristics.
+
+**Accurate**   
+
+1. Key words are translated accurately  
+2. Nothing is added or missing from the text  
+3. The text reflects the author's intended meaning  
+
+**Style**   
+1. The text uses the same style of writing as the source text. For example, poems in the source text are poems in the translated text. Accounts of historical events are translated as historical events.
+2. In prophecy, images are not explained for the reader unless the original author explained it.  
+
+**Clear**  
+1. The text is understood by a wide range of audiences.  
+2. The text uses common language.  
+3. The text uses proper language structures (word order, tenses, sentence structure)  
+4. The punctuation is correct.
+
+**Natural**  
+1. The text sounds like how we speak. It uses common language  
+2. The text sounds beautiful.
+3. The text is efficient and effective in its communication
+
+**Faithful**  
+1. The text does not favor a particular denomination’s understanding of scripture. 
+2. The text does not favor one person’s or group of people’s opinion over another.
+3. The text does not promote false doctrine.
+4. The text uses proper familial terms for God the Father and his Son.
+
+**Authoritative**  
+1. The translation is based on a good source text.  
+2. The text does not use language that people think is beneath God. 
+3. The text does not use language that is too informal.
+
+**Historical**  
+1. The translation does not appear to take place in my community.
+2. The names of people and places are not replaced with names of people and places in my community. 
+3. The translation describes historical events the way the source text describes them. 
+
+
+#### Step 8. Make each item in this list into a question with a yes or no response.
+
+**Accurate**  
+1. Are the key words translated accurately?  
+2. Is nothing added or missing from the text?  
+3. Does the text reflect the author's intended meaning?  
+
+**Style**   
+1. Does the text use the same style of writing as the source text?
+2. In prophecy, does the text avoid explaining images for the reader unless the original author explained it?
+
+**Clear**  
+1. Can a wide range of audiences understand the text?  
+2. Does the text use common language?
+3. Does the text use proper language structures (word order, tenses, sentence structure)?
+4. Is the punctuation correct?
+    
+**Natural**  
+1. Does the text sound the same way people speak when using common language?  
+2. Does the text sound beautiful?
+3. Is the text efficient and effective in its communication?
+    
+**Faithful**  
+1. Does the text avoid favoring a particular denomination’s understanding of scripture. 
+2. Does the text avoid favoring one person’s or group of people’s opinion over another.
+3. Does the text avoid promoting false doctrine.
+4. Does the text use proper familial terms for God the Father and his Son?
+    
+**Authoritative**  
+1. Is the translation based on a good source text?  
+2. Does the text avoid using language that people think is beneath God? 
+3. Does the text avoid using language that is too informal?
+    
+**Historical**  
+1. Does the translation avoid appearing to take place in my community?
+2. Does the translation avoid replacing names of people and places with names of people and places in my community?
+3. Does the  translation describe historical events the way the source text describes them?
+
+The questions are designed as yes/no questions. If the answer is “no” to any portion of the scripture (that is, any word, phrase, sentence, paragraph, chapter, or book), then that  portion needs to be reviewed and edited.

checking/qa-rubric/sub-title.md

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

checking/qa-rubric/title.md

@@ -0,0 +1 @@
+Designing a Rubric for Bible  Translation Quality

checking/qa-standards/01.md

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

checking/qa-standards/sub-title.md

@@ -0,0 +1 @@
+Why do we need to establish standards for our translation?

checking/qa-standards/title.md

@@ -0,0 +1 @@
+The Need for Establishing Standards

checking/re-church-review/01.md

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

checking/re-church-review/title.md

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

checking/re-community-review/01.md

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

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

@@ -0,0 +1 @@
+What is a community review?

checking/re-community-review/title.md

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

checking/re-intro/title.md

@@ -0,0 +1 @@
+Refinement and Revision

checking/re-refine-revise/01.md

@@ -0,0 +1,14 @@
+
+Refinement and revision are key aspects of making a quality translation. A translation ideally needs to be reviewed by a language community and their church leaders in order to provide feedback for the translation team to improve their translation. 
+
+### Refinement
+
+Refinement is the process of improving a translation before a translation project is complete. Refinement provides an open invitation (implied or direct) to members of the language community to suggest improvements to the translation. The translation team is encouraged to print or otherwise publish their translation so that it can be immediately useful. This allows the community and church leaders to review their work and provide feedback.
+
+In the refinement process, the community and church leadership use the rubric created by the translation team in order to assess the quality of the translation. If they find that any part of the translation lacks a particular characteristic, they let the translation team know. Then the translation team can adjust to translation so that it will have that characteristic. 
+
+### Revision
+
+Revision is the process of improving a translation after a translation project has been completed. Revision provides an opportunity for members of the language community to improve a translation whenever they determine there is sufficient need for a revision. There are a variety of needs for a translation to be revised, but this is a natural part of Church-owned Bible Translation emphasis on releasing early, revising often. 
+
+One marked difference between refinement and revision is that refinement always uses the rubric established by the translation team, while a revision often establishes a new rubric for assessing the quality of their work that is different from previously used rubrics. It is possible to adapt an old rubric to when creating a new rubric. Other times, an old rubric can be reused if the language community has determined that the standards established in the previous rubric were not met. 

checking/re-review-methods/01.md

@@ -0,0 +1,23 @@
+
+### Question and Answer Method
+
+One method for getting feedback about the translation is to use the Translation Questions or the Reviewers Guide  to find out how well people understand the scripture passage. If people have trouble answering a question, that may be an indication that something in the scripture has not been translated accurately, clearly or naturally. 
+
+The translator or leader will read (if it is a written translation) a portion of the translation to the gathered listeners. Before reading, he should tell the people listening to stop him if they hear something that does not sound accurate, clear, or natural. In this situation, it is often easiest for the reviewer to notice if a translation is not natural. Alternatively, if the people are literate, each one in the group can be asked to read a passage of the newly translated material. It is best, even if everyone in the group is literate, to have the portions read out loud to the whole group. Portions should not be too long (the length read is subject to the abilities of the group and the type of passage). It is also very important for  listeners to understand that they are now a part of the team helping to improve the quality of the scripture. They themselves are not being tested. Rather the questions are designed to help them provide feedback on the meaningfulness of the new translation. 
+
+After a portion is read aloud, a translator will read a question and wait for the listeners to answer. Their answers will help the translator know if anything in the passage needs to be worded differently to make it more  clear.
+
+### Other Checking Methods
+
+As well as asking questions, there are other checking methods that you may also use to ensure that the translation is easy to read and sounds natural to the listeners. Here are some other methods that you may like to try:
+
+* **Retell Method**: The translator reads a few verses and asks someone else to retell what was said. The translator compares what the person says to the text. This helps to check the clarity and naturalness of the translation and offers alternate ways of saying the same thing.
+
+* **Reading Method**: Someone from the community reads a portion of the translation aloud while the translator takes notes where the pauses and mistakes occur. This will show how easy or how difficult it is to read and understand the translation. Afterward the translator looks at the places in the translation where the reader paused or made mistakes and considers what part of the translation was difficult. The translators may need to adjust the translation at those points so that it is easier to read and understand.
+
+* **Offer Alternate translations**: In passages where the translators are not sure of the best way to express a word or phrase, they may ask other people for an alternative translation or offer a choice between two translations and see which translation people think is the most clear.
+
+* **Reviewer Input**: The translators ask others whom they respect to read the translation and to take notes and tell where it might be improved. These reviewers might give better word choices, more natural expressions, and even spelling adjustments.
+
+* **Discussion Groups**: The translators asks someone to read the translation to a group of people. The translators encourages the reader and the others to ask questions for clarification. The translator pays attention to the words people use, since alternate words and expressions come up when someone is trying to make sense of a difficult point; these alternate words and expressions might be better than the ones in the translation. The translator pays attention to the places where people do not understand the translation, and then works to make those places clearer.
+

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

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

checking/re-review-methods/title.md

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

checking/toc.yaml

@@ -1,48 +1,42 @@
-title: "Table of Contents"
+title: "Quality Assurance"
 sections:
-  - title: "Introduction to Checking"
+  - title: "Introduction to Quality Assurance"
     sections:
-      - title: "The Need for Translation Checking"
-        link: intro-checking
-      - title: "Authentic Assessment in Checking Scripture"
-        link: intro-check
-      - title: Designing a Rubric for Bible Translation Quality
-        link: authentic-assessment
-      - title: "Checking Levels"
-        link: intro-levels
-  - title: "Church Authority to Check Translation"
-    sections:
-      - title: "Church Authority and Checking"
-        link: authority-process
-      - title: "Affirmation Level One"
-        link: authority-level1
-      - title: "Affirmation Level Two"
-        link: authority-level2
-      - title: "Affirmation Level Three"
-        link: authority-level3  
-  - title: "Checking Process"
-    sections:
-      - title: "Level One Check - Translation Team"
-        link: level1
-      - title: "Level Two Check - Community"
-        link: level2
-      - title: "Level Three Check - Church Leadership"
-        link: level3
-  - title: "Types of Checks"
+      - title: "The Need for Quality Assurance"
+        link: qa-need
+      - title: "The Need for Establishing Standards"
+        link: qa-standards
+      - title: "Designing a Rubric for Bible Translation Quality"
+        link: qa-rubric
+      - title: "The Church's Authority to Assess Quality"
+        link: qa-authority
+  - title: " Checking a Translation"
     sections:
+      - title: "Translation Team Check "
+        link: chk-team-intro
       - title: "Self-Edit"
-        link: self-edit
+        link: chk-self-edit
       - title: "Peer-Edit"
-        link: peer-edit
+        link: chk-peer-edit
       - title: "Key Word Check"
-        link: key-word-check
+        link: chk-key-words
       - title: "Verse-by-Verse Check"
-        link: verse-by-verse
-      - title: "Other Methods"
-        link: other-methods
-  - title: "Detail Checks"
+        link: chk-verse-by-verse
+      - title: "Detail Checks"
+        sections:
+          - title: "Complete Versification"
+            link: chk-verses
+          - title: "Consistency Checks"
+            link: chk-consistency
+  - title: "Refinement and Revision"
     sections:
-      - title: "Complete Versification"
-        link: verses
-      - title: "Consistency Checks"
-        link: consistency-check
+      - title: "Introduction to Refinement and Revision"
+        link: re-intro
+      - title: "Community Review"
+        link: re-community-review
+      - title: "Community Review Methods"
+        link: re-review-methods
+      - title: "Church Leadership Review"
+        link: re-church-review
+
+

checking/verse-by-verse/01.md

@@ -1,10 +0,0 @@
-This step requires at least three people—the translator of the passage and two partners from the translation team—One partner who can translate the mother tongue to the source language and the second with appropriate competence in the source language.
-
-The translator will read their translation one verse at a time, out loud, in the mother tongue. Without using any resources, one partner will listen to the mother tongue translation and verbally translate the mother tongue to the source language. A second partner will listen to the first partner’s verbal back-translation and compare it to the source text. The two partners will suggest edits where appropriate.
-
-The wording will not be exactly the same between the source text and the back-translation, but it is important that:  
-(1) the meaning in the translation is the same as the meaning in the source text   
-(2) all of the events and important details found in the source text are present in the translation and  
-(3) no new or extra information has been added. 
-
-If the meaning is not the same, or if all of the events and important details are not present, the text should be edited. The team should consult the source text, Translation Notes, Translation Words, and other translations or other resourses to help them make corrections and improve the translation. 

intro/guidelines-church-approved/01.md

@@ -1,18 +1,7 @@
-The goal of the translation of biblical content is to produce a high-quality translation that is used and loved by the church. High-quality translations must be accurate, clear, and natural (see [Qualities of a Good Translation](../translate/guidelines-intro/01.md)). But for a translation to be used and loved by the church, it must be church-affirmed.
+The goal of the translation of biblical content is to produce a high-quality translation that is used and loved by the church. High-quality translations are accurate, clear, and natural (see [Qualities of a Good Translation](../translate/guidelines-intro/01.md)). But for a translation to be used and loved by the church, it must be church-affirmed. This means that the local church recognizes it to be the Word of God and desires to use it.
 
-Creating a church-affirmed translation is all about the process of translation, checking, and distribution. The more church networks that are involved in these processes, the more likely they will affirm the translation.
-
-As many church networks as possible should be contacted and encouraged to become a part of the translation and even to send some of their people to be a part of the translation team. They should be consulted and asked for their input into the translation project, its goals, and its process.
+In order to produce a translation that the church affirms, as many church networks as possible should be contacted and encouraged to become a part of the translation  project and to send some of their people to be a part of the translation team. They should be consulted and asked for their input into the translation project, its goals, and its process. They should be involved in distributing the translation, reviewing it, and providing feedback so it can be refined. The more involved they are in these processes, the more likely they will affirm the translation.
 
 If the church cannot actively lead the translation and coordinate all the efforts, it is necessary that whoever is leading the translation be affirmed by the church networks, preferably before they even start.
 
-### Church Affirmation and the Checking Levels
-
-Wycliffe Associates has developed three levels of translation checks to be done by three different groups of people. The goal of each of these checks is to assign an affirmation level to the translation. The affirmation level shows how broadly the church affirms the translation.
-
-* Level 1 states that the church-affirmed translation team affirms the quality the translation.
-* Level 2 states that the pastors and lay-people of local churches affirm the quality of the translation.
-* Level 3 states that leaders of multiple church networks affirm the quality of the translation.
-
-At each checking level, the people leading the translation should encourage participation and input from the church networks. These steps will encourage local church ownership of the translation among as many church networks as possible. With this affirmation, there should be nothing hindering the translation from being used to strengthen and encourage the church.
-
+After the translation team has checked the quality of their translation, they are encouraged to share it with the community and the church leaders so that they can review the translation and give feedback. Encouraging the community and as many church networks as possible to participate and give input will encourage them to own and affirm the translation. And if they do this, there should be nothing hindering the translation from being used to strengthen and encourage the church.

intro/guidelines-collaborative/01.md

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

intro/statement-of-faith/01.md

@@ -1,5 +1,5 @@
 ### Essential Beliefs
-We consider Essential beliefs to be those that define us as believers in Jesus Christ. These cannot be disregarded or compromised.
+We consider Essential beliefs to be those that define us as believers in Jesus Christ. These cannot be disregarded or compromised. 
 
 We believe:
 
@@ -15,6 +15,8 @@ We believe:
 
 Peripheral beliefs are those beliefs based on Scripture where sincere believers may have disagreements in their interpretation. These include areas such as modes of baptism, the rapture, second coming of Christ, the Lord’s Supper and church practices. On peripheral beliefs, we can agreeably accept differences.
 
+All contributors to the Bible In Every Language website (see https://bibleineverylanguage.org) agree to translate the Bible in harmony with standard Christian doctrine as expressed in the Statement of Faith.
+
 ### Divine Familial Terms
 
 The divine familial terms are the words "Father" and "Son" when they refer to God the Father and God the Son. God is divine, and these terms show their family relationship to each other. Whenever the words "Father" and "Son" are used in the Bible to refer to the relationship between God the Father and God the Son (or between God the Father and Jesus Christ), they should be translated with the literal, ordinary words that people use to show the relationship between a man and his own son. (See: [Translating Son and Father](../jit/guidelines-sonofgodprinciples/01.md) and [Son of God and God the Father](../jit/guidelines-sonofgod/01.md).) All contributors to the Bible In Every Language website (see https://bibleineverylanguage.org) agree to do this.

intro/ta-intro/01.md

@@ -1,8 +1,8 @@
 
 The Translation Manual contains the following sections:
 
-* [Church Owned Bible Translation](../../intro/wa/01.md) - This section introduces how Bible translation is done with Wycliffe Associates. Among other things, it describes the Gateway Languages Strategy and tells about translation tools and resources to support that strategy.
+* [Church Owned Bible Translation](../intro/wa/01.md) - This section introduces how Bible translation is done with Wycliffe Associates. Among other things, it describes the Gateway Languages Strategy and tells about translation tools and resources to support that strategy.
 * [Translation Theory and Practices](../../translate/translate-manual/01.md) - This explains the basics of translation theory and provides simple explanations of standard practices.
 * [Translation Topics](../../jit/figs-intro/01.md) - These are practical translation helps, specifically targeting potential challenges, that are also linked from the Translation Notes.
-* [Checking](../../checking/intro-checking/01.md) - This explains the steps of checking that should begin as soon as a draft is completed, and continue throughout the remainder of the project. It also suggests who should be involved and provides best practices for affirming quality.
+* [Quality Assurance](../../checking/qa-need/01.md) - This explains the processes by which the translation team, the church, and the community work together to ensure the quality of the translation.
 

intro/wa/title.md

@@ -1 +1 @@
-Church Owned Bible Translation Training
+Church Owned Bible Translation

translate/first-draft/01.md

@@ -1,28 +1,27 @@
 
 ### 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. As a team divide the section you are beginning with among you. For example if you are starting with the book of Mark, divide its sixteen chapters up for each translator to take a portion. This division will help ensure that no one is duplicating someone else's work; however, it can serve as a guide and need not be static. In other words, as you progress in the project you may need to rearrange who is doing which parts to help accomodate the speed of each translator. 
+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. As a team divide the section you are beginning with among you. For example if you are starting with the book of Mark, divide up its sixteen chapters for each translator to take a portion. This division will help ensure that no one is duplicating someone else's work; however, it can serve as a guide and need not be static. In other words, as you progress in the project, you may need to rearrange who is doing which parts to accommodate to the speed of each translator. 
 
 ### Consume--the first step of MAST
 
-* 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. This is step 1 of the MAST process and is called "Consume." It should not take longer than five to seven minutes. 
+Read the chapter in the source text, thinking about what it means. Consider the chapter as a whole, noticing its form and style as well as the setting and background. Even as you think of these things, do not get bogged down. This step should only take a few minutes.
 
 ### Verbalize--the second step of MAST
 
-* Once you have consumed the chapter, verbalize it to a fellow translator. (This step can be done to anyone, even someone who does not speak the language, although it is always best to take turns doing this with other translators on the team.) You will verbalize what you have just read in your mother-tongue. Give a summary of the passage with as much detail as you remember. The person who is listen can give you feedback or reminders when you are done. You may also want to check the text and see if there is anything major you forgot. This process should not take more than a few minutes. 
+Once you have consumed the chapter, express what you just consumed. This is best done to another translator who also speaks the target language. (But it is such an important brain process, that if no one is available, it is still essential that the translator do this step by telling it to someone who cannot speak his target language or even to no one in particular.) Give a summary of the passage with as much detail as you remember. The person who is listening can give you feedback or reminders when you are done. You may also want to check the text and see if there is anything major you forgot, but it is important to do this without putting too much time in or studying. This process should take only take a few minutes.
 
 ### Chunk--The third step of MAST
 
-* After verbalizing the passage you are ready to chunk it into workable parts. (If you are using translation Studio this chunking has been done for you).  Break down the chapter into its individual meaning packets. These should be small enough for you to remember easily, but large enough to include at least a full thought. Often these chunks are 2-4 verses. They can be longer in narrative passages. Just look for where your brain naturally takes a break or seperates information and make note of those. Then read over the first chunk of your section so that you are ready to blind draft it. 
+After verbalizing the passage you are ready to chunk it into workable parts. (If you are using BTT Writer, this chunking has been done for you).  Break down the chapter into its individual meaning packets. These should be small enough for you to remember easily, but large enough to include at least a full thought. Often these chunks are 2-4 verses. They can be longer in narrative passages. Just look for where your brain naturally takes a break or separates information and make note of those places. Once you have divided the chapter into chunks, review the first chunk doing steps one and two again in your head before moving on to step 4. You will do this for each chunk as you work through the rest of the steps.
 
 ### Blind draft--the fourth step of MAST
 
-* Close your source text and any other resources. This is important because if you are looking at some source in a different language, it will interfere with your ability to write naturally in your mother tongue. Then write a draft from memory of the first chunk in your chapter. Although this can be a stressful step, try to relax and just write everything you remember. Don't worry if you forget something or don't word it eaxctly right. After this step come four checking steps, so you will have opportunity to make corrections, additions, and other edits. This step is about getting the intial draft down in natural, easy-to-read language. 
+Close your source text and any other resources. This is important because if you are looking at some source in a different language, it will interfere with your ability to write naturally in your mother tongue. Then write a draft from memory of the first chunk in your chapter. Although this can be a stressful step, try to relax and just write everything you remember. Don't worry if you forget something or don't word it exactly right. After this step come four checking steps, so you will have opportunity to make corrections, additions, and other edits. This step is about getting the initial draft down in natural, easy-to-read language. 
 
 When you have finished these first four steps of the MAST process you have a first draft!
 
 The next part of the translation process is to check it.    
-For MAST steps 5-8, see [Types of Checks](../checking/self-edit/01.md).    
-To learn about checking, see [Introduction to Checking](../checking/intro-checking/01.md).
+To learn about the MAST checking steps, see [Translation Team Check](../checking/level1/01.md).
 
 

translate/resources-questions/01.md

@@ -1,10 +1,10 @@
-The Translation Questions are comprehension questions that can be used to check your translation. They are based on the text of the ULB, but they can be used to check any Bible translation. They ask questions about the content of the Bible, which should not change as it is translated into different languages. Along with each question is a suggested answer for that question. You can use these sets of questions and answers as a way to check the accuracy of your translation, and you can also use them with members of the language community.
+The Translation Questions are comprehension questions that can be used both to check your translation and to do a community review of your translation. They are based on the text of the ULB, but they can be used with any Bible translation. They ask questions about the content of the Bible, which should not change as it is translated into different languages. Along with each question is a suggested answer for that question. You can use these sets of questions and answers as a way to check the accuracy of your translation.
 
-Using Translation Questions during community checks will help the translator know if the Target Language translation is clearly communicating the right thing. If members of the community can correctly answer a question using only the Target Language translation, then this indicates that the information that the question asked about was likely translated accurately. 
+Using Translation Questions during community reviews will help the translator know if the Target Language translation is clearly communicating the right thing. If members of the community can correctly answer a question using only the Target Language translation, then this indicates that the information that the question asked about was likely translated accurately. 
 
 #### Checking Translations with Translation Questions
 
-In order to use Traslation Questions when doing a self-check, follow these steps:
+In order to use Translation Questions when doing a self-check, follow these steps:
 
 1. Translate a passage, or chapter, of the Bible.
 1. Look at the section called "Questions."
@@ -12,11 +12,12 @@ In order to use Traslation Questions when doing a self-check, follow these steps
 1. Think of the answer from the translation. Try to not answer from what you know from other Bible translations.
 1. Click on the question to have the answer displayed.
 1. If your answer is correct, you may have done a good translation. But remember, you still need to test the translation with the language community, to see if it communicates that same meaning to others.
+1. These questions can also be used as part of checking during peer edit and verse-by-verse checking following the same steps.
 
-In order to use Translation Questions for a community check, follow these steps:
+In order to use Translation Questions for a community review, follow these steps:
 
 1. Read the newly completed translation of a Bible chapter to one or more community members.
-1. Tell the listeners to only answer the questions from this translation and to not answer using what they know from other translations of the Bible. This is a test of the translation, not of the people. Because of this, testing the translation with people who do not know the Bible well is very useful.
+1. Tell the listeners to answer the questions  only from this translation and not to answer using what they know from other translations of the Bible. This is a test of the translation, not of the people. Because of this, testing the translation with people who do not know the Bible well is very useful.
 1. Look at the section called "Questions."
 1. Read the first question entry for that chapter.
 1. Ask the community members to answer the question. Remind them to think of the answer only from the translation.

translate/translate-process/01.md

@@ -5,7 +5,7 @@ There are two things to do in translation:
 
 1. Discover the meaning in the source language text--this is initially done during step one: consume, step two: verbalize and step three: chunk. 
 2. Re-tell the meaning in the target language translation--this is done during step 4: blind draft.
-3. The checking steps revisit these two steps several times to confirm meaning and the retelling of that meaning. 
+3. The quality assurance steps revisit these two steps several times to confirm meaning and the retelling of that meaning. 
 
 Instructions for translation sometimes divide these two things into smaller steps. The graphic below shows how these two fit into the translation process.
 ![](https://cdn.door43.org/ta/jpg/translation_process.png)

translate/translate-retell/01.md

@@ -1,13 +1,15 @@
 MAST is a simple process for translation that emphasizes meaning transference. It has eight steps that are specifically designed to help translators understand and then retell the meaning of the text. The first three steps are for discovering the meaning. The fourth step is concerned with retelling the meaning. The final four steps affirm the discovery of meaning and help the translator make sure that the retelling is accurate and natural. Here are the steps:
 
-1. **Consume**: Read the chapter in the source text, thinking about what it means. Consider the chapter as a whole, noticing its form and style as well as the setting and background. Even as you think of these things, do not get bogged down. This step should only take a few minutes. 
-2. **Verbalize**: In the target language express what you just consumed. This is best done to another translator who also speaks the target language. But it is such an important brain process, that if no one is available, it is still essential that the translator do this step by telling it to someone who can't understand his target language or even speaking it out loud to no one in particular. The process of retelling what he read out loud in his heart language helps to transfer its meaning into his memory for later. 
-3. **Chunk**: Break down the chapter into its individual meaning packets or workable parts. This step will occur naturally in your mind and should be easy to transfer to paper. The chunks should be as long as needed to cover the meaning of a portion of the story, but not so long that you cannot remember the whole thing. Usually 1-4 verses are contained in a chunk, although with narrative passages it could be longer. Once you have divided the chapter into chunks, review the first chunk doing step one and two again in your head before moving on to step 4. You will do this for each chunk as you work through the rest of the steps. 
-4. **Blind draft**: Close the source text and write down from memory the meaning of the chunk you just reviewed. This may seem scary, but if you will force yourself to try, you will realize you remember more than you had at first expected. And whatever you did not remember can be added during the checking steps. This step merely provides the first draft. Writing down what you remember without referencing the source text will help you to write it naturally in your own language. (For more help with steps 1-4, see [Make a First Draft](../translate/first-draft))
-5. **Self-edit**: Read your blind draft and compare it to the source text to see if you missed anything. Use the Translation Helps to check your understanding of the form of the text, the historical setting, and the meaning of the text. Have you represented them accurately? Make any necessary changes, additions or deletions.  (See [Self-Edit](../checking/self-edit/01.md))
+1. **Consume**: Read the chapter in the source text, thinking about what it means. This step should only take a few minutes. 
+2. **Verbalize**: Tell in your own language what you just read. The process of telling out loud in your heart language what you read helps to transfer the meaning into your memory for later.
+3. **Chunk**: Break down the chapter into chunks that you can easily remember and quickly retell or write. These chunks will normally be 1 to 4 verses long.
+4. **Blind draft**: Close the source text and write down from memory the meaning of the chunk you just reviewed. Writing what you remember without referencing the source text will help you to write it naturally in your own language. This step provides the first draft. Whatever you did not remember can be added during the checking steps.  (For more help with steps 1-4, see [Make a First Draft](../translate/first-draft))
+5. **Self-edit**: Read your blind draft and compare it to the source text to see if you missed anything or changed anything. Use the Translation Helps to check your understanding of the source text. Make any necessary changes, additions or deletions.  (See [Self-Edit](../checking/self-edit/01.md))
 6. **Peer-edit**: You will do this step for a translation partner just as another translator on the team will do it for you. Repeat the same process as self-edit but with a partner's draft of a passage. (See [Peer-Edit](../checking/self-edit/01.md)) 
-7. **Key word check**: (A key word is a word that is significant for communicating the meaning and theology of the passage.) This check needs to be done with at least two translators. Using the translation Words as a guide, read through the passage and make sure all words in the list are accurately represented in the passage. You may also find other key words in the passage that need to be checked. If you don't understand the meaning of a key word from the list, consult the translation Notes. You may also want to research the meaning using the source text or other translations. It is important that the meaning of the key word is clearly represented. Often these words are absent from target languages. If you have no word in your language that is a fit for one of the key words, you will need to discuss together with the team ways of representing that meaning in your translation. This could include borrowed words, creating a new word, or word phrase, or recreating a word to broaden its meaning. As you do this check, it will hep to make a list of the terms you are using, so you have a reference for checking other passages. This will cut back on future workload and help to maintain consistency. (See [Key Word Check](../checking/key-word-check/01.md))
-8. **Verse-by-verse check**: This final step should be done with three people when possible--the translator and two others from his team. The translator will read their translation one verse at a time, out loud, in the mother tongue. Without using any resources, one partner will listen to the mother tongue translation and verbally translate it into the source language. A second partner will listen to the first partner’s verbal back-translation and compare it to the source text. Each verse should be checked against the source text, using the Translation Notes and Translation Questions as resources to confirm the accuracy and meaningfulness of the passage. The two partners will suggest edits where appropriate. (See [Verse-by-Verse Check](../checking/verse-by-verse/01.md))
+7. **Key word check**: A key word is a word that is significant for communicating the meaning and theology of the passage. Work with another translation partner to compare your translation to the source text to see if all the key words are represented adequately in the translation. The partner will suggest edits where appropriate. (See [Key Word Check](../checking/key-word-check/01.md))
+8. **Verse-by-verse check**: Read your translation out loud one verse at a time to two translation partners. One partner will listen and verbally translate the verse back into the source language. The second partner will listen to the first partner’s verbal back-translation and compare it to the source text to check the accuracy of the translation. The two partners will suggest edits where appropriate. (See [Verse-by-Verse Check](../checking/verse-by-verse/01.md))
 
-Consistently following the eight steps will help the team develop a translation that is meaning-based, natural, and accurate. 
+For another presentation of the eight steps, see https://bibleineverylanguage.org/processes/mast/. 
+
+Consistently following the eight steps will help the team develop a translation that is accurate, clear, and natural.